Privacy

What we can't see

• Your conversations. Messages, replies, titles, attached files and images, and memory notes are encrypted on your device before they're saved. We store only the encrypted copies. The key that opens them is unlocked by your password, a passkey or your recovery key, and those never leave your device.
• What you ask the model. Your browser first checks the sealed hardware that runs the model, then encrypts each request to it. Our servers pass requests and replies along without being able to read them.
• Agent mode (not open to customers yet). Web searches run in a confidential machine that your browser checks the same way. What you ask and what it finds travel encrypted between your browser and that machine.

Files

Files is Tacy's encrypted file storage, included in every plan up to the plan's storage limit.

• Encrypted before upload. Your browser encrypts each file with a key of its own before it leaves your device. We store only the encrypted copy. File and folder names, and how your folders are arranged, are encrypted too, so our servers never see them.
• What we can see. How many files and folders you have, how many versions each file has, which are in the trash, when each was added or changed, and each file's size rounded up (padded), so the stored size shows only roughly how big a file is. We use this to show and enforce your storage limit.
• Attachments. With Files on, a file you attach in a saved chat is also kept in Files, in a folder named after the chat and encrypted the same way. It counts toward your storage and stays in Files if you delete the chat. Temporary chats work as before.
• Agents read only what you pick. For an agent task, your browser hands over the keys of just the files you picked, encrypted to the confidential machine it checked first, and the files are decrypted only inside that machine. A key opens only its file, nothing else in your Files. For a task that runs now, the keys and the text stay in the machine's memory and are gone when the task ends.
• Scheduled tasks. A scheduled task reads its files on every run, so the keys of the files you picked stay on that machine's encrypted disk until you remove the schedule or it expires. Deleting a file for good stops runs from reading it. Documents a scheduled run makes are saved to Files by your browser, encrypted like any upload, the next time you open Tacy; the machine can't write to your Files.
• What we learn when agents read files. Our server learns which of your files a task reads and how many, and, for a scheduled task, when a run reads them. Cloudflare sees the confidential machine download the encrypted copies. Neither sees a key, a name or what's inside.

What we do keep

We can read these:

• Your username (a pseudonym is fine), when you created the account, your plan, and whether you've set a recovery key.
• For firm accounts: your work email, your role, your firm's name and groups, and the IDs your firm's sign-in provider uses for you.
• Your passkeys' names (such as "iCloud Keychain" or "Chrome on macOS") and when each was added and last used.
• For each sign-in: how you signed in, a device label such as "Safari on iOS", and when it started and was last used. We don't store IP addresses, locations or your full browser details.
• If we invite you by email: your email address, which Cloudflare's email service sends the invite to. It's kept only with the invite and deleted when you use the invite (your account doesn't keep it), when we cancel it, or within an hour after it expires (7 days after the latest link was made).
• When someone signs up: to limit how many accounts can be made from one connection each day, a hash of the IP address, made with a key that changes daily. We never store the address itself, and we delete the hash after about 48 hours.
• Daily usage: how many requests, prompts and documents, their estimated cost, encrypted data sizes, and token counts per model.
• Details of each request: its type (chat reply, document, web search and so on), the model, timings, token counts, sizes, whether it worked and an estimated cost. Never content, titles, file names, search terms or web addresses, and never linked to a conversation.
• For each conversation and memory note: its ID, encrypted size, how many messages a conversation has, and when each was created, changed or archived.
• Encrypted copies of your key, which are useless without your password, a passkey or your recovery key, and the hashes we use to check sign-ins.
• If you send us feedback, we receive what you choose to send, readable: your note, and a conversation only if you tick the box to attach it. We keep it until we delete it or you delete your account.

We don't sell any of this, show ads, or train models on your data.

Who else handles your data

• Cloudflare hosts this site, the app, our database and the encrypted copies of files (R2). Your traffic, including your IP address, passes through it. We keep request logs turned off. When you sign up, Cloudflare Turnstile checks that you're a person, not a bot; it runs in the signup page and sees your browser and connection, never your conversations.
• Tinfoil runs the models and reads attached documents, inside sealed hardware. Outside that hardware it sees our traffic, not who you are.
• Phala hosts the confidential machine for agent mode and for web search in chat, which aren't open to customers yet. It can't read what runs inside.
• Exa runs web searches, in agent mode and in chat, only once you allow them. Before each search you see the exact terms, with details like email addresses and phone numbers masked; Exa gets those terms from our confidential machine and nothing else from your chat. Exa may keep search terms and use them to improve its service unless we have a zero-retention agreement with it; we've asked for one and don't have it yet. Always allow skips the question for later searches; you can change it in Settings → Chat.
• Tavily runs image searches, only in agent mode and only once you allow them, with the same masked terms and nothing else from your chat. Tavily may keep the terms it receives, use them to improve its service (including training its AI), and pass them to other search engines such as Google to answer. Websites the agent opens, and the sites its pictures come from, see a visit from that machine, not from you.
• WorkOS will handle single sign-on for firm accounts. It's built but not switched on yet. It will see your work email and your firm, never your conversations or keys.

The app doesn't take payments yet, so no payment provider holds your details.

How long we keep it

• Daily usage: 31 days. Details of each request: 90 days.
• The signup check's IP hashes: about 48 hours.
• Files in the trash: 30 days, then deleted for good, with their keys. Deleting your account deletes all your files.
• A sign-in lasts at most 7 days (12 hours for firm sign-ins), or until you sign out. Its record is then deleted.
• Everything else stays until you delete it or your account.
• Our database provider's point-in-time backups keep deleted data for up to 30 days. Conversations stay encrypted there too.

Export and delete

• Export: Settings → Your data downloads a readable copy, decrypted on your device, or an encrypted backup.
• Delete: Settings → Your data → Delete account removes your account and everything tied to it at once. A firm account is removed by its firm, which manages its member list.
• Devices: Settings → Devices lists your sign-ins. You can end any of them.

Cookies and tracking

• This site sets no cookies and loads no analytics or third-party scripts.
• The app sets only the cookies that keep you signed in. Your browser also keeps a few app settings, such as your chosen model. If you turn on "Stay unlocked on this device", it also keeps the key that opens your conversations on that device until the time you chose.
• No third-party analytics, ads or trackers. The app reports the usage and request details listed above to us.

Limits to know about

• The app runs code we send to your browser. We restrict what it can load and fingerprint every file we ship, but you are trusting that code.
• We and our providers still see some metadata: when you use Tacy, roughly how much, and your IP address in transit.
• If you lose your password, every passkey and your recovery key, nobody can recover your history. Not even us.

Changes

When the way we handle data changes, we'll update this page and the date at the top.

Questions or requests: support@tacy.io.