Speaker Cleaner Privacy Policy
Policy information
Application: Speaker Cleaner (Android package com.speakercare.cleaner).
Privacy contact: wangjuang2022+speaker@gmail.com
Policy date: November 2, 2026.
1. Core features and information on your device
Speaker Cleaner provides locally generated audio, sound tests and illustrated care guidance. Playback and care guides work offline. No account is required, and there are no in-app purchases or subscriptions. Optional banner advertising is described below; cleaning does not require watching or interacting with an ad. The app does not record sound, inspect water or dust with a sensor, or upload photographs. Its illustrations are packaged project images, not photographs taken from your device.
Your language choice, manual frequency, duration, pulse setting and saved custom presets, including names you enter, are stored in the app's private storage. The app does not upload these custom names or a copy of your saved presets. It disables Android app backup and declares exclusions for app data. The release services described below still process diagnostic and usage information.
2. Release builds and Firebase services
Release builds use Google Firebase Crashlytics, Google Analytics for Firebase and Firebase Remote Config, including their required installation and session components. Debug builds use the package suffix .debug, contain no Firebase SDK and do not send Firebase crash reports or usage events.
Crashlytics helps investigate crashes and reliability problems. Reports can include error stacks, relevant app state, device and app versions, timestamps, and SDK installation or session identifiers. The app adds its build type and version code, and Analytics can supply recent usage breadcrumbs. It does not deliberately attach your name, email address or custom preset names to these reports. Runtime errors may still contain environment information.
Analytics helps understand basic feature use. The app records screen names, the start and end of cleaning, automatic or manual mode, the selected built-in preset, the reason playback ended and its elapsed duration. These are predefined categories, not your saved preset names. The SDK can also collect installation or app-instance identifiers, session and engagement information, and app, device and regional context. Network services receive the connection IP address; this is different from requesting precise GPS location.
The integration removes advertising-ID and Android AdServices identifier, attribution and Topics permissions. Firebase advertising-ID collection remains disabled, and Firebase advertising storage, advertising user data and advertising personalization consent remain denied. These Firebase settings do not disable the separate UMP privacy requests, permitted ad requests, or non-advertising Analytics and diagnostic processing described here.
Remote Config delivers settings controlling diagnostic and usage reporting and the optional banner feature. It can process installation identifiers, country and language codes, time zone, platform and app metadata, and configuration context. Reporting policy changes take effect on a later launch; the banner switch can take effect after a foreground fetch or real-time update. Cached or packaged values are used when requests fail. Reporting defaults are enabled; the banner default is disabled. Turning off a switch does not itself stop Remote Config requests. The app currently has no in-app control that turns off all Firebase processing.
The app does not enable Firebase sign-in, player databases, cloud file storage, push messaging, Performance Monitoring, A/B experiments or Remote Config personalization. An internet connection is not required for the core audio features. SDKs may cache information on the device and retry transmission when connectivity returns.
Banner advertising and Google UMP
The app includes Google Mobile Ads and the Google User Messaging Platform (UMP). Banner advertising is disabled by default locally and in the published remote configuration. If enabled later, a banner may appear in a separate area at the top of the home or cleaning-result screen. Ads are hidden during preparation, playback, sound tests, care guidance and interruption recovery. The app does not add interstitial, app-open or rewarded ads, and does not require an ad to start or stop cleaning.
UMP checks the applicable privacy-message and choice status when the app enters the home screen, even while banner advertising is disabled. Google receives the network request and related app, device, region and consent information needed to provide that service. If a message is required, a loaded form is shown while the app is still on the foreground home screen; a late form waits until the user returns home. Required advertising privacy options are available from Help → Privacy & about → Ad privacy choices. A request or form failure does not block the audio tools. Where the SDK permits, a previously valid choice may be used; an initial failure without request permission does not enable ads.
When the banner switch is enabled and the SDK permits ad requests, Google Mobile Ads can process IP address, approximate location derived from network information, app and device information, SDK or app identifiers, ad requests, impressions, interactions and diagnostic information to deliver, measure and protect advertising. The initial integration requests non-personalized ads and does not request Android advertising-ID permissions. Non-personalized ads can still involve local storage, identifiers and measurement; they do not mean no data processing. Choices offered depend on region and the messages configured for this app. Core settings and custom preset names are not deliberately attached to ad requests.
Debug builds still contain no Firebase SDK, but they include the advertising and UMP SDKs for development. Ordinary debug builds default to banners off. Explicit local test builds use Google's dedicated test banner unit and may simulate a consent-test region; those test overrides are disabled in release builds. Test SDK requests can still contact Google. Ad and consent records are handled under Google's applicable service policies; the app does not promise a fixed retention period or an app-wide deletion button for those records.
3. Recipients, hosting and external links
Google processes the diagnostic, configuration, usage, privacy-choice and permitted advertising information through the services above. The developer uses the associated project reports to maintain stability, understand feature use and review advertising delivery. The app has no account-based cloud storage or developer-operated endpoint for uploading your saved custom presets.
The online policy is delivered through Cloudflare at juantools.com/privacy/speaker-cleaner; the previous speaker-privacy.juantools.com address redirects here. When you open it, the hosting service receives request information, including your IP address, request time and browser information, to deliver and protect the page. Hosting logs are governed by the service settings and Cloudflare's policies. The policy itself contains no app advertising, submission forms or external fonts. Cloudflare may apply its delivery, security and configured website analytics processing.
Links to Google and other external sites open under those sites' policies. The in-app Feedback action opens your email app with the support address and a subject identifying Speaker Cleaner. You review and send the message yourself. The app does not automatically attach logs, device identifiers, saved presets or files. You can also copy the support address. If you send an email, the developer receives the address, message and attachments you choose to send and uses them to respond and handle your request. Please avoid sending unnecessary sensitive information. No email is sent merely by opening this policy or the Feedback panel.
Google, Cloudflare and email providers may process information in countries other than your own under their published policies and applicable arrangements.
4. Retention, deletion and choices
Saved custom presets remain on your device until you delete them in the app or remove the app's data. Other local settings remain until changed, cleared through Android's Clear storage control or removed when you uninstall. These local actions do not automatically delete information already sent to a service provider.
Google currently describes a 90-day Crashlytics retention period before deletion processing begins. Firebase installation identifiers are retained until a supported installation-deletion request is made; Google's published deletion process can take up to 180 days across affected live and backup systems. The app does not currently provide an installation-deletion button, and uninstalling or emailing the developer does not itself call that API. A later installation or use of installation-based services may create a new identifier.
Analytics data is handled under the property's retention settings and Google's service rules. Those controls apply differently to event-level information and aggregate reports; the app does not promise a single fixed deletion period for all Analytics data. Use the official retention information linked below or contact the developer for questions about information that can be identified in this app's project.
For a privacy request, email the contact above with the app name, the request and an approximate time period. App and Android versions may help locate relevant records. Do not initially send identity documents, complete presets or unrelated sensitive material. The developer will assess information it can identify and control, explain limitations and act as required. An email address alone may not identify a pseudonymous SDK installation. Requests do not guarantee deletion of third-party records outside the developer's control.
Depending on applicable law, you may have rights to access, correct, delete or obtain a copy of information, restrict or object to processing, withdraw applicable consent, or contact a data protection authority. The developer handles identifiable correspondence for the time needed to answer, resolve requests and meet applicable obligations, then deletes or anonymizes it unless further retention is required.
5. Permissions and security
The app does not request microphone, camera, photo-library, contacts or precise-location access. Network permissions support UMP and permitted advertising requests, and Firebase services in release builds. Sound playback uses locally synthesized audio, not microphone recordings. The app does not automatically change your media volume.
App data uses Android's private storage, and the integrated online SDKs use encrypted transport. No storage or network transmission can be guaranteed completely secure. Protect access to your device and avoid including sensitive material in messages.
6. Questions and policy updates
Contact the privacy email for questions, including concerns involving a child's information. The app does not provide accounts or social messaging. This policy and relevant in-app notices will be updated when features or data practices change. Additional notice or choices will be provided where required. The published full policy is in English.