Subprocessors
To run Enqlave we rely on a small number of trusted service providers (“subprocessors”) that process data on our behalf. We keep this list short by design, and we publish it so you always know who is involved.
| Subprocessor | Purpose | What they process | Location |
|---|---|---|---|
| Supabase, Inc. | Account sign-in, encrypted library sync and storage, diagnostics | Account identifiers; your library only as encrypted ciphertext we cannot read; diagnostic counts, durations, and error codes | United States |
| Google LLC (Gemini API) | Generates answers to questions you ask, when configured | Document content is sent directly from your device, using your own API key, at the moment you ask a question | United States |
| Anthropic, PBC (Claude API) | Generates answers to questions you ask, when configured | Document content is sent directly from your device, using your own API key, at the moment you ask a question | United States |
| Apple Inc. | App distribution (TestFlight) and Sign in with Apple | Your Apple ID identifier and basic install/device information | United States |
Enqlave sends document content to an AI provider only when you ask a question, and only to the provider whose key you have configured — the request goes straight from your device under your own key, not through a server we operate. Your stored library is encrypted on your device before it syncs; our cloud holds it as ciphertext it cannot read.
Our marketing website is hosted by Netlify, Inc. and the domain is registered with Porkbun, LLC. These handle only website data — never your documents.
We’ll update this page before adding or changing a subprocessor. Questions: hello@enclave-ai.com.
← Back to home