Privacy Policy

We are very delighted that you have shown interest in our enterprise. Data protection is of a particularly high priority for the management of the mystage.fm. The use of the Internet pages and mobile apps of the mystage.fm is possible without any indication of personal data; however, if a data subject wants to use special enterprise services via our website or mobile apps, processing of personal data could become necessary. If the processing of personal data is necessary and there is no statutory basis for such processing, we generally obtain consent from the data subject.

The processing of personal data, such as the name, address, e-mail address, or telephone number of a data subject shall always be in line with the General Data Protection Regulation (GDPR), and in accordance with the country-specific data protection regulations applicable to the mystage.fm. By means of this data protection declaration, our enterprise would like to inform the general public of the nature, scope, and purpose of the personal data we collect, use and process. Furthermore, data subjects are informed, by means of this data protection declaration, of the rights to which they are entitled.

As the controller, the mystage.fm has implemented numerous technical and organizational measures to ensure the most complete protection of personal data processed through this website and our mobile apps. However, Internet-based data transmissions may in principle have security gaps, so absolute protection may not be guaranteed. For this reason, every data subject is free to transfer personal data to us via alternative means, e.g. by telephone.

1. Definitions

The data protection declaration of the mystage.fm is based on the terms used by the European legislator for the adoption of the General Data Protection Regulation (GDPR). Our data protection declaration should be legible and understandable for the general public, as well as our customers and business partners. To ensure this, we would like to first explain the terminology used.

In this data protection declaration, we use, inter alia, the following terms:

a) Personal data

Personal data means any information relating to an identified or identifiable natural person (“data subject”). An identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person.

b) Data subject

Data subject is any identified or identifiable natural person, whose personal data is processed by the controller responsible for the processing.

c) Processing

Processing is any operation or set of operations which is performed on personal data or on sets of personal data, whether or not by automated means, such as collection, recording, organisation, structuring, storage, adaptation or alteration, retrieval, consultation, use, disclosure by transmission, dissemination or otherwise making available, alignment or combination, restriction, erasure or destruction.

d) Restriction of processing

Restriction of processing is the marking of stored personal data with the aim of limiting their processing in the future.

e) Profiling

Profiling means any form of automated processing of personal data consisting of the use of personal data to evaluate certain personal aspects relating to a natural person, in particular to analyse or predict aspects concerning that natural person's performance at work, economic situation, health, personal preferences, interests, reliability, behaviour, location or movements.

f) Pseudonymisation

Pseudonymisation is the processing of personal data in such a manner that the personal data can no longer be attributed to a specific data subject without the use of additional information, provided that such additional information is kept separately and is subject to technical and organisational measures to ensure that the personal data are not attributed to an identified or identifiable natural person.

g) Controller or controller responsible for the processing

Controller or controller responsible for the processing is the natural or legal person, public authority, agency or other body which, alone or jointly with others, determines the purposes and means of the processing of personal data; where the purposes and means of such processing are determined by Union or Member State law, the controller or the specific criteria for its nomination may be provided for by Union or Member State law.

h) Processor

Processor is a natural or legal person, public authority, agency or other body which processes personal data on behalf of the controller.

i) Recipient

Recipient is a natural or legal person, public authority, agency or another body, to which the personal data are disclosed, whether a third party or not. However, public authorities which may receive personal data in the framework of a particular inquiry in accordance with Union or Member State law shall not be regarded as recipients; the processing of those data by those public authorities shall be in compliance with the applicable data protection rules according to the purposes of the processing.

j) Third party

Third party is a natural or legal person, public authority, agency or body other than the data subject, controller, processor and persons who, under the direct authority of the controller or processor, are authorised to process personal data.

k) Consent

Consent of the data subject is any freely given, specific, informed and unambiguous indication of the data subject's wishes by which he or she, by a statement or by a clear affirmative action, signifies agreement to the processing of personal data relating to him or her.

2. Name and Address of the controller

Controller for the purposes of the General Data Protection Regulation (GDPR), other data protection laws applicable in Member states of the European Union and other provisions related to data protection is:

3. Cookies

The Internet pages of the mystage.fm use cookies. Cookies are text files that are stored in a computer system via an Internet browser.

Many Internet sites and servers use cookies. Many cookies contain a so-called cookie ID. A cookie ID is a unique identifier of the cookie. It consists of a character string through which Internet pages and servers can be assigned to the specific Internet browser in which the cookie was stored. This allows visited Internet sites and servers to differentiate the individual browser of the dats subject from other Internet browsers that contain other cookies. A specific Internet browser can be recognized and identified using the unique cookie ID.

Through the use of cookies, the mystage.fm can provide the users of this website with more user-friendly services that would not be possible without the cookie setting.

By means of a cookie, the information and offers on our website can be optimized with the user in mind. Cookies allow us, as previously mentioned, to recognize our website users. The purpose of this recognition is to make it easier for users to utilize our website. The website user that uses cookies, e.g. does not have to enter access data each time the website is accessed, because this is taken over by the website, and the cookie is thus stored on the user's computer system. Another example is the cookie of a shopping cart in an online shop. The online store remembers the articles that a customer has placed in the virtual shopping cart via a cookie.

The data subject may, at any time, prevent the setting of cookies through our website by means of a corresponding setting of the Internet browser used, and may thus permanently deny the setting of cookies. Furthermore, already set cookies may be deleted at any time via an Internet browser or other software programs. This is possible in all popular Internet browsers. If the data subject deactivates the setting of cookies in the Internet browser used, not all functions of our website may be entirely usable.

4. Collection of general data and information

The website of the mystage.fm collects a series of general data and information when a data subject or automated system calls up the website. This general data and information are stored in the server log files. Collected may be (1) the browser types and versions used, (2) the operating system used by the accessing system, (3) the website from which an accessing system reaches our website (so-called referrers), (4) the sub-websites, (5) the date and time of access to the Internet site, (6) an Internet protocol address (IP address), (7) the Internet service provider of the accessing system, and (8) any other similar data and information that may be used in the event of attacks on our information technology systems.

When using these general data and information, the mystage.fm does not draw any conclusions about the data subject. Rather, this information is needed to (1) deliver the content of our website correctly, (2) optimize the content of our website as well as its advertisement, (3) ensure the long-term viability of our information technology systems and website technology, and (4) provide law enforcement authorities with the information necessary for criminal prosecution in case of a cyber-attack. Therefore, the mystage.fm analyzes anonymously collected data and information statistically, with the aim of increasing the data protection and data security of our enterprise, and to ensure an optimal level of protection for the personal data we process. The anonymous data of the server log files are stored separately from all personal data provided by a data subject.

5. Processing of personal data when using our apps

We offer various apps through Google Play, the Apple App Store, and, where applicable, other distribution platforms. The personal data processed depends on the app being used and the functions selected by the user.

5.1 General technical data

Where an app establishes a connection to our servers, the following data in particular may be processed:

• IP address of the device used
• user, device, or installation identifier
• date and time of access
• server function or resource accessed
• app version
• operating system and device information
• status and error data

The processing is carried out to provide the requested function, enable communication between the app and the server, identify technical errors, and ensure the security of our systems.

The legal basis is Article 6(1)(b) GDPR where the processing is necessary to provide an app function requested by the user. Processing to ensure security, analyze errors, and prevent misuse is based on Article 6(1)(f) GDPR. Our legitimate interest lies in the secure, stable, and misuse-free operation of our apps and IT systems.

5.2 Google Play and in-app purchases

Our apps are made available through Google Play, among other platforms. The provider of the service for users in the European Economic Area is generally:

When an app is downloaded, updated, or purchased, Google processes personal data under its own responsibility under data protection law. This may include, in particular, Google Account details, device information, the IP address, payment information, and information about downloads and purchases.

For paid apps or in-app purchases, we receive from Google a transaction identifier, a purchase token, the product purchased, the purchase status, and the time of the transaction.

We process purchase information to activate and manage purchased functions on the basis of Article 6(1)(b) GDPR. Where data must be retained to comply with tax or commercial-law obligations, the processing is based on Article 6(1)(c) GDPR.

5.3 Apple App Store and in-app purchases

Our apps are also made available through the Apple App Store. The provider responsible for users in the European Economic Area is:

When an app is downloaded, updated, or purchased, Apple processes personal data under its own responsibility under data protection law. This may include Apple Account details, device information, the IP address, payment information, and information about downloads and purchases.

For paid apps, in-app purchases, or subscriptions, we may receive purchase and receipt information from Apple, including transaction identifiers, the product purchased, the purchase status, and the time of the transaction, as well as subscription status and validity dates where applicable. We do not receive your card or bank details from Apple.

We process purchase information to verify, activate, restore, and manage purchased functions on the basis of Article 6(1)(b) GDPR. Where data must be retained to comply with tax or commercial-law obligations, the processing is based on Article 6(1)(c) GDPR.

Further information about Apple's processing is available in its Privacy Policy and the App Store & Privacy notice.

5.4 Note Recognition and AI Note Recognition

The apps “Note Recognition & Sheet Music” and “AI Note Recognition” use the device microphone when the user starts an audio analysis. Access takes place only after the corresponding operating-system permission has been granted.

Audio data captured through the microphone is used to identify pitch, frequency, and the notes played. The audio analysis is performed on the device. The audio recording is not transmitted to us or to third parties.

Where an export or sharing function is used, the sheet-music or MIDI result generated by the analysis, together with technical metadata, may be transmitted to our servers. The original audio recording is not transmitted as part of this function. If a sharing link is generated, anyone who has that link can access the shared data. Users should therefore share such a link only with persons who are intended to receive access.

In addition, technical app activity may be processed. This may include, in particular, function calls, export operations, technical events, and error messages. This data is processed to provide and improve the app, diagnose errors, and prevent misuse.

Recordings stored locally generally remain on the device and can be removed by the user through the app or by deleting the app.

5.5 WWW Notifier (Pro)

The apps “WWW Notifier” and “WWW Notifier Pro” allow users to regularly check websites they have selected for changes.

For this purpose, the app processes in particular:

• the website addresses entered by the user;
• the section of a website selected by the user;
• the specified checking interval;
• locally stored comparison data from previous and current versions of the page;
• the time and result of the most recent check;
• notification settings configured by the user.

This data is generally stored on the device and is not transmitted to our servers.

To check a website, the app establishes a direct connection to the web server selected by the user. In doing so, the operator of the target website receives technically necessary connection data, in particular the IP address, the date and time of access, device or browser information, and, where applicable, cookies or other data requested by the target website.

The privacy policy and terms of use of the respective operator of the monitored website govern the processing of data by that operator. We have no influence over the data processing carried out by the operator of the target website.

The data remains stored on the device until the user deletes the relevant monitoring task, the app data, or the app.

5.6 Gravity Wars and Gravity Wars 2

This section covers “Gravity Wars” (version 1) and “Gravity Wars 2” (also listed on Google Play as “Gravity Wars 2: Battle Arena”). Data processing differs between the versions.

Gravity Wars (version 1)

When “Gravity Wars” (version 1) is used, data may be processed that is necessary to run the game, store game progress, and provide global leaderboards.

This may include in particular:

• a player name or pseudonym chosen by the user;
• a pseudonymous user, device, or installation identifier;
• game results, progress, and statistics;
• technical app activity;
• security, error, and misuse data.

The identifiers are used to recognize a user in subsequent game sessions, associate games with the user, store results, and prevent duplicate submissions or manipulation. A pseudonymous identifier is not anonymous data as long as it can be associated with a device or a particular use.

The player name, score, and ranking may be published on a global leaderboard. Users should therefore not use their real name or other directly identifying information as their player name.

Gravity Wars 2

Gravity Wars 2 is a single-player game that can be played without signing in and without an internet connection. Game progress is first stored on the device. As soon as a connection to our servers is available, the game automatically creates a pseudonymous online account in the background. The account enables cloud saves, online leaderboards, restoring progress on another device, and in-app purchases. No email address, telephone number, real name, or password is required for it. The preceding information about version 1 does not apply to Gravity Wars 2.

Storage on the device

Gravity Wars 2 stores a local game profile on the device, including in particular:

• unlocked arenas and personal records for each arena, including difficulty levels reached and completed, waves reached, and the associated survival duration;
• experience points, the player level calculated from them, and the Credits balance;
• tutorial status, previously acknowledged notices, and game settings;
• a randomly generated local profile identifier and, once signed in, the identifier and generated player name of the online account, a copy of the entitlements confirmed for the account (for example "Pro"), and game events not yet transmitted to the server.

The device's sign-in credentials for the online account, a random device identifier and a secret device key, are generated by the app itself. They are kept separately from the game profile in the operating system's protected storage (Android Keystore or iOS Keychain). The device identifier is not a hardware or advertising identifier provided by the operating system or device manufacturer. The game language is selected locally based on the system language. Automatic Android app-data backup is disabled for Gravity Wars 2.

Local data remain stored until the app data or the app are deleted. On iOS, the Keychain entry may survive an uninstall; after reinstalling, the device then reconnects to the same online account. Deleting the app or its data does not delete the online account; the account deletion described below is provided for that.

Online account and player name

For the online account we process:

• an internal, randomly generated account identifier;
• an automatically generated player name made of an English adjective, a noun, and a number (for example "NeonOtter1"), which currently cannot be changed;
• the account status and the times the account was created and last used;
• for each connected device, the device identifier, a cryptographic hash of the device key, the type of connection (registration, restore, or Google sign-in), and the times it was set up and last used;
• short-lived access tokens (generally valid for one hour), stored on the server only as a hash;
• if the user creates a recovery code, a cryptographic hash of the code and the time it was created. The code is shown only once in the app and is not stored in plain text by the app or by us. It can be used once.

The recovery code or a linked Google account can be used to restore the online account on another device. If a restore replaces an unsecured guest account on the device, we transfer, after the user confirms, that guest's purchases, purchased Credits and, within the game rules, its progress to the restored account and then delete the guest account.

Cloud save and game progress

While an online account exists, the game transmits every change to game progress to our server as an individual game event, also afterwards following a period of offline play. This includes in particular:

• experience points and Credits earned per run, and Credits spent together with the equipment chosen for them;
• arena unlocks, personal records, tutorial status, and acknowledged notices;
• on the first connection, a one-time transfer of the existing local game profile with its random local profile identifier;
• for each event, a random event identifier, the event type, the time reported by the device, the time of processing on the server, and the result of the check;
• a ledger of Credits added and deducted.

The server checks the events for plausibility and limits how many experience points and Credits can be credited within a period. Unusual values are flagged for manual review; accounts are not blocked automatically. All devices connected to the account receive the merged game progress.

Highscores and completed runs

For every regularly completed run (not for the tutorial and not for abandoned runs) we store the arena, a random run identifier, the difficulty level reached and completed, the wave reached, the survival duration, the end time reported by the device and the time of receipt on the server, the equipment used (items, total price, catalogue version), the type of app build (release, test, or development version), the app version, and whether and why the run counts in the leaderboards. We keep at most 1,000 runs per account; older ones are deleted automatically, while personal records are retained.

From ranked runs we create a monthly and an all-time leaderboard for each arena. They show all users of the game the generated player name, the current player level, the rank, the difficulty level and wave reached, the time, and the equipment of the respective run. Account identifiers, Credits, purchases, and device information are not shown. Runs that fail our plausibility checks, and runs from test and development versions, are stored but not ranked.

Users can switch participation in the public leaderboards off and on again at any time with the switch for participation in leaderboards and statistics on the Account screen; it is switched on by default. The setting is stored on our server with the online account and applies to all devices connected to the account. While it is switched off, none of the account's results, including results achieved earlier, appear in any public leaderboard, neither in the monthly and all-time leaderboards nor as a world record. Game progress, Credits, purchases, Pro, and personal records are fully retained. If participation is switched on again, results that are still stored and valid can reappear in the leaderboards. The same switch also controls the internal statistical analysis (see below).

Credits and in-app purchases

Gravity Wars 2 offers a one-time "Pro" purchase and Credit packs through Google Play. There is no advertising and no subscription. Payment is handled by Google (Section 5.2); we do not receive payment, card, or bank details. When a purchase is made, the app passes a hash of the account identifier to Google so that the purchase can be assigned unambiguously to the account. The app then sends the purchase token to our server, which verifies the purchase directly with Google and credits Credits and Pro to the online account only after the payment has been confirmed.

For this purpose we store in particular the store, the store order number, a hash of the purchase token, the product, the quantity, the purchase status, whether it is a test purchase, the assigned account hash, the times of purchase, crediting, completion and, where applicable, refund, the Credits credited, and a log of the processing steps. We keep the purchase token itself only until the purchase has been completed with Google. We regularly reconcile refunds and chargebacks with Google and reverse the corresponding benefits. Purchased Credits and Credits earned in the game form one balance, which is used to pay for equipment for runs.

In the version installed through Google Play, the Google Play rating dialog may appear after a run. Google processes any rating submitted there under its own responsibility; we receive no personal data about it.

Optional link with a Google account

Users can voluntarily link their online account with a Google account in order to restore it on another device later. Sign-in takes place in Google's sign-in window; we do not receive a password. Google gives the app a sign-in token, which the app forwards to our server. The server verifies the authenticity of the token and stores only the permanent, pseudonymous identifier of the Google account and the time of linking. Other information contained in the token, such as the email address, name, or profile picture, is neither stored nor evaluated. The link can be removed in the game at any time. Google's privacy notices apply to Google's processing during sign-in.

Technical data, security, and recipients

Each connection to our server involves the technical connection data described in Section 5.1. Our game application uses the IP address only briefly in memory to limit the number of requests per sender (IPv6 addresses truncated to the /64 network) and does not store it in the game database. All connections are encrypted with HTTPS. We store device keys, access tokens, and recovery codes only as cryptographic hashes.

Gravity Wars 2 contains no third-party advertising, analytics, or crash-reporting SDKs and does not access the advertising identifier, location, contacts, camera, or microphone. Hosting providers engaged by us operate the server and database as processors. Our server communicates with Google to verify purchases and Google sign-ins. Other users receive the player name and game results only to the extent described above through the leaderboards.

Internal statistical analysis

In addition, we analyse the data described above, which are stored anyway for the account, cloud save, leaderboards, and purchases, internally and in aggregated form for statistical purposes, for example the number of accounts and registrations, the number and distribution of runs per arena, difficulty levels reached and survival durations, equipment chosen, progress and unlocks, Credit transactions, and the number and type of purchases. The purpose is to improve game balance, difficulty, the in-game economy, and stability, and to develop Gravity Wars 2 further. We collect no additional data on the device for this and use no third-party analytics services.

The analysis uses read-only database access that can read only the fields required and has no access to player names, purchase tokens, order numbers, or credentials. Our internal overviews show only aggregated values without account, run, or purchase identifiers; shares, averages, and distributions are not shown for fewer than five players. The results are not used to make decisions about individual players or to build player profiles. Only persons authorised by us have access.

The legal basis is Article 6(1)(f) GDPR. Our legitimate interest lies in improving the game and developing it economically. Users can object to this analysis at any time directly in the app (Section 8 g) by switching off participation in leaderboards and statistics on the Account screen. From then on, the account's data, including data already stored, are not included in any internal analysis, and its results no longer appear in the public leaderboards. Game progress, Credits, purchases, and Pro are retained; the data continue to be stored for game operation but are not analysed. The switch can be turned on again at any time. In addition, privacy requests, including an objection, can be sent by email to kontakt@mystage.fm, for example if the app cannot be accessed; for account-related requests, we first check that the request comes from the account holder. After the online account has been deleted, its data are likewise no longer included in analyses; purchase records retained without a link to the account are then counted only as a plain number of purchases.

Legal bases

Processing to provide the online account, cloud saves, restore, leaderboards, and the Google link, and to verify, credit, and manage purchases, is carried out to perform the contract of use on the basis of Article 6(1)(b) GDPR. Processing for security, plausibility checks of game results and credits, prevention of misuse and fraud, error analysis, and internal statistical analysis is based on Article 6(1)(f) GDPR. Our legitimate interest lies in secure, fair, and stable game operation, protection against manipulation, and further development of the game. Where purchase data are retained because of statutory obligations, the legal basis is Article 6(1)(c) GDPR.

Leaderboard ranking, plausibility checks, and crediting limits are applied automatically according to fixed game rules. They serve only to run the game and do not produce legal or similarly significant effects within the meaning of Article 22 GDPR. Without an online account, for example after it has been deleted, the game remains playable offline; cloud saves, leaderboards, restore, and purchases are then not available.

Retention and account deletion

We store account, progress, run, and leaderboard data for as long as the online account exists. Access tokens expire after a short time and are deleted regularly; a recovery code is deleted when it is used.

The online account can be deleted in the game at any time: on the arena selection screen, tap the profile icon at the top right and choose "Delete online account". This deletes the account together with the player name, device connections, recovery code, Google link, cloud save with its event history and Credit ledger, stored runs, leaderboard entries, and entitlements. The entries disappear from the leaderboards immediately. Local game progress on the device is kept. Online features stay off until the user turns them on again, which creates a new account.

Deletion can also be requested without the app by email to kontakt@mystage.fm, mentioning "Gravity Wars 2" and the player name. To check that the request comes from the account holder, we may ask for proof, for example a screenshot of the Account screen. Uninstalling the app or clearing its data does not delete the online account.

After deletion, only the following data are retained, without any link to the game account:

• purchase records with their processing log, to the extent and for as long as we need them to comply with statutory retention obligations, handle refunds, and prevent a purchase from being redeemed again. They still contain the store order number and the account hash and are therefore not anonymous. A purchase of a deleted account is not credited to another account automatically; our support can help in justified cases;
• an import record for each game profile transferred into the account, so that the same progress cannot be credited more than once. It contains the random local profile identifier or, after a guest-account merge, the identifier of the former guest account, together with the amounts transferred and the time.

We delete these data as soon as they are no longer required for these purposes and no statutory retention periods prevent deletion.

5.7 Brain Duel

“Brain Duel” provides local brain games as well as online features for friendships, direct duels, random ranked matches, and a global ranking. The first time the app connects to the server, a pseudonymous game account is created automatically; no email address, telephone number, or sign-in with a platform account is required.

• an installation identifier randomly generated by the app, an internal user identifier, and an authentication token, which is stored on the server only as a cryptographic hash;
• an automatically generated or user-selected display name and an individual friend code;
• account and usage timestamps, in particular account creation, most recent authentication-token use, online status, and last-seen time;
• friend requests, their status and timestamps, friendships, and invitation, readiness, and opponent-assignment data;
• for ranked matches in particular, game type and version, match and opponent identifier, score, remaining-time bonus, accuracy, average reaction time, score timeline, game-start identifier, result, rating before and after the match, and numbers of wins, losses, draws, and ranked matches played;
• for direct friend duels in particular, score, correct and incorrect inputs, average reaction time, rounds completed, and start and finish times; and
• the technical connection, log, security, error, and misuse data described in Section 5.1.

The random installation identifier is generated by Brain Duel itself and is not a hardware or advertising identifier provided by the operating system or device manufacturer. The identifiers and authentication token are used to recognize the user, protect the account, associate matches and friendships, and prevent duplicate submissions and manipulation. They are pseudonymous but not anonymous while they can be associated with an account, device, or particular use.

The pseudonymous user identifier, display name, rating, number of ranked matches played, and rank are made available to other Brain Duel users through the global ranking. Friends may see, in particular, the pseudonymous user identifier, display name, online status, and last-seen time. Participants in a direct duel receive the other participant’s pseudonymous user identifier and game result. In random ranked matches, a pseudonymous user identifier, display name, rating, and recorded gameplay data from an earlier match may be provided to a later opponent as an asynchronous replay. Users should therefore not use their real name or other directly identifying information as their display name.

Ranked-match recordings may also be evaluated to train and validate aggregated behavioural models for virtual opponents. Opponent selection, calculation of player rating and rank, and generation of virtual gameplay are performed automatically according to rules. These operations serve only to run the game and do not produce legal or similarly significant effects within the meaning of Article 22 GDPR.

Invitations and direct-duel rooms are processed in the server’s volatile memory and are not stored in the game database. Pending invitations generally expire after approximately 60 seconds; room and result data are discarded no later than when the server process restarts. Short-lived online sessions generally expire after approximately 90 seconds if they are not refreshed. The last-seen time, by contrast, is stored with the pseudonymous account.

On the device, the app stores in its app preferences, in particular, the user and installation identifiers, authentication token, display name, friend code, rating, and number of ranked matches played. It also stores local overall and per-game statistics, including numbers of games, best results, correct and incorrect inputs, reaction times, daily best results, and most recent play time, as well as the selection whether to skip game introductions. These local data are removed by clearing the app data or deleting the app. Deleting the app does not, however, automatically terminate the pseudonymous account or erase data already stored on the server.

Brain Duel currently contains no advertising, usage-analytics, or crash-reporting SDKs and does not access location, contacts, the camera, or the microphone. Hosting and infrastructure providers engaged by us may receive the data necessary to provide the server and database as processors. Data used for online matches and social features are also disclosed to friends or opponents to the extent described above.

Processing to create and manage the pseudonymous account and provide the game, friendship, presence, matching, and ranking features requested by the user is based on Article 6(1)(b) GDPR. Processing to ensure secure, stable, and fair gameplay, analyse errors, prevent misuse and fraud, and create and validate virtual opponents is based on Article 6(1)(f) GDPR. Our legitimate interest lies in the security, functionality, fairness, and further development of Brain Duel. A particular online feature cannot be used without the data necessary to provide it.

Account, profile, friendship, ranking, match, and replay data are retained for as long as they are required for the game account, multiplayer operation, rankings, security, and misuse prevention. They are then erased or anonymised unless statutory retention duties or overriding documentation, security, or legal-enforcement interests require otherwise.

No account-deletion feature

Brain Duel currently provides no feature that allows users to close or delete the pseudonymous game account themselves. Deleting the app or its local data likewise does not delete the server-side account or the data linked to it. This does not affect statutory data-subject rights, in particular the right to erasure subject to Article 17 GDPR. Requests concerning those rights may be sent to kontakt@mystage.fm, stating Brain Duel and, if possible, the user identifier or friend code. The applicable conditions and possible exceptions are described in Section 8.

5.8 Xferly

The app “xferly” enables file transfers between devices. The app uses WebRTC data channels for the transfer of files. File contents are generally transferred directly between the participating devices and are not stored on our application server.

To establish a connection, xferly uses our signaling server. For this purpose, technical connection data and signaling data may be processed, including IP addresses, date and time of access, app version, pairing codes, WebSocket connection data, WebRTC session descriptions, ICE candidates, connection status, and error data. This data is used to establish and secure the connection, route connection requests, prevent misuse, and diagnose technical errors.

Where a direct WebRTC connection cannot be established, xferly may use STUN or TURN relay infrastructure. In such cases, connection metadata and encrypted WebRTC traffic may pass through relay servers. File contents are not stored by us on these relay servers.

If the user signs in to use account-based functions such as “My devices”, xferly uses Firebase Authentication. In this context, authentication data may be processed, including Firebase user ID, e-mail address, e-mail verification status, display name, profile photo URL, and authentication tokens. For device management, we may process device or installation identifiers, device display name, platform, device type, app version, online status, last-seen timestamps, and device unlinking or revocation status.

When a user selects a file for transfer, the app processes the selected file locally on the device. File metadata such as file name, file size, transfer status, and checksums may be shown in the app and transmitted to the receiving device as part of the transfer. Received files and transfer history may be stored locally on the user's device or in browser storage, depending on the platform. The user can delete local transfer history and received files through the app or the operating system.

The legal basis for processing data required to provide file transfer, pairing, account, and device-management functions is Article 6(1) lit. b GDPR. Processing for security, abuse prevention, error analysis, and stable operation of our systems is based on Article 6(1) lit. f GDPR. Our legitimate interest lies in providing a secure and reliable file-transfer service and protecting our systems against misuse.

After logging in, users can delete their account directly from the “Accounts” page. Account and device data are stored for as long as they are required to provide the account-based functions or until the user unlinks the device, deletes the account there, or requests deletion, unless statutory retention obligations apply. Temporary pairing and signaling data are retained only as long as necessary for connection establishment, security, troubleshooting, and operation of the service.

5.9 NextPanel Comics

“NextPanel Comics” is a comic app in which users can read comic series, participate in story votes, submit reactions, share episodes, unlock content, collect in-app rewards, use avatars, and optionally appear on leaderboards. The public web offering can be used without login; the mobile app uses an anonymous guest account.

When the mobile app starts, an anonymous session is created or restored. For this purpose, we process in particular a hashed installation identifier, an internal mobile user ID, an internal device ID, platform, app version, locale, last-seen timestamp, access and refresh tokens or token hashes, and technical security, error, and misuse data. Optionally, an attestation token may be processed to verify the integrity of app usage.

For profile, community, and progress features, we may process in particular display name, selected avatar, leaderboard opt-in, wallet balances such as Ink and Comic Keys, unlocked series or episodes, avatar ownership and avatar purchases using in-app currency, submitted votes, episode reactions, reading, sharing, and activity events, achievement progress, achievement rewards, league and leaderboard points, and timestamps of the respective actions. If leaderboard visibility is enabled, display name, avatar, rank, score, and achievement information may be shown to other users. Users should therefore not use their real name or other directly identifying information as their display name.

If the user enables push notifications, push tokens, platform, app version, and the time of token updates may be stored to deliver notifications and technically manage delivery.

The public web offering for NextPanel Comics provides series, episodes, preview images, voting results, app links, and sharing pages. In general, no user accounts are created there and no JWT token is used. When the sharing function is used, browser-provided sharing or clipboard functions may be used; further processing by the operating system, browser, or selected target app is governed by their respective privacy terms.

Comic content, story suggestions, images, covers, avatars, and visual canon information may be created or analyzed with the help of AI service providers, in particular OpenAI. For this purpose, series descriptions managed by us, prompt blocks, episode content, image descriptions, reference images, aggregated voting results, and technical generation data may be transmitted to the provider. Mobile user identifiers, push tokens, refresh tokens, and direct account data are not intentionally transmitted to AI service providers. Users should nevertheless avoid entering personal data in display names, votes, or other freely configurable content if they do not want such data to be processed.

Processing is carried out to provide the app functions, recognize the anonymous guest account, synchronize progress, votes, reactions, wallet, unlocks, and achievements, provide community and leaderboard features, create and deliver comic content, analyze errors, prevent misuse and fraud, and maintain the security of our systems. The legal basis is Article 6(1) lit. b GDPR where processing is required to provide functions requested by the user. Processing for security, error analysis, abuse prevention, product improvement, generation and management of app content, and aggregated reach and performance analysis is based on Article 6(1) lit. f GDPR. Our legitimate interest lies in operating the app and public web offering securely, stably, fairly, and economically. Where statutory retention obligations apply, Article 6(1) lit. c GDPR is the legal basis. Where consent is obtained for individual optional features, Article 6(1) lit. a GDPR is the legal basis.

The mobile app stores session data, tokens, and the installation identifier locally on the device, in particular in the secure storage of the operating system. Images and content may be cached locally to reduce loading times. Local data can be removed by deleting the app or through operating system functions; server-side account data is not necessarily fully deleted by doing so.

Users can delete their anonymous mobile account directly in the app. Account- and device-related server data is deleted or anonymized unless statutory obligations, security interests, fraud prevention, or documentation obligations require otherwise. Aggregated voting, reaction, statistics, and security data may remain without a direct account reference.

5.10 Daily Quiz

Daily Quiz creates a pseudonymous profile without requiring a name, email address, telephone number, or social login. We process the profile identifier, authentication secret (hashed on the server), nickname, region, quiz language, answers, results, history, reports and moderation outcomes, and Pro access dates to provide gameplay, rankings, reporting, and access management. Technical logs are described in Section 5.1. These functions rely on Article 6(1)(b) GDPR; security, moderation, and service improvement rely on Article 6(1)(f), and statutory obligations on Article 6(1)(c).

Leaderboards may show your nickname, region, score, days played, rank, and pseudonymous profile identifier. Avoid identifying details in nicknames and reports. Credentials are stored in the device's secure storage; profile and language preferences are stored locally. The requested language is sent to the backend. We do not collect precise location, contacts, or advertising identifiers, use third-party tracking SDKs, or sell personal data. Hosting providers process operational data on our behalf.

First-party activity events, including app opens, quiz activity, archive use, and subscription activity, contain profile identifiers, timestamps, and event details for operation and improvement. Archive and subscription-funnel events lose their profile link after 30 days and contain no answer text or payment details. Other data are retained as needed for gameplay, moderation, and security, then deleted or anonymised unless legal retention duties apply.

Pro access requires a paid subscription through Apple or Google, which handle payments. We may process receipts or tokens, transaction identifiers, products, subscription status, renewal information, and validity dates to verify and restore access, but no card or bank details. Minimal store records may remain independently after deletion for restoration, fraud prevention, accounting, and legal obligations.

Use “Delete account” in Settings to remove your profile, quiz history, answers, rankings, store entitlement links, and reports targeting your nickname. Local data are cleared except for the language preference. Retained reports and analytics lose their profile link; your profile identifier and current nickname are redacted from retained report text and related audit notes, and profile audit identifiers and metadata are removed. Uninstalling alone does not delete server data. Deletion does not cancel subscriptions; manage them through the relevant store. Restoring a purchase does not restore deleted quiz history. Privacy requests: kontakt@mystage.fm.

6. Routine erasure and blocking of personal data

The data controller shall process and store the personal data of the data subject only for the period necessary to achieve the purpose of storage, or as far as this is granted by the European legislator or other legislators in laws or regulations to which the controller is subject to.

If the storage purpose is not applicable, or if a storage period prescribed by the European legislator or another competent legislator expires, the personal data are routinely blocked or erased in accordance with legal requirements.

7. International data transfers

We endeavour to host and process data within the EEA wherever possible. Where personal data is transferred outside the EEA, we rely on an adequacy decision, the EU Standard Contractual Clauses, or another valid transfer mechanism, in each case supplemented by any safeguards required. Google states that Google LLC is certified under the EU-U.S. and Swiss-U.S. Data Privacy Frameworks and the UK Extension and, where required, additionally uses Standard Contractual Clauses.

8. Rights of the data subject

a) Right of confirmation

Each data subject shall have the right granted by the European legislator to obtain from the controller the confirmation as to whether or not personal data concerning him or her are being processed. If a data subject wishes to avail himself of this right of confirmation, he or she may, at any time, contact any employee of the controller.

b) Right of access

Each data subject shall have the right granted by the European legislator to obtain from the controller free information about his or her personal data stored at any time and a copy of this information. Furthermore, the European directives and regulations grant the data subject access to the following information: the purposes of the processing; the categories of personal data concerned; the recipients or categories of recipients to whom the personal data have been or will be disclosed, in particular recipients in third countries or international organisations; where possible, the envisaged period for which the personal data will be stored, or, if not possible, the criteria used to determine that period; the existence of the right to request from the controller rectification or erasure of personal data, or restriction of processing of personal data concerning the data subject, or to object to such processing; the existence of the right to lodge a complaint with a supervisory authority; where the personal data are not collected from the data subject, any available information as to their source; the existence of automated decision-making, including profiling, referred to in Article 22(1) and (4) of the GDPR and, at least in those cases, meaningful information about the logic involved, as well as the significance and envisaged consequences of such processing for the data subject.

Furthermore, the data subject shall have a right to obtain information as to whether personal data are transferred to a third country or to an international organisation. Where this is the case, the data subject shall have the right to be informed of the appropriate safeguards relating to the transfer.

If a data subject wishes to avail himself of this right of access, he or she may, at any time, contact any employee of the controller.

c) Right to rectification

Each data subject shall have the right granted by the European legislator to obtain from the controller without undue delay the rectification of inaccurate personal data concerning him or her. Taking into account the purposes of the processing, the data subject shall have the right to have incomplete personal data completed, including by means of providing a supplementary statement.

If a data subject wishes to exercise this right to rectification, he or she may, at any time, contact any employee of the controller.

d) Right to erasure (Right to be forgotten)

Each data subject shall have the right granted by the European legislator to obtain from the controller the erasure of personal data concerning him or her without undue delay, and the controller shall have the obligation to erase personal data without undue delay where one of the following grounds applies, as long as the processing is not necessary: The personal data are no longer necessary in relation to the purposes for which they were collected or otherwise processed. The data subject withdraws consent to which the processing is based according to point (a) of Article 6(1) of the GDPR, or point (a) of Article 9(2) of the GDPR, and where there is no other legal ground for the processing. The data subject objects to the processing pursuant to Article 21(1) of the GDPR and there are no overriding legitimate grounds for the processing, or the data subject objects to the processing pursuant to Article 21(2) of the GDPR. The personal data have been unlawfully processed. The personal data must be erased for compliance with a legal obligation in Union or Member State law to which the controller is subject. The personal data have been collected in relation to the offer of information society services referred to in Article 8(1) of the GDPR.

If one of the aforementioned reasons applies, and a data subject wishes to request the erasure of personal data stored by the mystage.fm, he or she may, at any time, contact any employee of the controller. An employee of mystage.fm shall promptly ensure that the erasure request is complied with immediately.

Where the controller has made personal data public and is obliged pursuant to Article 17(1) to erase the personal data, the controller, taking account of available technology and the cost of implementation, shall take reasonable steps, including technical measures, to inform other controllers processing the personal data that the data subject has requested erasure by such controllers of any links to, or copy or replication of, those personal data, as far as processing is not required. An employees of the mystage.fm will arrange the necessary measures in individual cases.

e) Right of restriction of processing

Each data subject shall have the right granted by the European legislator to obtain from the controller restriction of processing where one of the following applies: The accuracy of the personal data is contested by the data subject, for a period enabling the controller to verify the accuracy of the personal data. The processing is unlawful and the data subject opposes the erasure of the personal data and requests instead the restriction of their use instead. The controller no longer needs the personal data for the purposes of the processing, but they are required by the data subject for the establishment, exercise or defence of legal claims. The data subject has objected to processing pursuant to Article 21(1) of the GDPR pending the verification whether the legitimate grounds of the controller override those of the data subject.

If one of the aforementioned conditions is met, and a data subject wishes to request the restriction of the processing of personal data stored by the mystage.fm, he or she may at any time contact any employee of the controller. The employee of the mystage.fm will arrange the restriction of the processing.

f) Right to data portability

Each data subject shall have the right granted by the European legislator, to receive the personal data concerning him or her, which was provided to a controller, in a structured, commonly used and machine-readable format. He or she shall have the right to transmit those data to another controller without hindrance from the controller to which the personal data have been provided, as long as the processing is based on consent pursuant to point (a) of Article 6(1) of the GDPR or point (a) of Article 9(2) of the GDPR, or on a contract pursuant to point (b) of Article 6(1) of the GDPR, and the processing is carried out by automated means, as long as the processing is not necessary for the performance of a task carried out in the public interest or in the exercise of official authority vested in the controller.

Furthermore, in exercising his or her right to data portability pursuant to Article 20(1) of the GDPR, the data subject shall have the right to have personal data transmitted directly from one controller to another, where technically feasible and when doing so does not adversely affect the rights and freedoms of others.

In order to assert the right to data portability, the data subject may at any time contact any employee of the mystage.fm.

g) Right to object

Each data subject shall have the right granted by the European legislator to object, on grounds relating to his or her particular situation, at any time, to processing of personal data concerning him or her, which is based on point (e) or (f) of Article 6(1) of the GDPR. This also applies to profiling based on these provisions.

The mystage.fm shall no longer process the personal data in the event of the objection, unless we can demonstrate compelling legitimate grounds for the processing which override the interests, rights and freedoms of the data subject, or for the establishment, exercise or defence of legal claims.

If the mystage.fm processes personal data for direct marketing purposes, the data subject shall have the right to object at any time to processing of personal data concerning him or her for such marketing. This applies to profiling to the extent that it is related to such direct marketing. If the data subject objects to the mystage.fm to the processing for direct marketing purposes, the mystage.fm will no longer process the personal data for these purposes.

In addition, the data subject has the right, on grounds relating to his or her particular situation, to object to processing of personal data concerning him or her by the mystage.fm for scientific or historical research purposes, or for statistical purposes pursuant to Article 89(1) of the GDPR, unless the processing is necessary for the performance of a task carried out for reasons of public interest.

In order to exercise the right to object, the data subject may contact any employee of the mystage.fm. In addition, the data subject is free in the context of the use of information society services, and notwithstanding Directive 2002/58/EC, to use his or her right to object by automated means using technical specifications.

h) Automated individual decision-making, including profiling

Each data subject shall have the right granted by the European legislator not to be subject to a decision based solely on automated processing, including profiling, which produces legal effects concerning him or her, or similarly significantly affects him or her, as long as the decision (1) is not is necessary for entering into, or the performance of, a contract between the data subject and a data controller, or (2) is not authorised by Union or Member State law to which the controller is subject and which also lays down suitable measures to safeguard the data subject's rights and freedoms and legitimate interests, or (3) is not based on the data subject's explicit consent.

If the decision (1) is necessary for entering into, or the performance of, a contract between the data subject and a data controller, or (2) it is based on the data subject's explicit consent, the mystage.fm shall implement suitable measures to safeguard the data subject's rights and freedoms and legitimate interests, at least the right to obtain human intervention on the part of the controller, to express his or her point of view and contest the decision.

If the data subject wishes to exercise the rights concerning automated individual decision-making, he or she may, at any time, contact any employee of the mystage.fm.

i) Right to withdraw data protection consent

Each data subject shall have the right granted by the European legislator to withdraw his or her consent to processing of his or her personal data at any time.

If the data subject wishes to exercise the right to withdraw the consent, he or she may, at any time, contact any employee of the mystage.fm.

9. Data protection provisions about the application and use of Google Analytics (with anonymization function)

On this website, the controller has integrated the component of Google Analytics (with the anonymizer function). Google Analytics is a web analytics service. Web analytics is the collection, gathering, and analysis of data about the behavior of visitors to websites. A web analysis service collects, inter alia, data about the website from which a person has come (the so-called referrer), which sub-pages were visited, or how often and for what duration a sub-page was viewed. Web analytics are mainly used for the optimization of a website and in order to carry out a cost-benefit analysis of Internet advertising.

The operator of the Google Analytics component is Google Ireland Limited, Gordon House, Barrow Street, Dublin, D04 E5W5, Ireland.

For web analytics through Google Analytics, the controller uses a configuration under which Google truncates and anonymizes the IP address of the data subject’s Internet connection when our websites are accessed from a Member State of the European Union or another state party to the Agreement on the European Economic Area.

The purpose of the Google Analytics component is to analyze the traffic on our website. Google uses the collected data and information, inter alia, to evaluate the use of our website and to provide online reports, which show the activities on our websites, and to provide other services concerning the use of our Internet site for us.

Google Analytics places a cookie on the information technology system of the data subject. The definition of cookies is explained above. With the setting of the cookie, Google is enabled to analyze the use of our website. With each call-up to one of the individual pages of this Internet site, which is operated by the controller and into which a Google Analytics component was integrated, the Internet browser on the information technology system of the data subject will automatically submit data through the Google Analytics component for the purpose of online advertising and the settlement of commissions to Google. During the course of this technical procedure, the enterprise Google gains knowledge of personal information, such as the IP address of the data subject, which serves Google, inter alia, to understand the origin of visitors and clicks, and subsequently create commission settlements.

The cookie is used to store personal information, such as the access time, the location from which the access was made, and the frequency of visits of our website by the data subject. With each visit to our Internet site, such personal data, including the IP address of the Internet access used by the data subject, will be transmitted to Google in the United States of America. These personal data are stored by Google in the United States of America. Google may pass these personal data collected through the technical procedure to third parties.

The data subject may, as stated above, prevent the setting of cookies through our website at any time by means of a corresponding adjustment of the web browser used and thus permanently deny the setting of cookies. Such an adjustment to the Internet browser used would also prevent Google Analytics from setting a cookie on the information technology system of the data subject. In addition, cookies already in use by Google Analytics may be deleted at any time via a web browser or other software programs.

In addition, the data subject has the possibility of objecting to a collection of data that are generated by Google Analytics, which is related to the use of this website, as well as the processing of this data by Google and the chance to preclude any such. For this purpose, the data subject must download a browser add-on under the link https://tools.google.com/dlpage/gaoptout and install it. This browser add-on tells Google Analytics through a JavaScript, that any data and information about the visits of Internet pages may not be transmitted to Google Analytics. The installation of the browser add-ons is considered an objection by Google. If the information technology system of the data subject is later deleted, formatted, or newly installed, then the data subject must reinstall the browser add-ons to disable Google Analytics. If the browser add-on was uninstalled by the data subject or any other person who is attributable to their sphere of competence, or is disabled, it is possible to execute the reinstallation or reactivation of the browser add-ons.

Further information and the applicable data protection provisions of Google may be retrieved under https://www.google.com/intl/en/policies/privacy/ and under http://www.google.com/analytics/terms/us.html . Google Analytics is further explained under the following Link https://www.google.com/analytics/ .

10. Legal basis for the processing

Art. 6(1) lit. a GDPR serves as the legal basis for processing operations for which we obtain consent for a specific processing purpose. If the processing of personal data is necessary for the performance of a contract to which the data subject is party, as is the case, for example, when processing operations are necessary for the supply of goods or to provide any other service, the processing is based on Article 6(1) lit. b GDPR. The same applies to such processing operations which are necessary for carrying out pre-contractual measures, for example in the case of inquiries concerning our products or services. Is our company subject to a legal obligation by which processing of personal data is required, such as for the fulfillment of tax obligations, the processing is based on Art. 6(1) lit. c GDPR. In rare cases, the processing of personal data may be necessary to protect the vital interests of the data subject or of another natural person. This would be the case, for example, if a visitor were injured in our company and his name, age, health insurance data or other vital information would have to be passed on to a doctor, hospital or other third party. Then the processing would be based on Art. 6(1) lit. d GDPR. Finally, processing operations could be based on Article 6(1) lit. f GDPR. This legal basis is used for processing operations which are not covered by any of the abovementioned legal grounds, if processing is necessary for the purposes of the legitimate interests pursued by our company or by a third party, except where such interests are overridden by the interests or fundamental rights and freedoms of the data subject which require protection of personal data. Such processing operations are particularly permissible because they have been specifically mentioned by the European legislator. He considered that a legitimate interest could be assumed if the data subject is a client of the controller (Recital 47 Sentence 2 GDPR). 9. The legitimate interests pursued by the controller or by a third party

11. The legitimate interests pursued by the controller or by a third party

Where the processing of personal data is based on Article 6(1) lit. f GDPR, our legitimate interests are, in particular, carrying out our business activities, preventing fraud, ensuring the security of our IT systems, and establishing, exercising, or defending legal claims.

12. Period for which the personal data will be stored

The criteria used to determine the period for which personal data is stored are the applicable statutory retention period and the existence of a legitimate interest pursuant to section 11. Once the relevant period has expired, the corresponding data is routinely deleted unless it is still required for the performance of a contract or steps prior to entering into a contract.

13. Provision of personal data as a statutory or contractual requirement; requirement necessary to enter into a contract; obligation of the data subject to provide the personal data; possible consequences of failure to provide such data

We clarify that the provision of personal data is partly required by law (e.g. tax regulations) or can also result from contractual provisions (e.g. information on the contractual partner). Sometimes it may be necessary to conclude a contract that the data subject provides us with personal data, which must subsequently be processed by us. The data subject is, for example, obliged to provide us with personal data when our company signs a contract with him or her. The non-provision of the personal data would have the consequence that the contract with the data subject could not be concluded. Before personal data is provided by the data subject, the data subject must contact any employee. The employee clarifies to the data subject whether the provision of the personal data is required by law or contract or is necessary for the conclusion of the contract, whether there is an obligation to provide the personal data and the consequences of non-provision of the personal data. 12. Existence of automated decision-making

14. Existence of automated decision-making

As a responsible company, we do not use automatic decision-making or profiling.

Large parts of this Privacy Policy were created using the privacy policy generator of DGD Deutsche Gesellschaft für Datenschutz GmbH, which operates as an external data protection officer in Dresden, in cooperation with data protection lawyer Christian Solmecke.