Privacy Policy

Onda mobile application and website · Revision 2.0 · Applies to Onda from version 2.0.4, effective on the date of its public release · Русская версия

1. Scope and effective date

This Policy describes how data is handled in the Onda mobile application and on musiconda.web.app. Revision 2.0 takes effect on the date Onda 2.0.4 is publicly released in the App Store. The provisions about Meta concern the iOS version with this integration; they do not describe data collection by earlier versions that did not contain it.

Apple's App Store and other services you use separately have their own privacy policies. Our use of service providers within Onda is described below.

2. Provider and contact

Onda is provided by Maksim Shvyrkov, an independent developer (“we”, “us”). For privacy questions or requests, contact aihelphelp1@gmail.com.

If you contact us, we receive the address and information you include in your message. We use that correspondence to handle your enquiry and any applicable legal obligations. Please do not send passwords, payment-card details or full purchase receipts unless specific information is necessary to resolve your request through an appropriate channel.

3. Overview

Onda requires no account or sign-in. Apple processes purchases. On iOS, Onda uses Meta App Events after tracking permission to measure and improve advertising for Onda. This involves installation and activation information, paywall views, checkout starts and eligible confirmed new purchases.

Refusing or withdrawing tracking permission does not change music playback, the free allowance, prices, purchases or restoration. The five free minutes are free access, not a subscription trial.

4. Optional Meta measurement and data

The integration uses Meta iOS SDK 18.1.1 through the facebook_app_events 0.31.0 plugin. After permission, it can send the following information:

ActivityInformation
Installation and activationInformation used by Meta to recognise an installation and app activation or session. An installation event can be reported after permission, rather than at the time of download.
Paywall view — paywall_showThat the user opened the screen displaying purchase plans. It is not a listening event.
Checkout start — InitiatedCheckoutThat the user started a purchase, with the selected product identifier. It is sent before the outcome of Apple's purchase flow; cancellation does not turn it into a purchase.
Confirmed new purchase — PurchaseThe purchased product identifier, transaction amount and currency, when the transaction meets the integration's eligibility checks and reliable price information is available.

The SDK can add device and SDK-generated identifiers, including the advertising identifier when permitted, event timing and session information, and technical details about the device, app and operating system. Meta also receives network information when a request reaches its services, including the IP address. SDK diagnostic features can collect crash information and other technical data for analytics, reliability and operation of the SDK.

These identifiers can associate activity with a device even though Onda has no user accounts. Meta can associate app activity with advertising interactions. Its use of the data, including advertising, measurement and service operation, is subject to the applicable Meta terms and privacy policy linked in section 9.

Our event parameters do not include listening history, Apple ID, email, payment-card details, the full receipt or signed transaction. The local transaction ID and purchase-attempt identifier described in section 6 are not included in our Meta event parameters. This integration does not request contacts, photographs, precise location, microphone, camera or health data.

Onda does not send StartTrial. Purchase is not sent for restoration, historical purchases, pending or cancelled purchases, automatic renewals or refunds. Sandbox purchases are excluded from the production Meta purchase stream. These measurement rules do not determine your purchase rights or access to Onda.

5. Tracking permission and withdrawal

Before tracking permission is granted, Onda does not initialize Meta SDK. Our measurement requires an authorized status from Apple's App Tracking Transparency (ATT). A denied, restricted or unanswered request does not permit our manual events. Permission is checked when the app returns to the foreground and before manual event submission. A failure to read permission is not treated as consent.

You can change your choice in iOS Settings → Privacy & Security → Tracking. When Onda observes withdrawal, it stops submitting its manual events and disables advertising identifier collection through its SDK settings. Our analytics layer does not record actions during refusal for later submission after a new permission.

Withdrawal is not deletion. It does not erase data Meta has already received. Events already handed to the SDK may be in its memory or persistent queue, or a request may already be in progress. Onda does not have a supported mechanism to purge the entire SDK queue or cancel every request; we do not promise that changing ATT immediately removes those events or stops every SDK network operation. The SDK's handling of previously queued data is separate from our manual-event checks.

ATT is a system permission. It does not replace any additional notice or consent required by the law applicable to a user. Availability of tracking permission is not proof that all other legal consent requirements have been met.

6. Data kept on the device

Onda stores settings, onboarding progress, free-use time, access state and reminder settings locally. Some free-use state is stored in iOS Keychain and can survive reinstallation. We therefore do not promise that uninstalling the app removes every local value. Browser settings remain until the relevant site data is cleared.

A separate local purchase-measurement journal stores the product, attempt start time, a random identifier for a purchase attempt and processed transaction IDs. The attempt identifier is passed to Apple to associate the result with that attempt. Processed transaction IDs help prevent duplicate purchase events. This journal does not replace the application's entitlement records.

The journal has no fixed automatic retention period. Processed transaction IDs remain in the app's local storage until that data is removed. Withdrawal of ATT does not erase the journal's processed transaction IDs, cancel a subscription or remove purchased access. Meta may maintain its own local SDK storage separately.

7. Purchases

Apple processes subscriptions and one-time purchases. Onda uses StoreKit transaction and entitlement information to provide and restore access. We do not receive payment-card details through the app. Apple's processing is described in the Apple Privacy Policy.

With permission, an eligible new purchase can also generate the Meta event described in section 4. An analytics failure does not invalidate a successful purchase. Apple manages subscription cancellation and refunds; withdrawing tracking permission is not a request to cancel a purchase.

8. Website and file hosting

The website and files served from it are hosted on Google Firebase Hosting. When you visit the website or request a hosted file, Google receives technical request data, including the IP address. Google describes use of Hosting IP data for abuse prevention and usage analysis, with retention of a few months, in its Firebase privacy documentation. This is the provider's stated retention, not a deletion schedule controlled by Onda.

The current standard iOS build includes its music files. Playing those bundled files does not itself require a request to Firebase. Website visits, including opening a privacy or support link, are separate from Meta measurement in the app.

The website does not include a Meta pixel or advertising cookies. This does not mean that the iOS app has no advertising measurement: the app uses the SDK described in this Policy. Onda does not combine hosting request records with its Meta events.

9. Recipients and purposes

Meta receives optional app measurement data. Onda uses the resulting reports to measure and improve its advertising. SDK data can also support Meta's advertising, analytics and service functionality as described in its applicable terms. See the Meta Privacy Policy and Meta Business Tools Terms.

Apple processes purchases and related account information through its services. Google provides website and file hosting. Messages sent to our support address are also handled by the email services involved.

Onda has no separate server for collecting its app measurement events. This does not mean that data stays on the device: Meta receives the SDK data. We remain responsible for our own handling and disclosure of data; links to provider policies do not remove those responsibilities or your statutory rights.

10. Retention and international processing

Local app storage is described in section 6. Meta and Apple determine retention in their services under their applicable policies and legal obligations. Onda does not set a fixed period for those services and cannot promise immediate deletion from their systems or backups. Firebase Hosting retention is described in section 8.

We keep support correspondence for handling the enquiry and any applicable recordkeeping or legal requirements. Requests to delete correspondence are considered subject to those requirements; we do not promise automatic deletion after a fixed number of days.

Our providers may process data outside your country. The relevant provider terms describe their international processing and safeguards. Contact us about the arrangements applicable to your request. Nothing in this Policy removes protections required by the law applicable to you.

11. Security

Device storage is protected by the operating system. Our Meta event parameters are limited to the fields described above. Onda does not enable detailed Meta request and response logging in its standard public configuration. No method of storage or transmission provides an absolute guarantee of security.

12. Children and restricted tracking

Onda does not ask for a date of birth. If iOS reports restricted tracking, Onda does not initialize Meta for the first time or submit its manual events. If permission was previously granted, the withdrawal limitations in section 5 also apply. System restrictions do not replace any applicable requirements concerning children or parental consent. Contact us if you believe a child's data has been handled improperly.

13. Your rights and data requests

Depending on applicable law, you may have rights to access, correct or delete data, restrict or object to processing, obtain portability, withdraw consent, opt out of advertising-related sharing, or complain to a supervisory authority. Write to aihelphelp1@gmail.com, identifying Onda and describing your request. We handle requests within the applicable legal time limits.

Onda has no user account or central user database. We may need proportionate information to identify the data relevant to a request, and we may be unable to match a person to a particular SDK identifier. We will explain the outcome or any applicable limitation. You may also use the rights and contact channels in Meta's, Apple's and Google's privacy policies for data held in their services. We cannot promise to locate or erase every provider-held record ourselves.

Turning off tracking, deleting the app and requesting deletion of provider-held data are separate actions. None of them automatically cancels an Apple subscription.

14. Policy changes

Changes to our data practices will be reflected in this Policy. Where required, we will provide additional notice and request consent before a new use of data. The revision and effective-date information appear at the top of this page.

15. Applicable law

The processing of personal data in connection with Onda is subject to applicable data protection laws.

This Policy does not select the law of any particular country as its governing law and does not limit users’ rights or remedies under mandatory applicable law, including the laws of their country of residence where applicable.

If a provision of this Policy conflicts with those mandatory requirements, those requirements prevail.