Encryption in transit and at rest
All traffic between your browser and Intenio runs over TLS 1.3. Data at rest — proposals, sections, analytics, client activity — is encrypted inside Supabase's managed PostgreSQL infrastructure hosted on AWS.

Security
Proposals, client data, signatures, and payments touch sensitive business information. Here is exactly how Intenio protects them.
All traffic between your browser and Intenio runs over TLS 1.3. Data at rest — proposals, sections, analytics, client activity — is encrypted inside Supabase's managed PostgreSQL infrastructure hosted on AWS.
Each proposal gets a cryptographically random UUID token. Links expire after 30 days by default. Tokens are single-use per proposal — a new token is minted on every re-send. Optional password protection adds a PBKDF2-derived layer on top (100 k iterations).
Every signature records the signer name, IP address, user-agent string, exact timestamp, and a SHA-256 hash of the signed document content. Records are written to an immutable audit table and a tamper-proof PDF certificate is stored in Supabase Storage.
Intenio never handles or stores card data. All payment collection is delegated to Stripe, a PCI DSS Level 1 certified processor. Connect payouts to your bank use Stripe Connect under Stripe's KYC and fraud controls.
The app runs on Vercel's edge network. Row-Level Security (RLS) policies in Supabase enforce per-user data isolation at the database layer — not just the API layer — so one account cannot read another's proposals even with a valid session token.
Client-facing endpoints (sign, auth, analytics) are rate-limited per IP using an in-memory sliding window. The client auth route limits to 5 attempts per token per 60 seconds. Stripe webhook payloads are verified via HMAC signature before processing.
Intenio is built on a small set of well-audited infrastructure providers. Each handles a specific part of the security surface.
If you discover a security vulnerability in Intenio, please email security@intenio.io before disclosing publicly. We aim to respond within 48 hours and will credit responsible reporters.
Questions about security?
Reach out and we will respond within one business day.
Last reviewed: June 2026