Chromic Audio Privacy Policy

한국어·English

Version: 0.3  |  Date: 2026-08-30  |  Effective date: 2026-08-30

This policy is written and verified based on the actual implementation of the Chromic Audio app (version 3.0.1) and its backend as of the publication date (verified 2026-08-30).

1. Operator / Developer

Operator: Klisten Inc (corporation) — the business registration number is not published

Contact: support@klisten.com  ·  Website: https://www.chromicaudio.com  ·  Privacy: https://www.chromicaudio.com/privacy  ·  Terms: https://www.chromicaudio.com/terms

2. Scope

This policy applies to personal information processed in connection with your use of the Chromic Audio app ("the App"). Most DSP (sound processing), music playback, and sound personalization features operate on-device.

3. Information We Process

We process information only to the extent necessary to provide the service. Account, authentication, and subscription/entitlement-related information may be transmitted to the relevant service providers and our backend. In contrast, local media content, microphone audio, and hearing-personalization profiles — i.e., all audio and hearing-related data — are not transmitted off the device.

3.1 Account Information (only when using account features)

  • Email address, unique user identifier, display name (if provided by the login provider)
  • Login providers: Google Sign-In (currently operational), Apple Sign-In (server setup to be verified), Kakao/Naver/Facebook (currently inactive)
  • Guest mode: the App can be used without an account

3.2 Subscription / Purchase Information

  • The App uses Google Play Billing. Payment, cancellation, and restoration of the subscription product (klisten_pro_subscription) are handled through your Google Play account.
  • Purchase tokens are processed transiently in the billing flow and are not transmitted to our server.

3.3 Local Media Access

  • Automatic media-library scan: With your explicit permission (e.g., READ_MEDIA_AUDIO), the App automatically indexes audio files only from the device media database and reads their listings and metadata (title, artist, album, duration) for playback. Automatic indexing is limited to audio files.
  • User-selected files (SAF): The App accesses only files you explicitly select through the system file picker. Access is limited to the selected file itself; the App does not copy or upload files and does not automatically read unselected files or folders.
  • Content accessed is used only for on-device playback and is not transmitted to any server.

3.4 Bluetooth / Device Information

  • The name of connected earphones/headphones is read on-device only for auto-applying presets. No transmission; no location linkage.

3.5 Microphone Use

  • The microphone permission (RECORD_AUDIO) is actually used only by ActiveTune (real measured response calibration).
  • WiseAudio's hearing-response test plays test tones through the device output and collects only your responses; it does not use the microphone.
  • Microphone audio (ActiveTune measurement) is processed transiently in device memory only; it is not stored or transmitted. If you deny the permission, only ActiveTune measurement is unavailable.

3.6 WiseAudio / ActiveTune / Musical Auto Data

  • WiseAudio: hearing-test responses and pre-test questions are processed transiently in memory (not stored or transmitted). The resulting personalized EQ is stored on-device only.
  • ActiveTune: measurement microphone input is not stored; only calibration state (flag, profile identifier) is stored on-device.
  • Musical Auto: analyzes and applies the current track and DSP state on-device only.

3.7 Analytics / Crash / Messaging Data

  • Firebase Analytics (Google LLC): collects app interaction information such as usage events and screen views, diagnostic information, and device identifiers (including the advertising ID) to improve service quality. The SDK initializes automatically, and collection may start on app launch regardless of sign-in status.
  • Firebase Crashlytics (Google LLC): collects app crash logs and diagnostic information to improve stability. The SDK initializes automatically.
  • Firebase Cloud Messaging (Google LLC): may issue a device-identifying messaging token; push notifications are not currently used.
  • Analytics and crash information is used only for service operation and quality improvement; it is not sold and is not used for serving third-party ads.
  • No advertising is displayed in the App (no third-party ad SDKs).

4. Transmission Summary

TypeDetails
TransmittedAccount authentication information (email/ID/tokens) to login providers and backend; subscription-status lookups; Google Play billing interface; app analytics, crash, and diagnostic information (Section 3.7) to Firebase (Google LLC)
Not transmittedAudio data, raw microphone audio, hearing-test responses, hearing questionnaire answers, personalized EQ/profile, presets, Bluetooth device names, local media files

5. Third-Party Processors

ProcessorPurposeData Transmitted
Google LLC (Google Play / Google Sign-In)Subscription payment/restore/cancel; loginPurchase information; Google account identification (when chosen by you)
SupabaseAccount/subscription storage & lookupEmail, user ID, subscription status
Firebase (Google LLC)App analytics, crash reporting, messaging tokens (auto-initialized)Usage events, crash logs, diagnostics, device identifiers (including advertising ID)

These act as service providers. No sale or advertising-related sharing. The Facebook SDK (facebook-login) is bundled and initializes automatically, but is currently unused because no Facebook login app ID is configured. Kakao and Naver SDKs are currently inactive; this policy will be updated if they are activated.

6. Sharing / Sale / Advertising

  • Sale to third parties: none  ·  Advertising: none  ·  Sharing: limited to the processors in Section 5

7. Storage Location and Retention

  • Local data: on your device. Retained for the period of use; removed when app data is deleted.
  • Server data: backend (Supabase, hosting region: Singapore, ap-southeast-1). Retained while the account exists; on account-deletion request the account and related subscription/entitlement data are deleted (excluding non-identifying audit records).

8. Deletion / Account Deletion

  • Local data: Device settings > Apps > Chromic Audio > Storage > Clear data.
  • Account deletion: when you request backend account deletion through the in-app "delete account" function, deletion runs only for your own authenticated request (idempotent); the account and related subscription/entitlement data are deleted and on-device login information is cleared (verified in the live environment, 2026-08-28). Web guidance: https://www.chromicaudio.com/account-deletion

9. Security

  • In transit: HTTPS (TLS); cleartext traffic is blocked. At rest (local): app-private sandbox; least-privilege principle.

10. Children

The App is not directed at children (target audience 13+), and we do not knowingly collect personal information from children under 13.

11. Your Rights / International Transfers / Policy Changes

  • Requests for access, correction, deletion, and restriction: support@klisten.com
  • Some account/subscription data is transmitted to the Supabase cloud backend (hosting region: Singapore, ap-southeast-1); processing is carried out to provide the service (account, authentication, and subscription features).
  • We will update this page, in-app notices, and store Data Safety information when the policy changes.

12. Contact

Privacy contact: support@klisten.com