Access. Data. Control.
How accounts, API keys and workspaces are protected, and what remains after a request.
Reviewed October 18, 2026Accounts and sessions
Passwords are stored as individually salted hashes. Sessions use a secure HttpOnly cookie. A password reset ends existing sessions; API keys are revoked separately.
Keys and workspaces
A new API key is shown in full only when created; the server stores its hash. Requests and saved materials belong to a workspace. Member and billing management is restricted to owners and administrators.
Verification and recovery
An email verification link lasts 24 hours and requires the same account to sign in and confirm explicitly. A password-reset link lasts 30 minutes. Both are single-use; the server stores token hashes.
Network and external events
The public website and API use HTTPS. Browser mutations are checked against the request origin and current workspace. Stripe and SendGrid delivery events require signature verification; repeated events are deduplicated.
Cards and transactional email
Card details are entered on Stripe’s page; the console does not store full card numbers or CVC. Open and click tracking is disabled for transactional email. Provider acceptance, delivery and user action are distinct events.
Retention and deletion
| Category | Current practice |
|---|---|
| Ordinary API request | The API gateway does not write the context and questions of ordinary requests to the history database. It retains usage metadata. Saving a shared request is a separate user action. |
| Account, usage and billing | Account details, memberships, usage metadata and financial records are retained. These records have no general automatic deletion period. Discuss individual deletion requirements with the team. |
| Shared requests | Context and questions remain until the author or an administrator deletes them. A deleted record may remain in backups until rotation. |
| Contact-form inquiries | Name, email, topic, message and inquiry ID: 90 days in the primary database. A notification copy may remain in the team mailbox for handling the inquiry. |
| Email delivery ledger | Identifiers, recipient hash, message type, status and timestamps: 90 days. This ledger does not contain message bodies, link tokens or open tracking. |
| Verification and password reset | Single-use links have their own expiry times. Token-hash records are removed by cleanup after they have been expired for more than 24 hours. |
| Evaluation datasets | JSONL import and report viewing happen in the browser. A run sends context and questions to the model, but not expected answers. A downloaded report contains inputs and responses. |
| Backups | The seven most recent private database snapshots are retained. Backup rotation is not a promise of recovery within a particular time or a separate SLA. |
Scheduled cleanup runs while the service is operating. Deletion from the primary database does not mean immediate deletion from backups or provider systems. Agree any required retention periods with the team before submitting production data.
Report a concern
Contact Codebridge about security, access or data deletion. Include the page address, time and a description of the issue. Do not send passwords, API keys, payment details or another account’s data. This page does not establish an SLA response time.