What leaves your phone
Which of your recordings, words and settings stay on your phone, which leave only when you choose, and which requests ScribeKey makes on its own.
ScribeKey keeps your recordings, transcripts and Dictionary on your phone. Your words leave the phone only when you turn on something that sends them: a cloud provider you set up, a place you save notes to, a backup, or a problem report you send. This page explains each case. The privacy policy is the binding statement.
What stays on your phone
ScribeKey has no account. Your words reach ScribeKey only in a problem report that you choose to send. These stay in the app’s private storage:
- Recordings and transcripts. Each dictation becomes a session with its audio and its text.
- Your Dictionary: Words, Replacements, Shortcuts and Suggestions.
- What ScribeKey learns from your corrections when
Learn from my edits is on. - Recognised voices from meetings.
- The vectors that Search by meaning makes from your sessions.
The work done on these also stays on the phone when it runs on device. Speech with a downloaded model, Basic cleanup, Refine, the on-device Skills (Summary and Action items), notes after a meeting, and Search by meaning all run on the phone and send nothing.
The app has no analytics, crash reporting or advertising code. Nothing is uploaded after a crash.
What leaves only when you set it up
Cloud processing uses your own provider account and your own API key. ScribeKey sends the request to the address you configured and to no one else.
| You turn on | What is sent | Where it goes |
|---|---|---|
| Cloud speech | The recorded audio | Your speech provider |
| A Cloud skill, when you choose it | The session’s text, the Skill’s instructions and the name of the app you dictated into. The Email Skill also sends your sign-off. | Your Skills provider |
| Finding speakers in the cloud | The meeting’s recording | Your provider |
API keys are stored encrypted on the phone and are never included in a backup. You can remove one key or all of them on Cloud connections.
On device versus cloud explains when each stage runs where.
What leaves to places you choose
These send your words to a place you picked:
- Note destinations. A notes folder, a WebDAV server, or Notion through your own Composio key receive each finished session as Markdown.
- Backups. Copies in a folder you chose are encrypted with your backup password. Android backup, when you turn on
Include your sessions , carries your sessions only, and only when Android encrypts the backup with your screen lock. Recordings never go to Android’s cloud backup. - Problem reports. A report leaves only when you tap a way to send it, after the app shows you the whole report. Send to ScribeKey delivers it to ScribeKey’s support mailbox. It can include the text of one session you attach, never its audio.
Requests that carry none of your words
ScribeKey makes a few requests that send nothing about you or your sessions:
- A model download fetches the model’s files from Hugging Face.
- At launch, the app checks the model list in ScribeKey’s public catalogue on GitHub.
- The Skills list and a Skill link you paste are fetched from GitHub or the address you gave.
The server that answers any request sees your IP address and the time.
Turn off every cloud stage at once
The switch does not stop the places you chose to send notes and backups. Privacy & security names each one that is still on.
Note
A password field gets nothing. ScribeKey refuses to dictate into a field the app marks as secure, and it keeps no audio and no text from that attempt.