Effective Date: October 18, 2026
CleanSonic (“CleanSonic,” “we,” “us,” or “our”) respects your privacy. This Privacy Policy explains how we collect, use, store, and share information when you use the CleanSonic mobile application.
Microphone and Noise Meter Data
CleanSonic may request microphone permission only when you use the Noise Meter feature.
The microphone is used to calculate live sound-level measurements, such as current, minimum, average, and maximum decibel values. Audio is processed on your device for this purpose.
Microphone input may be written temporarily to the app’s private storage only as required for metering. It is deleted when measurement stops and is never uploaded to our servers or shared with third parties.
Sound Tone and Frequency Data
CleanSonic generates sound frequencies locally on your device for sound-tone routines, frequency playback, and speaker tests.
We may store a local tone-session history on your device, such as the selected mode, frequency, duration, completion status, and session date. This information is used only to provide app functionality and is not uploaded as user content. The sound features do not diagnose your device or confirm that water, dust, or debris has been removed.
Application Preferences
We may store application preferences locally on your device, including your selected language, onboarding status, settings, and tone-session history.
Purchases and Subscription Information
Purchases and subscriptions are processed by Apple through the App Store.
We use RevenueCat to manage subscription offerings, premium-access status, and purchase restoration. RevenueCat may process technical device information, app-specific identifiers, Apple purchase receipts, transaction information, subscription status, and entitlement information necessary to provide subscription services.
CleanSonic does not receive or store your full payment-card information.
Analytics and Attribution Information
CleanSonic may use Firebase Analytics, Mixpanel, and our advertising measurement partners to understand app performance, feature usage, subscription events, and advertising-attribution performance. Firebase Crashlytics receives crash reports and device information to fix errors, and Firebase Remote Config receives technical identifiers to deliver app settings.
These services may process limited technical and usage information, such as device type, operating system, app version, language, app interactions, event timestamps, app-specific identifiers, IP-address-related technical data, and advertising or attribution identifiers where permitted. Answers you give during onboarding, such as why you use the app and how you heard about it, may also be recorded as analytics events.
If you allow tracking in Apple’s App Tracking Transparency prompt, our advertising measurement partners may receive app events, an anonymous app identifier, and the advertising identifier for advertising measurement. If you do not allow tracking, our advertising measurement partners receive app events without the advertising identifier, only for aggregated advertising measurement (including Apple’s SKAdNetwork).