keyspeake

Notice: This Privacy Policy was drafted to explain the operational data handling and security architecture of keyspeake. It does not constitute legal advice and should be reviewed by a qualified legal professional before launch.

Privacy Policy

Effective Date: August 2, 2026 • Published by Sirpur Nikhil (India)

1. Core Architecture & Philosophy

keyspeake is a desktop application built around a local-first privacy architecture. We believe your voice data and dictation history belong strictly to you.

Audio recorded by keyspeake is processed locally or transmitted directly to the third-party transcription provider you explicitly choose and configure. There is no keyspeake server in the data path. We do not operate proxy servers, central relays, or backend APIs that collect, intercept, or store your audio or transcripts.

2. Outbound Network Traffic

All network requests originated by keyspeake are customer-triggered by action or explicit configuration. The application initiates network calls only to the following endpoints:

  • API Key Validation: Direct validation requests sent to Groq when testing or validating a Groq key.
  • Speech-to-Text Transcription: Direct transcription requests sent to Groq, Deepgram, or OpenAI, depending on your configured provider, using your own API key.
  • Text-to-Speech (TTS): Direct audio generation requests sent to your configured text-to-speech provider.
  • Text Cleanup / LLM Post-Processing: Optional text enhancement requests sent to your configured LLM endpoint (e.g., Groq or OpenAI) when text cleanup is enabled.
  • Local Sidecar Integration: Communication with a customer-configured local sidecar URL (such as a local model or custom endpoint), if explicitly set.
  • App Update Version Check: Requests for a small static version file hosted on keyspeake.com to check for software updates. This request carries no personal identifiers, telemetry, audio, or system data.

3. Local Data Storage & Files

keyspeake stores application state and user data strictly on your local disk. Files written to your local storage include:

  • Configuration File: Application preferences, key mappings, and settings.
  • Rolling Debug Log: Diagnostic log files maintained locally for troubleshooting.
  • Text-to-Speech Cache & Index: Cached TTS audio files and an index manifest to accelerate audio playback.
  • Current Playback Manifest: Temporary operational manifest tracking active audio playback sessions.
  • Crash Recovery Audio: Temporary audio files saved to prevent data loss in the event of an unexpected application crash.
  • Dictation History Log: A local log recording transcribed dictation entries.
  • Persisted Dictation Audio: Saved dictation audio files, created only when the user explicitly turns on local audio persistence.

4. API Key Storage & Handling

keyspeake uses a Bring-Your-Own-Key (BYOK) model.

  • Local Storage: API keys are stored in plain text inside your local configuration file on your machine.
  • Log Masking: Keys are masked before any terminal output or log entry, ensuring API keys are never written to log files.
  • Direct Transmission: API keys are sent exclusively to the official third-party provider endpoint (Groq, Deepgram, or OpenAI) to authenticate requests. They are never sent to keyspeake or any other server.
  • UI Isolation: API keys are strictly isolated and never exposed to the application's user interface layer.

5. Telemetry & Analytics

There is no analytics, telemetry, or usage tracking anywhere in the product, full stop. We do not collect product metrics, crash telemetry, or usage statistics.

6. Website Waitlist

keyspeake is not yet released. If you enter your email address into the waitlist form on this website, that address is the only thing we store, and it is stored solely so we can email you once when the product is available.

Specifically: we record your email address and the date you submitted it. We do not record your name, IP address, location, browser, or referring page, and the site sets no tracking or analytics cookies. The address is stored in a Cloudflare D1 database on infrastructure we control.

We will never sell, rent, or share your address with anyone, and we will not add you to a newsletter or any recurring mailing. To be removed from the waitlist at any time — before or after launch — email privacy@keyspeake.com and your address will be deleted.

This section covers the website only. It does not change anything described above about the application itself, which continues to send nothing anywhere except the transcription provider you configure.

7. Payment Processing

Payments for keyspeake licenses are processed by Lemon Squeezy, serving as Merchant of Record. The keyspeake product itself never sees, collects, or stores payment details (such as credit card numbers or billing addresses).

8. Operating Entity, Governing Law & Contact

keyspeake is operated by Sirpur Nikhil in India. Questions or privacy matters regarding keyspeake are subject to the governing laws of India.

For privacy questions or inquiries regarding keyspeake, contact us at:

Email: privacy@keyspeake.com