Tenant isolation in the database
Every CRM record carries the ID of the workspace it belongs to. PostgreSQL Row-Level Security policies restrict every query to a single workspace, and the application connects with a database role that cannot bypass those policies. If a request is missing its workspace context, it sees no data at all. Isolation is covered by automated tests that try to read, write, update and delete across workspaces.
Encryption
All traffic to our sites and apps is encrypted in transit with TLS, and HTTP Strict Transport Security is enabled. Data at rest is encrypted by our managed database and storage providers. Multifactor authentication secrets and backup codes are additionally encrypted at the application level.
Accounts and sessions
Passwords are stored only as strong one-way hashes. Sessions use long random tokens that expire and can be revoked. Login attempts are rate-limited, and you can review your active sessions and sign out other devices. Multifactor authentication is optional for customers and required for all of our administrative staff.
Audit logs
Security-sensitive and administrative actions — such as permission changes, subscription changes and template releases — are written to append-only audit logs that record who did what and when. The application cannot edit or delete audit entries.
Payments handled by Stripe
Checkout and payment method updates happen on Stripe-hosted pages. Card numbers and security codes go directly to Stripe and are never transmitted to or stored on our servers.
AI data handling
AI features only process workspace data when the workspace has opted in. Requests are checked against the requesting user's permissions, so AI cannot surface records that user couldn't already see. External AI providers are used only under data processing agreements. Prompts are not stored by default.
Backups and recovery
Production databases will run on managed infrastructure with automated daily backups and point-in-time recovery. Restore procedures will be documented and tested on a regular schedule.
Least privilege for our team
Staff access is granted by specific permission rather than all-or-nothing, administrative tools are separated from the customer app, and production secrets are kept in a secret manager — never in source code.