Keyphony Privacy Policy

Jinian Company provides Keyphony. This policy explains how the native Mac app handles input and local preferences, and what happens when you contact us. Contact: [email protected].

Effective: October 10, 2026 (UTC). Last updated: October 11, 2026 (UTC). Scope: native Keyphony 1.0 for Mac. This policy describes the app’s input handling, local preferences and support flow. Publication of this policy does not announce Mac App Store availability.

Keyboard input

Inside Keyphony, physical key events trigger sound and visual reactions. Its sound pad handles physical key events without interpreting typed characters. Editable settings fields use normal macOS text input; saved combination names are local preferences, not a keystroke history.

Monitoring typing in other apps is optional. The app uses your selected-apps or all-apps scope and explicitly saved external On/Off choice. A saved On choice may be restored after a normal quit and restart only when macOS Input Monitoring permission and safety conditions allow it. An initial permission wait can preserve the On choice while external input remains stopped; permission revocation or a safety stop after activation can switch it Off. The app checks the foreground app’s identifier to apply that choice, then uses physical key codes, press/release state, repeat state and modifiers for sound playback. Temporary held-key and modifier state is kept in memory during use.

The reviewed implementation does not save typed text or a keystroke history, extract text from other apps, or send those input events to the developer. It does not read clipboard contents. The external observer returns original keyboard events unchanged.

External monitoring stops when Secure Input is detected, permission is revoked, or observation is interrupted. These checks cannot identify every password field. Switch sound Off before entering sensitive information. Revoke Input Monitoring in System Settings to stop access to other apps’ typing.

Local settings and files

The app stores preferences and saved combinations on your Mac in its application-support storage. These can include sound and volume choices, the external typing scope and On/Off choice, audio and visual preferences, language, combination names, selected output-device identifiers, selected-app bundle identifiers and per-app sound preferences. These preferences are separate from typing history. App names, icons and paths used to display the app picker are temporary presentation information; the allowed-app list stores selected bundle identifiers.

JSON import and export read or write the file you choose. Exported files can contain your combination names and preferences, so review them before sharing. Keyphony does not upload these files. Files remain until you change or remove them; the reviewed app has no automatic expiry for local preferences.

You can remove saved combinations in the app. “Delete this app’s saved combinations” clears its combination store; it does not promise to erase every category of app preference or any exported JSON file. Other preferences and permission choices may remain. Contact support for help locating remaining app data before removing files manually.

Network, analytics and SDKs

The reviewed native app source and Release inventory contain no developer-server client, advertising or analytics SDK, or external Swift package dependency. No app-owned route for uploading input, preferences or usage diagnostics was identified. Normal keyboard-sound use does not require an account or a developer server. This is a description of the reviewed build, not a claim that every service on your Mac collects no data.

The app uses Apple system frameworks for its interface, graphics, audio and macOS integration. Its audio meter examines the app’s own output; it does not record microphone input. Local elapsed-time measurements support rendering and device refresh. Store transactions, downloads and any operating-system diagnostics you choose to share are handled by Apple under Apple’s privacy policy, separately from the app’s own processing.

If you contact support

The app’s Help and support link opens the public support page in your default browser; the page’s email link opens your configured email handler, and the app does not prepare a message, attach diagnostics or files, or send email.

When you email us, your email address, message and any information you choose to include reach our published Gmail support mailbox. We use that information to respond to and handle your request. Delivery and storage also involve the email providers; see Google’s privacy policy. Avoid sending sensitive input or unrelated personal files.

You can ask us about, or request deletion of, information you sent to support at [email protected]. Contact us to discuss the request and any records that must be retained. This policy does not promise a fixed retention period or deletion of an email provider’s backups.

This website is separate from the app

These Keyphony support and privacy pages do not load Google Analytics or the website’s analytics-consent script. Cloudflare hosts this website and receives requests needed to serve pages. In browser visits, the hosting layer also adds a Cloudflare Web Analytics beacon that sends page URLs, browser/operating-system information and page-performance measurements to Cloudflare. This website measurement is separate from the app and from the Google Analytics consent setting. See Cloudflare Web Analytics and Cloudflare’s privacy policy. Other parts of jiniancompany.dev use optional, consent-based Google Analytics as described in the separate website privacy notice (Korean). Website analytics choices do not enable analytics inside Keyphony.

Changes and questions

We will update this page if the app’s handling changes and show the updated date here. For questions about this policy or privacy requests, email [email protected]. The English text is the primary version; the Korean guide below explains the same practices.