Security & trust
Email is a decade of your life in plaintext. We engineered for that.
Quri's security model is simple to state and strict in practice: your data is encrypted at rest, isolated per tenant on every query, exportable and deletable on demand — and for enterprises, it runs on keys you own.
01 — Encryption at rest
Secrets never sit in plaintext.
OAuth tokens, refresh tokens, and enterprise API keys are encrypted with AES-256-GCM before they touch a database, each with a unique nonce and authenticated tags to prevent tampering.
Decryption happens only inside isolated server-side action runtimes — the code paths that serve queries and mutations physically cannot read secret material. Email content and derived embeddings are encrypted at rest by our infrastructure providers.
02 — Tenant isolation
Cross-tenant reads are impossible by construction.
Every record in Quri is keyed to the account that owns it, and every vector search carries a mandatory tenant filter derived from your authenticated session — not from anything a client sends us. No public API accepts a user ID as a parameter.
The same boundary applies to storage: every stored object lives under a tenant-scoped path. One user, one namespace, no exceptions — including for our own staff.
03 — GDPR workflows
Export everything. Delete everything. Actually.
Every plan includes self-serve export of all data we hold about you, in portable formats, and deletion that cascades through the search index, embeddings, encrypted tokens, and object storage — with backups purged on a fixed schedule.
Disconnecting a mailbox immediately revokes our provider access. We are a processor of your email, never a co-owner of it; data processing agreements are available for Business and Enterprise plans.
04 — BYOK — bring your own keys
Enterprise runs Quri on keys you control.
Enterprise customers supply their own OpenAI and Qdrant credentials. Embedding, retrieval, and answering then run against accounts you own, bill, and can revoke unilaterally — Quri becomes the application layer over your data plane.
BYOK uses the same audited code paths as the platform keys; only the client connection differs. Your keys are stored with the same AES-256-GCM envelope encryption and are decryptable only in isolated runtimes.
05 — Infrastructure
A small, serious stack — no data sprawl.
Quri runs on Convex for application data and serverless functions, Qdrant Cloud for vector search with EU-region hosting available, and S3-compatible object storage for attachments. Analytics are aggregate-only and never contain email content.
Traffic is TLS 1.2+ end to end. Role-based access control separates users, org admins, and platform operators, and production access for operators is logged and reviewed.
The honest inventory
What we store, and what we never will.
We store
- Email content and headers, indexed for your search
- Vector embeddings derived from your emails
- OAuth tokens — AES-256-GCM encrypted
- Account, org, and billing metadata
- Aggregate usage metrics (counts, never content)
We never store
- Your email provider password
- Plaintext OAuth tokens or API keys
- Your data in model training sets
- Cross-tenant indexes of any kind
- Payment card numbers (handled by Stripe)
Responsible disclosure
Found something? Tell us first.
We welcome good-faith security research. Report vulnerabilities to security@askquri.com and we'll acknowledge within 48 hours, keep you updated, and never pursue action against research conducted in good faith. Coordinated disclosure window: 90 days.
For security teams
Running a vendor review? Enterprise plans include the full compliance pack — DPA, architecture overview, and a direct line to the people who built this page.