Privacy··3 min read

Is voice typing safe? A privacy checklist for dictation apps

What happens to your voice when you dictate? A plain-language checklist to judge any voice typing app on Android, from audio storage and AI training to password fields.

read before you talk YOU SAY my card number is no waitI shouldn't say that outloud AWRITE WRITES Never dictate cardnumbers. Awriteswitches off in cardfields.

Voice typing means sending your voice to software, and your voice says a lot: what you write, who you write to, sometimes where you are. It is fair to ask what happens to it. Here is the checklist we would want answered before installing any dictation app, and how Awrite answers it.

The checklist

Question to askWhy it mattersAwrite
Is my audio stored after the text is made?Stored audio can leak or be reviewed laterNot stored
Is my voice or text used to train AI?Your private messages could shape a public modelNever
Where does my history live?Server-side history is another copy of your dataOn your phone only
Does it listen all the time?Always-on mics are a real riskOnly after you tap the mic
What does it do in password and card fields?Sensitive data should never pass through itSwitches off completely
Can I delete my account and data?You should be able to leaveYes, from Settings

The microphone: only when you tap

A good voice typing app records only between your tap and the moment you stop. No wake words, no background listening. Android also shows a green mic dot in the corner whenever any app is recording, so you can always check.

Private fields: the feature most apps forget

This is the one we care about most. Some text boxes should never see a voice app: passwords, PINs, one-time codes, card numbers, CVV, expiry dates. Awrite detects these fields and steps aside:

  • the floating bubble hides,
  • the mic on the Awrite keyboard is turned off,
  • it never reads what is typed there and never pastes into it.

Type those with your fingers, the way they should be typed.

About the accessibility permission

Any app that shows a floating button over other apps and types into them needs Android's accessibility permission. It is a powerful permission, so it is worth knowing how it is used. Awrite uses it to notice when a text box opens, show the bubble, and insert your text at the cursor. It does not collect what is on your screen. If you would rather not grant it, use the Awrite keyboard instead, which needs no accessibility permission at all.

Red flags in any dictation app

  • No privacy policy, or one that says audio "may be retained to improve services".
  • History synced to a server by default with no way off.
  • Asks for contacts, location or SMS permissions it does not need.
  • Free with no plan and no clear business model.
Read our full privacy policy. It is short on purpose.

Simple habits that keep you safe

  • Type passwords, PINs and OTPs by hand, always.
  • Do not read out card numbers or bank details, in any app.
  • Check the green mic dot if you ever wonder what is listening.
  • Review app permissions once in a while: Settings → Privacy → Permission manager.

Quick answers

Does Awrite store my voice?

No. Your voice is used only to create the text and is not saved. Your dictation history stays on your phone.

Is my voice used to train AI?

Not with Awrite. Your voice and text are never used to train AI models.

Does Awrite work in password fields?

No, on purpose. In password, PIN, OTP and card fields, Awrite switches itself off: the bubble hides, the mic is disabled and it never reads or types there.

Why does a floating mic need accessibility permission?

Android only lets an app show a button over other apps and type into their text boxes through accessibility. Awrite uses it to show the bubble when a text box is open and to insert your text.

Awrite Team
We build Awrite, AI voice typing for Android. Published 4 Nov 2026.

Keep reading