Privacy Policy

Replyzee works without an account. To write your reply, the message you paste is sent to our AI provider, used only to generate that reply, and then discarded — we never store it. We do not sell data and we do not build a profile of you.

When you paste a message and ask for a reply, that text is transmitted over an encrypted connection to the AI provider that generates the reply. The text is used for that single request and is not saved to our database, not linked to your identity, and not used to train any model. Once your reply is returned, the pasted text is discarded.

Because your text leaves your browser to be processed, avoid pasting highly sensitive personal details (passwords, financial data, government IDs) into the tool.

• We do not retain the text you paste into the reply tool after your reply is generated.
• Names, email addresses or phone numbers — unless you email us directly.
• Account data, because there are no accounts.

We record usage events so we know which situations people need most: the type of event (a search, a tone selection, a copy), the public page slug, and the tone chosen. These events contain no message content and no account identifier, but like any website analytics they are tied to your browser session, so they are not fully anonymous.

Our hosting and infrastructure providers process standard server logs, including IP addresses, for security and abuse prevention. Those logs are retained for a short period and are not used for advertising.

Replyzee uses no tracking cookies of its own. If advertising is enabled in future, ad partners may set their own cookies; the Cookie Policy describes that and how to opt out.

Replyzee is not directed at children under 13, and we do not knowingly collect information from them.

Because we do not hold personal data tied to you, there is usually nothing to export or delete. If you have emailed us and want that correspondence removed, write to privacy@replyzee.app and we will delete it.

If this policy changes materially, we will update the date above and describe what changed on this page.