Angrezify is a voice-to-English keyboard assistant for Android, operated by TrendMindAI ("we", "us"). This policy explains exactly what we collect, what we do not collect, who else processes your data, and what control you have.
We have tried to write this in plain language rather than legal padding. If anything here is unclear, write to us at privacy@angrezify.app.
1. The short version
- Your voice recordings are not stored. Audio is sent for transcription, transcribed, and then deleted. It is not written to our database and not kept on your phone after it is sent.
- We never read passwords, OTPs or payment fields. The Accessibility Service that powers the bubble explicitly skips password fields and does not run inside payment apps at all.
- We do keep your converted messages so that the History screen works. You can delete them.
- We do not sell your data and we do not show ads inside Angrezify. We do use the Android advertising ID to measure our own app-install ads — see section 6a.
2. What we collect
| What | Why | Where it is kept |
|---|---|---|
| Email address and name from your Google account | To create your account and restore your subscription on a new phone | Our database, until you delete your account |
| Voice recording | To convert your speech into text | Not stored. Processed and discarded — see section 3 |
| Transcript of what you said, and the English message produced from it | To show your History screen and to let you re-use past messages | Our database, until you delete it or delete your account |
Detected language, recording length, and the package name of the app you
were typing into (for example com.whatsapp) |
To show the History entry in context and to find quality problems | Our database, alongside the transcript |
| Daily counts — number of conversions, how many of them were made from the floating bubble, and total seconds of audio | To enforce fair-use limits, detect abuse, and see how often Angrezify is actually used | Our database, aggregated per day |
| Trial and subscription status, and the payment reference from Google Play | To know whether your subscription is active | Our database |
| Your name, occupation and theme | To personalise the app | Only on your phone. These never reach our servers |
| Notification token — an identifier Google issues to this installation of the app — together with your chosen app language, app version, Android version, and whether notifications and offers are switched on | To send you occasional updates and offers from Angrezify, and to make sure we do not send them to anyone who has switched them off — see section 5 | Our database, until you delete your account. A record of which notifications were sent to, shown on and opened on your phone is kept for 90 days |
| Crash reports and diagnostics — an install ID, your phone model, Android version, app version, which part of the app failed, and a short technical label for the failure | To find out that something is broken on real phones, and fix it — see section 6b | Crash reports with Google (Firebase Crashlytics); diagnostic events in our database for 30 days |
| Usage milestones — a note that this installation of the app reached a step for the first time (for example: finished onboarding, switched the Accessibility Service on, got a first English result, opened the payment screen), with the date and your app version; and whether the Accessibility Service is switched on | To see where people get stuck while setting up and using Angrezify, and to spot a payment that did not complete — see section 6b | Our database, linked to your account once you are signed in, until you delete your account and for no more than 14 months — see section 7 |
What we do not collect
- The contents of your screen, your chats, or anything you did not dictate
- Passwords, PINs, OTPs, card numbers or UPI IDs
- Your contacts, photos, files or location
- Any data at all from apps on our blocklist (see section 4)
3. Your voice, specifically
This is the part people care about most, so here is the whole path:
- You tap the bubble and speak. The recording is written to a temporary file in the app's private cache on your phone.
- The file is uploaded over an encrypted connection (HTTPS) to our server.
- Our server sends it to our speech-recognition provider, which returns text.
- The audio is discarded. It is never written to our database.
- The temporary file on your phone is deleted as soon as the upload finishes — whether it succeeded or failed. If the app is closed or crashes mid-way, any leftover file is deleted the next time you record.
We keep the text, not the sound. If you would rather not keep even the text, you can clear your History at any time.
4. The Accessibility Service — what it does and does not do
Angrezify uses Android's Accessibility Service. This is a powerful permission and you deserve a precise explanation of why we need it.
What it is used for: two things only.
- To notice that the screen you are on has a text box you can type into, so the bubble can appear at the right moment.
- To place the English text into that text box when you tap Insert.
What it never does:
- It does not read password fields. Any field the system marks as a password is skipped in code, before anything else happens.
- It does not run inside payment apps. Google Pay, PhonePe, Paytm and Android Settings are on a blocklist — the bubble does not appear there at all.
- It does not read, copy, record or transmit the contents of your screen. It looks for an editable field and nothing else.
- It does not act on your behalf, tap buttons, or send messages. Only you press send.
The only thing we record about the surrounding app is its package name — for
example com.whatsapp — stored with the History entry so you can tell
your messages apart.
You can turn the service off at any time from Android Settings → Accessibility → Angrezify, or with the switch on the app's Home screen. The app keeps working; only the floating bubble stops.
5. Other permissions
| Permission | Why |
|---|---|
| Microphone | To record what you dictate. Only while you are holding a recording open. |
| Notifications | To show a small persistent notice while Angrezify is active, as Android requires. From app version 2.13, also to show occasional updates and offers from Angrezify. You can switch these off at any time in Profile → Offers & updates, or in Android's notification settings. The app works the same either way. |
| Run in background / ignore battery optimisation | Optional. Some phones kill background services aggressively, which switches the bubble off. This permission stops that. You can decline it. |
| Advertising ID | To measure which of our own ads led to an install, and to count three app events (see section 6a). It is never used to show you ads inside Angrezify. |
| Query installed apps | Only to check which UPI apps you have, so the payment screen shows the right options. We do not read your full app list for any other purpose. |
6. Who else processes your data
We use a small number of service providers. They process data on our instructions and are not permitted to use it for their own purposes.
| Provider | What they handle |
|---|---|
| Sarvam AI | Speech-to-text conversion of your recording |
| Google (Gemini API) | Turning the transcript into polished English |
| Supabase | Account sign-in and database hosting |
| Google Sign-In | Authentication — we receive your email and name, never your Google password |
| Hostinger | Server hosting |
| Google Play Billing | Subscription payments. We never see your card, UPI ID or bank details |
| Meta Platforms (Facebook SDK) | Measuring installs and app events from our own ads — see section 6a |
| Google (Firebase Analytics) | App usage analytics and install measurement — see section 6a |
| Google (Firebase Crashlytics) | Crash reports and app diagnostics — see section 6b |
| Google (Firebase Cloud Messaging) | Delivering notifications to your phone. Google receives the notification token and the text of the notification |
Some of these providers may process data on servers outside India. Where that happens, it is done under the provider's own contractual safeguards.
6a. Analytics and advertising
We advertise Angrezify on Meta (Facebook and Instagram) and on Google. To know which of our ads actually bring people in — rather than guessing — the app includes the Meta (Facebook) SDK and Google Firebase Analytics.
What they receive:
- Your Android advertising ID, plus basic device and app details such as device model, Android version, app version and country.
- Three events, with no content attached: onboarding completed, first dictation, and subscription purchased (with the amount in INR).
What they never receive: your voice, your transcripts, your messages, your email, your name, your contacts, or anything you dictated or typed.
We do not show ads inside Angrezify, and we do not sell or rent your data to anyone.
You can reset or delete your advertising ID at any time from Android Settings → Privacy → Ads. Deleting it stops this measurement for every app on your phone.
6b. Crash reports and diagnostics
From Angrezify version 2.9.3 onwards, the app reports its own failures to us. Before this, if Angrezify crashed on your phone, or the bubble failed to place text into a message box, we had no way of knowing it had happened. That is the only reason this exists.
What is sent when something breaks:
- An install ID — a random identifier the app generates for itself the first time it runs. It is not your device's ID, it contains nothing about your phone or about you, and a new one is created if you clear the app's data or reinstall it.
- Your phone model, manufacturer, Android version and Angrezify version — so we can tell whether a problem affects one kind of phone or everybody.
- Which part of the app failed, and a short technical
label for the failure — for example
mic / failed / SecurityException. - When the bubble fails, the package name of the app you were
typing into — for example
com.whatsapp— because text insertion behaves differently in different apps. This is the same package name already described in section 4. - If the app crashes, the crash stack trace: a technical record of where in our code the crash happened.
What a crash report or diagnostic event never contains: your voice, your recordings, your transcripts, your messages, your email address, your name, your contacts, the contents of your screen, or anything you dictated or typed. A diagnostic event carries only fixed labels that we chose in advance — never text that you produced. Our database itself refuses to store anything longer than a short label, so this is enforced by the system and not only by our intentions.
Crash reports are handled by Google Firebase Crashlytics. Diagnostic events go to our own server and nowhere else. Neither is used for advertising, and neither is sold or shared.
Usage milestones
Failure reports tell us what broke. They do not tell us where people simply stop — for example, how many people install Angrezify but never switch the bubble on, or open the payment screen and leave. So the app also reports a small, fixed set of milestones: a note that this installation reached a particular step for the first time.
What a milestone contains:
- A fixed label that we chose in advance — for example "onboarding started", "Accessibility Service switched on", "bubble tapped", "first English result", "text inserted", "payment screen opened", "purchase completed" or "payment still pending" — with the date and time, the install ID described above, and your Angrezify version. Each label is sent once per installation, not every time you do that thing.
- For one milestone only — the first time text is successfully
placed into a message box — the package name of that
app, for example
com.whatsapp. This is the same package name already described in section 4. - Whether the Accessibility Service is switched on or off for Angrezify — a yes or a no, with the date it was first switched on and the date it last changed. It says nothing about what was on your screen.
- Like a diagnostic event, the report also carries your phone model, manufacturer and Android version.
How it is linked to you: when you are signed in, a milestone is stored against your account. That is what lets us answer questions such as "of the people who signed up this week, how many got as far as using the bubble?", and it is how we notice a payment that went through at Google but did not switch your subscription on, so that we can put it right. A milestone reached before you sign in carries only the install ID; once you sign in on that installation, we can connect it to your account.
What a milestone never contains: your voice, your recordings, your transcripts, your messages, anything you dictated or typed, the contents of your screen, your contacts or your phone number. Milestones go to our own server and nowhere else: they are not sent to Meta or Google, they are not used for advertising, and they are not sold or shared. The three advertising events described in section 6a are separate from these.
From the same information we also keep anonymous daily totals — for example, how many installations reached a step on a given day, or how often each tone was chosen. These totals contain no install ID and no account, and cannot be traced back to you.
Earlier versions of Angrezify already sent a few of these labels (such as "first English result" and "payment screen opened") as diagnostic events. From 6 October 2026 they are kept as described in section 7, and version 2.13 adds the rest.
7. How long we keep things
- Audio: not kept. Deleted immediately after transcription.
- History (transcripts and messages): until you delete them, or until you delete your account.
- Account and subscription records: for as long as your account exists. After deletion we may keep minimal billing records where tax or accounting law requires it.
- Usage counts: aggregated per day, retained for up to 12 months for abuse detection.
- Analytics and advertising measurement: held by Meta and Google under their own retention policies, typically up to 24 months.
- Diagnostic events: 30 days in our database, then deleted automatically.
- Usage milestones: until you delete your account, and in any case for no more than 14 months. A milestone that carries only an install ID, with no account connected to it, is deleted after 90 days. The copy that carries your phone model is deleted after 30 days, like any other diagnostic event. Anonymous daily totals, which contain no install ID and no account, are kept.
- Accessibility on/off status: kept with our record of this installation of the app. Deleted when you delete your account, or after 180 days in which the app has not been opened.
- Crash reports: held by Google under Firebase Crashlytics' own retention policy.
- Notification token: until you delete your account. If you uninstall the app the token stops working and we stop using it.
- Notification delivery records (sent, shown, opened): 90 days, then deleted automatically.
8. Your rights
Under India's Digital Personal Data Protection Act, 2023, and comparable laws elsewhere, you may:
- ask what personal data we hold about you,
- ask us to correct anything that is wrong,
- delete your History, or your entire account — see how to delete your account,
- withdraw consent — switching off the Accessibility Service stops the bubble and everything it does, though the app still records that the service is off and still processes anything you dictate inside the app itself; uninstalling the app stops all further collection from your phone,
- complain to us, and if unsatisfied, to the Data Protection Board of India.
To exercise any of these, write to privacy@angrezify.app. We respond within 30 days.
9. Children
Angrezify is for adults. It is listed on Google Play for users aged 18 and over, and we do not knowingly collect data from anyone under 18. Under India's Digital Personal Data Protection Act, 2023 anyone under 18 is a child, and we do not process children's data. If you believe a child has created an account, write to us and we will delete it.
10. Security
All traffic between the app and our servers uses HTTPS. Your session token is stored in the app's private storage. Our database uses row-level security, so one account cannot read another's data. No system is perfect; if we ever discover a breach affecting your data, we will notify you and the relevant authority as the law requires.
11. Changes
If we change this policy in a way that affects you, we will update the date at the top and, for significant changes, tell you inside the app before the change takes effect.
12. Contact
TrendMindAI
F1102, Atharv Landmark, Jagatpur–Chenpur Road, Ranip, Ahmedabad, Gujarat 382470, India
Email: privacy@angrezify.app