Privacy
Policy
How the Moozza app, api.mozza.tech server and mozza.tech website collect, use, store and share data.
At a glance
- Moozza does not sell personal data.
- Passwords, one-time codes and payment details are not stored on Moozza servers.
- Music, the local media library, cache and diagnostic logs remain on your device until you choose to export or delete them.
- De-identified sign-in and network failure diagnostics are sent only with separate consent. You can change your choice in settings.
- The third-party services listed below are used for advertising, analytics, payments, VK sign-in and support.
- You can request deletion of data associated with you at privacy@mozza.tech. The procedure is described in section 9.
1. Operator and scope
The operator of the Moozza app, api.mozza.tech server and mozza.tech website is verydox.studio. Questions about data processing and deletion can be sent to privacy@mozza.tech. For general support, contact support@mozza.tech.
This policy covers the main Android version of Moozza, server-side Premium and diagnostic features, and the website. Moozza is an independent app and is not affiliated with VK.
2. Data we process
VK sign-in and music
To sign in and retrieve content available to you, the app exchanges an account ID, session token, technical device ID and request parameters with VK. Your login, password and one-time code are sent to VK only for the sign-in method you select. With manual token sign-in, the token is sent directly to VK for validation and then kept only in the app's encrypted storage. The session is excluded from Android backups. The Moozza server does not receive your VK password, one-time code or token.
Optional VK listening statistics
Starting with Moozza build 482, the app can send VK the identifiers and context of VK music tracks you actually play, listening intervals, timestamps, playback positions, player actions, and technical playback and device information. These events are associated with your VK account and may also be sent while the app is in the background. Their purpose is listening statistics and VK Year in Review. VK determines whether and how received events are included in its statistics; successful delivery does not guarantee inclusion in Year in Review.
The preference is initially enabled for an account without a saved choice, but collection and transmission do not start until you accept the separate in-app disclosure. You can decline or turn off VK listening statistics in Settings → Privacy, independently of de-identified diagnostics. Your choice is retained separately for each account. Turning it off stops collection and deletes unsent events. Turning it on again starts with subsequent listening; old playback history is not uploaded. Local audio files and internet radio are excluded. No advertising identifier is collected for this feature.
Events are sent directly over HTTPS to VK, not through the Moozza server. An account-specific private delivery queue is excluded from Android backups, expires after at most 24 hours, and is limited to 5 MiB per account. It contains no session tokens or signed audio URLs. Signing out deletes that account's unsent events. Events already received by VK cannot be automatically withdrawn by Moozza; VK's own policies and controls apply to their subsequent processing.
Device and installation
The app creates a random private installation identifier and a derived public support ID in the format MZ-…. The installation ID, package name, version and build type are sent to the server. The private ID is stored on the server as a one-way hash. The support registry does not store your phone model, email address, IP address or VK ID.
Premium, promo codes and payments
When you purchase or restore access, the following may be processed: your email address, its hash and encrypted copy, order or invoice number, product, amount, currency, payment status, entitlement source, creation, verification and expiry dates, a hash of the promo code used, and links between the entitlement and up to two installations. Payment details are entered with Google Play, DigiSeller or their selected payment provider and are not sent to Moozza servers.
To understand whether Premium checkout works, the server records the steps taken by an installation: opening the Premium screen, displaying a DigiSeller offer, selecting payment, creating a link, opening the payment page and confirming a purchase. These steps are linked to a one-way hash of the random installation ID, app version, package name, country and selected provider. The payment form contents, payment details, raw IP address and app browsing history are not included in this funnel.
A one-time email code is valid for 10 minutes, is stored only as a strong hash and is deleted after its operational retention period expires. Unsuccessful checkout sessions are automatically deleted within one year at the latest.
Advertising, analytics and stability
Integrated SDKs may process the advertising ID, IP address, approximate region, technical identifiers, device, operating system and app version information, usage events, ad impressions and interactions, performance data, errors and purchase information. Moozza uses AppMetrica, Yandex Mobile Ads, Google Mobile Ads and Google User Messaging Platform. Consent settings available in your region can be changed in the app's advertising privacy settings.
Local media library
Titles, artists, artwork and other tags of local audio files, selected folders, cache, playback queue, playback history and settings are processed primarily on your device. The app does not upload your audio files to the Moozza server. Some ordinary settings may be included in Android system backups; the encrypted VK session is excluded.
Error reports and diagnostic logs
A technical report is created only after an explicit action by you. It may include the installation ID, app and Android versions, device model, system WebView, network and VPN status, network operator and country, public IP address, approximate region and internet service provider, results of limited DNS, TCP, TLS and HTTPS checks, a sanitized sequence of actions and an error stack trace. Passwords, codes, tokens, cookies and raw request bodies are excluded.
You can enable extended logging yourself only after authorization for the specific installation or with a one-time code. The log has a size limit, is stored locally, is not sent to the server automatically and is shared only through the system export menu you choose. A report exported by email is processed in the support mailbox. The admin panel stores the report ID, app and Android versions, error class, installation ID if provided, receipt time and investigation status. The full email remains in the mailbox and is loaded into the panel only when an administrator requests it.
Automatic network failure summaries
Only with your consent, when a request to VK, the Moozza server or an audio server fails because of a network error, the app may send the service and error categories, app version and package name, connection type, VPN presence and general network status. From the connection address, the server determines the country, region, ASN and internet service provider to distinguish widespread blocking or network outages from app errors. Raw IP addresses, URLs and request paths, request or response contents, tokens, VK accounts and installation IDs are not stored in these statistics. The panel provides aggregate counts only.
Automatic sign-in summaries
De-identified diagnostics are enabled by default when no choice has been saved. If enabled, the app sends the sign-in method, stage, availability and selected method of additional verification, result, short error code, duration, version and build type. The server adds the country, region and internet service provider from the connection address. Login names, phone numbers, email addresses, IP addresses, passwords, one-time codes, tokens, VK IDs and VK responses are not recorded in the aggregates. An event is associated only with a one-way hash of a random installation ID, aggregated into statistics and signed with a separate non-exportable Android Keystore key. The server rejects invalid signatures and duplicate events. You can turn consent off or on at any time in the Privacy section of settings. If you decline, queued events awaiting transmission are deleted.
Data-related requests
The dedicated mailbox privacy@mozza.tech receives requests for access, correction and deletion. The protected admin panel stores a masked sender address, a one-way hash of the address, the subject, receipt time and processing status. The full text is not copied into the panel database: it remains in the mailbox and is loaded from there only when an administrator opens the request.
3. Processing purposes
- sign-in, playback, recommendations, radio, downloads and caching;
- displaying ads and managing consent;
- purchasing, restoring and protecting Premium against abuse;
- user support, troubleshooting and improving stability;
- API security, rate limiting and fraud prevention;
- aggregate app and website analytics.
The grounds for processing depend on the feature: carrying out actions you request and fulfilling the service terms, legitimate interests in security and stability, compliance with payment-related obligations, and consent where required by applicable law.
4. Sharing and third-party services
Data is shared only to the extent necessary for the selected feature:
- VK — sign-in and music content;
- Yandex and AppMetrica — advertising, analytics, errors and performance;
- Google — Google Play, payments, advertising, consent and system services;
- DigiSeller and the payment services selected on its page — external payments and order verification;
- MaxMind GeoLite2 — local country detection for offer availability; the IP address does not leave the Moozza server for this purpose;
- IPinfo — fallback country detection and, for network failure diagnostics, country, region, ASN and internet service provider detection;
- Radio Browser, Apple iTunes Search and image/audio servers — finding radio stations and artwork, and delivering selected content;
- Beget and email providers — API and website hosting, and processing support requests.
Individual providers may apply their own policies, retention periods and cross-border processing arrangements. Moozza does not sell personal data or share your local audio files with advertising or analytics systems.
5. Retention and security
- Local data — until you delete it in the app, clear app data or uninstall the app.
- The installation registry, when not linked to Premium — up to 180 days after the last request; records associated with an entitlement are retained longer.
- A temporary IP HMAC and network detection result — up to 24 hours; network error aggregates without raw IP addresses — up to 90 days; ordinary web server logs — according to the hosting retention periods and security settings.
- Successful and unsuccessful sign-in aggregates and de-identified daily installation presence — up to 90 days; technical event identifiers used to prevent duplicate submissions — up to 7 days.
- Unpaid Premium funnel steps — no more than one year; confirmed purchase information is retained with the payment record to the extent necessary for restoration and dispute resolution.
- Payment records and entitlements — while the entitlement remains valid and afterwards to the extent necessary for purchase restoration, dispute resolution, fraud prevention and compliance with legal requirements.
- Email error reports — while needed to respond to you and investigate the issue; sanitized summaries are retained for the period set by the operator.
- Data deletion requests — until the request is completed, and afterwards only to the minimum extent necessary to confirm that it was fulfilled and comply with legal requirements.
We use HTTPS, rate limiting, one-way hashing of identifiers, AES-256-GCM for email addresses, access controls and administrator action auditing. Absolute security of data transmission and storage cannot be technically guaranteed.
6. Android permissions
- audio/storage access — finding, playing, editing and deleting selected local music;
- network access and connection status — online content, radio, advertising, payments and diagnostics;
- approximate location — advertising SDK features and regional requirements, only within the permissions granted in Android;
- notifications and background services — playback and download controls;
- changing audio settings and keeping the device awake — proper playback;
- camera access through Google's system scanner — only if you choose QR-code sign-in; the app does not receive ongoing camera access.
You can revoke permissions in Android system settings. The related features may then become unavailable.
7. The mozza.tech website
The hosting service processes technical logs containing the IP address, date and time, page, referrer and browser information. AWStats produces aggregate server statistics. Google Analytics loads only after you select Allow analytics, with Google Signals and ad personalization disabled. Your choice is stored in localStorage. Declining does not restrict access to the website.
You can change website consent by clearing mozza.tech data in your browser. The website does not use Moozza profile forms; email links open in your email app.
8. Your rights
Subject to applicable law, you may request information about processing, a copy of your data, correction, cessation or restriction of processing, withdrawal of consent or deletion, and may challenge the operator's actions. Reasonable verification of ownership of an email address, order or installation ID may be required to protect your data.
Withdrawing consent does not affect the lawfulness of processing before withdrawal. Advertising consent settings, where required, are available in the app. Uninstalling the app does not cancel a Google Play subscription; you can manage it in Google Play.
9. Deleting Moozza server-side data
Moozza does not create a separate password-based account. However, using Premium, a promo code or diagnostics may create server records associated with you: the purchase email address, Premium entitlement information, linked installations, authorization for extended diagnostics and an index of submitted error reports.
To request deletion, email privacy@mozza.tech from the address used for your purchase and include the public installation ID MZ-…, if available. You can find the ID in About Moozza. If this information is insufficient, support will request only the details necessary to verify ownership of the record.
After verification, email addresses, installation links, diagnostic authorization and report indexes that can be reliably associated with your request will be deleted or de-identified. Your Premium entitlement may no longer be restorable afterwards. Certain payment or request fulfilment records may be retained where required by law, accounting, fraud prevention or dispute resolution. You will be informed of this in the response.
Deleting Moozza data does not delete your account or data with VK, Google, Yandex, DigiSeller or a payment service. Requests to those providers must be made separately under their policies.
Request data deletionData relating to minors
Moozza has a 16+ age rating and is not intended to deliberately collect children's data. A legal representative may contact support if they believe a minor's data has been processed improperly.
10. Policy changes
The current version is always available at https://mozza.tech/privacy/. When the types of data processed or the processing purposes change materially, the document date is updated and new consent is requested where required.