Privacy Policy
Last updated: 6 November 2026. This is a translation for your convenience. The German version at /datenschutz/ is authoritative to the extent permitted by the mandatory law of your country of habitual residence. This policy applies to the QORA app (Android, Android TV, Google TV, Fire TV) and to the website qoraplayer.com.
1. Controller and contact
Dominique Feld
Jolie Webdesign
An der Schule 20
54296 Trier
Germany
Email for all privacy requests: support@qoraplayer.com
We have not appointed a data protection officer because the legal requirements for doing so are not met.
2. Summary
- QORA supplies no content. QORA is a player for the access you have with your own provider. The app fetches channel lists, programme guide and streams directly from your device at your provider's server. With QORA Ultra, the app also asks your provider's server during playback for the status of your plan, such as how many streams are permitted and currently running. These requests do not pass through us, and we receive nothing from them.
- No plain-text access data with us. Your provider's access data is stored encrypted on your device. If you use cross-device sync, it reaches your account only in encrypted form (details and a transition notice in section 4.3).
- No advertising, no advertising profiles. QORA uses no advertising ID and builds no profiles for advertising. Usage statistics with Firebase Analytics only run if you agree (section 4.22).
- Without an account and without consent, no connection to Firebase, except through Google ML Kit. The app itself then sends nothing to us or to Firebase. Only Google ML Kit, according to Google, uses Firebase Remote Config and Firebase Installations for translating descriptions (section 4.24). Data then leaves your device only with the requests to your provider and with five Google functions: the QR scanner when you open it (section 4.12), the Cast library as soon as you open a channel, film or episode on a phone or tablet (section 4.13), Google's purchase library as soon as you open the plans page (section 4.7), rating through Google Play, when the app asks Google Play after the end of a film or an episode whether the rating window can appear (section 4.23), and the translation of descriptions on a phone or tablet, when a film or series page shows a description; the app then detects its language and translates it if it is foreign (section 4.24). The text of the description stays on your device. In the version from the Amazon Appstore (Fire TV), Google's purchase library and rating through Google Play are not used. Instead, as soon as you open the plans page or the QORA Ultra window, the app asks the Amazon Appstore on your device for the prices and your Amazon user ID (section 4.7a). If you choose voice search, your device's voice input (usually Google) listens briefly with your microphone permission and may evaluate your voice on its provider's servers for this (section 4.15). What is added with an account or consent is described in section 4.
- Consent only where needed. Crash reports, usage statistics and the playback log in your account only run if you agree. You can withdraw your consent in the app at any time.
3. Website qoraplayer.com
3.1 Visiting the website
- Data: IP address, date and time, requested address, amount of data transferred, browser and operating system (user agent), previously visited page (referrer) if your browser sends it.
- Purpose: delivering the website, detecting attacks and faults.
- Legal basis: Art. 6(1)(f) GDPR. Our legitimate interest is the secure and reliable operation of the website.
- Recipient: united domains GmbH (Germany) as host of the website.
- Retention: united domains keeps these server logs. How long they are kept is determined by united domains. We do not analyse them and do not combine them with other data. We will tell you the current period on request.
The website sets no cookies, uses no analytics tool and loads fonts and images from our own server. This also applies to the demo content at qoraplayer.com/demo/ if you enter the demo list in QORA.
3.2 QORA Player (Jolie Webdesign): Delete account
On the Delete account page of QORA Player (Jolie Webdesign) you sign in to your QORA account in order to delete it.
Merely opening the page loads no library from Google and makes no connection to Google. Only the server logs from section 3.1 are created.
- Purpose (opening the page): displaying the page.
- Legal basis (opening the page): Art. 6(1)(f) GDPR (providing the page), see section 3.1.
Only after you click "Sign in with Google" or "Sign in" does the page load the Google Firebase library from Google servers (www.gstatic.com) and connect to Firebase Authentication and Cloud Firestore. Google receives your IP address and browser information, and when you sign in with Google also the data listed in section 4.1. After sign-in, Firebase stores a sign-in state in your browser until you sign out or the account is deleted.
- Purpose (sign-in and deletion): signing in and deleting your account.
- Legal basis (sign-in and deletion): Art. 6(1)(b) and (c) GDPR (fulfilling your erasure request under Art. 17 GDPR). Storing the sign-in state in your browser is strictly necessary for this function you requested (§ 25(2) no. 2 of the German TDDDG).
- Recipient: Google (see section 5).
3.3 Pairing links at qoraplayer.com/k/
A QR code for pairing two devices contains a link to qoraplayer.com/k/. The pairing code sits after the # sign. Your browser does not send this part to our server; the server only sees a request for /k/. The page reads the code only in your browser, removes it from the address bar immediately, loads no scripts from third-party servers and sends nothing on. What happens on the way through Google Play is described in section 4.6.
3.4 Contact by email or WhatsApp
- Data: your message, your email address or phone number and anything else you tell us.
- Purpose: answering your request.
- Legal basis: Art. 6(1)(b) GDPR where your contract or a request before a contract is concerned, otherwise Art. 6(1)(f) GDPR (legitimate interest in answering requests).
- Recipients: emails to support@qoraplayer.com are stored in the mailbox at our mail provider united domains GmbH (Germany). If you write to us via WhatsApp, WhatsApp Ireland Limited processes the message; processing within the Meta group outside the EU cannot be ruled out. If you do not want this, write to us by email.
- Retention: we delete your message no later than twelve months after receipt, longer only where a statutory retention obligation applies. At your request we delete earlier unless such an obligation prevents it.
3.5 Notices from rights holders
If you send us a notice of an infringement through the rights holders page, we process your name, your email address, the details of the right concerned, the location of the content and your reasons.
- Purpose: to examine, answer and document the notice.
- Legal basis: Art. 6(1)(c) GDPR in conjunction with Art. 16 of Regulation (EU) 2022/2065, alternatively Art. 6(1)(f) GDPR (legitimate interest in defending legal claims).
- Recipients: emails to support@qoraplayer.com are stored in the mailbox with our email provider united domains GmbH (Germany). We pass the data on to third parties only where a legal obligation exists or the platform concerned has to be informed.
- Storage period: until the matter is closed and afterwards for as long as claims may become time-barred, at most three years from the end of the year in which it was closed (Sections 195, 199 German Civil Code). Longer only where a statutory retention duty or pending proceedings require it.
3.6 Affiliate links
This website contains affiliate links, marked with *. We take part in the Amazon Associates Programme (Amazon Europe Core S.à r.l., Luxembourg), the Awin affiliate network (AWIN AG, Berlin) and the CHECK24 partner programme (CHECK24 Vergleichsportal GmbH, Munich). No data is sent to these providers when our pages load. Only when you click an affiliate link are you taken to the provider. Their privacy policy applies there, and the provider can use cookies or an identifier in the link to recognise that you came from our website and credit us with a commission. The legal basis is our legitimate interest in financing the website (Art. 6(1)(f) GDPR).
4. The QORA app
4.1 Account with Google or with email and password
You only need an account for QORA Ultra, including the free trial.
- Data when signing in with Google: account identifier (Firebase UID), email address, display name and profile picture address of your Google account.
- Signing in with Google on Fire TV: Fire TV has no Google services. The app therefore requests a device code from Google and shows a QR code linking to Google's confirmation page together with a short code to enter. It then checks with Google until you have confirmed the sign-in on your phone with Google. Google receives our app identifier, the device code and the IP address of the TV. Google processes the confirmation on your phone as an independent controller under the Google Privacy Policy. After that, everything is the same as for any sign-in with Google.
- Data when signing in with email and password: account identifier, email address, whether the address is verified, and your password. Firebase stores the password only as an irreversible hash. Firebase sends you verification and password emails.
- In both cases: IP address, device and app information (user agent) and a check value from Google (Play Integrity or reCAPTCHA Enterprise) showing that the sign-in comes from a genuine app.
- Purpose: sign-in, managing your account, protection against misuse.
- Legal basis: Art. 6(1)(b) GDPR (user contract). For misuse protection Art. 6(1)(f) GDPR; our legitimate interest is protecting accounts against unauthorised access.
- Recipient: Google (Firebase Authentication) as our processor; for sign-in on Fire TV also Google (Google account sign-in) as an independent controller.
- Retention: until you delete your account. An account without current access to QORA Ultra that has not been used for 12 months is deleted by us. If it has a confirmed email address, we send you an email 30 days before (section 4.21).
- Deletion: in the app under Settings, Account, "Delete account", or on the website at /en/delete-account/ (section 7).
4.2 Cross-device sync: lists, favourites, progress
- Data: names and type of your playlists, favourites, watch list, recently watched channels and titles, progress per title (title, image address, position, duration), hidden and locked folders, the name of your device and a device identifier (see below). We never store the parental-control PIN itself, only a random additional value and a check value calculated from it.
- Device identifier: so that each of your devices has its own sync state and a device does not appear twice after a reinstall, each device's document carries a device identifier. This is the Android ID that Android provides to the QORA app on your device. It differs for every app, stays the same when you reinstall QORA and changes when the device is reset to factory settings. The app reads the Android ID only when it needs the identifier, i.e. at the first sync with your account or the first upload of the playback log, never on a plain start without an account. If the device provides no usable Android ID, the app creates a random identifier. We do not use it for advertising or profiles.
- Purpose: keeping continue-watching, favourites and lists the same on all your devices (QORA Ultra).
- Legal basis: Art. 6(1)(b) GDPR.
- Recipient: Google (Cloud Firestore, data centre in Frankfurt am Main) as our processor.
- Retention: until you remove the list or the device or delete your account; after QORA Ultra ends, at most 12 months (section 4.19).
- Deletion: remove the list in the app, remove the device under "Connected devices", or delete your account.
4.3 Your provider's access data
Without an account, the access data (address, user name, password or M3U link) is stored only on your device, encrypted with a key from the Android Keystore.
With cross-device sync we also store it in your account, but only as an encrypted block. Only the app on your devices has the key. It passes from device to device only through the end-to-end encrypted pairing (section 4.5). We therefore cannot read your access data in plain text.
Transition notice: App versions 0.9.70 to 0.9.105 additionally stored this key in your account so that a new device could take over the access data without pairing. As long as such an old key is stored in an account, decryption would be technically possible with authorised read access to our database, for example through the Firebase administration console. We do not use this possibility. Newer versions no longer store the key and delete the old key from your account at the next sync.
- Purpose: making your access available on all devices (QORA Ultra).
- Legal basis: Art. 6(1)(b) GDPR.
- Recipient: Google (Cloud Firestore, Frankfurt am Main) as our processor, encrypted only.
- Retention and deletion: as in section 4.2.
4.4 Household profiles
- Data: profile name, colour, whether it is a children's profile, time of creation and change. A profile PIN is stored only as an additional value and check value as in section 4.2.
- Purpose: profiles on all devices of your household (QORA Ultra).
- Legal basis: Art. 6(1)(b) GDPR.
- Recipient: Google (Cloud Firestore, Frankfurt am Main).
- Retention: until you delete the profile or your account; after QORA Ultra ends, at most 12 months (section 4.19).
4.5 Pairing devices
- Data: an end-to-end encrypted block with the access to be transferred, an additional value, a check value and the time. The key is provided solely by the code shown or scanned on the two devices involved.
- Purpose: transferring your access from phone to TV or between other devices (QORA Ultra).
- Legal basis: Art. 6(1)(b) GDPR.
- Recipient: Google (Cloud Firestore, Frankfurt am Main).
- Retention: the app deletes the block when pairing is complete. If it is left behind, our server deletes it automatically no later than about 20 minutes after it was created.
4.6 Pairing through Google Play (Install Referrer)
The pairing code is not transmitted to qoraplayer.com. Only when a device sends data to a phone on which QORA is not yet installed does the link lead to the Play Store and carry a pairing identifier there. Google Play passes this identifier to the app on installation (Install Referrer) so that you do not have to scan the QR code a second time. Google sees the identifier and keeps it retrievable for up to 90 days; we as operator do not see it. The app reads it once on your device and does not send it on. No later than about 20 minutes after it was created, the related data block is deleted, after which the identifier opens nothing.
- Legal basis: Art. 6(1)(b) GDPR. Reading the identifier on your device is strictly necessary for the pairing you started (§ 25(2) no. 2 TDDDG).
- Recipient: Google Play as Google's own service, not as our processor.
4.7 Purchase and subscription through Google Play
- Data: when you buy, Google Play receives from us only an irreversible hash of your account identifier (SHA-256) so that the purchase can be matched to your account. We store the plan purchased, whether it is the yearly or monthly plan, the status and term of the subscription, the product, a checksum of the purchase receipt and the times of purchase, renewal, cancellation or refund. Your payment data is processed by Google Play alone; we never see it. For the contract confirmation (see below) we also store whether, when and with what result it was sent (message identifier, reply of the mail server).
- Contract confirmation: after you buy a plan, including a switch between the yearly and the monthly plan, we send a confirmation of your contract to the verified email address of your account. It contains the statutory contract information, the withdrawal policy and the model withdrawal form as text, and the terms of use as a PDF attachment. The law requires this for distance contracts (§ 312f(2) German Civil Code).
- Technical data of the purchase library: for purchases QORA uses the Google Play billing library. It opens a connection to Google Play when you open the plans page, and with a signed-in account also when the app starts, to reconcile existing purchases. Google states about this library that it logs use of the programming interface (such as success and failure) and problems with the service connection, and that this information is used to improve the library's performance and to give better support for errors (release notes of Play Billing Library 6.0). Google names no further data types for it. In our test, after opening the plans page, without an account and without consent, the app sent a message to a Google server (firebaselogging.googleapis.com) whose source is the purchase library; we cannot see its content. The message does not depend on your consent switches, and QORA has no switch for it. Anyone who does not open the plans page and has no account does not trigger it, according to our measurements.
- Notice about payment problems: If you subscribed to QORA Ultra through Google Play, the app asks Google Play through the purchase library when you open the home screen whether there is a message about your subscription, for example because a payment failed. Google Play shows this message itself, and you can also change your payment method there. We do not see your payment data in the process.
- Purpose: unlocking QORA Ultra, verifying purchases, taking refunds and cancellations into account, sending the contract confirmation.
- Legal basis: Art. 6(1)(b) GDPR; the contract confirmation also Art. 6(1)(c) GDPR (§ 312f(2) German Civil Code), as does keeping proof of purchase. For the purchase library's connection to Google Play, Art. 6(1)(b) GDPR applies (you open the purchase service), and for that it is also strictly necessary under § 25(2) no. 2 TDDDG (German Telecommunications Digital Services Data Protection Act). For the library's log message to Google (use of the interface, connection problems), Art. 6(1)(f) GDPR applies. Our legitimate interest is a working purchase process with few errors. We do not classify the log message itself as strictly necessary for the purchase. We cannot see whether the library stores or reads information on your device for it. You can object to this processing under Art. 21 GDPR (see section 8).
- Recipients: Google Play (billing and purchase verification) and Google (Cloud Firestore and Cloud Functions, Frankfurt am Main). The technical data of the purchase library goes to Google, which processes it under its own responsibility. The contract confirmation goes through an encrypted mail server of our mail provider to your address.
- Retention: we delete the subscription state together with your account. At that point we detach the purchase record from your account; afterwards it contains neither the account identifier nor its hash. We keep it as long as we need it as proof towards Google Play and because of statutory retention obligations.
- Cancelling: you cancel your subscription in Google Play. Deleting your account does not end the subscription.
4.7a Purchase and subscription through the Amazon Appstore (Fire TV)
If you download QORA from the Amazon Appstore (Fire TV), you buy QORA Ultra through Amazon. Amazon, not Google Play, is then the seller and payment processor. This version uses neither the Google Play billing library nor rating through Google Play (sections 4.7 and 4.23).
- Purchase interface on the device: when you open the plans page or the QORA Ultra window, the app asks the Amazon Appstore on your device for the prices and your Amazon user ID for QORA, even without a QORA account. With a signed-in account, this also happens when the app starts, to reconcile existing purchases. This access is strictly necessary for that purpose (§ 25(2) no. 2 TDDDG). Whatever Amazon receives in the process, Amazon processes as an independent controller.
- Data: after a purchase, when the app starts with a signed-in account and when you restore purchases, the app sends the Amazon receipt IDs of your QORA purchases and the Amazon user ID that Amazon provides to the app for QORA to our server. The server uses them to ask Amazon for the state of the subscription (Receipt Verification Service), and for active subscriptions it also checks regularly on its own. We store your QORA account identifier, the tier, the plan (yearly or monthly), the state of the subscription and the end of access, the product, a checksum of the receipt ID, the receipt ID and the Amazon user ID (for regular re-checks), whether it was a test purchase, and when we last checked with Amazon. We never see your payment details or your Amazon account.
- Purpose: unlocking and re-checking QORA Ultra, assigning the purchase to your QORA account.
- Legal basis: Art. 6(1)(b) GDPR. We base keeping the purchase record after the subscription ends on Art. 6(1)(f) GDPR; our legitimate interest is being able to prove the purchase if Amazon raises queries or in the event of a dispute.
- Recipients: Amazon (Amazon Appstore, billing and purchase verification) as an independent controller; Google (Cloud Firestore and Cloud Functions, Frankfurt am Main) as our processor. For the transfer to the USA, see section 6.
- Retention: we delete the subscription state together with your account. We keep the receipt ID and the Amazon user ID as long as your account exists, so that we can verify renewals, cancellations and refunds and restore purchases. When your account is deleted, we remove both from the purchase record and detach it from your account. We keep the remainder, without identifiers, as long as we need it as proof towards Amazon.
- Cancelling, withdrawal, refunds: you cancel the subscription in your Amazon account under Your Apps, Subscriptions. You can declare the withdrawal to us by email or to Amazon; Amazon carries out the refund, otherwise we do (section 4a.3 of the terms of use). Deleting your account does not end the subscription.
4.8 Playback log in your account (only with consent)
- Data: names of channels watched with time, switches to a lighter version of a channel, technical measurements such as buffering and error events, buffer level and hints shown, Wi-Fi signal strength and link speed (not the network name or address), whether all permitted streams of your plan are in use as reported by your provider, device, platform and app version, stored under the device identifier from section 4.2. Stream addresses containing access data are blacked out before storage. No location data.
- Purpose: seeing measurements from all your devices in one place and narrowing down stuttering (QORA Ultra).
- Legal basis: your consent (Art. 6(1)(a) GDPR, § 25(1) TDDDG).
- Recipient: Google (Cloud Firestore, Frankfurt am Main).
- Retention: until you clear the log, withdraw your consent or delete your account; after QORA Ultra ends, at most 12 months (section 4.19).
- Withdrawal: at any time in the app under Settings, App, Privacy. Withdrawal applies to the future.
4.9 Playback report to support and stutter analysis
With QORA Ultra you can send a playback report to our support. It includes the stutter assessment: you receive an answer, usually within 24 hours on working days.
- Data: account identifier, your verified email address as reply address, the report (as in section 4.8, access data blacked out), device name, app version, time of receipt and the targeted response time.
- Purpose: reviewing your report and answering you.
- Legal basis: Art. 6(1)(b) GDPR.
- Recipients: Google (Cloud Functions and Cloud Firestore, Frankfurt am Main). The report is also sent by email through an encrypted mail server to our mailbox support@qoraplayer.com at our mail provider united domains GmbH (Germany).
- Retention: in the database we delete the report automatically 90 days after receipt, immediately if you delete your account. The email with the report is also stored in our mailbox. Deleting your account does not remove it automatically. We delete it no later than twelve months after receipt, and immediately at your request to support@qoraplayer.com, unless a statutory retention obligation prevents this.
Report a problem (all tiers, including Free). With an account you can report a problem in the help section. In the current app version this feature is still switched off; it will appear with a later update. The report is short: app version, device manufacturer and model, device type (phone, tablet or TV), Android version with API level, whether your access is Xtream or M3U, the traffic light of your last connection test since the app was started ("unknown" if there was none), the last error text and the last ten lines of the playback log. The address of your provider, user name and password are not included; we remove them in the app and once more on our server. You receive a ticket number. If your email address is verified, we also send it to you by email. At most three reports per account are possible within 24 hours of the first report; in addition, a daily limit applies to all accounts combined. With the report we also store your account identifier, your verified email address (if any), your tier and the time of receipt; these details are also included in the email to our mailbox. Purpose, legal basis, recipients and storage period are the same as above. Automatic pre-sorting by an automation service is planned but currently switched off; it would receive the report with ticket number, tier and time of receipt, but without account identifier and without email address.
4.10 Crash reports (only with consent)
- Data: technical course of the crash, app state, device model, Android version, free memory and a random identifier of the installation for crash reports, plus technical session information (app, device, duration of use).
- Purpose: finding and fixing errors.
- Legal basis: your consent (Art. 6(1)(a) GDPR, § 25(1) TDDDG). Without your consent, collection is switched off.
- Recipient: Google (Firebase Crashlytics) as our processor. Crashlytics is operated worldwide, including in the USA (section 6).
- Retention: 90 days.
- Withdrawal: at any time in the app under Settings, App, Privacy. Reports not yet sent are discarded. On request to support@qoraplayer.com we delete reports already sent before the end of that period.
4.11 Technical base data of the Google components
The app uses program components from Google Firebase. They only become active when you use an account or agree to crash reports or usage statistics; before that they send nothing to Google. They then create a random installation identifier and send it to Google together with the IP address and device and app information when they contact Firebase. For server calls (for example purchase verification or support reports) the name of the function called and a technical device token from Google (messaging token) are added. QORA does not use push notifications.
- Purpose: operating the Firebase services, assigning calls, protection against misuse.
- Legal basis: with an account Art. 6(1)(b) GDPR where the data is needed for account, sync or purchase, otherwise Art. 6(1)(f) GDPR (secure operation); without an account your consent to crash reports (section 4.10) or to usage statistics (section 4.22). Storing the identifier on your device is strictly necessary for these services (§ 25(2) no. 2 TDDDG).
- Recipient: Google (Firebase) as our processor.
- Retention: until the installation is deleted, that is at the latest when the app is uninstalled.
4.12 QR scanner
To scan a pairing code, QORA uses the Google Code Scanner from Google Play services. It only starts when you start a scan; before that it sends nothing. The scanner processes the camera image on your device; QORA itself has no camera permission. According to Google, it then receives device information (manufacturer, model, Android version, build), package name and app version, a technical identifier of the device or installation that is not meant to identify a person, performance and latency values, image format and resolution, the type of event (for example start or detection) and error codes. According to Google the transfer is encrypted (HTTPS) and not passed on to third parties. You can avoid it only by not starting the scan; you can also read the code with your phone's camera app or type it in.
- Purpose: operating the scanner, diagnostics and usage analytics by Google.
- Legal basis: Art. 6(1)(b) GDPR (you start the scan yourself). Access to device information is strictly necessary for the scan you start (§ 25(2) no. 2 TDDDG).
- Recipient: Google (ML Kit through Google Play services).
- Retention: determined by Google, see Google's privacy policy.
4.13 Casting to a Cast device
For streaming to a Google Cast device (for example Chromecast or a TV with Google TV), QORA uses Google's Cast library. On phone and tablet it starts as soon as you open a channel, film or episode, even without an account and even if you do not cast. According to Google it then sends data about device discovery and Cast sessions and information about your device and the app's Cast feature to a Google server. Google describes the data as anonymous, encrypts it in transit, keeps it only briefly, aggregates it before deletion and does not pass it on to third parties. Google's purpose: monitor use and performance of the library, detect errors, improve Cast. According to Google neither you nor we can switch this off. On TV we do not call the library.
When you cast, QORA passes the stream address to your Cast device. Depending on your provider, this address contains your access data (username and password). The Cast device uses it to fetch the stream directly from your provider; a receiver app from Google runs on the device for this. Google does not disclose whether it processes the address in doing so. We do not receive it.
- Legal basis: Art. 6(1)(b) GDPR when you cast, otherwise Art. 6(1)(f) GDPR. Our legitimate interest is working Cast support that can detect a Cast device in the network without you having to switch it on first.
- Recipient: Google (Google Play services) under its own responsibility.
- Retention: according to Google it keeps the data only briefly and aggregates it before deletion. The exact period is determined by Google, see the Google Privacy Policy.
4.14 Misuse protection and server logs
- Data: a counter per account and purpose (purchase verification at most 20 calls per hour, withdrawal at most 10 per hour, support reports at most 5 per day, problem reports at most 3 per day) with the start of the time window and the number of calls; for support reports and problem reports also a checksum of the content, the number and the time of the last request, so that a repeated call is not counted twice. In the logs of our server functions, individual messages contain a shortened fingerprint (SHA-256) of the account identifier and of the purchase token, reference numbers, and error codes and error messages. No reports, no access data. We also keep daily counters without account reference, for example how many accounts or subscriptions were added or ended on a day and how many problem reports arrived in total on a day (a shared limit for all accounts). They contain no identifier and no information about individual persons.
- Authenticity check (App Check): The version from Google Play attaches a Google Play Integrity token to requests to our servers (sign-in, database, server functions). It shows that the request comes from an unmodified QORA from Google Play. Google checks device and app information for this; we only receive the result of the check, no device data.
- Purpose: preventing misuse, securing operation, finding errors.
- Legal basis: Art. 6(1)(f) GDPR.
- Recipient: Google (Cloud Firestore and Cloud Logging).
- Retention: per-account counters until the account is deleted, daily counters without account reference without a deletion deadline; server logs 30 days under Google Cloud's default setting.
4.15 Voice search
Next to the search field you can search by microphone if your device offers voice input. Voice search only starts when you select the microphone. Recording and recognition are handled by your device's voice input, depending on the device Google, the device manufacturer or another provider, under its own responsibility. Depending on the device, the provider evaluates the recording on your device or on its servers. For this, QORA asks for your device's microphone permission the first time. It only listens while voice search is running (the microphone glows gold), for about 15 seconds at most. QORA stores no recording, receives only the recognised text and uses it solely for searching in the app. You can withdraw the permission at any time in the Android settings. The recognised text stays on your device; QORA does not send it to us.
- Purpose: searching by voice.
- Legal basis: Art. 6(1)(b) GDPR (you start voice search yourself). Accessing the microphone and taking over the recognised text are strictly necessary for the search you requested (Section 25(2) No. 2 TDDDG).
- Recipients: none on our part. What your device's voice input processes is governed by its provider's privacy notice.
- Retention: none with us; with the voice input provider according to its rules.
4.16 Data only on your device
The app stores access data, lists, favourites, progress, profiles, parental control, the playback log and the device identifier from section 4.2 on your device. This data leaves the device only in the cases described above. Storing it and reading the Android ID are strictly necessary for the app you use (§ 25(2) no. 2 TDDDG). It remains until you delete it in the app or uninstall the app.
4.17 Withdrawing from the contract
If you bought QORA Ultra through Google Play, you can withdraw from the contract within the withdrawal period with the "Vertrag widerrufen" (withdraw from contract) function in the app (for its location see section 6 of the terms of use). For withdrawal from a purchase through the Amazon Appstore, see section 4.7a. You can also declare the withdrawal by email to support@qoraplayer.com.
- Data: your name (as you enter it), the contract designation (plan and purchase date), the Google Play order number, the end of the withdrawal period, an irreversible check value of your purchase, date and time of receipt, an identifier of the process, the state of the acknowledgement of receipt (sending, message identifier, reply of the mail server) and the state of the refund (status, time, error code). For the acknowledgement of receipt we use the email address of your account. For every withdrawal we also send an internal notice email to our support mailbox (plan, start of the account identifier, order number, time of receipt, state of the refund, without your name and your email address) so that the refund can be checked. We delete this notice email like other support emails at the latest twelve months after receipt.
- Purpose: receiving your withdrawal, confirming its receipt, triggering the refund and proving both.
- Legal basis: Art. 6(1)(c) GDPR (§ 356a German Civil Code, in Austria § 13a FAGG; acknowledgement of receipt) and Art. 6(1)(f) GDPR (legitimate interest in proving timely refund and confirmation and in defending legal claims). Keeping the record after an account deletion rests on Art. 17(3)(e) GDPR.
- Recipients: Google (Cloud Functions and Cloud Firestore, Frankfurt am Main) as our processor; Google Play, which carries out the refund; our mail provider (encrypted mail server) for the acknowledgement of receipt and the notice email.
- Retention: we keep the record as proof until the end of the third year after the year in which you withdrew (sections 195, 199 German Civil Code) and then delete it. Deleting your account does not end this retention. Until then the record still contains your name and the former account identifier and is used only as proof.
4.18 Welcome email and QORA Ultra to try, 14 days from your first channel
When you create an account, it gets all features of QORA Ultra once for 14 days, without a purchase and without payment details. The 14 days run from your first channel: they start when a channel, a film or an episode plays with your account for at least ten seconds for the first time. Until then you can already use QORA Ultra, for example to set things up, for at most 90 days after your account was created. At that moment the app tells our server once that the first playback is running, without names of channels or programmes. The server then sets the end of the trial to 14 days later. After that the free version applies automatically; nothing is charged and no subscription is created. We also send you one welcome email in the language of your account (section 4.20).
Once the 14 days are running, the app reminds you of the end of the trial: three days before with a notification on phone and tablet and a notice on the home screen, one day before with a notification, and after the trial has ended with a notice in the app. If you have not allowed QORA to show notifications, you only see the reminders as a notice in the app. You did not ask for these notifications yourself, so the app shows at most two of them in seven days on a device, and none while a playback has failed and none has run since. If a notification is dropped for this reason, the notice in the app remains. Programme reminders you set yourself do not count. The app schedules these reminders itself on your device, from the trial end stored in your account. It sends nothing to us for this, and there is no push message through a server. Whether notifications appear is up to your Android settings for QORA.
- Data: the time your account was created, the state of the trial (waiting for your first playback or running), its start and its end, and the state of the welcome email (whether, when and with what result it was sent: message identifier, reply of the mail server, an error code if it failed). For sending we use the email address of your account; if you signed up with email and password, only after you have confirmed the address. We do not store the address a second time for this. On your device the app remembers that the start of the trial has been confirmed, so that it reports it only once.
- Content of the email: where QORA runs, how to get started, sync and pairing, the trial, notes on purchases and on help. It is a service email without advertising; we do not send further emails of this kind.
- Purpose: explaining how to get started, providing the trial, starting the 14 days only with your first playback, granting the trial only once per account and reminding you of its end in good time.
- Legal basis: Art. 6(1)(b) GDPR (contract of use).
- Recipients: Google (Firebase Authentication, operated worldwide, see sections 5 and 6; Cloud Functions and Cloud Firestore, Frankfurt am Main) as our processor; our mail provider (encrypted mail server) for sending.
- Retention: until you delete your account. If sending fails, we try at most five times; the email waits at most seven days for a confirmed address.
4.19 Paused data after QORA Ultra ends and deletion after 12 months
When the trial or your subscription ends, at first we delete nothing. The data in your account from sections 4.2 to 4.4 and 4.8 stays stored but is no longer synced. That way everything is back right away if you book QORA Ultra again. If you stay on the free plan, we delete this data 12 months after your last access to QORA Ultra ends. 30 days before, you receive a notice in the app and, if your account has a confirmed email address, an email. We do not keep a block for pairing devices (section 4.5); as described there, it is deleted no later than about 20 minutes after it was created.
- Data: lists including encrypted access data, the sync state of your devices, profiles and, if you consented, the playback log; in addition the end of your last access to QORA Ultra, the times of the notice and the deletion, and the state of the notice email (whether, when and with what result it was sent: message identifier, reply of the mail server). For the notice email we use the email address of your account, only if it is confirmed. Without a confirmed address we send no email; the notice in the app remains.
- Purpose: keeping your data ready for a return to QORA Ultra, informing you in good time before deletion and deleting data we no longer need after that.
- Legal basis: for lists, sync state and profiles as well as for the notice and the deletion, Art. 6(1)(f) GDPR. Our legitimate interest is to let you return to QORA Ultra without setting everything up again and to inform you before the deletion. You can object (section 8) or delete the data yourself at any time (section 7). For the playback log, your consent remains the basis (Art. 6(1)(a) GDPR, section 4.8). If you withdraw it, we delete the log.
- Recipients: Google (Cloud Firestore and Cloud Functions, Frankfurt am Main) as our processor; our mail provider (encrypted mail server) for the notice email.
- Retention: 12 months after your last access to QORA Ultra ends, from the trial or a subscription. If you book again before that, the period only starts with the next end. Your account (section 4.1) and the subscription state (section 4.7) remain until you delete the account or we delete it after 12 months without use (section 4.21), as do the times of notice and deletion, so that we do not write to you twice.
4.20 Language of your account
We send emails to you in German, English or French, in the language in which the app is shown on your device. This applies to the welcome email (section 4.18), the contract confirmation (section 4.7), the confirmation of receipt of a withdrawal (section 4.17), the ticket number of a problem report (section 4.9) and the notices before a deletion (sections 4.19 and 4.21). For this, the app stores the language in your account, also on the free plan. The emails for confirming your address and for your password are sent by Firebase (section 4.1).
- Data: the language (German, English or French) and the time at which the app last stored it. The app stores it after a sign-in and when the language of the app changes. If no language is stored, we write to you in German.
- Purpose: sending you the emails about your contract and your account in your language.
- Legal basis: Art. 6(1)(b) GDPR (contract of use).
- Recipient: Google (Cloud Firestore and Cloud Functions, Frankfurt am Main) as our processor.
- Retention: until you delete your account or we delete it under section 4.21. After QORA Ultra ends, the language stays stored so that the notices from sections 4.19 and 4.21 also reach you in your language.
4.21 Deletion of accounts that have not been used for 12 months
If you have no current access to QORA Ultra and do not use your account for 12 months, we delete it. The 12 months start with your last use, but no earlier than the end of your last access to QORA Ultra. Use means that you sign in or use the app with your account; we see this from the time at which the app last renewed your sign-in. 30 days before the deletion we send you an email if your account has a confirmed email address. If you use the account during this time, we delete nothing, and the 12 months start again. We never delete an account in this way while it has a current subscription, a current trial or other access to QORA Ultra.
The deletion works like a deletion of the account by you (section 7): the account and all data in it. We detach purchase records from your account (section 4.7), and we keep a withdrawal record as described in section 4.17. The data on your devices is not affected; QORA keeps running there on the free plan.
- Data: the times of creation, last sign-in and last renewal of the sign-in that Firebase Authentication keeps for your account anyway, the end of your last access to QORA Ultra, the planned deletion date and the state of the notice email (whether, when, in which language and with what result it was sent: message identifier, reply of the mail server, an error code if it failed). For the email we use the email address of your account, only if it is confirmed. Without a confirmed address we send no email and delete on the same date.
- Purpose: not keeping accounts and data that nobody uses any more, and informing you in good time beforehand.
- Legal basis: Art. 6(1)(f) GDPR. Our legitimate interest is not to store data longer than necessary (storage limitation, Art. 5(1)(e) GDPR) and to inform you before the deletion. If you want to keep your account, it is enough to open QORA with your account.
- Recipients: Google (Firebase Authentication, operated worldwide, see sections 5 and 6; Cloud Functions and Cloud Firestore, Frankfurt am Main) as our processor; our mail provider (encrypted mail server) for the notice email.
- Retention: We delete this information together with the account. Every period above that runs until your account is deleted also ends with this deletion.
4.22 Usage statistics with Firebase Analytics (only with consent)
If you agree, QORA uses Firebase Analytics to measure how the app is used: whether setup works, how quickly the first playback succeeds and whether reminders and notices help. The app asks you with a separate switch, next to the questions on crash reports and the playback log. Without your consent, collection is switched off and the app sends nothing to Firebase Analytics.
These ten events are measured, each only with the details named. Firebase Analytics records the first one by itself, QORA reports the others:
| Event | When | Details |
|---|---|---|
| first_open | first start after installation | none beyond the data below |
| setup_step | a setup step starts or ends | step, result, method (such as QR code or by hand), type of access (Xtream or M3U), type of error, duration |
| playback_success | a playback is running | whether it is the first, type (live, programme from the archive, film or episode), time until the picture appears, rough level of interruptions |
| trial_state | the trial starts or ends | state, duration, whether a playback ran before the end |
| upgrade_view | the offer for QORA Ultra is shown | occasion, plan shown |
| subscription_state | our server confirms a new state of your subscription, such as purchase, renewal, payment problem or end | state, plan, origin (Google Play, trial or granted by us) |
| notification_permission | the app asks for permission to show notifications | stage, result, occasion, Android version |
| lifecycle_message | a reminder or notice from the app is shown or opened | stage (shown or opened), type, way of delivery (notification or notice in the app) |
| habit_action | you add a favourite, a profile or a paired device | type, whether for the first time, rough number of your devices |
| cancel_feedback | you voluntarily give a reason for cancelling in the app | reason from a list, plan, rough length of your subscription |
- Data: the events above; in addition, from Firebase Analytics itself, a random installation identifier for Analytics, device model, Android version, app version, language setting, an approximate location (country, region and city) that Google derives from the IP address, as well as sessions and their duration, screen views, purchases and subscriptions through Google Play with product and price, updates of the app and of Android, and removal of the app. Never recorded: your provider's access data (user name, password), server and list addresses, PINs, names of channels, films, series or programmes, your email address and your account identifier. QORA does not read your device's advertising ID.
- Purpose: improving QORA: seeing where setup gets stuck, how many people reach the first playback, how the trial and the subscription are received and whether reminders help or get in the way. No advertising and no advertising profiles result from it.
- Legal basis: your consent (Art. 6(1)(a) GDPR), also for storing the identifier on your device and reading information from your device (§ 25(1) TDDDG). Without your consent, collection is switched off.
- Recipient: Google (Google Analytics for Firebase) as our processor under Google's data processing terms for measurement and advertising services (Google Ads Data Processing Terms). Google processes the data worldwide, including in the USA (section 6). We have switched off sharing this data with Google for Google's own purposes.
- Retention: 2 months for events with the identifier of your installation; this is how it is set in Firebase. Aggregated reports without reference to you can remain longer.
- Withdrawal: at any time in the app under Settings, App, Privacy. The app then switches collection off immediately and sends no further events.
4.23 Rating through Google Play
After you have used QORA for a while, the app may ask you for a rating, at most every 60 days on a device and never in a session with a playback error. Google Play shows the window for this itself (in-app review), and Google decides whether it appears. Stars and text go to Google Play and appear publicly in the store listing, like any rating there. We do not learn from the app whether or how you rated. On TVs without this window, the app shows a notice with a QR code to the store listing once; the code only contains its address.
- Data: on your device, when the app last asked, the number of longer playbacks and, on a TV, whether the notice with the QR code has already been shown. These markers apply per device and do not leave it. When the app asks whether the rating window can appear, it contacts Google Play through the Play Store app. Whatever Google Play receives in the process, Google processes under its own responsibility.
- Legal basis: Art. 6(1)(f) GDPR. Our legitimate interest is to receive feedback in the store without disturbing you. The markers on your device make sure the app rarely asks and shows the notice on a TV only once. Storing them is strictly necessary for this (§ 25(2) no. 2 TDDDG). You submit the rating itself to Google, which processes it under its own responsibility according to the Google Privacy Policy.
- Recipient: Google Play, with every request from the app for the rating window and with your rating.
- Retention: the information stays on your device until you uninstall QORA or clear its app data.
4.24 Translation of descriptions
Only on phones and tablets, not on TVs. If your provider delivers the description of a film or series in a language other than the one QORA runs in on your device (your device language or the language chosen for QORA in Android), QORA translates it into that language when you open the film or series page, provided the language is reliably detected and ML Kit supports both languages. This is controlled by the "Translate descriptions" switch in the settings under Extra features. It is on by default. If it is on, the app detects the language of every description it has not yet stored in translated form. If it is off, it detects no language and downloads no language pack. Language detection and translation run on your device with Google ML Kit; the text of the description does not leave your device. For each language, the app downloads a language pack of about 30 MB from Google's servers once, the first time it is needed, and only over a network without data metering such as Wi-Fi or LAN. Every translation is labelled "Automatically translated · powered by Google Translate", and a tap shows the original.
- Data: according to Google, it receives technical data similar to that of the QR scanner (section 4.12): device information (manufacturer, model, Android version, build), package name and app version, a per-installation identifier that is not meant to uniquely identify a person or a device, performance values, input and output size, the type of event (for example the download of a language pack) and error codes. In addition, the detected language and the configured language pair. According to Google, ML Kit also uses Firebase Remote Config and Firebase Installations for its own configuration. According to Google, the transfer is encrypted (HTTPS) and the data is not passed on to third parties. On your device, the app stores the language packs and up to 500 translated descriptions so that the same text is not translated again.
- Purpose: showing descriptions in your language; at Google, operation, diagnostics and usage analytics of ML Kit.
- Legal basis: Art. 6(1)(b) GDPR (translation is a feature of the app that you use and can switch off in the settings). Storing language packs and translations on your device and accessing device information are strictly necessary for this feature (§ 25(2) no. 2 TDDDG).
- Recipient: Google (ML Kit), under its own responsibility according to the Google Privacy Policy.
- Retention: language packs and translations stay on your device until you uninstall QORA or clear its app data; the translations are kept in the cache, which Android may also clear earlier. Whatever Google receives, Google stores according to its own rules, see Google's privacy policy.
4.26 Login occupancy and "End live"
Only with Plus or Ultra and only if you have added several logins from your provider. So that two of your devices do not use the same login at the same time, a device reports in your account which login it is currently using for live TV, a film or a series. If other devices hold all of your logins, the app shows the device's name and a button that ends playback there. This only works while the app is open on the other device and it has a network connection. QORA changes nothing at your provider.
- Data: for occupancy, one entry per device under its device identifier: a fingerprint of the login (16 characters, calculated from server, port and username; the username and password themselves are not included), the expiry time and the time of the last change. For "End live", one entry per target device under its device identifier: the type of command, the name of the sending device, the expiry time and the time of the last change.
- Purpose: avoiding interruptions caused by logins used twice and letting you free an occupied login on one of your devices.
- Legal basis: Art. 6(1)(b) GDPR (a feature of the app that you use).
- Recipient: Google as our processor (Cloud Firestore, section 5).
- Retention: an occupancy entry is valid for 5 minutes, is renewed during playback and is deleted when playback ends. A command is valid for 60 seconds and is deleted as soon as the target device has followed it. An entry left over after that, for example after a crash or because the target device could not be reached, no longer has any effect and stays in your account until a new one replaces it or you delete your account (section 7).
4.27 Trailers from YouTube
If your provider lists a trailer for a film or series, QORA shows a "Trailer" button. Only when you tap it does the app load YouTube's embedded player (youtube-nocookie.com and youtube.com). If that fails, QORA opens the trailer in the YouTube app or in the browser. Kids profiles have no trailers.
- Data: IP address, device and browser details (user agent), the video ID and, as origin, the address qoraplayer.com. YouTube may store cookies or similar identifiers in the storage of QORA's trailer view.
- Purpose: playing the trailer at your request.
- Legal basis: Art. 6(1)(b) GDPR (a feature of the app you use). Anything YouTube stores on or reads from your device in the process is necessary for the trailer you requested (Section 25(2) No. 2 TDDDG).
- Recipient: Google Ireland Limited (YouTube), as an independent controller under Google's privacy policy.
- Retention: QORA stores none of this on its own servers. Google stores what it receives according to its own rules.
4.28 Subtitle search on OpenSubtitles
Only if you sign in with your own OpenSubtitles.com account in the player under Subtitles. Without signing in, QORA sends nothing to OpenSubtitles.
- Data: username and password of your OpenSubtitles account for signing in; for each search the title, the year or TMDB number of the film, for series the season and episode, and the language you want; when downloading, the ID of the selected subtitle; plus IP address and app details. QORA stores the username and password encrypted on your device only, never on our servers.
- Purpose: searching for and loading subtitles at your request.
- Legal basis: Art. 6(1)(b) GDPR (a feature of the app you use).
- Recipient: OpenSubtitles.com, as an independent controller under OpenSubtitles' privacy policy.
- Retention: The sign-in details remain on your device until you sign out, uninstall QORA or clear the app data. OpenSubtitles stores what it receives according to its own rules.
5. Processors and other recipients
- Google Ireland Limited (Gordon House, Barrow Street, Dublin 4, Ireland) with Google LLC (USA): Firebase Authentication, Cloud Firestore, Cloud Functions, Firebase Crashlytics, Google Analytics for Firebase, Firebase Installations, Cloud Logging. Google processes this data as our processor under the Firebase and Google Cloud data processing terms, and for Google Analytics for Firebase under the Google Ads Data Processing Terms. Database and server functions run in the europe-west3 region (Frankfurt am Main). Authentication, Crashlytics and Analytics are operated worldwide.
- Google Play (distribution, billing including the purchase library, in-app review, Install Referrer), Google account sign-in (device code confirmation on Fire TV, section 4.1), Google Play services (QR scanner, Cast) and Google ML Kit (translation of descriptions, section 4.24): Google operates these services under its own responsibility according to the Google Privacy Policy.
- Amazon (Amazon Appstore on Fire TV: distribution, billing and purchase verification, section 4.7a): Amazon processes this data as an independent controller according to the Amazon Privacy Notice.
- YouTube (Google Ireland Limited): only if you tap a trailer (Section 4.27), as an independent controller.
- OpenSubtitles.com: only if you use the subtitle search with your own account (Section 4.28), as an independent controller.
- united domains GmbH (Germany): website hosting and email mailbox.
- WhatsApp Ireland Limited: only if you write to us via WhatsApp.
We do not sell data and do not pass it on for advertising.
6. Transfers to third countries
Google LLC is based in the USA. Even with storage in Frankfurt, Google companies in the USA may access data, for example for maintenance and operation, and some services (Authentication, Crashlytics, Analytics) also process data there. Google LLC is certified under the EU-US Data Privacy Framework. For the USA there is therefore an adequacy decision of the European Commission of 10 July 2023 (Art. 45 GDPR). For transfers not covered by it, the EU standard contractual clauses in Google's data processing terms apply (Art. 46(2)(c) GDPR).
For purchase verification when you buy through the Amazon Appstore (section 4.7a), our server sends your Amazon user ID and the receipt ID to Amazon's verification service. It may be operated by companies of the Amazon.com group in the USA. Amazon.com, Inc. and its US subsidiaries, including Amazon.com Services LLC, are certified under the EU-US Data Privacy Framework and the Swiss-U.S. Data Privacy Framework; the adequacy decision of 10 July 2023 therefore applies here as well (Art. 45 GDPR, for Switzerland Art. 16(1) FADP).
For users in Switzerland: We disclose personal data to these countries: Ireland (Google Ireland Limited) and Germany (data centre in Frankfurt am Main), which provide adequate data protection under Annex 1 of the Swiss Data Protection Ordinance, and the USA (Google LLC; for a purchase through the Amazon Appstore also companies of the Amazon.com group). Google LLC and Amazon.com, Inc. with its US subsidiaries are certified under the Swiss-U.S. Data Privacy Framework; for certified organisations adequate protection applies (Art. 16(1) FADP, Annex 1 DPO). According to its own information, Google operates Firebase Authentication, Crashlytics and Analytics in data centres in several countries, including the USA; Google lists the locations at cloud.google.com/about/locations. Where data reaches countries without adequate data protection, we rely on the standard contractual clauses in Google's data processing terms, which the FDPIC recognises with adaptations for Switzerland (Art. 16(2)(d) FADP).
7. Deleting your account
You can delete your account yourself at any time:
- in the app under Settings, Account, "Delete account" (confirmed with your password for an email account)
- on the website at /en/delete-account/
- by email to support@qoraplayer.com if you can no longer sign in. Please write from your account's address so that we can check that the request comes from you.
On deletion we immediately remove your account, your lists including encrypted access data, the sync state of all devices, profiles, logs, open pairings, login occupancy and commands to your devices (section 4.26), the subscription state, your support reports in the database and the per-account counters from section 4.14. We detach purchase records from your account (sections 4.7 and 4.7a); for a purchase through Amazon we also delete the receipt ID and the Amazon user ID.
After the trial or subscription ends, we also delete the data in your account on our own after 12 months (section 4.19). An account without current access to QORA Ultra that has not been used for 12 months is deleted entirely. If it has a confirmed email address, you receive an email 30 days before (section 4.21).
Not deleted automatically:
- A withdrawal record (section 4.17): we keep it as proof until the end of the third year after the year of the withdrawal (Art. 17(3)(e) GDPR) and then delete it.
- Emails in our support mailbox, that is support reports (section 4.9) and your own messages to us (section 3.4). We delete them no later than twelve months after receipt. Write to us if you want them deleted immediately; if you ask us by email to delete your account, we do this at the same time, unless a statutory retention obligation prevents it.
- Crash reports (section 4.10): they expire after 90 days; we delete them earlier on request.
- Server logs (section 4.14): they expire after 30 days.
You cancel your subscription where you bought it: in Google Play or, on Fire TV, in your Amazon account under Your Apps, Subscriptions. Deleting your account does not end a running subscription.
8. Your rights
You have the right of access (Art. 15 GDPR), rectification (Art. 16 GDPR), erasure (Art. 17 GDPR), restriction of processing (Art. 18 GDPR) and data portability (Art. 20 GDPR). You can withdraw consent at any time with effect for the future (Art. 7(3) GDPR).
Right to object: where we process data on the basis of our legitimate interest (Art. 6(1)(f) GDPR), you may object at any time on grounds relating to your particular situation (Art. 21 GDPR).
If you live in Switzerland, you also have the rights under the Swiss Federal Act on Data Protection, in particular access (Art. 25 FADP, free of charge and as a rule within 30 days), data release or transfer (Art. 28 FADP) and rectification, erasure and objection (Art. 32 FADP). You can file a report with the Federal Data Protection and Information Commissioner (FDPIC), Feldeggweg 1, 3003 Bern (Art. 49 FADP).
For all requests an email to support@qoraplayer.com is sufficient.
You can also lodge a complaint with a data protection supervisory authority. In Austria this is the Datenschutzbehörde (Barichgasse 40 to 42, 1030 Vienna), in Liechtenstein the Datenschutzstelle (Kirchstrasse 8, Postfach 684, FL-9490 Vaduz), in Luxembourg the Commission nationale pour la protection des données (CNPD, 15, Boulevard du Jazz, L-4370 Belvaux), in Switzerland the FDPIC (see above). The authority responsible for us is:
Der Landesbeauftragte für den Datenschutz und die Informationsfreiheit Rheinland-Pfalz
Hintere Bleiche 34
55116 Mainz
Germany
9. Obligation to provide data, no automated decisions
You are not obliged to give us data. Without an account you can use QORA in the free plan on one device. For QORA Ultra, including the trial, we need the account data from section 4.1. We do not make automated decisions, including profiling, within the meaning of Art. 22 GDPR. QORA may be used from the age of 18. Child profiles are a feature for parents.
10. Changes
If the processing changes, we update this policy. The version published here with the date above applies.