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 document covers Volume Lock Free, Android package volumelock.vlocker. Website processing is described in the website privacy notice.
On-device data and permissions
Volume settings, rules, profiles, PIN controls and related preferences are kept locally. Android backup and device-transfer behavior can depend on the record and device settings. Clearing app storage or uninstalling removes local data as applicable.
The app requests access to audio settings, notifications, background operation and Do Not Disturb controls where required for functionality. It does not use these functions to collect contacts, messages, camera, microphone or precise location information.
Compatibility diagnostics
To diagnose compatibility problems and improve reliability, the app automatically sends a pseudonymous device identifier and technical device, app and feature-operation information to the developer’s Cloudflare-hosted service. This supports app functionality and diagnostics and is separate from advertising or Firebase Analytics. Compatibility diagnostic records are retained for 180 days after the last received report.
Advertising and analytics
The reviewed Free source includes Google Mobile Ads, Google’s consent platform and Liftoff Monetize (Vungle), InMobi and Mintegral mediation dependencies. Which providers receive requests depends on initialization, configuration, region and available consent. A packaged dependency does not prove that it serves an ad.
Advertising providers may process advertising/app identifiers, IP address and network-derived approximate location, app/device information, requests, views, interactions, consent signals and diagnostics for advertising, measurement and fraud prevention. Firebase Analytics separately processes app-instance/device information, app events and IP-derived approximate location for app measurement.
Use the native advertising Privacy Options when available and Android/Google advertising settings. Verified Premium suppresses covered banner and fullscreen advertising requests; this does not disable Firebase Analytics or required purchase/security processing. A website switch cannot change an app’s native advertising choices.
Purchases, licensing and security
Google Play handles payment details, account purchase context and current offers. The Free app and its Cloudflare verification service can process product/purchase-token information, package/version, a random installation identifier, signed entitlement credentials and Integrity information to verify, restore and maintain Premium and prevent misuse.
Entitlement and operation records are separate from local volume settings. The developer does not receive your Google password or card details through this verification protocol. Uninstalling, clearing local data or requesting deletion does not cancel a Google Play subscription or issue a refund.
Providers and international processing
Firebase Remote Config retrieves app configuration and, in Free, advertising configuration. Firebase can process a Firebase installation identifier and app/device configuration information to provide this service. Configuration requests are separate from advertising consent and an ad-free benefit; they follow Firebase’s privacy information.
Google privacy · Firebase privacy · Cloudflare privacy
Providers may process information in different countries under their own practices and safeguards. Website and email processing have separate scopes from local app records.
Support information
If you contact support, we receive your sender address, message and the attachments or transaction details you choose to send. We use them to answer your request and for relevant security, transaction or legal obligations. Do not send passwords, authentication codes, card details or raw purchase tokens.
Retention and deletion
Local settings remain until changed or removed through app/device controls. Subscription purchase and entitlement records have separate retention rules:
- Purchase-token material and lookup hashes: 60 days after final verified expiry and completed acknowledgement work, subject to active-access and outstanding-work safeguards.
- Current entitlement state and minimal lineage: while operationally needed, then up to 24 months after final closure.
- Historical order rows and verified lifecycle events: rolling 24 months from their authoritative order or event timestamps.
- Installation associations for closed, expired entitlements: 90 days after last use.
- Idempotency response metadata: 24 hours; a processing lease lasts at most two minutes.
- Encrypted purchase-notification payloads: seven days. Resolved notification, quarantine and inactive-alert metadata: 90 days after resolution or inactive transition.
- Cloudflare delivery queues: 24 hours. Operational Workers Logs: up to seven days under the documented plan.
Active access, incomplete verification or acknowledgement work, missing authoritative order information and scoped legal, security or dispute holds can delay deletion of affected records. Other purchase or access-verification records can have different lifecycles; no universal expiry applies to every purchase record. The 60-day rule does not delete all purchase or entitlement information. Uninstalling or clearing local data does not delete server records.
Support messages and attachments follow a manual deletion procedure at 24 months after case closure, with scoped exceptions for legal, security, refund or unresolved-dispute obligations. Provider-controlled records and backups follow the provider’s own retention and deletion processes.
Your choices and requests
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.
Established app notice
App versions and enabled features can differ. This app-specific website notice supplements the established app notice at volumelock.app/volume-lock/privacy/. This website does not change existing in-app or Google Play policy links.
Changes to this notice
Review the updated date when practices change. New app releases must be reviewed against their actual processing and notices.