Voice Data Policy
Voice input is one of Tick's most useful features — and one of the most private. Here's exactly how it works, with nothing left vague.
One-sentence summary
Your microphone audio is processed entirely on your device and converted to text. Tick only ever sees the resulting text transcript — never any audio.
How it works, step by step
- 1You tap the mic button in the app
- 2Your device's native speech engine starts listening
- 3Audio is processed entirely on-device, in real-time
- 4The resulting text transcript appears in your note or AI field
- 5You tap the mic again or tap X to stop recording
On Android
Tick uses Android's built-in speech recognition API — the same engine that powers voice typing on your keyboard. Audio is processed locally on your device. We have no involvement in or visibility into the speech processing itself.
What we never do
Record or store audio files of any kind
Transmit audio to our servers or any third party
Keep any recording of your voice
Access your microphone in the background without your knowledge
Share voice data with advertisers, analytics services, or anyone else
What happens to the transcript?
The text transcript that results from speech recognition appears in whichever field you were using:
Note editor: transcript becomes part of your note and is stored locally on your device only.
AI assistant: transcript becomes your prompt text. It is only sent to the AI when you tap Generate — see our AI policy.
Microphone permission
Tick requests microphone permission only when you first tap the mic button. You have full control:
Grant permission — Voice input works in both the note editor and AI assistant.
Deny permission — Voice input won't work, but every other feature is completely unaffected.
Revoke any time — Go to device Settings → Apps → Tick → Permissions → Microphone.