Access Control Policy

Member access

Each member signs in to their own account. Access to data is limited to that account.

• Row-level security in the database, so each account can read only its own rows. Your browser never queries the database; every read runs through our API, scoped to the signed-in account.
• Every read and write from the product runs through our API, which checks the signed-in account before it touches data.

Connected services

When you connect a service we store a connection key so we can read what you authorized.

• AES-256-GCM encryption on the connection keys we store for the services you connect (for example Stripe), so a stored key is not readable as plain text.
• You can revoke a connection from the service itself at any time, and from Settings in the product.

Staff access

Only the founders and the people they authorize can reach production systems or administrative tools. Privileged actions are recorded.

• An audit log of privileged actions by our staff. Each privileged admin action records one row (who, what and when), and the owner reads the log behind a permission. The write is best effort: it never blocks a request.
• Multi-factor authentication is enforced on staff accounts that access production systems.

Not yet in place

• A written, scheduled review of who holds access: not yet in place.

Questions

Write to security@cerqular.ai for anything on this page. For personal data requests write to privacy@cerqular.ai.

Status of this text

Counsel review of this policy has not been completed. It states what the code and the infrastructure do today, and where a control is not yet in place it says so.

Other policies

• Information Security Policy
• Endpoint Protection Policy
• Incident Response Policy
• Data Classification Policy
• Vulnerability Management Policy
• Data Protection Policy
• Breach Notification Policy