Privacy Policy for Clear Wave Water Eject
Privacy Policy for Clear Wave Water Eject
Introduction
Clear Wave Water Eject is a speaker utility app published by the developer. The app is designed to help users play guided sound waves for water eject, dust cleaning, speaker clarity, and speaker testing. The developer is committed to transparency about how the app accesses, stores, uses, and shares data.
Information We Collect
Data collected automatically via SDKs
Clear Wave Water Eject uses Google AdMob through the Google Mobile Ads SDK to display banner ads and interstitial ads. According to Google's documentation for the Google Mobile Ads SDK, the SDK may automatically collect and share data such as IP address, user product interactions, diagnostic information, and device or account identifiers for advertising, analytics, and fraud prevention purposes. Data handled by the Google Mobile Ads SDK is encrypted in transit using TLS.
Data stored locally
The app stores one local preference on the user's device: whether onboarding has been completed. This is stored using AndroidX DataStore preferences. The app does not upload this onboarding preference to the developer's server.
Data not collected by the app core
The app does not require an account and does not collect the user's name, email address, phone number, contacts, precise location, microphone audio, photos, videos, files, calendar data, financial information, health data, or messages. Cleaning sessions run on the device. The app does not upload speaker sound activity, cleaning history, selected frequencies, or custom frequency settings to a developer server.
Permissions Used
android.permission.INTERNET
- Purpose: Used to load Google AdMob ads.
- Data collection: The app core does not use this permission to send cleaning session data to a developer server. Google AdMob may use network access to request, serve, and measure ads.
android.permission.ACCESS_NETWORK_STATE
- Purpose: Used by the app and advertising SDK to check network availability for ads.
- Data collection: This permission alone does not collect personal data, but it supports ad loading behavior.
android.permission.VIBRATE
- Purpose: Used for the optional vibration assist feature during supported cleaning sessions.
- Data collection: This permission does not collect personal data.
Permissions added through included SDKs or merged manifests
The Google Mobile Ads SDK may add advertising or Android Privacy Sandbox related permissions such as com.google.android.gms.permission.AD_ID and Android AdServices permissions in the merged app manifest. These support ad serving, ad measurement, and related advertising functionality. Users may reset or delete their advertising ID through Android settings where available.
Third-Party Services
Google AdMob / Google Mobile Ads SDK
- Purpose: Display banner ads and interstitial ads, measure ad performance, support ad-related analytics, and help prevent fraud and abuse.
- Likely data categories: Approximate location signals derived from IP address, app interactions such as app launch and ad interaction information, diagnostic information, and device or other identifiers such as Android advertising ID or app set ID.
- Privacy policy and documentation:
- Google Privacy Policy: https://policies.google.com/privacy
- Google Advertising Technologies: https://policies.google.com/technologies/ads
- Google Mobile Ads SDK Data Disclosure: https://developers.google.com/admob/android/privacy/play-data-disclosure
- GDPR/EEA note: If the app is distributed to users in the EEA, UK, or Switzerland, the developer should configure the required Google consent flow or another compliant consent mechanism for personalized ads where legally required.
The app uses AndroidX, Jetpack Compose, Material 3, Navigation Compose, Lifecycle, and DataStore libraries for app UI, navigation, lifecycle handling, and local preferences. These libraries are not used by the developer as advertising, analytics, payment, social, or backend data collection services.
Data Retention
The onboarding completion preference remains stored locally on the user's device until the user clears app data or uninstalls the app. The developer does not operate a backend server for storing user accounts, cleaning history, speaker activity, or custom frequency settings. Data processed by Google AdMob is retained according to Google's policies and the user's applicable Google and Android privacy controls.
Data Sharing
The app core does not share cleaning session data, custom frequency values, account data, contact data, microphone audio, files, photos, or precise location data with the developer or a developer-operated server. Google AdMob may collect and share advertising-related data as described in Google's documentation for ad serving, measurement, analytics, and fraud prevention.
User Rights and Control
Users can delete local app data by clearing Clear Wave Water Eject's app data in Android settings or uninstalling the app. Users can control or reset advertising-related identifiers through Android settings where available. Users may also manage Google ad personalization controls through Google settings. For privacy questions, users can contact the developer at [SUPPORT_EMAIL].
Children's Privacy
Clear Wave Water Eject is not directed at children under 13. The app is a general speaker utility and includes Google AdMob advertising. The developer does not knowingly collect personal information from children through the app core. If the developer becomes aware that personal information from a child has been provided through a support request, the developer should take reasonable steps to delete it.
Account Deletion
Clear Wave Water Eject does not create user accounts and does not provide login or account registration. Therefore, there is no in-app account deletion process. Users can remove local app data by clearing app data or uninstalling the app.
Security
The app keeps its core cleaning functionality local to the user's device. The app does not upload speaker activity or cleaning history to a developer server. Google states that data collected by the Google Mobile Ads SDK is encrypted in transit using TLS. No method of electronic processing is perfectly secure, but the developer aims to use reasonable safeguards appropriate to the app's functionality.
Changes to This Policy
The developer may update this Privacy Policy when app features, SDKs, data practices, or legal requirements change. The updated version should include a new effective date.
Contact Us
For questions about this Privacy Policy, contact:
[watiindiah@gmail.com]
This Privacy Policy is a draft and should be reviewed before publication.