Security
Access control isn’t a feature bolted onto the AI — it’s enforced inside retrieval. What a person can’t open can’t shape their answer, cite itself, or leak through a paraphrase.
01
Your workspace's data is separated from every other customer's at the database layer, not just in application code. Every row of data is bound to your workspace, and the database itself refuses to return rows across that boundary — even if the application asked for them.
PostgreSQL Row-Level Security on every tenant table; policies fail closed, so an unresolved workspace context returns zero rows.
02
Permissions aren't applied to the answer after it's written — they're applied to the search itself. When your question goes looking for relevant passages, only documents you're allowed to see are candidates. Content outside your access is never retrieved, never ranked, and never reaches the AI model.
The access predicate runs inside both retrieval arms (semantic and keyword) before any cut-off, so "no accessible match" is indistinguishable from "no match".
03
Your documents are encrypted in transit and at rest. The OAuth tokens that connect your cloud drives get an extra layer of their own, and permission decisions are always made against the database — never trusted from a client token.
TLS in transit; encrypted storage at rest; connector OAuth tokens sealed with AES-GCM.
04
Everything that matters is recorded: uploads, downloads and denied download attempts, permission changes, invites, API keys. The log is append-only — nobody, including admins, can edit history — and exports to CSV for your own review or compliance workflow.
Append-only audit log with CSV export, covering document, permission, membership and API-key events.
05
Four roles — viewer, member, team manager, admin — plus teams and per-document grants decide who sees what. Grants can target a person, a team, or a minimum role. And nobody can hand out more access than they hold: roles above your own are not yours to assign.
Role changes and grants are themselves audited; the role hierarchy is enforced server-side.
06
It's your library. Export everything on request, and when you leave, full deletion on offboarding — documents, versions, conversations and index data.
Data export and complete offboarding deletion are available on request for every plan.
Controls mapped and documented as we work toward certification. We’d rather describe our posture precisely than borrow a badge — ask us for the current controls document any time.
Found something? Security contact:
Start on the free plan, grant access the way your org actually works, and watch the audit log fill in behind you.