Your voice, and your clipboard, stay on your Mac.

This policy applies to Koemoji (the "App"), provided by the Company, and to the Koemoji website (koemoji.jp), which the Company operates. The App is distributed in two editions: the one downloaded from this website (the "direct download") and the one provided through the Mac App Store (the "Mac App Store edition"). Differences in features mean data handling differs in places; where it does, this policy names the edition. Data handling in the App is different from data handling on the website and through the contact form, so they are described separately below.

We do not collect personal data through the App.

• There is no account and no sign-in.
• We do not run advertising, analytics, or tracking. The App has no mechanism for sending usage statistics or crash reports to us.
• We do not collect identifiers tied to your hardware (serial number, hardware UUID, MAC address, or similar).
• Neither the audio you record nor the recognized text is sent to our servers. We have no mechanism for receiving your data at all (see Section 3 for what happens if you configure an external service yourself).
• Clipboard history, sticky notes, and favorites you record or save are likewise never sent to our servers (see Section 5 for what happens if you turn on AI Access).
• The Mac App Store edition has no network entitlement at all. Because it has no feature that communicates externally, sending data out is not technically possible.

This "we do not collect data" statement is about the App. For what we receive when you use the contact form on our website, see Section 9.

Speech recognition and text formatting both run entirely on your Mac. Recorded audio is never sent outside the App by either edition.

The Mac App Store edition has no network entitlement, so it has no feature that communicates externally at all. It uses Apple Speech for recognition and Apple's Foundation Models for text formatting, both running on your Mac. It does not use external APIs, Whisper, automatic updates, or direct keystroke insertion through Accessibility. The recognized text is copied to the clipboard, and you paste it into the app of your choice; how that clipboard content is then handled also follows macOS's own settings and the destination app's own behavior. The Mac App Store edition also has the same clipboard history, sticky notes, and favorites features as the direct download — see Section 4. The current Mac App Store edition does not perform translation.

Used with its default settings, the direct download also keeps your data from leaving your Mac. It uses Apple Speech (macOS 26 or later) or an on-device Whisper model for recognition. If you choose Whisper, the recognition model file is fetched from Hugging Face — that request only downloads the model and never sends your data. Translation runs entirely on your Mac through macOS's own translation feature. Recognized text is typed directly into the app in front, using the Accessibility permission you grant.

The only communication the direct download performs automatically is a single update check: it fetches our update-manifest file (koemoji.jp) after launch and every 24 hours after that. All it asks is which version is current — it does not send your data, the version you are running, or any device identifier, and it does not use cookies. You can turn this check off in Settings.

For text formatting, the direct download alone lets you point it at an external service you provide yourself, such as an OpenAI-compatible API. This only takes effect once you enter both a URL and credentials; both fields start empty, so nothing is sent unless you configure it. If you do, the destination is the provider you chose, not us — we do not operate a general-purpose server for this, and we never receive what is sent.

Clipboard history records the text, images, and files you copy. The direct download records from the first launch. The Mac App Store edition records nothing until you turn recording on; the setup assistant asks you when you first open the app. What it records is stored only on your Mac (inside the app's sandbox container in the Mac App Store edition, inside your home folder in the direct download) and is never sent to our servers. Text longer than 100KB is written out as a text file in the same storage area.

When the source app marks a copy as transient, concealed, or auto-generated — the convention password managers and similar apps use (the nspasteboard.org convention) — Koemoji does not record it, whether it is text, an image, or a file.

From the History and Privacy panes in Settings, or from the setup assistant you can open from the menu bar, you can exclude specific apps from recording (or, the other way around, record only the apps you list), pause and resume recording, skip just the next copy, cap how many entries or how long they are kept, and delete all history, optionally including your favorites. While recording is paused, neither what you copy nor the results of voice dictation are added to history.

Text inside a copied image is recognized on your Mac using Apple's Vision text-recognition feature, so image copies become searchable. This recognition also never leaves your Mac and is never sent to us (it is unavailable on Intel Macs, because of the processing cost).

Transcripts you keep on screen as sticky notes, and anything you save as a favorite, are stored the same way — only on your Mac, alongside your clipboard history.

The direct download has a setting that lets an AI tool you connect on the same Mac — over MCP, for example — read Koemoji's clipboard history. It is off by default. Even when turned on, the connection is confined to communication that stays entirely on your Mac (a Unix domain socket) and never touches the network. Whether a connected AI tool may write back to the clipboard, change favorites, or delete history entries can each be allowed or denied separately.

When an AI tool reads your history, text that looks like a secret — a password or an API key, for example — is automatically detected by default and returned masked. Seeing the actual value requires answering a confirmation prompt in Koemoji each time; an approval is good for a single disclosure and expires after 60 seconds.

This feature does not involve us receiving your data or providing it to a third party. Koemoji itself never sends history contents anywhere; what a connected AI tool then does with what it reads — including whether it sends it on to an external AI service — is governed by that tool's own policies and its provider's.

The Mac App Store edition does not have this feature.

The App asks for microphone access to convert speech to text. The microphone is used only while you are recording.

Recordings are stored on your device temporarily for processing and deleted afterward. The App's settings, replacement dictionary, prompts, and operation log are all stored only on your Mac and are never sent to us. They live inside the App's sandbox container in the Mac App Store edition, and inside your home folder (preference files, a settings directory, and log files) in the direct download. The recognized text is used for the dictation itself (copied to the clipboard in the Mac App Store edition, entered into the frontmost app in the direct download). While clipboard history recording is on, it is also saved to the history, and when you use sticky notes, as a sticky note, in both cases only on your Mac (see Section 4).

Only if you explicitly turn on advanced diagnostic logging does recognized text get written to an on-device log, with recordings kept for up to about an hour. This information also stays on your device and is never sent to us. You can reset your settings from the App's own reset feature, and remove logs and other stored information by deleting the App's data from your Mac.

The App calls on macOS features for speech recognition and text formatting. The direct download also uses macOS's own translation feature for translation. macOS may fetch language data or models it needs to do this, but we never receive your recorded audio or typed text through this. For how Apple handles data, including through the App Store, see Apple's privacy policy.

Apple's Privacy Policy

Our website uses Cloudflare for delivery and security. Cloudflare may process data such as your connection's IP address. See Cloudflare's privacy policy for details.

Our web server (Caddy) keeps access logs with identifying information removed, retaining only the operational information needed to investigate problems and confirm the site is running. We do not use advertising, cross-site tracking technology, or per-visitor analytics on our website.

Cloudflare's Privacy Policy

Using the contact form sends your name, the type of inquiry, your reply-to email address, any company or organization name you choose to enter, and your message directly to a server we operate. Cloudflare Turnstile verifies the submission to guard against abuse.

We use this information to reply to you, investigate issues, keep a record of how we handled your request, and prevent and respond to disputes.

We delete contact data we hold within one year of the date we last acted on it, as a rule. Where the law requires us to keep it longer, or a dispute makes it necessary, we keep it only as long as that requires. You can ask us to delete contact data we hold about you by reaching us through the contact in Section 12, except where a legal requirement or a legitimate business reason means we cannot.

Cloudflare's Privacy Policy

We let subcontractors such as Cloudflare handle information only to the extent each service requires. Beyond that, we do not disclose contact data to third parties without consent, except where the law requires it, or where it is necessary to protect someone's life, body, or property and obtaining consent is impracticable.

We may update this policy when the App, the website, or how we handle data changes. Where a change is significant, we will let you know in a way suited to what changed. Updates are posted on this page with a new last-updated date.

For questions about this policy, or about the contact data we hold, please reach us through our contact page.