Speaker Cleaner
Privacy Policy
A plain-language explanation of the data used by the iPhone app and this legal website.
1. Scope and who is responsible
This Privacy Policy applies to the Speaker Cleaner iPhone app (the “App”) and the Speaker Cleaner legal website (the “Site”). In this policy, “we,” “us,” and “our” mean Vasilkoff CY Ltd, the data controller or business responsible for the processing described here.
The App provides user-started speaker tones, channel playback, an optional microphone-based digital level display, and an optional camera snapshot. The App does not currently provide user accounts, subscriptions, purchases, advertising, or a customer-content backend.
2. Data handled on your device
Audio playback
Tones are generated on your iPhone. Playback settings and the audio signal are not uploaded by the App.
Microphone level
If you start measuring and allow microphone access, audio buffers are processed in memory to calculate uncalibrated dBFS readings. The App does not record or upload raw microphone audio.
Camera and snapshots
If you choose the camera tool, camera frames and a captured image are processed on-device. A snapshot remains temporarily in App memory for review and is saved to Photos or passed to the iOS share sheet only when you choose that action.
Local preferences
The App stores appearance, onboarding progress, completed-session count, and the last completed-session identifier in local device preferences.
Microphone, camera, Photos add-only, and notification access are controlled by iOS. Denying one of these permissions does not prevent use of unrelated features. Saving or sharing a snapshot sends the image to the destination you select; that destination’s privacy terms then apply.
3. Firebase services used by the App
The App uses Google Firebase. Firebase may process identifiers, device and app information, IP-derived information, and service-specific technical data on our behalf. The exact categories depend on the service:
| Service | Data and purpose |
|---|---|
| Google Analytics for Firebase | Automatically collected app-interaction, session, app, device, and approximate-location information, together with app-instance or installation identifiers, is used to understand use and improve reliability. Analytics is enabled. The App links the no-IDFA Analytics library, has no advertising SDK, and does not request App Tracking Transparency permission or collect Apple’s advertising identifier (IDFA). |
| Firebase Crashlytics | Crash stack traces, installation identifiers, timestamps, app version, operating system and device characteristics, and related technical state are used to identify and fix crashes. We do not intentionally attach raw microphone audio, photos, notification tokens, contact details, or a user account ID to crash reports. |
| Firebase Cloud Messaging and Apple Push Notification service | Firebase may create an installation identifier and FCM registration token when its messaging service initializes. If you authorize notifications, the App also registers with Apple’s service and maps the APNs token to Firebase; Apple and Firebase then process tokens, notification payload, and delivery/interaction information to deliver and measure notifications. The App does not persist or log the raw FCM token in its own storage and currently has no separate token backend. |
| Firebase Remote Config | Firebase installation identifiers and fetch metadata are used to retrieve a limited informational-message flag and text. The App fetches asynchronously, keeps local defaults when offline, and does not remotely control tone frequency, volume, duration, routing, calibration, or other audio behavior. |
For Firebase’s service-by-service disclosures, retention information, security controls, and processing locations, see Firebase Privacy and Security.
4. Data used by this Site
This is a static Firebase Hosting site. It includes no JavaScript analytics, advertising pixels, cookies, forms, accounts, or third-party web fonts. When you request a page, Firebase Hosting processes ordinary access data such as your IP address and request information to serve, secure, and operate the Site.
5. How long data is kept
| Data or service | Retention |
|---|---|
| Local preferences | Remain on your device until you change/reset them where the App allows, clear the App’s data through iOS, or delete the App. |
| Live microphone data and unsaved snapshot | Processed transiently in memory during the active feature or review flow; not uploaded by the App. A saved or shared image is retained by the destination you choose. |
| Google Analytics for Firebase | Google Analytics retains user- and event-level data according to the property’s configured period; standard properties support 2 or 14 months. If reset-on-new-activity is enabled, new activity restarts the retention period for the user identifier. The control does not apply to standard aggregated reports. See Google’s Data retention documentation. |
| Firebase Crashlytics | Firebase states that crash stack traces, extracted minidump data, and associated identifiers are retained for 90 days before removal. |
| Firebase Cloud Messaging | Firebase installation IDs are retained until deletion is requested through the applicable API, then removed from live and backup systems within 180 days. |
| Firebase Remote Config | Firebase installation IDs are retained until deletion is requested through the applicable API, then removed from live and backup systems within 180 days. Activated values may also remain in the App’s local Firebase cache. |
| Firebase Hosting | Firebase states that Hosting retains IP addresses for a few months. |
We may retain information longer where reasonably necessary to meet legal obligations, resolve disputes, protect security, or establish legal claims. Where a third-party service controls deletion schedules, its documented schedule applies.
7. Your choices and controls
- You can allow or deny notifications, microphone, camera, and Photos access, and later change those permissions in iOS Settings.
- You decide whether to start playback, start microphone processing, open the camera, capture a snapshot, save it, or share it.
- Deleting the App stops future App collection from that installation and removes the App’s local preferences, subject to iOS behavior. It does not automatically erase data already held by Firebase.
- The current App does not provide an in-app Analytics or Crashlytics opt-out. We do not claim that changing unrelated iOS permissions disables those services.
8. Your privacy rights
Depending on where you live, you may have rights to request access, correction, deletion, restriction, objection, or portability, and to complain to a privacy regulator. These rights can be limited by applicable law and by whether we can reasonably identify data associated with your installation.
To make a request, contact sp@vasilkoff.com. We may need enough information to verify and process your request, but the App has no account system and we should not ask for information that is unnecessary.
9. Security
We limit the App’s data handling to the services and permissions described above and avoid persisting raw audio, camera frames, and notification tokens in our own App storage. Firebase states that data is encrypted in transit and that Crashlytics and Cloud Messaging data are also encrypted at rest. No method of storage or transmission is completely secure.
10. Changes to this policy
We may update this policy when the App, Site, service providers, or legal requirements change. We will post the revised version here and update the effective or last-updated date. If a change materially affects how personal data is handled, we will provide additional notice where required by law.
11. Contact
Questions or privacy requests can be sent to:
Vasilkoff CY Ltd
sp@vasilkoff.com