Privacy

1. Who we are

This website and the Enqlave app are operated by Enclave AI LLC, 5830 East 2nd St. PMB 91378, Casper, WY 82609, United States. For the personal information described on this page, Enclave AI LLC is the data controller. You can reach us at hello@enclave-ai.com.

2. The short version

Enqlave is built so that we cannot read your documents. This page covers two separate things: (a) the small amount of information this website collects when you join the waitlist, and (b) how the app itself protects your library.

3. What this website collects

When you join the waitlist, you choose to send us:

• Email (required) — so we can contact you about beta access.
• Name (optional) — so we can address you properly.
• Device and country (optional) — to understand who's interested and plan rollout.
• A short note about your use case (optional) — to help us build the right thing.

We do not run third-party advertising or analytics trackers on this page beyond what our host needs to serve it.

4. How we use it

We use your waitlist details only to contact you about the Enqlave beta and to understand demand. We don't sell your information, and we don't share it for advertising.

5. Who processes it

Waitlist submissions are processed and stored by our hosting provider, Netlify, acting on behalf of Enclave AI LLC. You can ask us to delete your waitlist entry at any time (see Contact). See our full list of subprocessors.

6. The app itself

Enqlave is designed around zero-knowledge encryption:

• Your documents are encrypted on your devices before anything is uploaded.
• Our cloud stores only ciphertext — encrypted data we cannot decrypt or read.
• Encryption keys stay on your devices, secured by the system keychain.
• AI features run against the provider key you configure, or — if you configure none — a key we issue for your account, which routes through OpenRouter. Either way the request goes straight from your device to the provider, never through our servers. Content is sent whenever Enqlave reads, indexes, summarises or answers — most often when you file a document, when the search index is built, and when you ask a question, though not only then. When a document is read, what leaves your device is the file itself, not an extract of it. See our list of subprocessors for who receives what.
• To make sharing and sync work, our servers do see account and sharing metadata — who your devices are (public keys only), which libraries you’re a member of, and a timestamped record of every change each device syncs. They never see what’s inside a document, but that record does show when you work, from which device, how large your library is and how fast it grows.
• Two things on our servers are not encrypted, and we would rather name them: the names you give your libraries, and a fingerprint (a SHA-256 hash) of each file’s contents, which is how your devices recognise the same document and store it only once. Someone who already holds an identical copy of a file could use that fingerprint to confirm it is in your library; it does not reveal a document to anyone who has never seen it.
• To be precise about scope: zero-knowledge is a claim about our cloud. On your own computer, your documents and Enqlave's search index are ordinary files, protected by your device's own security — FileVault and your login on a Mac, and the always-on filesystem encryption on iPhone — not by Enqlave's sync encryption.

Our Terms of Service describe the service itself in more detail.

7. What else leaves your device

Encryption is about what our cloud holds. These are the other things Enqlave sends out, and who receives them:

• Place lookup — off by default. Enqlave can plot places mentioned in your documents on a map, which means sending those place names — they may be addresses, employers, clinics, schools or courts — to Apple to be turned into coordinates. The switch is in Enqlave’s settings; turning it off stops new lookups and leaves places already found on your map. Opening the map itself also requests map tiles from Apple for the area shown, which is framed on your documents’ own locations. Tagging a scan with where it was taken, on iPhone, is a separate feature behind the system location permission.
• Diagnostics — on by default, and can be turned off in Enqlave’s settings. They cover which screens and features you use and for how long, performance and crash measurements, and counts — including, once a day, how many documents your library holds, how large it is, and roughly how they are spread across categories. They never include filenames, document content, or your search text.
• How much AI you use — always recorded, and not optional. Each time Enqlave uses AI it records the number of tokens, which model, and roughly what for (filing, indexing, chat, answers) against your account. This is what enforces your daily usage limit, so unlike the switches above it has no off setting — turning it off would stop your own limit from working. It records amounts, never what the documents said.
• Google Drive — only if you connect it. Google records a read-only grant over your whole Drive. That breadth is what lets Enqlave list the contents of a folder you pick; a narrower grant cannot see files that were already there. Enqlave reads only the folders you connect.
• Saving a web page. Your device fetches that page from the site directly, the way a browser would — so the website sees the request.

8. Your choices

You can leave the waitlist, request a copy of what we hold about you, or ask us to delete it — just email us. Once the app is live, your library is yours to export or delete from your devices.

9. Contact

Questions about privacy? Email hello@enclave-ai.com, or write to Enclave AI LLC, 5830 East 2nd St. PMB 91378, Casper, WY 82609, United States.