Curzora

Privacy policy

Effective 1 November 2026

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

What we never keep

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.

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

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.