Security and auditing

Session security, access control, the audit log, rate limits and backups: the platform's security layers.

Identity and sessions

• Passwords are stored irreversibly (bcrypt).
• Sessions are managed with HttpOnly + Secure cookies; a client verification header blocks CSRF.
• Failed login attempts hit a rate limit (brute-force protection).
• The session cookie is valid on all org subdomains; logout ends the session everywhere.

Data access control

• Access decisions are made server-side: profile and sharing rules are enforced at the API layer and cannot be bypassed around the UI.
• File access follows record access: whoever cannot see the record cannot download its files.
• Cross-org access is architecturally closed (multi-tenant isolation).

Audit log

Setup > Audit Log records critical operations: logins, settings changes, deletions, exports, super admin org entries. Entries can be filtered and exported.

Rate limits

Login, sign-up, e-mail sending and web form endpoints are rate limited; abuse and floods are blocked.

Backups and continuity

• Org data is backed up automatically every night; recent copies are kept.
• Deleted records land in the Recycle Bin first; permanent destruction writes an erasure log (see Compliance).

Your part

1. Use strong, unique passwords; never share accounts (everyone gets their own user).
2. Deactivate a departing employee's user immediately.
3. Treat API tokens as secrets and revoke unused ones.
4. Design profiles on the least-privilege principle.