How we protect your data

Last updated November 2, 2026.

• Encryption: data travels over TLS. Sign-ins to connected systems are encrypted with AES-256-GCM, using a key for each company that is wrapped by a cloud key management service.
• Separation: each company has its own database schema and role, and row-level security in Postgres decides what each person can read. The check runs in the database, not only in the app.
• Least access: connectors ask for the permissions their features need, and can reach only the vendor hosts they declare.
• Sandboxing: screens written by the builder run in a locked-down frame that can reach data only as the person viewing them.
• Audit: changes to data, access and connections are written to an audit log in the same transaction.
• Hosting: Google Cloud in the United States. Backups age out within 30 days.

Reporting a problem

If you think you've found a security problem, write to the form on our data page. Please give us time to fix it before telling others.