SpeaklySpeakly

Data and Privacy

The privacy summary in Settings, what actually leaves your machine, and how to erase your local data

Settings → Data and Privacy holds Speakly's privacy summary and both controls that erase local data. Reach it from the main window: click Settings at the bottom of the left sidebar, then Data and Privacy in the Account group of the dialog's own sidebar.

What leaves this computer

The panel at the top of the screen is titled 🔒 Your words stay on your device, and it says: "What you dictate never leaves this computer. Transcriptions, audio files and your API keys are stored locally and are never sent to us — not the text, not a sample of it, not a summary." One thing does leave: a usage counter.

  • What is sent — one row per recorded usage entry with four fields: the entry's id, the word count, which engine processed it, and when it was created.
  • When — in the background, once as soon as the app signs in and every two minutes after that, and only for rows not yet sent. Offline, they wait.
  • What the server keeps — the word count, the engine, that client timestamp and your user id. Nothing else from the row is stored.
  • What is never sent — the transcript text, a sample or summary of it, the audio, the text read from your screen, your API keys, and your Dictionary, Notes or Custom Prompts.
Why the count exists
The screen gives the reason in its own words: "It is what tells us which models people actually rely on, so we support those first." And the limit: "It cannot tell us what you said. There is no field for it."

Your audio and text reach exactly the engines you picked, called directly from your machine with your own keys: the transcription engine in Settings → Transcription and — when a rule or Agent Mode runs — the model in Settings → Post-Processing, which is also where the screen text goes when you enable it. With local models they reach nowhere at all. Speakly's server is never in that path.

What else the screen shows

  • How Speakly Works — BYOK requests go straight from your device to the provider; transcriptions, notes and settings are stored locally; API keys are never sent to Speakly's servers
  • What Our Server Does — this panel lists two entries, Authentication (sign in with Google) and License Verification (checking whether your Pro license is active); the usage counter described above is the third thing it does
  • Local Data Management — the two controls below
  • Legal — Privacy Policy and Terms of Service open in your browser

Delete history

  1. Open Settings → Data and Privacy
  2. Under Local Data Management, click Delete history. Its description reads: "Erases every saved transcription and the audio files kept with them. Your API keys, settings, dictionary and downloaded models stay."
  3. Confirm in the Delete transcription history? dialog with Delete History
What Delete history reaches
It clears the dictation history — the entries under Recent Activity — and deletes the audio files kept with them. The lists on the Transcribe Media, YouTube and Live Transcription pages are stored separately and are not cleared by this button: delete those entries one by one, or use Erase & Restart.

Erase & Restart

  1. In the same Local Data Management panel, click Erase & Restart
  2. The Erase everything and restart? dialog lists what goes: your API keys, the transcription history and the audio files kept with it, Dictionary, Notes and Custom Prompts, app settings and preferences, and the login session
  3. Confirm with Erase & Restart. Speakly erases the data, restarts, and you sign in again

Two things survive it, in the dialog's own words: "Downloaded models are kept, and nothing on our server is touched." The locally stored usage entries do not survive, so Settings → Statistics starts from empty afterwards.

Deleting the account

Account deletion is the only thing left in Settings → Account → Danger Zone: Delete account, described as "Permanently delete your account and all associated data. This action cannot be undone." It deletes the account on the server first, then wipes local data. The local-data controls used to sit in that zone; they are the two above now.

Nothing here can be undone
Your transcription history exists only on this computer, so there is no server-side copy to restore from after a deletion.
Data and Privacy — Speakly