This agreement is part of the terms between the company below ("we") and the customer who builds an app for a radio station on myradioapp.eu ("you"). It covers the personal data of your app's listeners, which we process on your behalf to run your app and your station's page. For that data you are the controller and we are your processor, in the sense of Article 28 of the General Data Protection Regulation. You accept it with the terms: when the account is opened, or on the page your account shows when either text changes.
Who we are
Xania Media
Belgium
billing@myradioapp.eu
What we process, and why
Only what it takes to run the app you publish and your station's page, and only for that.
- Whose data: people who install your app, and people who open your station's page.
- Installations of your app: the token used to deliver notifications, the version of the app, the station chosen, a random id our server gives the installation, and when it was last seen. They are used to deliver the notifications you send and to count how many phones open the app each day; the daily counts themselves say nothing about anyone.
- Request logs: for each request to our server, the IP address shortened by removing its last part, the app or browser identifier, the address asked for and the result. They are used to keep the service working and to find abuse.
- Reports: when a listener reports a dedication or a question in your app, the report is passed to the streaming platform you use for them, with an id derived from the installation, never the installation id itself.
- Advertising: views and taps on your own advertising are counted per campaign. The counts are numbers, not people.
We do not use this data for our own purposes, do not sell it and do not combine it with the data of other customers' apps.
How long
- Request logs are deleted after 90 days.
- An installation that has not been seen for 180 days is deleted, with everything kept for it.
- When you delete your project, or your account, the installations of its app are deleted with it. Its request logs follow within the 90 days above.
What we commit to
- Your instructions. We process this data only as these terms, this agreement and what you set in your panel ask. If an instruction seems to us to break data protection law, we tell you.
- Confidentiality. Only the people who run the service can reach the data, and they are bound to keep it confidential.
- Security. The app talks to our server only over HTTPS. Each app identifies itself with its own project key, and what it sends is kept under that project; no app can read listener data back. Addresses in the request logs are shortened before they are stored, and data is removed on the schedule above. Signing keys are stored encrypted.
- Your listeners' requests. Listeners who write to us about their data are directed to you, and we help you answer them. The data holds no names or contact details, so an installation is usually found through the phone itself: removing the app stops all processing for that phone, and its installation is deleted here as above.
- Incidents. If personal data we process for you is lost, exposed or changed without authority, we tell you without undue delay after we learn of it, with what we know then and the rest as we find it out, so that you can meet your own obligations.
- Help with your obligations. We give you the information you need for your records, for an impact assessment, or to answer a data protection authority about our part.
- Showing it. We give you the information needed to show that we keep to this agreement. If that is not enough, you may have an audit carried out once a year, at your cost, with 30 days' notice, by an auditor bound to confidentiality, in a way that does not expose other customers' data.
Who else processes it
You allow us to use these sub-processors:
- The company whose servers run the platform and store the data above.
- Google, through Firebase Cloud Messaging, which delivers notifications to your listeners' phones. Google may process the notification token and the message outside the European Economic Area, under its own data processing terms for Firebase.
Before we add or replace a sub-processor, we tell you at least 30 days in advance by email to your account's address. If you object and we cannot meet the objection, you can end your subscription before the change takes effect. Each sub-processor is bound to protect the data at least as this agreement does.
The streaming platform that receives your listeners' reports is your own provider, which you chose for your station; it receives them on your instruction, not as our sub-processor.
What you answer for
- Having a lawful basis for what your app does, and telling your listeners about it.
- The privacy page of your app, which your listeners read and whose text you can change in your panel.
- What your notifications and your advertising say.
Duration and law
This agreement lasts as long as we process data for you, and ends with your last project. It is governed by Belgian law, as are the terms. Questions: billing@myradioapp.eu.