Yappr is a macOS dictation app. It records what you say, turns it into text, and pastes the text where your cursor is. This page describes what the current version of that software does with the data it touches. It is written from the code, not from an intention.

1. Who is responsible for this

Yappr is made and run by one person. There is no company behind it — no incorporated entity, no team, no staff. Through the rest of this page, “I” means that individual developer and “you” means you. An earlier draft of this page said “we”, which flattered the size of the operation and left every obligation attached to nobody.

The developer is based in Spain. Under the EU General Data Protection Regulation that individual is the data controller for whatever processing described here is his to answer for — section 10 is specific, and honest, about where that is and is not the case. Because the developer is established in Spain, the Spanish supervisory authority is the lead authority; see your rights.

2. What this covers

This policy covers the Yappr macOS application and this website. It describes the behaviour of the app as of the date at the top of the page. Where the software changes, this page has to change with it; see Changes to this policy.

It does not cover what the third parties named in section 5 do with what reaches them. Those are their systems and their documents, and section 5 links them rather than paraphrasing them.

3. What happens when you dictate

One dictation is one pass through the following. Nothing here is optional or configurable except where it says so.

  • You hold the hotkey and speak. The app captures audio from the microphone you have selected in macOS, from the moment the key goes down. To catch your first word, the app keeps the microphone open while it is running, so macOS shows it as in use; nothing is recorded until you press the key, and a press that turns out not to be a dictation is discarded without being saved or sent.
  • The audio is written to a file on your Mac before anything else happens, so that a crash mid-dictation does not lose your words. See what is stored for how long those files live.
  • The audio is transcribed on your Mac, by a speech model that runs locally on your machine. The audio is not uploaded.
  • The transcript text may then be sent to a third-party inference provider to be cleaned up — filler removed, punctuation added, and, in some apps, restructured. That provider is named in section 5. This step is skipped for short dictations and for dictations into a code editor; see what is sent.
  • A set of fixed, local corrections always runs on the result — your dictionary, brand-name spellings, question marks. These run on your Mac whether or not the cleanup step ran.
  • The text is placed on your clipboard and pasted into the app you are focused on. To put back what you had copied, the app keeps a copy of your clipboard and of the text in the field you are in, in memory on your Mac, from when you press the hotkey. They are normally gone within a minute of the dictation, and in every case within 12 minutes of the press. They are never saved to disk or sent anywhere, and anything a password manager marks as private is not kept. If pasting is blocked, the app tells you so, and a double tap of your hotkey pastes the text. In some cases, such as a copy the app does not keep, the text stays on the clipboard.

4. What is sent off your Mac

Everything in this section leaves your Mac and travels to the companies named in section 5. It goes first to a server I operate, which checks your plan and counts your usage without storing what you said — see section 7 — and then on to a routing service, which passes it to whichever company is running the language model that does the cleanup. Those model companies are not mine and I do not operate them.

Sent as part of a normal dictation

  • The transcript of what you said, when the cleanup step runs.
  • The name of the app or web surface you are dictating into — for example “Slack”, “Gmail”, “Cursor” — and a category derived from it, so the cleanup can match the register. The app reads the URL and window title of your frontmost browser tab in order to work that name out; the URL and the window title themselves are not sent.
  • Up to 200 names from your screen, whether or not you said them, when the cleanup step runs and “Use names on screen” is on, so the model spells them the way your screen does. They are taken from the text in the front window, as described in section 6; nothing else from the screen is sent.
  • The choices the app made about how to clean it up — the kind of app, how polished to make it, whether to shape it as a prompt for an AI — and any custom prompt you have set for that app. Since version 0.1.30 the instructions the model receives are written on my server from those choices; until then the app wrote them and sent them itself.

Sent when you use select-and-rewrite

  • The text you had selected in the other application, in full, along with your spoken instruction. This is how the feature works: the model cannot edit a selection it has not been given. The selection is read at the moment you press the hotkey, either through macOS accessibility APIs or, in apps where that does not work, by triggering a Copy and reading the clipboard (the app restores what was on your clipboard afterwards).

Sent while context memory is on — and only what you supplied

Context memory is on by default, and it only ever sends what you have supplied. Until you write, paste or import something — about yourself, the people and words you use, or a project — nothing below is sent, not even your email address. Turn it off in Settings → You and none of it is sent at all, until you add something new: adding context, during setup or later, switches it back on, because adding it is you asking for it to be used.

Until 22 September 2026 it was off by default, and setup asked for a profile that it then never used: what you pasted was stored and sent nowhere. Existing installs are switched on once, and everyone using one was told before it happened (section 16); after that the switch is yours.

While it is on, the following is added to the instructions sent with every cleanup:

  • The remembered facts for the current project, plus any facts you have marked as global — short sentences that you added. The app does not write them; until 11 September 2026 it also drew them from your dictations, and that is removed.
  • An overview paragraph about you — the one you wrote or pasted in Settings. Nothing else writes it.

    Until 10 September 2026 a model wrote it, from your past dictations. That is removed, and the reason is worth stating: it was asked to work out a name and an age from a batch of recent dictations, and where those dictations were emails to other people it recorded one of them as the user. Who you are is not something that can be inferred from what you happened to say last week, so nothing infers it any more.

    On 11 September 2026 the same was done for the remembered facts. Nothing in the context layer is now written by the app: every sentence in it is one you typed, pasted or imported, and you can edit or delete any of them in Settings.
  • Facts derived from the project you are working in — no longer produced. Until 11 September 2026 the app read your project’s package.json and emitted a short sentence such as “Built with Next.js.” It stopped along with the rest of automatic writing. It never read your source code and never sent file contents, file paths or dependency lists.
  • A list of names and words to spell exactly — at most 30, taken from the people you added in Settings → You, the words in your dictionary, and the names and file names that appear in the current project’s remembered facts. Since version 0.1.30. Everything on it is something you typed, pasted or imported.
  • One of your saved links, when you ask an email for one — if you ask Yappr to write an email and to include “the link”, “my site” or a link you saved by name, the one link from Settings → You → Links & shorthand that fits (its name and its address) is sent with that request, so the email can carry it. Never the whole list, and never with any other dictation. Since version 0.1.32. With context memory off it is not sent: the app adds the link to the email on your Mac instead.
  • Your account email address, so the app spells it — and the name inside it — correctly, and so “here’s my email address” can be written out for you. It is the address you signed in with. Until 13 September 2026 this was a separate field you typed in Settings; that field is gone, because a second copy could disagree with the first. It is sent only alongside facts or an overview you supplied — never on its own.
  • Up to 50 of your stored past dictations, in one background call — no longer sent. Rebuilding the overview paragraph used to mean sending the text of those dictations — with the app name and how long ago each one was — to the provider, periodically, while your machine was idle. Nothing rebuilds the overview any more, so that call was removed on 11 September 2026 and no background batch of your dictations leaves your Mac. The only text sent is the dictation you just spoke.

Sent when you import context

  • The text you paste into an “About you” or project box, once, so a model can sort it: which of your projects it belongs to, and which lines are notes, names, terms or links. Sent with it are the names of your existing projects and up to two notes from each, so a project you already have is recognised rather than added twice. It is sent when you paste, before you confirm what will be saved, so cancelling does not unsend it. Nothing is saved until you confirm. If you are signed out, nothing is sent and the paste is filed on your Mac as before.

Sent only if you turn on Talk to your apps

Talk to your apps is off until you turn it on in Settings → Apps. Until then nothing connects and nothing is read through it. The one exception stays on your Mac: if Yappr Agents is on, the first time a session pushes a project linked to Vercel, Yappr asks once whether to connect. To notice that, after each turn of a coding agent it reads that folder’s git history and looks for a Vercel file, on your Mac only, until you answer. Nothing is sent unless you click Connect. Once you have turned Talk to your apps on, Yappr asks Composio which apps are connected when Settings → Apps or the notch’s Apps opens or comes back into focus, and after a coding agent’s turn if Yappr Agents is on. That sends your account id, and Settings → Apps keeps doing it even if you later turn Talk to your apps off, so that Disconnect stays available. Each app needs its own sign-in. When you ask about a connected app, the request goes through my server and Composio to that app, and the answer comes back the same way to show in the notch. What passes through can be kept in Composio’s logs for up to one year. Your voice is still transcribed on your Mac; the audio is not sent.

  • Morning and end-of-day brief. At 8:00 and at 18:00, once each, a small mark appears on the notch if you have an app connected. Nothing is read for the mark. When you open the brief, or ask for it, Yappr asks Vercel, Supabase, GitHub, OpenRouter and Stripe, whichever you connected, through the same route, for the numbers below and anything wrong, and searches Hacker News for the word you saved under Watch for, if you saved one. Nothing goes to the language model.
  • Numbers over time. When you open an app in the notch, open the brief, or are already using the notch and the last check is at least two hours old, Yappr asks for each connected app’s numbers by day: Vercel visitors for the last 60 days, when your own pull requests were merged, the times of sign-ups to your newest Supabase project yesterday and today (only the times, read from its sign-in logs), and your OpenRouter credits and spend by day and model. Your Mac keeps one number a day for each app, for 62 days at most, to draw the charts and to notice an unusual day. It keeps no names, pages, emails or messages, and signing out deletes it. Nothing goes to the language model.
  • OpenRouter. You connect it with an OpenRouter key on Composio’s page; Yappr never sees or shows the key. Yappr reads only your credits and your spend by day and model, never your prompts or the model’s answers.
  • Hacker News. There is nothing to sign in to. When you ask about Hacker News, the words you searched for (or, for “is anyone talking about us?”, the word you saved under Watch for in Settings → Apps) go through the same route to Hacker News’ public search, and the stories come back: title, points, comments, age and the linked site. If you saved a word, the morning and end-of-day brief searches it once to show one line when it came up in the last day. Nothing is kept except that word, which stays in your settings until you clear it.
  • Resend. You connect it with a Resend API key on Composio’s page; Yappr never sees or shows the key. Reading what was delivered needs a Full access key. Yappr reads your sent emails of the last 7 days: when each was sent, whether it was delivered or bounced, and the address of each one that bounced, never a subject or a body. When you ask, or when you are already using the notch and the last check is at least two hours old, it counts them and shows a bounce from the last day on the notch. The counts and the addresses stay in memory and go when Yappr quits; nothing is written to your Mac.
  • Failed deploys, without you asking. If Vercel is connected and Yappr Agents is on, then whenever a turn of a coding agent ends in a folder that was just pushed, Yappr checks Vercel until that deploy finishes, and shows a small mark and a short line on the notch only if it failed. Each check sends your newest deploys (project, branch, commit message, state) and a failed deploy’s last log lines through the same route. It never checks at any other time, and nothing goes to the language model. Disconnect Vercel or turn off Talk to your apps to stop it.
  • Supabase. Asking what’s wrong brings back your project names, security findings (which can name your tables and functions), whether each service is up, and a count of database errors. Apart from SQL you run yourself (below), Yappr never asks for your database contents or the text of your logs, and nothing goes to the language model. Composio holds the sign-in, and what that sign-in permits may be broader than what Yappr asks for.
  • Run SQL from the notch (added 14 November 2026). If Supabase is connected and a coding agent asks you to run SQL in Supabase, the notch shows that SQL with a Run button. Only when you click Run, the SQL and the project it runs on go through our server and Composio to your Supabase project, and run there. What comes back passes through the same route and can include rows from your database; Yappr keeps none of it, and tells your agent only “done” with the number of rows, or Supabase’s error. Nothing runs without your click, and nothing goes to the language model.
  • Gmail. Asking what needs a reply sends the sender, subject and a short snippet of your unread Primary emails to the language model, so it can pick the ones a person is waiting on. Asking it to write a reply sends the opened email and what you said. Asking it to write a new email sends what you said, and each name you said is looked up in your Google contacts and Gmail. Asking a question about your email sends your question with the sender, subject and a short snippet of your inbox’s last month. Nothing is sent until you press Send. Yappr reads Gmail only when you ask.
  • Google Calendar. Creating an event sends your spoken sentence to the language model. Each name you said is then looked up in your Google contacts and Gmail. Asking a question about your calendar, or asking to change or cancel an event, sends your question with the titles, times and places of your events from a week ago to a month ahead. An event changes only when you press Save, and is cancelled or declined only when you press that button; its guests are told. Showing today’s calendar involves no language model. Yappr reads your calendar only when you ask.
  • Outlook (added 15 November 2026). Outlook mail and Outlook Calendar work like Gmail and Google Calendar above, through Microsoft under your own account. Asking what needs a reply sends the sender, subject and a short snippet of your unread mail to the language model; opening one email shows it in the notch. Yappr does not write or send email through Outlook. Creating an event, asking about your calendar, or changing, cancelling or declining an event sends the same things as for Google Calendar, and each name you said is looked up in your Outlook contacts and mail. Nothing changes until you press that button. Yappr reads Outlook only when you ask. Gmail, Google Calendar and Outlook are available to everyone who turns on Talk to your apps.
  • Stripe, Vercel and GitHub. Payments, customer names and email addresses, deploys, visitor numbers and pull requests pass through to the notch. No language model is involved.
  • Fix with Claude. Clicking it on a failed deploy or a finding opens a new task in your own Claude with the project, the branch and up to 4,000 characters of the log or finding. Nothing goes until you press Send there, and then it goes through your own Claude account. Build logs can contain secrets, so read it first.
  • Nothing is sent or created without your click. A reply goes out only on Send, and an invite only on Send invite.

Sent when the app first sets itself up

  • The speech model that runs on your Mac is downloaded, once, from a third-party model host — see section 5. That request carries your IP address and the app’s version string, as any download does.

5. Who receives it

This is the complete list of third parties that receive anything, in the version of the app this page describes.

  • Supabase — hosts the server the request passes through, and the database behind it. It receives your transcript in transit, because the request travels through code running on its platform. That code does not store the text; what the database holds is your email address, the hashed form of your password, which plan you are on and when your Pro time ends, counts of your usage, and — since 27 September 2026 — your invite code, who referred whom, and a running total of how many words have been cleaned up for your account (a number, never the words; see section 15) — and, if you subscribe to Pro, your subscription as Paddle reports it: its Paddle reference numbers, its status, which price it is on and when the current period ends — and, since 30 September 2026, whether you said yes or no to product news, when, where and to which wording (see section 15). Since 12 November 2026 you can sign in with Google: then Google sends Supabase your Google account’s email, name, profile picture address and account id, which Supabase keeps with your account; Yappr uses only the email, and Google learns that you signed in to Yappr. That database is in US East (Ohio), which makes it an international transfer in its own right — see section 11. And see section 7 for exactly what that server does and does not keep.
  • OpenRouter — the routing service my server sends the request to. It receives everything listed in section 4: your transcript, the app name and category, the instructions the app writes, your selected text on a rewrite, the text you paste when you import context, and — while context memory is on and only once you have supplied some — your remembered facts, your overview paragraph, your account email and, on an email that asks for one, one saved link. It then passes that on to whichever company is running the model.

    If you use Talk to your apps, it also receives the email details and spoken sentences listed there, under the same four companies and the same instruction.
  • Composio (Sampark Inc, doing business as Composio) — only if you turn on Talk to your apps. It holds your sign-in for each app you connect, receives your Yappr account id with each call, and every request and answer for those apps passes through it. What passes through, including email and message text, can be kept in Composio’s logs for up to one year, with a record of each call. Composio offers a zero data retention setting, but on the Composio plan Yappr uses it does not cover these apps.
  • The apps you connect — Google, Microsoft (Outlook), Stripe, Vercel, GitHub, Supabase, OpenRouter and Resend, each only if you connect it, and Hacker News’ public search when you ask it. They receive the requests you ask for, under your own account with them.
  • The company running the model — one of exactly four, and here they all are. My server asks for Groq first, and permits Fireworks, Together AI and DeepInfra as fallbacks if Groq is unavailable, so that your dictation still works rather than failing. Which one handles any given request can therefore differ from one dictation to the next.

    An earlier version of this page said only “usually Groq” and noted it was not guaranteed. That was true and it was not enough: a recipient you cannot name is one you cannot check. The list is set in the routing configuration, it is these four and no others, and adding a fifth is a change to this page as much as to the code.

    Every request also carries an instruction telling the router to refuse any provider that would collect data from it. I restrict the list to providers that state they do not retain requests or train on them — but I am naming a policy I set and an instruction I send, not auditing their machines. These companies are in the United States, so this is a transfer out of the EEA; see section 11. Groq’s documents: privacy policy, terms of use, and the legal index for its cloud service, which is where its services agreement and its data processing addendum live.
  • Hugging Face — hosts the speech model file the app downloads once, so that transcription can happen on your Mac. It receives what any file download tells a host: your IP address and the request headers. No dictation, audio or text is involved; this happens before you have said anything.
  • LRCLIB (lrclib.net, a free public lyrics library) — while Notchy’s Music is on, each song that starts in Music or Spotify is looked up there by its title, artist, album and length, so its lyrics can show. It also sees your IP address, as any request does. Nothing about you or your account goes with it, and videos playing in a browser are never looked up.
  • GitHub (owned by Microsoft) — hosts the installer and the update feed. Clicking “Download for Mac” on this site fetches the installer from it, and the app asks it whether a newer version exists and downloads the update from it. Each of those requests tells it your IP address and the request headers, as any file download does. No dictation, audio or text is involved, and nothing about your account is sent.
  • Paddle — sells Pro as merchant of record, and only if you choose to buy it. When you press Upgrade, my server sends Paddle your account email address and an internal reference to your account, so the checkout opens in your name and the payment can be matched to it afterwards — and the date Paddle takes the first payment: 1 January 2027 if you subscribe before then (with your plan and trial end date at that moment, so that cancelling can put your account back where it was), or the day your Pro trial ends. On its own checkout page Paddle then collects what a purchase needs — your card or other payment details, your country and postcode, and a tax number if you give one — which I never see. Paddle tells my server when a subscription starts, renews, changes or ends. For the purchase Paddle is a controller in its own right, under its privacy policy; the checkout page on this site loads Paddle’s script from Paddle, which is the one script from another company this site serves. Nothing about your dictations is sent to Paddle.
  • Resend — sends every email Yappr sends, from an address on useyappr.com: your sign-in codes and confirmation links, the reminder before a subscription’s first payment, and the product-news email, which goes only to people who said yes to it (section 15), and a founding member’s invitation to a friend (section 15). For each email it receives your email address and the email itself (for a sign-in email, the code or link in it; for product news, your own unsubscribe link); nothing about your dictations. It does not record whether you open an email or click its links. Resend is run by Plus Five Five, Inc. in the United States and processes data there, under its data processing addendum, and deletes what it holds within 90 days of the account being closed.
  • The host of this website — a third-party provider serving these pages as static files. Loading a page sends your IP address and user agent to it, as loading any web page does. Since 19 October 2026 the host also counts visits for me (Vercel Web Analytics): which page you opened, the page that sent you, your country, and your browser, operating system and device type. It sets no cookies and keeps no IP address; a visitor is counted with a value derived from the request that resets every day, so I can see how many people visit, not who they are. I also count how many times each of my short links (such as useyappr.com/x) is opened and how many times the Download button is clicked, with the time to the minute (kept 90 days) and noted against the link you came in on or the main domain of the website you came from (example.com, never the page), if any. No account, address or device is stored with that number. When you click Download, this site also keeps that same link or website name in your own browser (local storage, not a cookie) for up to a month; if you then confirm your Yappr email in that browser, the confirmation page sends that one word with your new account, and I store it with your account so I can see which places bring people who sign up. Nothing is kept or sent for a direct visit, and nothing at all if you confirm in another browser. This site sets no cookies, loads no advertising or tracking script, and serves its fonts from its own domain rather than fetching them from Google while you read. The one exception is the checkout page you reach from Upgrade in the app: it loads Paddle’s checkout, and whatever Paddle stores in your browser there is Paddle’s, under its policy.

There is nothing else. No other payment provider — Paddle, above, is the only one, and only when you buy; see the Terms. No other email-sending service: every email Yappr sends goes through Resend, above. When you write to the address in section 17, your email and my reply go through Google, as any mail to that address does. No crash reporter, no error tracker, no analytics beyond the host’s own visit counts above, no advertising network of any kind.

6. What is not sent

  • What Notchy shows in your notch. Notchy reads, on your Mac only: your battery and charger, your AirPods’ battery and name, the sound and screen brightness, what is playing (title, artist, album and artwork), and, if you turn on Next meeting and allow it, your calendar for the next day (each event’s title, times, the call link found in it and, since 13 November 2026, the names and email addresses of the other people invited). The pictures of AirPods come from your own Mac. None of it is sent to us or anyone (except a song’s title, artist, album and length to LRCLIB for its lyrics, below), written to disk, or kept after Yappr quits; the log notes numbers such as a battery level and, when lyrics are looked up, the song’s title, artist and length, never a meeting’s title, a name or a link. If you let Notchy replace Apple’s volume pop-up, the app holds back only the volume, mute and brightness keys, and never stores them. Join opens the meeting’s own link in your browser or meeting app. AirDrop from the shelf opens macOS’s own AirDrop window; the files go by AirDrop to the person you pick, never through us. After you have used it, Notchy also notices files arriving by AirDrop in your Downloads folder, by their name and the tag macOS puts on them, without opening them. If you hold your key and say something like “Notchy, tell them I’m 5 minutes late” while a meeting is coming up (Pro), Yappr writes that email on your Mac, to the people invited, and shows it to you; it leaves your Mac only when you press Send, through your Gmail or your own mail app. Spoken commands that start with “Notchy”, such as “Notchy, play some music”, are read on your Mac and are not kept.
  • Your audio. Transcription runs on your Mac. The app pins this: every read of its settings forces the local transcription engine, so the cloud transcription path cannot be selected in this build.
  • The URL or window title of your browser tab. Read locally, used to pick a category, not transmitted.
  • The text in the front window. When you press your key, and again every few seconds while you are recording, the app reads the front window’s title (in a browser, the tab’s title too), the text of the box your cursor is in — at most 4,000 characters around the cursor — and the text the window is showing on screen, up to 20,000 characters (never what is scrolled out of view), and keeps only the names in it. To read that text in some apps, such as Claude or Slack, the app asks them to turn on the accessibility features macOS provides for screen readers. This happens on your Mac, while you speak, and stops when the recording stops. If you switch to another window while recording, that window is read too. It only reads a window you can see. The text itself is not sent, not written to disk and not logged. Up to 200 of those names, including other people’s names, are sent with that dictation’s cleanup request, whether or not you said them, so the AI can recognise a name it misheard. The names are used for that one dictation and then dropped, and are not stored by Yappr. An email address or website on screen is kept the same way, so that one you say is written exactly as shown; addresses and websites are matched on your Mac only and are never sent. It never reads a password field (nor the window’s text while one is focused), a browser’s address bar, Yappr’s own windows, or password managers and banking apps. You can turn it off in Settings → General (“Use names on screen”); then nothing is read and nothing from the screen is sent.
  • Text you copy, and screenshots, images and files you take or copy. Text you copy while dictating is added to your words in the app you are dictating into: under “Additional context” in an AI chat or coding agent, and as plain text elsewhere. It is kept in memory only, never logged, never sent to the AI, and anything that looks like a password or key is skipped. Screenshots you take while dictating are pasted into the app you dictate into (as the picture itself in chat, email and document apps, as the file’s path in a terminal or code editor); otherwise images stay on your Mac. Yappr notices new screenshots, images and files you copy so it can offer them with your next dictation for 2 minutes (1 to 10, as you choose in Settings); they stay on your Mac and are only pasted where you dictate or sent from an agent’s reply card when you press Send. If that app or agent can read files, it may read this one and send it to its own provider. A file’s path pasted as text is saved in your History on your Mac.
  • Drawing on your screen while you dictate. While you dictate, you can circle things on your screen. When you do, Yappr takes a picture of that screen with your drawing on it and adds it to what you are dictating. It needs macOS’s Screen Recording permission for this, and asks for it during setup or when you press Allow in Settings, never while you dictate. The picture stays on your Mac until you paste it; Yappr never sends it to its own servers. Turn it off in Settings → General.
  • While macOS asks for a permission. During setup, Yappr reads where windows sit on your screen, so it can show one line beside macOS’s question, and the folder names Claude Code keeps, to tell whether to ask for your Documents folder. None of this is stored or leaves your Mac.
  • The list of programs running on your Mac. When you dictate into a terminal or a code editor, the app reads the list of running programs to tell whether an AI coding tool is running in it. It reads their names, and the full command lines only of the programs running inside that terminal or editor. This is held in memory for that one check and is not stored or sent. The app also reads program names, not command lines, to notice whether another dictation app is running. Until 28 September 2026 the check read the command line of every program on the Mac.
  • The Claude app’s own log file. When you dictate into the Claude desktop app, Yappr reads the end of that app’s log file (usually the last 256 KB, further back only until it finds the last time you switched tabs) to tell its Code tab from Chat. It is held in memory for that check and is not stored or sent.
  • What you type. To notice your hotkey, the app is told about key presses on your Mac. It uses that for five other things. It notices that you are typing a message, so the notch can remind you that you could say it instead; for that it keeps only the times of your last few key presses. To word that reminder it checks only what kind of app is in front, such as an AI chat or an email app (in a browser, which site the tab is on), never what you typed. It notes whether any key was pressed since its last paste, so a dictation that follows straight on gets a space in front of it, and one after you pressed Enter or moved the cursor does not. And when you press Use my words on the notch, it checks whether you pressed a key or clicked somewhere else since the paste, so it never undoes anything but that paste. And when an update has downloaded, it notes the time of your last key press or click, so it installs the update only when you have stepped away. While you dictate, Yappr also checks whether Shift, Command and the mouse button are held, so holding Shift can draw. It keeps only that moment and never writes it down. All of it is kept in memory, never which keys they were. Nothing about your typing is written to disk or sent anywhere. You can turn the reminder off in Settings → Notch.
  • What Yappr Agents reads, once you connect Claude Code, Codex or Cursor. Yappr Agents is on for everyone. It reads only from the tools it is connected to: the ones you pick when you set Yappr up (Claude Code, Codex and Cursor are picked unless you untick them), or, if you already used Yappr, each of the three that is on your Mac, connected once with the update. You can disconnect any of them, or turn Yappr Agents off, in Settings → Agents, and it stays off. Once connected, Claude Code tells Yappr, on your Mac, when a session starts, finishes, asks you a question or asks permission: the folder, what you asked, Claude’s last message, the question and its choices, and which app or terminal it runs in. Yappr also reads the end of each running session’s own log, the Claude app’s name for each conversation, and pictures a session saves or a page it runs on localhost, so the notch can show what each one is doing. All of it stays in memory on your Mac. Your answers go back to that session through Claude Code, and Yappr adds a short instruction to your prompts asking Claude to end with clear choices, which reaches Anthropic with your prompt. If you connect Codex, Codex tells Yappr the same things through its own hooks, and Yappr reads Codex’s name for each conversation. From Codex’s own log of your newest session Yappr reads only how much of your Codex usage limit is used and when it resets, for the ring on the notch; it reads nothing else there, and keeps it in memory. The instruction reaches OpenAI with your prompt. A new task you start on a Codex model runs your own Codex in that folder. If you connect Cursor (beta), Cursor tells Yappr the same things through its own hooks, and Yappr reads Cursor’s name for each chat; it reads no Cursor log, and drops the account email Cursor includes. Yappr’s servers receive only the button events in Yappr Agents — which buttons you used, and the short message below when you send words to a session by voice.
  • A short message to a session, when you send one by voice. When you say “Hey Yappr” and send words to one of your sessions (“ask the checkout session what’s left”), Yappr sends your words, that session’s name and the start of the last thing you asked it to my server and the cleanup model, to write them as a short message to the session. You see the message before Send; if it cannot be written, your own words are used. It is not stored, and nothing is sent this way unless you route words to a session.
  • Names from your coding agent, if you choose. During setup Yappr reads your coding agent’s notes and your recent projects’ instruction files (CLAUDE.md, AGENTS.md, README) and gives them to the agent you already use (Claude Code or Codex) to list the names, words and links in them. It runs on your own account, with no tools. As soon as it answers, the answer is sent once to be sorted, the same way as a paste, while setup goes on, even if you skip the screen that shows it. Nothing is saved until you confirm what it found.
  • Your source code, your file contents, or your file paths. A name you said that also appears on your screen, such as a file name, can be one of the names above; the code or text around it is not.
  • Your dictation history, your statistics or your log file. These stay on disk. Nothing uploads them. The log file is one you may choose to send for support, at which point you are sending its contents — see Logs.

7. Whether anything reaches me

Your text does. An earlier version of this page said nothing reached me, because the app called the model provider directly with a credential kept on your Mac. That is no longer how it works. The request now goes from your Mac to a server I operate, and from there to the model provider. Every transcript that gets cleaned up passes through my infrastructure.

What that server does with it is narrow, and it is the part worth being precise about. It reads the request in memory to check three things: that you are signed in, that your plan allows the request, and how many words it contains so your weekly allowance can be counted — the same count is added to your account’s running total, which decides whether an invite counts (section 15). Since version 0.1.30 it also writes the instructions for the model around your text, from the choices the app sent (see section 4). Then it forwards the request and discards the body. The text of a dictation is not written to a database, a log or a file at any point. (There is one thing you can hand over deliberately — a bug report — and it is described below.) What is written is counts and timestamps: requests this minute, dictations and words this week, dictations today, tokens today, and a running total of words for your account — and, since version 0.1.29, how long each dictation took, and, since version 0.1.46, short error reports and which Yappr Agents buttons you used. Those are numbers and error lines about the app, not copies of what you said.

The same goes for Talk to your apps: your emails, events and account details pass through that server and are not stored on it. Composio is different: it can keep them in its logs for up to one year (section 5). My server logs which kind of request ran, whether it worked and how long it took, and keeps a per-minute count of these requests for your account for 25 hours, to stop runaway use.

On the free plan, every dictation counts toward your week — including short ones that do not go out for cleanup. For those, the app sends my server the dictation’s word count: one number, never the words, which is added to your total for that week. It is kept with the weekly counts above and deleted on the same schedule. It is sent only while your account is on the free plan.

Those counts are deleted on a schedule, and the schedule is short because the numbers stop being useful almost immediately. The per-minute request count is kept for one day; it exists to stop a runaway loop, and the window it guards is one minute. The weekly word count is kept for four weeks — the current week, plus enough history to answer a question about a limit you hit recently. The daily token total, a single number for the whole service and not attached to anyone, is kept for a year so I can tell what the thing costs to run.

Two counts are kept for as long as your account exists, and deleted with it. The number of dictations you made each day, which is how I see which days Yappr is used and which enforces the published limit of 600 a day; and the running word total, which exists only to decide whether an invite counts. Until 27 September 2026 this page did not list the daily count at all, although it had been kept since 13 September; that was an omission, and this is the correction.

Founding membership, since 24 October 2026: if your account is one of the first 150, its founding member number and the date it was given are kept with your account and deleted with it, and, since 4 November 2026, the date it turned free if it did. The number comes as soon as you sign up and confirm your email (until 15 November 2026, on the third different day your account dictated, counted from the usage records in this section). Nothing else is kept for it. (From 24 to 27 October 2026 the number of hotkey presses each day, and your time zone's name, were also counted for a first-week goal; that goal is gone and those counts were deleted.)

Until 10 September 2026 there was no schedule at all. The per-minute counter had been accumulating since the server went live, which made it a minute-by-minute record of when each account was active — far more than a rate limiter needs, and longer than I have any business keeping it. It is now deleted hourly, and the old rows are gone.

I am telling you this rather than claiming it is nothing. “It passes through my server and is not kept” is a weaker statement than “it never reaches me”, and it is the true one. You do not have to take the storage part on faith either — it is a property of code I can be held to, not of a company I cannot audit.

Bug reports — the one thing you can hand over

If something goes wrong, you can send me a bug report from Settings. That report reaches me, and it is stored. It is the only thing in this product you can deliberately give me, and it exists because a report that never arrives fixes nothing.

You read it first. The entire report is shown on screen before anything is sent: the description you wrote, which app the dictation landed in, how long it was and how much came back. What you actually said is included unless you untick the box. The box starts ticked, because the words are what usually find the bug, and you see them in the report before you send it. When the dictation was spoken over text you had selected — to rewrite it, or a dictation that replaced it — the same box also includes that selected text, which can be words from your document or from someone else’s message. Untick it and the report carries the shape of the dictation and none of its words, selected or spoken. Right beside the Send button, the app shows the actual words that pressing it will send — what you said, what you had selected and what Yappr pasted — and the button itself says whether your words go with it.

It is never automatic. A report exists because you read it and pressed Send. Nothing is gathered in the background, and there is no code path that sends one without that press. If that ever changes, this section changes with it.

Reports are deleted after 90 days. That is shorter than anything else on this page, and deliberately so: a report can contain what you said, which is more than an email address, and a bug that has not been found in ninety days will not be found from that row. A copy is also written on your Mac, in ~/Library/Application Support/Yappr/bug-reports/, which you can read or delete yourself at any time. That copy is written first, so a report is never lost to a failed send.

Wait times — how long each dictation took

Since version 0.1.29, the app records how long each dictation took and sends that to my database when you are signed in. It is the one thing collected without you pressing a button, so it is spelled out exactly. Each dictation sends: the total wait from releasing your key to the text appearing, how much of that was transcription and how much was the AI step, which kind of cleanup it went through, how many words it had, the name of the app it landed in (such as “Slack”), and the version of Yappr.

None of your words are in it — no text, no window title, no file name. The table it goes into has no column that could hold any. It exists so I can see when someone is waiting unusually long and fix it, without asking them for their log files. It is deleted after 90 days, on the same schedule as bug reports, and it is sent only after the text is already on your screen, so it never adds to the wait it measures.

The audio is unchanged by any of this: it is transcribed on your Mac and is never uploaded. There is no third-party analytics in the app and no third-party crash reporter, and nothing about what you dictate is collected in the background — only the timings above and the things below. A bug report is different again: you write it, you read it, and you decide whether it is sent.

Errors — when the app breaks

Since version 0.1.46, when the app crashes or hits an error while you are signed in, it sends a short report of the error to my database, so I can fix problems people never write in about. Each report holds: what kind of error it was (a crash, an error the app caught, a window that stopped), which part of the app it came from, the first line of the error message, the place in Yappr’s own code where it happened, and the version of Yappr.

Before it is sent, the message is cut to its first line and cleaned: your home folder is replaced with “~”, and email addresses, web-address queries, long numbers and any long quoted text are removed, because those are where your words or details could ride along. None of your dictations are in it. The same error is sent at most once every ten minutes and no more than 40 a day. It goes to my own database, not to an error-tracking company, and it is deleted after 90 days.

Yappr Agents — which buttons you used

If you use Yappr Agents (the notch that shows your coding agents and lets you answer them), the app records what you did, not what was said: that a card appeared, that you answered it from the notch by picking one of its choices, that a card folded away unanswered, that you allowed or denied a permission (or it was handed back to the agent), that you dictated a reply to an agent session, asked for a goal by voice, or turned on do-not-disturb — with how long a card took to be answered and the version of Yappr.

Never the question, your answer, the session’s name, its folder or a command. The table it goes into has no column that could hold any. It exists so I can see whether the feature is actually used. It is sent only while you are signed in and deleted after 90 days.

Your apps on the notch are counted the same way: which kind of card it was (a deploy, a pull request, Stripe, the morning brief…), that it appeared, that you opened it, or that you acted on it (Fix with Claude, a link, a reply), and once a day which of those apps you have connected. Never a project, a deploy, an amount, an email, a name or a link. Same table, same 90 days.

Setting Yappr up

Even before you sign in, a new copy of Yappr tells my database three moments, each once: that it was opened for the first time, that it reached the account screen, and that an account was made — with a random number made for that copy, the version of Yappr and, on the last one only, your account, which ties the three to it. After that, it tells the name of each setup screen you reach (Mic, Accessibility, First try, Finished and the like), each once, with the same random number. Nothing else: no text, nothing about your Mac. It is deleted after 90 days.

Videos from me

Yappr checks a short list of videos when it opens, a few times a day and after you dictate, and keeps one connection open so a new video can reach you right away. That connection carries nothing about you. A video drops down from the notch and plays there. If I uploaded it, its file comes from Yappr’s own storage, once, with your Yappr sign-in, so Supabase, which hosts it, sees that request like any other, and it stays on your Mac until I remove the video or you sign out. If it is a YouTube video, YouTube’s player loads only when you press Play; from then YouTube sees your IP address and its own privacy policy applies. When you press Play, and when you watch to the end, Yappr tells me, with your account. If you answer a video by voice and press Send, your words come to me with your account. Both are deleted after 90 days. A video I send only to you, or to a few people, is stored with your account, so that only the accounts I chose can read it, until I remove it or you delete your account.

Questions from me

Now and then I ask a short question in the notch. When you press Send, your answer comes to me with your account: what you picked and what you wrote or said. A spoken answer is cleaned up like any dictation. Answers are deleted after 90 days. Yappr checks for questions the same way as for videos. A question I send only to you, or to a few people, is stored with your account, so that only the accounts I chose can read it, until I remove it or you delete your account.

Sometimes, right after you use a feature, the notch asks one short question about it. If you tap an answer or hold your key and say one, it comes to me with your account, the feature it was about, and whether you tapped or spoke. "Not now" and "Stop asking" send nothing. You can turn these questions off on the card or in Settings → Notch. These answers are deleted after 90 days too.

8. What is stored on your Mac

All of it lives in the app’s support folder, ~/Library/Application Support/Yappr/. It is ordinary files on your disk, readable by anything running as your user account, protected by macOS file permissions and by FileVault if you have it on. The app does not encrypt these files itself.

  • yappr-history.json — your dictations. For each one: what was transcribed, what was pasted, the app name, the timestamp, and the project it belonged to, plus which of the pasted words were spelling corrections, and whether Yappr added a Claude Code keyword (ultrathink or ultracode) on its own, so the dashboard can show you what changed. For a browser tab it also records the site — mail.google.com, never the address of the page — so that a correction you make in the dashboard applies to that site. Capped at the most recent 1,000 entries; older ones are dropped as new ones arrive.
  • yappr-app-actions.json — what you asked “Hey Yappr” to do with an app, so the dashboard can show it: your words, which app, when, what happened (“Added to Calendar”) and a link to that app. Nothing read from the app itself, such as an email or a payment, is kept. At most 200 entries.
  • context.db — an SQLite database holding your remembered facts and the overview paragraph. It holds only what you supplied, and is read while context memory is on.
  • yappr-stats.json — counts and durations used for the dashboard. No dictation text. Not pruned, so it covers all time without keeping what you said.
  • yappr-recording-ledger.json — when each recording in the last hour ended and how long it ran, which is how the app knows whether you are inside the 60 minutes of speech an hour that cleanup covers. Two numbers per recording and no text. Entries older than an hour are dropped each time it is written, so it never holds more than that.
  • yappr-settings.json — your settings, including your dictionary, your per-app rules, and any API credential the app has been given. Stored as plain JSON; the credential is not encrypted or held in the macOS Keychain. If you opened an invite link, the friend’s code from it is kept here too, until you use it or clear it from its box. It also keeps the names Yappr learned from your screen (a name it corrected in two dictations, shown under Settings → You, where you can remove each) and the names it has corrected once. They stay on your Mac and are never sent.
  • recordings/ — the audio of dictations, written before processing and deleted once the text has landed. Files that failed to process are kept so they can be retried, and are pruned to the 20 most recent and to 7 days, whichever is stricter.
  • yappr.log — a diagnostic log. It records timings, lengths, app names, error messages and short previews of dictated text. Credentials and licence keys are scrubbed from it before it is written, by name and by value shape. The log stays on your machine unless you send it for support, at which point you are sending its contents.

The speech model file itself is also downloaded to your Mac. It contains no data about you.

9. What you can delete, and how

  • Dictation history: Settings → Dashboard → Clear all. This empties yappr-history.json and yappr-app-actions.json.
  • Remembered facts: Settings → You, both for what is about you and for each project. Individual facts and whole project groups can be deleted, and the overview paragraph can be edited or replaced.
  • Stop sending context entirely: turn context memory off in Settings → You. It is on by default and sends nothing until you have supplied something. It stays off until you add something new, which switches it back on.
  • Connected apps: turn off Talk to your apps in Settings → Apps to stop using them. To remove a sign-in, use Disconnect in Settings → Apps. It deletes the sign-in at Composio and asks Composio to revoke its access. To be sure, check your Google or Microsoft account, or Stripe, Vercel, GitHub or Supabase, and remove any access still listed there. Disconnecting stops new requests; what Composio has already logged can stay there for up to one year from each call.
  • Everything, at once: quit Yappr and delete ~/Library/Application Support/Yappr/. That removes history, facts, statistics, settings, stored audio and logs. The app starts fresh.
  • The account, and everything held off your Mac: write to useyappr@gmail.com and ask. That is your email address, your plan state and when your Pro time ends, your invite code and referral records, the per-minute, per-day and per-week COUNTS of how often cleanup ran, and the running word total — there is no dictation text in any of it. It is deleted by hand, within a month, and there is no self-service button for it yet; saying so is more honest than implying otherwise.
  • Product news: the unsubscribe link at the bottom of any of those emails, or the switch in Settings → Account. Either works at once — see section 15.
  • Stop it listening or typing: revoke Microphone or Accessibility access in System Settings → Privacy & Security. The app cannot record or paste without them.

Text already sent to Groq is not mine to delete. Deleting your local history does not reach back into their systems.

One control that does not exist today: there is no switch that keeps dictation working while stopping the cleanup step. One existed, it was removed in a Settings redesign, and the stored value is reset when the app loads. If it comes back, this section and section 12 change with it.

10. Legal bases for processing (GDPR)

A legal basis presupposes a controller. For the files on your Mac, that is genuinely doubtful — I never receive them, never see them and cannot act on them; it is your machine and your copy. For the request that leaves your Mac it is much clearer: the software I wrote decides that the transcript is sent, what travels with it, and where it goes, so I treat that as processing I answer for. The list below is written on that reading. It has not been reviewed by a lawyer, and the reading itself is one of the things a review would test.

  • Talk to your apps — what you ask for and what the app returns. Basis: Article 6(1)(b), performance of a contract. You ask, and this is how the answer reaches you. For the other people named in your email, calendar or payments, the basis is Article 6(1)(f), legitimate interests: you are handling your own correspondence and records.
  • Running a dictation — the transcript, the app name and category, the instructions the app writes, and, on a rewrite, the text you had selected. Basis: Article 6(1)(b), performance of a contract. You press the hotkey to get text back; sending it for cleanup is how the feature you invoked works, and the feature cannot be delivered without it. If it were held that no contract exists while the app is free, the fallback basis would be Article 6(1)(f), legitimate interests — delivering the function you asked for at the moment you asked for it, which is also the least surprising possible use of it.
  • Storing your data on your Mac — history, remembered facts, statistics, settings, recent audio, the log. Basis, to the extent this is processing I carry out at all: Article 6(1)(b). History, retry-on-failure and your dictionary are features that cannot work without a file. None of it leaves your machine, and you can delete any of it at any time — section 9.
  • Context memory — remembered facts, the overview paragraph, and your account email alongside them. Basis: Article 6(1)(a), consent. The switch is on by default, but nothing about it happens until you supply something: every sentence in it is one you typed, pasted or imported for this purpose — during setup, on a screen that says it goes along with your dictations, or in Settings → You, where the switch that controls it lives. Supplying it is the affirmative act, each time — adding context after you had switched it off switches it back on — and a switch that is on with nothing behind it sends nothing. Consent is the right basis because the feature is optional — the app works without it, so it cannot be “necessary” for the contract. Turning it off, or deleting what you supplied, withdraws consent for the future; it does not reach back into what has already been sent.
  • Product news by email — your email address, and your answer with its date. Basis: Article 6(1)(a), consent, which is also what Spanish law requires before any commercial email (LSSI-CE, Article 21). You are asked; it is never a condition of the account and never ticked for you, and unsubscribing withdraws it for every email after — section 15.
  • Downloading the speech model — your IP address reaches the model host. Basis: Article 6(1)(b). The app cannot transcribe anything until the model is on disk.
  • The trial and invites — your invite code, who referred whom, and your running word total. Basis: Article 6(1)(b). The trial and the invite rewards are terms you agreed to (Terms, section 9b), and paying a reward means knowing whose code was entered and whether the 1,000 words have been reached.
  • An invitation to a friend — the address a founding member types, and a scrambled copy of it kept afterwards. Basis: Article 6(1)(f), legitimate interests: letting someone tell a friend about Yappr, limited to one email per address and kept to what stops a second one. See section 15.
  • Nudges about an invite — since November 2026. If you joined with a friend’s invite and have dictated under 1,000 words after three days, the friend sees that one of their friends is behind (a number, never who) and may nudge you: your notch then shows their first name, kept for a month with when you saw it. We also send you one reminder, once ever, on the notch and by email, with the same opt-out link as the invite. Basis: Article 6(1)(f), the same interest as the invitation, limited to one reminder.
  • Your address on the invite list of the friend whose code you entered — only if the box told you so as you entered it. Basis: Article 6(1)(f), legitimate interests: letting someone see which friends took them up, limited to the address alone and told to you first. See section 15.

Special category data. Dictation is open-ended: you can say anything into it, including things Article 9 treats as special category — health, beliefs, and the rest. The software cannot detect that and has no separate handling for it. I do not seek it, and no Article 9 condition is claimed for it. In practice the only reliable control is yours: if it is something you would not paste into a third-party service, do not dictate it.

Automated decision-making. Cleanup is automated text processing and it changes your words — that is the product. But there is no automated decision-making about you in the Article 22 sense: nothing here produces a legal effect concerning you or similarly significantly affects you, and no profiling is used to decide anything about you.

11. International transfers

The database holding your account is in the United States, and so is every company involved in cleanup. Until 11 September 2026 this section named only the routing service and the model companies, which described the transfer as something that happens while a dictation is in flight. That was incomplete in the direction that mattered: your email address and the hashed form of your password are stored in the United States, continuously, whether or not you ever dictate anything.

Specifically, the database and the server that runs cleanup are hosted in US East (Ohio). That is a choice about where the project was created rather than anything about you, and it is being reconsidered — but a policy that describes an intention rather than the current setup is worth nothing, so what is written here is where your data is today.

On top of that, every time cleanup runs, the transcript and what travels with it leave the EEA. There is no way to use the cleanup feature without that transfer happening; the only way to avoid it is not to use the feature.

Because the routing service can fall through to a different provider when the first is unavailable, the specific company receiving a given request is not fixed in advance — see section 5. The destination country is: it is the United States either way.

The mechanism is the EU Standard Contractual Clauses, and they are in force for every leg of this. Checked on 11 September 2026, by reading each company’s published addendum rather than assuming one existed:

  • The database and the server (Supabase). Its data processing addendum forms part of its terms of service, and states that accepting the agreement “shall have the same effect as signing the SCCs”. Module Two, controller to processor.
  • The routing service (OpenRouter). Its addendum is incorporated into its terms and takes effect when the customer accepts them, entering the parties into Module Two of the Standard Contractual Clauses by reference.
  • Email (Resend: founding invitations since 4 November 2026; product news since 21 October 2026, and every other email Yappr sends since this page’s date). Its addendum binds on accepting its terms, carries the 2021 Clauses for transfers from the EEA, and was read on 21 October 2026.
  • This website (Vercel). Its addendum becomes binding on entering the agreement, and carries the 2021 Clauses for EEA, UK and Swiss transfers.

None of these needed to be separately signed, which is worth saying because it is the opposite of what this page implied for five days. The companies running the models sit behind the routing service as its own subprocessors, and its addendum is what obliges it to hold them to equivalent terms.

Two download hosts are not in that list. GitHub, which serves the installer and the update feed, and Hugging Face, which serves the speech model, both receive your IP address and request headers when a file is fetched from them — see section 5. Both are United States companies, so that is a transfer too. Their addenda have not yet been read against this page the way the three above were, so no mechanism is claimed for them here; nothing you dictate ever reaches either.

Composio is reached only if you turn on Talk to your apps. Its addendum was read and accepted on 4 November 2026. Accepting it enters both parties into the Standard Contractual Clauses, Module Two, controller to processor, with no separate signature.

Two honest limits on the above. First, this is a careful reading of published documents on a stated date, not a lawyer’s opinion that the Clauses cover this exact shape of processing — that is a real distinction and it is why the date is given. Second, Standard Contractual Clauses are a contractual mechanism: they bind the companies involved, and they are the answer the law asks for, but they cannot bind a government. No adequacy decision and no Data Privacy Framework certification is being relied on here, and none is asserted.

Until 11 September 2026 this section said two things that were wrong. It said the request was made from your Mac with a credential held on your Mac and that no Yappr server was involved — which stopped being true on 7 September, when cleanup moved behind a server of mine. And it said the transfer mechanism had not been established, when in fact nobody had looked. Both are corrected here rather than quietly replaced, because a privacy policy that has been wrong should say where.

12. Your rights under the GDPR

If the GDPR applies to you, you have the rights below. Their shape here is unusual: because nothing reaches me, most of them are exercised on your own machine, immediately, without asking anyone.

  • Access (Article 15) — I hold no copy of anything you dictate, so there is nothing on my side to send you. Everything the app keeps is in ~/Library/Application Support/Yappr/ and you can open it right now; section 8 says what each file is.
  • Rectification (Article 16) — remembered facts are editable and deletable in Settings → You, and the overview paragraph can be edited or replaced.
  • Erasure (Article 17) — section 9. Deleting the support folder erases everything the app holds. Text already sent to Groq is not mine to erase; a request about it goes to Groq. What Composio has logged for Talk to your apps I cannot remove myself: tell me and I will pass your request to Composio, and those logs delete by themselves within a year of each call.
  • Restriction (Article 18) — turning context memory off stops that category of processing, and revoking Microphone or Accessibility access in System Settings stops the app functioning at all without deleting anything. Note the gap flagged in section 9: there is no setting that keeps dictation running while suppressing the cleanup call.
  • Portability (Article 20) — history is JSON, settings are JSON, remembered facts are SQLite. They are already machine-readable files on your disk, yours to copy or move.
  • Objection (Article 21) — where legitimate interests are relied on as the fallback basis in section 10, you can object. The controls above give effect to an objection immediately, which is faster than any process I could run.
  • Withdrawing consent (Article 7(3)) — turn context memory off. Withdrawal takes effect for the future and does not affect the lawfulness of what was sent while it was on.
  • Complaint to a supervisory authority (Article 77) — you can complain to the Agencia Española de Protección de Datos (AEPD), the Spanish authority, at www.aepd.es. If you live or work in another EU or EEA country, you may complain to your own national data protection authority instead — you do not have to come to Spain to do it.

A request that has to come to me goes to the address in section 17. It is published, a person reads it, and the answer comes within one month.

13. If you are in California (CCPA/CPRA)

Categories of personal information the software handles.

  • Identifiers — the email address you sign in with, and your invite code. (This line described a Settings field for an email address that was removed on 13 September 2026; the account address is the only one now.)
  • Audio information — your recorded voice. It stays on your Mac; transcription runs there and the audio is not uploaded.
  • The contents of your communications — what you dictate, and any text you select for a rewrite. Sent to Groq when cleanup runs. Under the CPRA the contents of a consumer’s communications, where the business is not the intended recipient, are treated as sensitive personal information, so that is what this is.
  • Electronic network activity — the name and category of the app you are dictating into. Not your browsing history: the URL and the window title are read on your Mac and are not transmitted, apart from up to 8 names in them that sound like something you said (section 4). The app’s name is also stored, with how long each dictation took, for 90 days — see section 7. So are short error reports and which Yappr Agents buttons and app cards you used, and the three setup moments, for 90 days.
  • Inferences — none. The app draws no conclusions about you. The overview paragraph and the remembered facts are text you wrote or pasted yourself; a model wrote the paragraph until 10 September 2026 and mined the facts until 11 September 2026, and both are removed. What is stored is stored on your Mac.

Sources: you, and the software running on your device. There are no data brokers, no purchased lists and no third-party enrichment. Purpose: producing the text you asked for. That is the only purpose. Retention: of what passes through my server while you dictate, I retain nothing — only counts, on the schedule in section 7, and how long each dictation took, error reports and Yappr Agents events and setup moments, each kept for 90 days. The one exception is a bug report you choose to send, kept for 90 days and described in section 7; how long the local files live is section 8; Groq’s retention is Groq’s to state, in the documents linked in section 5.

Personal information is not sold and it is not shared. I do not sell personal information, and I do not share it for cross-context behavioural advertising, as the CCPA and CPRA define those terms. There is no advertising, no ad network and no data broker anywhere in this product, and the website’s visit counts (above) are used only by me, to see how many people visit. That is why there is no “Do Not Sell or Share My Personal Information” link — not because one has been withheld, but because there is nothing for it to switch off. Sensitive personal information is used only to deliver the feature you invoked, and not to infer characteristics about you.

Your rights. To know what is collected and to access it; to delete it; to correct it; to opt out of sale or sharing; to limit the use of sensitive personal information; and not to be discriminated against for exercising any of them. In practice the first three are section 9, and you can act on them without me. The fourth has nothing to apply to. There are accounts and plans, but nothing about your plan, your trial or a price changes because you asked for any of this, so non-discrimination costs nothing to honour. Anything that does need to reach a person goes to section 17, which is published.

14. Children

Yappr is for people aged 16 and over. It is not designed for or directed at children, and nothing is knowingly collected from one.

Sixteen is a deliberate single number rather than a per-country one. COPPA sets 13 in the United States, GDPR Article 8 lets each member state set anything from 13 to 16, and the UK Age Appropriate Design Code adds its own expectations. Sixteen is the highest of those, so one figure satisfies all of them and the app needs no idea where you are.

What enforces it: the sign-up screen carries a checkbox, unticked by default, confirming you are 16 or over, and the account cannot be created without it. That is a statement you make, not a document you produce — and it is chosen over a real age gate on purpose. Verifying an age means collecting a date of birth from every user in order to screen out a few: more personal data held, another retention period to publish, and a worse outcome under data minimisation than the problem it solves.

If you believe someone under 16 has an account, write to me and I will delete it and everything attached to it.

15. Accounts

There is an account. You sign in with your email address and a password, and the session that results is what proves to my server that a request is yours. There is no third-party login and no “sign in with” button.

So a hashed form of your password is stored, alongside your email address. Both live in the authentication system Supabase provides. The password is hashed, meaning the stored value cannot be turned back into what you typed, and I never see the password itself. Until 10 September 2026 this page described a different sign-in method entirely — an emailed six-digit code — and stated there was no password to choose. That was wrong. An emailed sign-in code still exists as a second way in — it is how you get back into your account if you forget your password, and you can then choose a new one — but the password is what every account actually uses, and a stored credential is not something a privacy notice may leave out.

The account record itself holds your email address, which plan you are on and when your Pro time ends, your invite code, the running word total, your answer about product news (below), and the usage counters described in section 7. It does not hold anything you have dictated.

Product news

Since 30 September 2026 Yappr asks whether you want product news — an email when something new ships, at most once a week. It is opt-in: one question when you set up a new account, right after you sign in (two buttons of the same size, and nothing is chosen for you; leaving without pressing either saves nothing), one question in the app after an update (two buttons, “No thanks” as easy as “Yes”, asked at most twice in all), and a switch in Settings → Account you can change at any time. Saying no, or not answering, costs you nothing: the app works exactly the same.

What is stored with your answer: yes or no, the date and time it reached my server, where you gave it (the sign-up form, the question, the Settings switch, or an unsubscribe link), and which version of the wording you were shown — so that I can show what you agreed to, which the law asks me to be able to do. Each change is kept as its own line, so the history is there too. All of it lives with your account and is deleted with it.

Leaving is one click. Every product-news email has an unsubscribe link that works without signing in, and your mail app’s own Unsubscribe button works too. The link carries a random code that can do one thing — stop product news to your account — and the page says you are unsubscribed whatever the code was, so it tells nobody anything about an account.

What is not product news, and arrives whatever you answered: sign-in codes and email confirmations, your trial ending, billing and receipts, and the notice before a change described in section 16. Those are about the service you use, not marketing.

None has been sent yet. Product news is sent through Resend, named in section 5. Before the first one, everyone who said yes gets a short email from me saying so, as section 16 promises for a new recipient. Each product-news email goes to one person, with that person’s own unsubscribe link, and records neither opens nor clicks.

Invites and referrals

Since 27 September 2026 every account has an invite code, and a new account can enter someone else’s. What that stores, all of it in the database described in section 5:

  • Your invite code — a short random string made when your account is created. It identifies your account to someone you give it to, and to nobody else.
  • Who referred whom. If you enter a code, a record that your account was referred by that one, when, whether it has counted yet, and how many days it earned them.
  • A running total of words — how many words have been cleaned up for your account, ever. One number, never the words themselves, taken from the count in section 7. It is used for one thing: deciding whether you have reached the 1,000 words that make an invite count. It is counted for every account, including ones that never use an invite, because a code can still be entered up to 7 days after signing up and the words before that have to count too.

If the box where you typed the code said “The friend who invited you will see your email address.”, the person whose code you entered sees your email address, as your account holds it, in a list on their “Invite a friend” card. Nothing else about you sits beside it: not your word count, not whether you have counted, and not the days you earned them.

If you entered a code without that line on screen — every code entered before it was added — they see you only in their totals: how many people joined with their code, how many of those have counted, and how many days they have earned. Your address is never shown to them. One honest limit, for everyone: someone who has invited a single friend can tell from “1 counted” that that friend passed the line. Whether any one friend counted is shown nowhere else.

All of it is kept for as long as your account exists and deleted with it. Deleting either account deletes the referral record between the two; days already added to the other account stay added.

An invite link on this website (/r/ followed by a code) is an ordinary page: it shows the code and a download button, and it stores nothing and sends the code nowhere. Opening it reaches the website’s host like any page load, address included — see section 5.

If someone invited you, and what a founding member’s invitation does

Since 4 November 2026 a founding member can type a friend’s address and Yappr sends that friend one invitation, in the member’s name, with replies going to the member. If you got one, your address came from them, not from a list.

  • What happens to the address. It reaches my server and Resend (section 5) only to send that one email, which goes out through Resend’s Ireland region. Resend is a United States company, so section 11 still applies. Before it is sent, the member’s Mac asks its usual internet name service whether the part after the @ takes email; nothing about that is kept. I do not store the address. I keep a scrambled copy (a keyed hash), with who sent it and when, so you are not emailed again for 12 months; it is then deleted. Resend keeps the address in its own email logs for its usual period. Nothing is added to any list, and you get no reminder.
  • How to stop it. The link at the bottom of the email stops invitations to that address from anyone on Yappr, signed out, in one click. I then keep the scrambled copy for as long as it takes to honour that.
  • What the member sees. Never whether you opened it or already have an account, and Yappr does not record whether an email is opened. If you sign up and enter their code, the box tells you they will see your email address, and they do (above); otherwise they see totals only. The email shows one picture, loaded from this site; it is the same file in every invitation, so loading it does not tell me who opened it.
  • Your rights under section 12 apply. Write to me and I will remove the scrambled copy; that also removes what stops a second email, unless you have opted out.

Since 13 October 2026 that page also has a link that opens Yappr on your Mac with the code filled in. Clicking it hands the code from your browser to the app on the same Mac and to nobody else. The app keeps it in its settings file (section 8) and shows it in the box where a friend’s code goes; it is sent to the server only when you sign in with it there or press Add, exactly as a code you typed would be. Clear the box and it is gone. The app does not read your clipboard to find a code.

The waitlist, and the invite list

The beta was closed until 27 September 2026. Sign-up is open now. Two lists from the closed beta hold an email address and nothing else. Until 11 September 2026 this policy did not mention either of them — a real omission, because one was filled in by a form on the front page of this site.

The waitlist. Until sign-up opened, the home page had a form for your email address, stored so that I could tell you when you could get in, with a short tag recording where the signup came from. Nothing else. The form is gone; the addresses already on the list stay, under the deletion below. The list cannot be read back by anyone holding the key that ships in the website; reading it requires a credential that never leaves the server.

The invite list. While the beta was closed, signup was refused for any address I had not invited, and this list held those addresses — including people who never signed up. It is kept now only as a switch: if sign-up is ever closed again, it is what decides who may still create an account. While sign-up is open it is not consulted.

Both are deleted after six months, on a schedule, not by hand — the same promise as before sign-up opened. An address that has sat on the waitlist for six months is not a warm lead, and an invitation nobody used in six months has been declined rather than left pending.

16. Changes to this policy

This page carries the date it was last changed at the top, and where a change to the app changes what leaves your machine, this page changes in the same release rather than afterwards.

For a change that widens what leaves your machine, or that adds a recipient, you get an email before it takes effect. Not for a typo or a clarification — for those, the date at the top is the signal. The distinction is the point: a dated page nobody revisits is adequate notice for a rewording and useless for “your words now also go to a company you have not heard of”.

One exception: Composio, added with Talk to your apps, was announced on this page and not by email. It receives nothing unless you turn that on.

A second: showing a friend’s email address to the person who invited them (section 15) was announced on this page and not by email. It applies only to someone told so in the box where they enter a code, never to a code entered before.

Until 10 September 2026 this section said there was no way to notify you, because there were no accounts and so no addresses. There are both now — section 15 says so on this same page — and this paragraph had simply been left behind.

Another exception: founding invitations (section 15), added on 4 November 2026, were announced on this page and not by email.

17. Contact

For anything on this page — a question, or any of the rights in section 12 or section 13 — write to useyappr@gmail.com. A person reads it.

You will get an answer within one month. That is the deadline the GDPR sets and I am not going to quote you a shorter one I might miss. Requests are handled by hand: there is no self-service export or delete button in the app yet, and rather than imply there is, this says plainly that you email and I do it. If a request is complex enough to need longer, the law lets me extend it by two months and requires me to tell you why — so I will.

For formal notice, there is a postal address — the controller’s name and address are published in section 1. Email is faster and is the right route for an ordinary request; the address is there because Article 13 expects a controller to be reachable by post, and an email address on its own is not that.