keymere.

Privacy policy

Your keys stay with you.

Keymere is designed around local playback and local storage. Here is what that means in practice.

Updated 1 November 2026

Who is responsible

Keymere is published by Abid. For privacy questions or requests, contact mohdabidph@gmail.com.

Keyboard and mouse events

The Windows app receives key codes, key press/release events and mouse-button events and wheel deltas to trigger sounds and animate the visualizer. It does not build or upload a typing history, capture passwords, or send these events to a server. The browser playground handles events within its page.

The Typewriter is an explicit text editor: text you enter there is displayed on its paper and can be saved locally if draft autosave is enabled. This is separate from desktop input monitoring.

What stays on your device

Preferences, imported recording excerpts, sound selections, Keyfall best scores and enabled typewriter drafts are stored locally. The website uses browser storage, including localStorage and IndexedDB. The Windows app uses its local user profile. These stores are separate, so imports and preferences do not automatically sync between them.

Original audio files are not changed. Imports are decoded and cropped locally. Exporting a draft creates a file only when you choose to export it.

License activation

The Windows app sends your purchase key and a Keymere-specific hashed device identifier to Dodo Payments or the Keymere Gumroad activation API over HTTPS. Keys and verification times are stored together using Windows encrypted storage. The Gumroad device ledger is stored in a separate Cloudflare database and contains key hashes, device identifiers, a generic PC label and activation times; it does not store raw keys or desktop keystrokes. Licenses support three active PCs. Activation and periodic verification require internet access; previously verified licenses have up to three days of offline access. Explicit provider revocation or an ordinary refund disables access.

Website, purchases and support

The website uses Cloudflare Web Analytics to measure visits, page views, referring sites, country, browser and device type, and page-load performance. This helps us understand how the website is used and improve its performance. It does not send desktop keystrokes, imported recordings, typewriter drafts or purchase keys to analytics. Cloudflare describes its service as privacy-first and does not track people across its customers’ websites. See Cloudflare Web Analytics for details.

The Windows app has no analytics or advertising trackers. Keymere has no account system. The website host may also process ordinary request information such as IP addresses and browser details to deliver and secure the site.

When checkout links are enabled, purchases happen with the named external payment provider under its own privacy terms. Keymere does not collect full payment-card details. The publisher may receive purchase contact details, an order reference and payment status to deliver your purchase and handle refunds.

If you email support or submit a cashback claim, the publisher receives the information you send, including receipts, public post links and screenshots. Send only what is needed; never send passwords or full card details. Purchase and claim information is used for support, fulfillment, fraud prevention and applicable legal recordkeeping.

Your choices

You can remove imported packs in the sound library, disable or clear the typewriter draft, and clear browser site data. Clearing storage may permanently remove local imports and drafts; keep your originals. The Windows uninstaller preserves app data by default. Contact support for help removing the local profile.

You may request access to, correction of, or deletion of information you have sent to the publisher. Necessary transaction and legal records may need to be retained. Your local recordings cannot be retrieved remotely by the publisher.

Changes

This page will be updated if data practices change. A future feature that sends data off-device must be described here before it is introduced.