Privacy policy
This page says what Curzora does with your data: what it keeps, what it never keeps, who receives it and how to delete it.
Who runs Curzora
Curzora is run by Curzora, an individual developer (Uzbekistan). To ask anything about your data, write on Telegram.
What we keep
- Your email address, used to sign you in.
- If you are signed in: your questions, Curzora's answers with their steps, the name of the app you asked in, and a title made from your first question.
- Your plan, and counters of how much you have used this month: questions, agent tasks and, for each question, how much the AI and the voice were used and what that cost us. The counters hold no text.
- Your device: an install id, the platform (macOS or Windows), the app version and a device fingerprint. The fingerprint is a one-way hash made on your computer from its identifier; the identifier itself never leaves your computer. It ties the Free allowance to the device.
- Sign-ins on your devices: sign-in sessions, with a hash of the renewal token, the device and when it was last used, for each device. We also keep the interface language and the promo codes you redeemed, with the plans granted to you, the date and the period.
- The server's technical logs: the time and route of a request, the address of the connection, and error classes. Your email appears there only masked, for example us***@example.com. The logs never hold the text of a question, a screenshot, audio or a transcript.
What we never keep
- Screenshots and audio. They live in memory only: for the length of the request, or, while the agent works, until its task ends. Neither the app nor the server writes them to disk.
- Key presses and mouse input. The app looks at them on your computer only to recognize the hotkey and Esc, to see that you finished a step, to find what you circled and to stop the agent when you take the mouse. They are never stored and never sent.
- The clipboard. Curzora never reads it.
When the screen is captured and the microphone is on
The screen is captured only when you ask a question, when Curzora checks that you did a step, and while an agent task runs. The microphone is on only while you hold the hotkey, or while the microphone button in the input bar is on.
Who processes your data
The app talks only to the Curzora server, and sends its error reports to Sentry. It also checks for its own updates and downloads them from updates.curzora.space, which is kept in Cloudflare R2. That request carries no personal data: the name of the update file, the app version and a random code made on your computer that is not tied to you or your account; Cloudflare sees the IP address it comes from, as any website does. Your voice, questions and screenshots reach the companies below only through the Curzora server.
- Shupp and Anthropic. Your question and the screenshots go through the Curzora server to the AI service Shupp, and the Claude models of Anthropic answer. They receive the text of the question, the screenshots, the recent turns of the conversation, and the name and window title of the app you asked in. While the agent works, the screenshots it takes after its actions go the same way.
- ElevenLabs. Your voice goes through the Curzora server to ElevenLabs, which turns speech into text.
- Microsoft Azure. The text of a spoken answer goes to Azure, which turns it into sound. For Uzbek speech, your voice also goes to Azure for recognition, when that recognition is turned on.
- Resend. It sends you the sign-in code, so it receives your email address and the code.
- Zomro. The Curzora server runs on Zomro, in Germany.
- Cloudflare. It is the network in front of the server, so your traffic to the server passes through it.
- PostHog, in the United States (US Cloud). The server sends it counts of events: a sign-in, a question asked, an agent task, a plan change and an account deletion, each with only the plan and the platform. PostHog receives no text, no email and no IP address, and instead of your user id it receives a keyed hash of it.
- Sentry, in the European Union. The app and the server send it error reports: the type of the error and where in the code it happened, the versions of the app and the system, and for the server the method and path of the request. Request content, text, screenshots, audio, your email and your IP address are removed before a report is sent.
We do not sell your data, and Curzora does not train models on it. These companies handle data under their own rules, which this page cannot speak for.
How long we keep it
- Conversation history on Free: a conversation is kept for 7 days after its last answer. The server then erases its text; it checks every hour.
- Conversation history on Pro and Max: kept until you delete it.
- When you delete the history in the app, the text of the conversations is erased at once, in the app and on the server. Only a mark that a conversation existed and the usage counters stay, without any text.
- The email, the device records and the counters stay while your account exists. A sign-in code is kept as a hash next to the email it was sent to, and the server deletes it some time after it expires.
Deleting your account
In the app, open settings, then account, then delete account. Your data is removed from the server at once: the email, devices, sessions, plan records, usage counters and every conversation. Copies in the server's backups age out within 7 days.
Five things stay. Four of them are no longer linked to your account. First, the counter that limits Free use on a device: it holds no email and no name, only the device fingerprint and the number of questions and agent tasks per month. Second, the server's log lines that hold your masked email (for example us***@example.com): they are deleted as the logs rotate, which is by size, with no fixed period. Third, the anonymous count of how many times a promo code was used, which says nothing about who used it. Fourth, the counts of events PostHog received before the deletion: they carry a keyed hash of your user id, not the id itself, and once the account is gone nothing on the server ties that hash to you. Fifth, for each promo code you redeemed, the server keeps a keyed hash of your email (not the email itself), so the same code cannot be redeemed again with that address. This hash is kept as long as the server keeps the record of that promo code.
Changes
If this policy changes, the new text is published here with a new date at the top.
Contact
Write on Telegram: questions about your data, deletion requests, anything unclear in this page.