Privacy Policy

1. Desktop Application

Account (Optional for On-Device Mode)

On-Device dictation works without an account. Cloud Mode, history sync, and paid features need one. You can sign in with email or with Google (via Google OAuth). When you do, we collect and store the following in our database (hosted on Supabase):

• Your email address (for authentication)
• A randomly generated device identifier
• App version, operating system, and architecture
• Usage events, only if you turn usage analytics on (see Analytics below)

You can delete your account in Settings → Account or contact us for help. Meetings you shared with a team can remain in that team's archive after you leave or delete your account.

Audio & Transcription

Walkie offers both On-Device Mode and Cloud Mode.

• On-Device Mode — speech-to-text runs entirely on your device (CPU or GPU) using AI models on your machine. Audio never leaves your device.
• Cloud Mode — audio is sent to our cloud service (operated on Cloudflare Workers and processed by our transcription provider, Groq) for transcription and formatting. The final text is returned to the app. Walkie does not store the dictation clip after the result is returned. Walkie has enabled Groq's Inference APIs Zero Data Retention setting. Groq's published data controls say this prevents retention of request inputs and outputs for reliability and abuse review, while non-content usage metadata remains. It applies to eligible Groq inference requests, not Walkie's synced text, Cloudflare, Supabase, Soniox, or Speechify. Global ZDR is disabled; the enabled switch is specifically for Inference APIs. Your audio is not used to train models.

You choose your mode during setup and can switch at any time. Switching to On-Device Mode keeps speech-to-text fully on-device. When AI Polish is on, Cloud Mode also sends a destination-app category (such as email or chat). From Walkie 1.20.26, it sends selected text, up to 500 characters on each side of the cursor, or the sentence being rewritten only if you turn on “Read the text around my cursor” in Settings → Style. That switch is off by default. Turn AI Polish off to send audio for transcription without any document context. On-Device Mode does not send speech or polish context.

Text Cleanup, Transforms & Ask Agent (Optional)

Some optional features send text to our cloud service (processed by Groq) when you use them. Walkie’s own Ask Agent assistant runs only in Cloud Mode. In On-Device Mode, Ask Agent uses an agent on your computer (Claude Code, Codex, and so on) or does not send the question to Walkie.

• Polish / formatting cleans up a transcript into written text.
• Transforms rewrite text you have selected in another app, following a built-in instruction or one you wrote. In Cloud Mode the selected text and that instruction are sent; in On-Device Mode the rewrite runs on your computer and nothing is sent.
• Ask Agent, when it is answered by Walkie’s own assistant rather than by an agent on your computer.

When these run in the cloud, the relevant transcript or selected text is sent to our cloud service to produce the result. Walkie does not keep a separate copy of the processing request after the response; Cloud Mode transcription history can still sync the resulting text to your account. The text is not used to train models. Some platforms also offer on-device options (e.g., Apple Intelligence) that keep this processing local.

Ask Agent answered by your own agent does not pass through us. If you point it at Claude Code, Codex, Gemini CLI, Grok, OpenCode, Hermes or OpenClaw, Walkie starts that program on your computer, as you, and reads back what it prints. Your question goes wherever that agent is already configured to send it. We do not proxy it, store it, or see it.

To work out which project you mean, Walkie reads the title of the window you were last in and uses it to pick a folder on your computer for the agent to work in. The title is read on your machine, used to choose that folder, and discarded — it is never sent anywhere, and never added to your question.

Sync

We store the following in our database (hosted on Supabase) so your data is available across your devices:

• Settings — if you are signed in, your app preferences sync to your account. API keys, Slack tokens, Google tokens, and MCP server env maps are stripped before upload and are not synced.
• Transcription history, snippets, dictionary, and custom words — these are stored locally on your device. In On-Device Mode they stay only on your device and are never uploaded. In Cloud Mode they are also synced to your account (transcription history includes transcript text, any cleaned-up/formatted text, titles, and timestamps). Account access controls prevent other users from reading your private synced data. Synced content is not end-to-end encrypted: authorized Walkie operators and Supabase infrastructure can access plaintext when needed to operate the service or respond to a support or legal request. Data is encrypted in transit. Meeting audio files stored on your computer are ordinary files; they are not encrypted at rest on disk.

Analytics

Usage analytics are off unless you turn them on, in either mode. Walkie asks once after you have used it for a while, and you can change your answer any time with Share usage analytics in Settings. When they are on, we use PostHog for product analytics. This includes:

• A randomly generated device/session identifier
• App version, operating system, and architecture
• Feature usage events (e.g., app opened, recording started, which model was selected)

Our analytics provider may also process your IP address as part of standard request handling. These events are associated with your account when you are signed in. Analytics never include your audio, transcription text, email, or the name of the app you were in.

Walkie shares its PostHog account with our other product, B150. Every event we send is tagged with which product it came from, so Walkie's data can be filtered out on its own, but it is not a separate, Walkie-only analytics account.

Model Downloads

When you download a speech model, a request is made to our file server (hosted on Amazon Web Services / S3) to retrieve the model. Standard server access logs (IP address, timestamp, file requested) may be recorded. The download does not include your speech or transcript.

App continuity check

At startup, the signed-in desktop app asks a signed status endpoint (hosted on Cloudflare Workers) whether Walkie is still active. The response is only an on/off flag with a cryptographic signature — no account data, audio, or transcripts are sent. A successful “active” reply refreshes a local grace period of 90 days. If the app cannot reach that endpoint for 90 days. If the endpoint remains unreachable past that grace period, the current desktop release stops working. A valid signed “not active” status can also stop the app. This startup check runs when you are signed in, whether you use On-Device Mode or Cloud Mode. An unsigned On-Device install does not make this check.

Local diagnostics and support logs

Walkie writes a diagnostic log on your computer. Routine dictation log lines are designed to record events and lengths rather than your text. If you enable verbose Trace logging, cloud transcription can return short transcript fragments in response headers and the app can write them to that local log. Older app versions logged more speech content. Logs are not automatically uploaded to support; they leave your computer if you choose to export and send them. Settings → Support includes a tool to remove words from older logs before sharing.

Optional Integrations & Connectors

Walkie can optionally connect to third-party services to carry out voice actions (for example, connecting Gmail, or using web search, weather, or news features). These integrations are off by default and only run when you enable and use them. When you do, the data needed to perform the action is sent to the relevant third party (for example, Google APIs for Gmail). Review each service's own privacy policy before connecting it.

2. Mobile App (Keyboard)

On iOS and Android, Walkie is a dictation keyboard you switch to in any app to speak instead of type. It uses the same account as the desktop app.

Consent (Required)

Before any audio or text leaves your device, Walkie asks you to review and agree to how cloud processing works — including which providers receive your content. Nothing is sent until you agree, and you can review this disclosure again at any time from the app's settings.

Dictation (Speech-to-Text)

When you dictate with the Walkie keyboard in cloud mode, your recorded audio and your selected language are sent over an encrypted connection to our cloud service for speech-to-text. On iOS, transcription is performed by our provider Groq; on Android, real-time transcription is performed by Soniox. When Polish is enabled, the resulting text is additionally processed by Groq for grammar and formatting cleanup. The final text is returned to the keyboard and inserted where you are typing. Your audio is not retained after the text is returned and is not used to train models.

On iOS you can instead choose the on-device Apple engine or Local Mode, which transcribe entirely on your device — in those modes your audio never leaves it, and no cloud polish is performed in Local Mode.

Read Aloud (Text-to-Speech)

When you use Read Aloud, the text you choose to listen to is sent over an encrypted connection to our provider Speechify, or to Soniox when you pick one of its voices (offered for languages such as Turkish, Arabic, Japanese and Korean), which generates the audio you hear. Walkie sends the text only to generate that audio and does not retain it after the audio is returned.

Keyboard Permissions

On iOS, the Walkie keyboard requires Full Access so it can send your dictation for transcription and return the text. On Android, the keyboard requests microphone access for the same reason and listens only while you have it open and tap to dictate. Walkie does not read, log, or transmit what you type with other keyboards — it only processes the audio you explicitly dictate.

Data on Your Device

Your transcription history, dictionary, and snippets are stored locally on your device. Account authentication works the same way as in the desktop app (see Account above). Usage data works differently on mobile, as described next.

Usage Data (Optional, Anonymous)

The mobile app sends no usage data unless you say yes to Share anonymous usage data. Walkie asks once, during setup (or on the Home screen if you set the app up before the question existed), and you can change your answer any time in Settings → Privacy. One answer covers two things:

• App events, sent to PostHog: when you open, leave or install the app, finish setup steps, or change a setting (and what you changed it to), plus counts such as how many dictionary words or snippets you have and how long a text you had read aloud was. Each event carries your phone model, system version, language, time zone and Walkie version.
• Keyboard dictation counts, sent by our cloud service to PostHog for each Cloud Mode dictation: how many words, how many seconds of audio, which keyboard (iOS or Android), and which speech service and model turned it into text.

This data is anonymous: it uses a random identifier, not your account; PostHog builds no profile of you and does no location lookup. PostHog may still process your phone's IP address as part of standard request handling for app events; keyboard counts come from our servers, not your phone. It never includes what you say, type or have read aloud, your dictionary words, your name, or your email.

3. Website

The Walkie website (trywalkie.com) uses:

• Vercel Analytics for anonymous page view metrics
• Google Analytics and PostHog for traffic analysis
• Google Ads, Meta, X and Reddit pixels, to measure which of our ads lead to downloads, sign-ups and purchases, and to show our ads again to people who have visited the site
• Cloudflare Turnstile on the support form to prevent spam

Google Analytics, PostHog and the ad pixels store an identifier on your device, so they only load if you say yes to the cookie banner. Saying no, or not answering, keeps them off. You can change your answer anytime under Cookie settings at the bottom of any page; the change takes effect from the next page you load.

If you said yes and then sign up or buy, the Google tag sends Google a one-way hash of your email address so it can match that to an ad click. It never receives the address itself.

If you said yes and you arrived by clicking one of our ads, we keep that ad's click ID in a cookie, and link it to your account when you sign in, confirm your email, or buy. If you buy, we send Google the click ID, the purchase time and the amount, so it can tell which ad worked. We delete click IDs after 90 days, delete them from your device if you change your answer to no, and delete them with your account.

4. What We Don't Do

• We do not sell or share your personal data with third parties for their own marketing
• Walkie does not store cloud dictation clips after processing; desktop meeting recordings are stored until you delete them; mobile meetings keep only the transcript
• We do not use your audio or transcription content to train models
• We do not show ads in Walkie, and we never use your audio, transcripts, or anything you create in Walkie for advertising

5. Third-Party Services

We rely on the following service providers to operate Walkie:

6. Google User Data

Connecting a Google account is optional. Walkie works fully without it. Nothing below happens until you connect Google yourself in Settings, and you can disconnect at any time.

When you connect, Google asks you to approve specific permissions. Here is every permission Walkie requests and exactly what it is used for:

Limited Use

Walkie's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:

• We use Google user data only to provide and improve the features described in the table above.
• We do not transfer Google user data to others, except as needed to provide those features, for security purposes, or to comply with the law.
• We do not use Google user data to train generalized AI or machine-learning models.
• We do not use Google user data for advertising, and we never sell it.
• No human at Walkie reads your Google data, except with your explicit permission (for example if you send us a support log), to investigate a security incident, or where the law requires it.

What Walkie keeps

• Calendar events — read when Walkie checks for upcoming meetings. Walkie keeps the details of events it attaches to a recording (such as the title, time, and attendee list) so your meeting notes stay labelled. Other events are not stored.
• Names and photos — looked up for the attendees of a meeting you are actually in, and cached so your notes render without asking Google again. Walkie does not download your address book, and photos are fetched only for the people who appear in your meetings.
• Connection tokens — the credentials that keep the connection alive are stored in Walkie's settings on your own device and are never uploaded to our servers. They are excluded from settings sync, so connecting Google on one device does not connect it on another — you connect each device yourself.

Disconnecting

You can disconnect Google at any time in Walkie's Settings, which deletes the stored tokens. You can also revoke Walkie's access directly from your Google account at myaccount.google.com/permissions. Revoking access stops all of the above immediately. Cached names, photos, and event details attached to past meetings are removed when you delete those meetings or your account.

6a. Zoom User Data

The optional Zoom desktop integration is currently Coming soon in the public app while Marketplace review and live verification are completed. The next desktop release reads completed meeting occurrences and participant display names only after you connect Zoom and select a meeting. It also reads your Zoom account identifier to support removal checks. It requests three read permissions and does not upload audio, transcripts or notes to Zoom.

Zoom tokens, raw participant rosters and names selected from Zoom suggestions use AES-256-GCM encryption. Separate per-account keys for raw data and confirmed labels are held in macOS Keychain, Windows Credential Manager or Linux Secret Service. Protected writes stop when that store is unavailable; there is no plaintext fallback. Raw rosters and selected Zoom labels are excluded from ordinary cloud sync and AI summary/chat input. Explicit user exports or public share links may include selected labels. Different names you type yourself remain ordinary user-authored meeting data and may be synced. Restoring the unchanged Zoom name preserves its protection.

Earlier test connections may require fresh authorization. Names whose Zoom origin cannot be established remain ordinary meeting data. The final release candidate and live connection are being verified before public availability.

Our HTTPS callback delivers authorization to Walkie on your computer. Our server exchanges the one-time code and temporarily reads the connected Zoom profile to identify the account. Tokens return to the desktop for encrypted storage. We do not retain the returned profile, Zoom tokens, code or verifier on the server. We retain hashed Zoom identifiers and connection references for removal checks. Those hashes are pseudonymous, not anonymous. Hosting providers may retain request metadata under their policies.

Disconnect deletes the current Walkie account's local Zoom tokens, raw imported rosters and their encryption key while retaining chosen speaker labels. To revoke authorization at Zoom, use Marketplace → Manage → Added Apps → Walkie → Remove. We record the verified removal using hashed identifiers. The desktop checks at startup and before accessing the connection, then clears credentials, raw imports and Zoom-derived speaker labels. Offline devices perform cleanup at their next successful online check. Your authored transcript text, meeting notes, calendar attendees and ordinary labels remain.

Temporary authorization attempts are removed by scheduled cleanup. Connection references can remain while retained Zoom labels need removal checks; deleting your Walkie account removes its references. Hashed removal records remain for replay protection, including devices that reconnect after a long time offline. They do not contain your Walkie account identifier.

See the Zoom connection guide for installation, usage, removal and troubleshooting.

7. Data Retention

• Account and usage data associated with your account is retained while your account exists. Deleting your account removes its active database records, including account-linked usage records.
• Synced settings and transcription history are retained until you delete the entries or your account. The production Supabase dashboard reports a Free Plan, which does not include scheduled project backups. We have not verified retention of any internal operational copies held by Supabase.
• Desktop meeting recordings and transcripts remain until you delete the meeting or your account. Mobile meetings retain transcripts only; temporary audio is removed after transcription. Meetings shared with a team can remain in that team's archive after your account is deleted; the team owner can delete archived meetings.
• Local history and recordings are managed on your device. A failed dictation of at least 10 seconds can leave a recovery audio file until you retry, discard it, or replace it with a new long recording; it has no automatic expiry. Deleting your cloud account does not erase copies stored on your devices.

You can delete your account in Settings → Account or request help at the address below. Infrastructure providers may retain request metadata under their own schedules; Groq Zero Data Retention applies to eligible Groq inference content, not those records or any provider-held operational copies.

8. Your Rights (GDPR)

If you are located in the European Economic Area (EEA), you have the following rights under the General Data Protection Regulation:

• Access — request a copy of the personal data we hold about you
• Rectification — request correction of inaccurate data
• Erasure — request deletion of your personal data
• Restriction — request that we limit processing of your data
• Portability — request your data in a structured, machine-readable format
• Objection — object to processing based on legitimate interest
• Withdraw consent — withdraw consent at any time by deleting your account

To exercise any of these rights, contact us at the email below. We will respond within 30 days.

Legal Basis for Processing

We process your data under the following legal bases:

• Contract — an account is required to provide Cloud Mode, sync, and paid features you request. On-Device dictation does not require an account
• Legitimate interest — aggregated usage data helps us improve the application
• Consent — analytics and advertising cookies on the website, usage analytics in the desktop and mobile apps, and sending your audio or text to the third-party processors named above. You can withdraw: decline the cookie banner or change your answer under Cookie settings, turn off Share usage analytics (desktop) or Share anonymous usage data (mobile, Settings → Privacy), or switch the app to On-Device Mode
• Legitimate interest, and your own consent obligations — for other people captured in a meeting you record. You are the controller for that recording: you decide to record, you decide what happens to the notes, and you are responsible for having whatever permission the law where you and they are sitting requires. Walkie processes that audio on your instruction

International Transfers

Walkie is operated from the United States, and the processors named above are largely US-based, so using Walkie means your data is transferred outside the European Economic Area. Those transfers rely on the European Commission's Standard Contractual Clauses, which our processors incorporate into their terms, or on an adequacy decision where one applies to that provider.

Complaints

Write to us first at support@b150.ai and we will fix what we can. If you are in the European Economic Area or the United Kingdom you also have the right to complain to your national data protection authority, and you do not need our permission to do it.

9. Children's Privacy

Walkie is not directed at children under the age of 13. We do not knowingly collect personal information from children.

10. Changes to This Policy

We may update this policy from time to time. Changes will be posted on this page with an updated revision date.

11. Contact

If you have questions about this privacy policy or want to exercise your data rights, contact us at support@b150.ai