Privacy

The public pages of this site (the landing page, sign in, sign up, password reset, the roadmap, the changelog and this page) load two analytics tools. Google Analytics counts visits: which page was viewed, the site that sent the visitor, and the browser, device and approximate location Google derives from the request. It sets cookies to tell a returning visitor from a new one, and Google receives that data. Microsoft Clarity records how a visitor moves through those pages, including a replay of the page as they saw it, and Microsoft receives that recording. What is typed into the sign-in, sign-up and password forms is masked and is not part of the recording.

Both run only while you are signed out. Neither is loaded on any page you see once you are signed in, so they never see your workspace, your tasks, your documents or your journal. Signing in loads a fresh page, which is what stops tracking carrying over.

There is no other analytics or advertising script anywhere in Zorapilot.

An account holds your email address, your name and your password, hashed. A workspace holds what you put in it: projects, tasks, documents, journals, decisions, settings and the records of agent runs. That content is yours. It is stored in Zorapilot's database and is not sold, rented or shared.

Journals carry their own rule: an agent or API token can read a journal only when that journal is on its reading list, and a new journal is on nobody's list.

For security, Zorapilot keeps a record of sign-ins, failed sign-ins, sign-outs and changes to access: passwords, API tokens, connected accounts, MCP servers, the Anthropic key, and deleting a workspace or an account. Each record holds the time, the IP address and the browser it came from. A failed sign-in for an address with no account records neither the address nor an account. These records are kept for 90 days and then deleted.

When you request a feature or ask for help in Settings, Zorapilot keeps your message and sends it on with your name, email address and workspace: a feature request to the team's task board, a help request to the team's help desk. A help request also includes the page you came from and your browser, so we can see what you saw.

Zorapilot is built on other companies' services, and each one receives part of it:

• Vercel hosts the app and handles every request to it.
• Neon hosts the Postgres database everything is stored in.
• Anthropic receives the content an agent run works with, because the runs call Claude with your own API key.
• Resend sends the app's email, such as a password reset.
• ClickUp holds the team's task board, where feature requests arrive.
• OtterFront runs the team's help desk, where help requests arrive and replies are sent from.
• Google Analytics receives the signed-out visit counts described above.
• Microsoft Clarity receives the signed-out page recordings described above.
• Cloudflare R2 stores files you upload.
• Google and GitHub receive requests only for the account you connect yourself, and only for what that connection reads.

Your Anthropic API key is stored encrypted and is never shown again after you save it.

Connecting a Google Calendar asks Google for two things: permission to read your calendars (calendar.readonly) and your Google account's email address. Zorapilot cannot create, change or delete anything in your calendar.

It reads the list of your calendars and, for the day being shown, each event's title, time, location and which calendar it is on. Those are used to show your day, to keep booked time out of your focus block, and as context for the agent runs you set up, such as the daily brief, which send them to Anthropic with your own API key. Events are read when needed and are not kept in Zorapilot's database; a brief an agent writes can mention them. The email address only labels which account is connected. The access Google grants is stored encrypted.

Nothing from your calendar is sold, used for advertising, or used to develop, improve or train generalized AI or machine learning models.

Zorapilot's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Settings → Connections → Disconnect deletes the stored access. To also remove Zorapilot from your Google account, use Google's third-party connections page.

All of it is yours to delete, without asking anyone. Settings → Workspaces deletes a workspace and everything in it. Settings → Profile closes your account, which deletes every workspace you own, everything in them, and the account itself. Both ask you to type the name back first, and neither can be undone. The security records described above are the one exception: they stay for the rest of their 90 days, so that what happened to an account can still be traced after it is gone.

Zorapilot is run by Phan Ventures LLC. Questions about this page or about what is stored go to support@zorapilot.com.