# Trust. Trust · Human page: https://quelvio.com/trust · Machine view: https://quelvio.com/ai/trust How Quelvio protects your knowledge. Your knowledge is among the most sensitive corpus your company holds — every memo, every decision, every internal discussion. Quelvio is built so your data stays separated and yours, people see only what they're already allowed to see, everything is encrypted and audited, and you stay in control of access and removal. This page documents the protections in place today. ## Stored in your own cloud. **Quelvio platform · storage in your own cloud** Where your data is stored On every plan, your content is stored only in your own storage. During setup, before you connect it, Quelvio keeps what it reads from your public website, your setup answers and corrections, and the first answer until you connect your storage, at most 14 days, then moves them there and deletes them here; backup copies are cleared within 7 more days. The application and sign-in run at enterprise.quelvio.com. ### Your documents Your documents, and everything Quelvio draws from them, are stored only in your own cloud account, encrypted with your key. Apart from the setup hold described above, Quelvio keeps no copy, only metadata such as ids, statuses and counts. ### Connector tokens Connector tokens live only in your secret manager. Google and Microsoft connect through your own apps with no secret at all. You can cut Quelvio off at any time from your own console. ### Processing Quelvio’s servers run the application and, by default, the processing. Content passes through them in memory while it is read and written to your storage, and is not kept there, apart from the setup hold described above. ### Outside processors Content is processed by Typesafe (Jev) and, when models run through Quelvio, by Alibaba Cloud (Qwen). When models run in your own cloud, by the models you choose there. ## 01 · Controls at a glance. **Hosted platform · enterprise.quelvio.com today** The controls and details below describe the hosted platform at enterprise.quelvio.com as it runs today, where Quelvio stores your content in its own infrastructure. Its search sends document text and queries to Voyage AI for embeddings and ranking. The privacy policy lists the hosted platform’s sub-processors. [See the sub-processors](https://quelvio.com/privacy#6-subprocessors) Eight headline controls that operate across every Quelvio tenant. Each links to the architectural detail below. 1. [Tenant isolation](https://quelvio.com/trust#isolation): Your knowledge is fully separated from every other customer's, at every layer — database row-level security on your data, per-customer retrieval, partitioned storage — and continuously verified. 2. [Authentication](https://quelvio.com/trust#auth): OAuth 2.1 for humans, Personal Access Tokens for headless, Service Accounts for CI — all hashed, never logged. 3. [Per-tenant policies](https://quelvio.com/trust#policies): Admin-configured session age, idle limits, IP allowlists, PAT and Service Account caps — fail-closed on violation. 4. [Atomic offboarding](https://quelvio.com/trust#offboarding): HRIS-driven revocation of every session and credential in a single transaction. Idempotent, rolled back on failure. 5. [Tamper-proof audit](https://quelvio.com/trust#audit): Every sign-in, change, and query captured in a hash-chained, exportable audit trail admins can review — and it can't be quietly altered. 6. [Encryption](https://quelvio.com/trust#encryption): TLS 1.2+ in transit. How content is encrypted at rest, and where its keys are kept, is set when Quelvio's service is hosted; it will be named here. 7. [Data residency](https://quelvio.com/trust#residency): Your content is stored only in your own storage, in the region you choose for it. Some processing happens in the United States, as the privacy policy's Section 6 lists. 8. [Data deletion & erasure](https://quelvio.com/trust#rtbf): Key-destruction erasure across all backup copies — when you erase, we destroy the key and every copy becomes permanently unreadable. Anyone can pause or erase what's remembered about them, anytime. ## 02 · Architecture in detail. ### 02·1 · Tenant isolation Your knowledge is fully separated from every other customer's, at every layer. Each tenant has its own dedicated retrieval space, and your data carries database row-level security tied to your tenant identity — content is reachable only within your own tenant, by construction, not by a filter that could be left off. Source-side access controls travel with your content: the permissions from Google Drive, Confluence, Slack, and every other connected tool are honored on every result, at the same layer as tenant identity. That separation is continuously verified — the boundary between tenants is checked on an ongoing basis so it holds, always. ### 02·2 · Authentication and access Sign in with your own identity provider over single sign-on (SAML or OIDC). People authenticate through the directory you already run, and sensitive administrative actions require step-up multi-factor protection. Administrative access uses per-operator identity — there is no shared admin key. Every credential is stored only in hashed form, never in readable text. The plaintext is shown exactly once at issuance and is never written to logs or audit records. Programmatic access uses scoped tokens, each rate-limited and budget-capped. People see only what they're already allowed to see, so two employees with different roles in the same company get results filtered to exactly the documents they have standing access to at the source. ### 02·3 · Tenant-configurable security policies Administrators set access policies for their own company: maximum active and idle session age, IP allowlists, and caps on how many credentials each person and team can hold. Policies belong to your company alone — there is no cross-tenant inheritance or default fall-through. Enforcement is fail-closed. An expired session, a request from outside the IP allowlist, or a credential request beyond the configured caps is denied — and every denial is paired with an audit entry the admin can inspect. ### 02·4 · Atomic offboarding When a person leaves, offboarding is instant and complete: every session, token, and service account they hold is removed in one step. It's all-or-nothing — if anything can't complete, the whole operation rolls back so the admin can retry cleanly, never leaving access half-removed. Offboarding can be triggered automatically from your HR system over a signed connection, or manually by an admin in the dashboard. Every removal is recorded in the audit trail, so the full record of who was offboarded and when is visible to admins and procurement reviewers. ### 02·5 · Tamper-proof audit Every sign-in, configuration change, credential issued or revoked, query, and offboarding action is recorded in a complete audit trail. The trail is hash-chained, so any change to a past record is detectable — the record can't be quietly altered after the fact. Each answer is traceable to the sources that informed it, so when a removal request lands, the team can confirm exactly what surfaced that content and where it was cited. Admins review the audit trail directly from the dashboard and export it for procurement and compliance teams. Retention is configurable, with long-term retention for Enterprise, and the trail can stream to your own security tooling. ### 02·6 · Encryption Encryption at rest. How each customer's content is encrypted at rest, and where its keys are kept, is set when Quelvio's service is hosted; it will be named here. Data in transit is protected with TLS 1.2+. Bring your own key (Enterprise). How you bring your own key is set when Quelvio's service is hosted; it will be named here. ### 02·7 · Data residency Your content, and the index built from it, are stored only in your own storage, in the region you choose for it. Some processing happens in the United States: the privacy policy's Section 6 lists each provider and where it processes. ### 02·8 · Data deletion & erasure Deletion that survives backups. How erasure reaches every copy of your content, backups included, is set when Quelvio's service is hosted; it will be named here. What erasure keeps. Erasure destroys your content and its keys. We retain the minimal billing and audit records the law requires us to keep (invoicing, tax, and the security audit trail) — these contain no document content. This balances your right to erasure (GDPR Article 17) with our legal retention obligations. Source-driven deletion. When a document is removed in Google Drive, Confluence, or another connected source, it disappears from results immediately, with a full permanent purge shortly after. ### 02·9 · Backups & resilience How your data is backed up, and where the backups are kept, is set when Quelvio's service is hosted; it will be named here. ## 03 · Compliance posture. Quelvio's security controls are aligned to leading frameworks — SOC 2 and ISO 27001 — and operate across every tenant today. Detailed security documentation is available to enterprise customers under NDA, alongside a Vendor Security Questionnaire and customer information packet for procurement review. **Also covered** - **GDPR**: GDPR-compliant. Data Processing Agreement (DPA) available to customers on request. - **HIPAA**: Business Associate Agreement (BAA) available on request for in-scope deployments. - **ISO 27001**: Security controls aligned to the ISO 27001 framework. ## 04 · Reporting a security concern. Email security@quelvio.com to report a vulnerability or suspected incident. We acknowledge reports within one business day and provide a triage assessment within five business days. For high-severity reports, on-call engineering responds the same day. Researchers acting in good faith under the disclosure policy will not be pursued under the Computer Misuse Act or equivalent statutes. We ask for a private disclosure window before publication. Email [security@quelvio.com](mailto:security@quelvio.com) ## 05 · Additional resources. - [Privacy Policy](https://quelvio.com/privacy): Data we collect, how we use it, retention, your rights. - [Terms of Service](https://quelvio.com/terms): The agreement that governs your use of Quelvio. - [Data Processing Agreement (DPA)](mailto:security@quelvio.com?subject=DPA%20request): Article 28 DPA available on request to enterprise customers. (On request) - [Sub-processors](https://quelvio.com/privacy#6-subprocessors): Current list of infrastructure, AI, and operations sub-processors. - [Vendor Security Questionnaire](mailto:security@quelvio.com?subject=Security%20questionnaire%20request): Customer information packet (CAIQ-style) for procurement review. (On request) - [Security documentation](mailto:security@quelvio.com?subject=Security%20documentation%20request): Detailed security documentation available under NDA. (On request) ## Procurement review? Talk to us. Vendor security questionnaires, DPAs, and the customer information packet are available to enterprise prospects under NDA. [Email security@quelvio.com](mailto:security@quelvio.com?subject=Security%20review) · [Start a trial](https://quelvio.com/early-access) ## Related - [Human view of this page](https://quelvio.com/trust) - [Everything for agents: llms.txt](https://quelvio.com/llms.txt)