Privacy Policy
Last updated: 7 September 2026
This Privacy Policy explains what information Wizzr handles when you use the Wizzr AI reply assistant. Wizzr is initially intended for users in the United Kingdom, United States, Canada, Australia, New Zealand, Ireland, and Singapore.
Information you provide
When you use Wizzr, you may provide conversation text by typing or pasting it, or select a screenshot manually from your device. This information is used to generate suggested replies for you. Please avoid including passwords, access tokens, verification codes, financial details, or other information that does not need to be part of a conversation.
Account and service information
Supabase provides Wizzr's authentication and account services. Wizzr also uses Supabase to store or query daily generation usage and entitlement metadata needed to enforce the service's plans. Wizzr's server/API runs through Cloudflare.
When an account is deleted, Wizzr's retired-email protection stores an HMAC-derived representation of the normalized email address rather than the original email address. This limited representation may be retained to help prevent reuse of an email address associated with a deleted account.
How generation works
Your submitted conversation text or manually selected screenshot is sent through Wizzr's server/API to OpenAI to generate reply suggestions. The repository does not show Wizzr persistently storing screenshots or conversation text in Wizzr's own database. Screenshots are held in the app's memory for the generation request and are not uploaded by the reporting feature.
Provider-specific retention, deletion, and model-training practices are governed by the applicable provider terms and settings. Wizzr does not make a retention or training promise here that cannot be established from the app.
How we use information
- To authenticate users and provide Wizzr features.
- To generate suggested replies from user-provided text or screenshots.
- To enforce daily generation limits, rate limits, and entitlement rules.
- To respond to support, account-deletion, and safety reports sent by you.
- To protect the service against abuse and prevent deleted-account email reuse.
Sharing
Wizzr sends relevant service data to the providers used in its architecture, including Supabase for authentication/account and usage data, Cloudflare for the server/API, and OpenAI for reply generation. Wizzr does not show a feature that sells your conversation content. Do not send information to Wizzr that you are not comfortable transmitting through these services.
Reports and support emails
If you choose to report a generated reply, Wizzr opens a draft email addressed to app.wizzr@gmail.com. Nothing is sent automatically by the app. The draft includes the selected report category and the individual generated reply so you can review it before deciding whether to send it. It does not automatically include your screenshot or full conversation.
Your choices
You can stop using Wizzr, remove a selected screenshot before generation, request account deletion, or contact us with privacy questions. See the account-deletion information page for the available deletion routes.
Contact
For privacy questions or requests, contact app.wizzr@gmail.com. We will handle requests using information needed to identify the relevant account safely. Do not send passwords, access tokens, verification codes, or recovery codes.