Scope and controller
Aizen Apps is the publishing name of Alexander Aizendorf, an individual developer. Contact the developer and data controller at volumelockkapp@gmail.com.
This notice describes the prepared first-release processing for com.aizenapps.earbudfinder. Earbud Finder is coming soon. Website processing has a separate notice.
App data and processing
Earbud Finder helps you find detectable Bluetooth devices and keep device information on your phone. You do not need to create an Earbud Finder account. The first release is being prepared with Google advertising and optional Google Play purchases to remove covered advertisements. Earbud Finder is not yet available through a public download on this website.
Bluetooth, location and local records. When you start discovery, the app processes available Bluetooth Low Energy advertisements, including device names, transport identifiers, signal strength and observation times. For an explicitly selected audio device, it can read Android's public audio-profile connection state. Tracking starts only when you enable it for a saved device. A connection observation does not establish an earbud's location or prove that it was physically left behind.
Saved devices, names and display choices, selected-photo references, tracking and alert preferences, observations, Found records and connection history are kept locally. Where location access and a suitable reading are available, the app can record the phone's position following a device contact, with the location reading's own time and reported accuracy. This is a phone-location reading, not GPS reported by an earbud. The app does not upload these local finding records or photos to its purchase-verification service or include them in its advertising or Remote Config requests. If you choose to open a recorded point in a map, that point is passed to the map app or browser you use. Android location services and external map providers have their own data practices.
Observation, Found and connection-unavailable timeline entries have a 30-day retention window, pruned during normal app processing and maintenance. The separate latest-contact record, completed-Found receipts and current connection-episode state remain until the saved device is removed. Clearing the timeline does not clear these separate records or restart an unchanged loss episode. Removing a saved device deletes its associated local records; removing a selected-photo reference does not delete the original photo from your device. App-owned database and settings are excluded from Android backup and device transfer by the app's backup configuration.
Advertising and privacy choices. The first production release uses Google Mobile Ads. Google's SDK can collect and share IP addresses and network-derived approximate location, advertising and app-set identifiers, app launches, taps and ad interactions, and app/SDK performance diagnostics for advertising, analytics and fraud prevention. Google states that its SDK data is encrypted in transit using TLS. Available advertising modes and consent/privacy choices depend on your region and Google's consent system; the app exposes its Privacy choices action when that system requires it. You can also reset or delete your advertising ID through Android settings. Google processing is described in the Google Privacy Policy and Google Mobile Ads data disclosure. Liftoff/Mintegral advertising is not included in this production release.
Remote configuration. Firebase Remote Config obtains advertising configuration. Firebase can process a Firebase installation identifier and app/device configuration information to provide that service. This configuration processing is separate from advertising consent and the ad-free benefit. Firebase Analytics event collection is permanently disabled in Earbud Finder; this does not disable Google's separate advertising analytics or Firebase configuration requests. See Firebase privacy information.
Purchases and verification. Google Play handles payment methods, prices, taxes, offers and the Google account purchase context. The app and its verification service can process a randomly generated installation identifier, package/app version, product and purchase-token information, signed entitlement credentials and Google Play Integrity information to verify, restore and maintain the purchased benefit and prevent misuse. The developer does not receive your Google password or payment-card details through this verification protocol. The developer-operated service uses Cloudflare infrastructure and keeps purchase/entitlement status, installation associations and operation records scoped to this app. These are purchase records, not cloud finding history. See the Cloudflare Privacy Policy.
Purchase-verification records have a different retention policy from the local timeline. Protected purchase-token material is eligible for cleanup only after terminal purchase conditions, expired access/refresh horizons and outstanding-work safeguards are satisfied; the current subscription rule includes a minimum of 60 days after confirmed expiry. This is not deletion of all purchase information after 60 days. Active purchase material and purchase/entitlement metadata, installation associations and records preventing duplicate or replayed operations can remain; these metadata records currently have no automatic expiry. Removing the app, clearing its local data or clearing history does not cancel a Google Play subscription, issue a refund or delete those server records.
Diagnostics and support. An app-private, size-limited diagnostic log can contain app/OS/device-model information, event counts and timings, and sanitized exception classes and stack frames. It does not record Bluetooth transport identifiers, device names, purchase tokens or coordinates. The app does not automatically upload this log. If you choose Send diagnostic report, an email app opens a snapshot addressed to aizensoftapps@gmail.com; you control whether to send it. Report snapshots are kept in app cache and older cached reports are cleaned during later report preparation. We receive the message, sender address and attachments you send and use them for support. Privacy requests for information controlled by the developer can be sent to volumelockkapp@gmail.com, subject to verification and applicable retention obligations. Provider-controlled records are subject to the provider's own controls.
Requests and provider controls
Depending on applicable law, you may request access, correction, deletion, restriction, objection or portability, withdraw consent or contact a competent supervisory authority. Send requests about records controlled by the developer to volumelockkapp@gmail.com. Verification may be necessary; an order reference alone is not authority to disclose private purchase records. Provider-controlled records follow the provider’s own controls.
Changes to this notice
Processing and published notices must be checked before a new release. Material changes carry an updated date and any notice required by applicable law.