SECURITY · UPDATED OCT 15, 2026
What we built to deserve the access.
You're accountable for what AI does in your queue. Here's how Copious handles the access you give it, and what isn't built yet.
01
The boundary
Intake reads structure, never content. The fields it reads are fixed in code at the ingestion boundary. It's not a setting. Freshdesk and Intercom send message text with every ticket anyway; it's dropped on arrival, before anything is stored, logged, or analyzed. The full list of what intake reads and never reads is on the pricing page.
02
Credentials
Helpdesk, Notion, and Slack credentials are encrypted at rest in Supabase Vault. Only our server can decrypt them, and only to make a read or write you asked for. They're never sent back to a browser, masked or otherwise. Disconnecting deletes the stored credential.
03
Access
Copious is invite-only. The database checks for an active invite before it saves anything; the screen isn't the only gate. Each account sees only its own Record. Staff tools show counts, never contents.
04
The Check
The Check runs your rules on a prompt before it's sent. It never calls a model. Every override of a HELD prompt is logged.
05
Logs
Staff actions are logged, and that log can't be edited or deleted.
06
Abuse limits
The chat and the contact form are rate limited. Ask Copious refuses messages that look like customer details.
07
Not yet
No SOC 2 report. No single sign-on through your own identity provider. No choice of data region. Each one goes on this page when it's real, not before.
08
Report a problem
Found a security issue? Write to hello@copious.app with SECURITY in the subject. A person reads every report.