Musopia Data Subprocessor list

Effective date: 12th September 2022

Data Subprocessors of Musopia

Revenuecat ltd

Musopia uses revenuecat as the service for handling the subscriptions of its customers, spanning from Apple Appstore, Google Play Store and web payments options.

The main categories of information shared with RevenueCat to enable handling your subscription states are:

  • Subscription events: trial and subscription purchases, cancellations
  • Your account identifier: for example, if you’ve signed up using email, your email address. This is used to establish that your active accounts has paid for the subscription
  • Other identifiers (like advertising identifiers): if you’ve accepted the ATT prompt to transmit your advertising identifiers

More information about the information shared with revenuecat:
https://www.revenuecat.com/docs/apple-app-privacy

Stripe ltd

Musopia uses Stripe as the service for handling the payments user account subscriptions via website signup and subscription.

The main categories of information shared with Stripe to enable handling your subscription:

  • Subscription events: trial and subscription purchases, cancellations
  • Subscription plan type, sku, price and currency
  • Your account identifier: for example, if you’ve signed up using email, your email address. This is used to establish that your active accounts has paid for the subscription

More information about the information shared with Stripe:
https://stripe.com/en-gb-fi/privacy

Appsflyer ltd

Musopia uses appsflyer as a service for determining, which advertisements used to market Musopia applications results in trials and subscriptions being started.

In order to track the install and the related, Musopia applications share following data with Appsflyer:

  • appsflyer_id
  • event_name: name of the event. For example: ”client started trial”, ”client started subscription”
  • advertisement identifiers: campaign, adset, ad user install came from
  • ip address: for determining coarse geolocation

On IOS, the information shared with appsflyer is dependent on your ATT prompt request - if you decline the ATT prompt, the advertisement identifiers are not available for the appsflyer SDK and thus not sent to appsflyer.

More details: https://www.appsflyer.com/legal/privacy-policy/

Flurry

Musopia uses flurry to track high-level application metrics, for example:

  • number of installs
  • number of active installs
  • purchases
  • total purchase value, refunds and so on.

More details: https://developer.yahoo.com/flurry/legal-privacy/terms-service/flurry-analytics-terms-service.html

Google Cloud – Firebase Analytics

Musopia uses Firebase analytics by Google as a service to collect and analyse user events in order to monitor, analyse and report on the usage patterns of the applications.

To do this, the following are shared with Firebase Analytics:

  • Pseudonymous user identifiers (user_pseudo_id, device id, advertising id where available)
  • User account identifier (if available)
  • Coarse location (city level)
  • App install source (such as a facebook campaign tag from which the install originated from)
  • User subscription status
  • User membership in app content experiments (ids) and messaging segments
  • User app use start date
  • Interaction events user has triggered in the application, for example:
    • tuner use
    • lesson use
    • purchase interactions via the app UI
    • questionnaire and ratings prompt interactions
    • song plays
    • navigation

More details: https://firebase.google.com/support/privacy

Facebook

Musopia uses facebook as an advertisement platform to markets its applications. In order to do this, the following information is shared with Facebook:

  • SHA256 digest of user emails or device identifiers (if available). Needed to create lookalike audiences for user acquisition.
  • Conversion event name and value: for example client_subscription_trial_monthly, 0.00 USD

More details: www.facebook.com/business/gdpr

For IOS users, the information shared with facebook is determined by your responses to ATT - ads identifier information is shared if you’ve accepted the ATT prompt by Apple. In other cases, only anonymous tracking information is shared via Apple’s privacy preserving SKADNetwork advertising solution.

Musopia uses Google Ads as an advertisement platform to markets its applications. In order to do this, the following information is shared with Google Ads:

  • Pseudonymous user identifiers (user_pseudo_id) and advertising identifiers (idfa), where applicable*
  • User conversion events - signals that purchase, trial, activation or video watching has occurred

https://policies.google.com/privacy

*For IOS users, the information shared with google is determined by your responses to ATT - ads identifier information is shared if you’ve accepted the ATT prompt by Apple. In other cases, only anonymous tracking information is shared via Apple’s privacy preserving SKADNetwork advertising solution.

Jotforms

Musopia uses Jotforms as a platform to collect usage surveys information from the Musopia app user. The results of the collected surveys are used as a feedback to analyse, prioritise and improve app features and thus provide better service to the Musopia app users.

More information on the data processed on Musopia behalf by Jotform:
https://www.jotform.com/privacy/

Zendesk

Musopia uses Zendesk as a platform to collect, answer and manage support queries the users of its apps might have. In order to perform these, Musopia shares with Zendesk the following details:

  • Your name and email, if you provide these to us with your support request
  • Your device identifiers and user identifiers (for example device_id, user_pseudo_id, account_id) needed to provide support for your account in particular
  • Debug information, including error logs and other details that are available on your device that help identify the cause your error or support issue.

More details:
www.zendesk.com/company/customers-partners/eu-data-protection