RUNLINE
DE/EN
← Back to the home page

Legal

The complete Privacy Policy for RUNLINE.

Translation notice: This English translation is provided for convenience. If wording differs or questions of interpretation arise, the German original is authoritative.

RUNLINE Privacy Policy

Last updated: 4 September 2026

We are pleased that you use RUNLINE. This Privacy Policy explains which personal data we process, why we process it, how we protect the data of underage users in particular, and which rights you have.

RUNLINE is a sports entertainment app. The app turns running into an interactive audio experience. In order for RUNLINE to work, the app processes location data and certain movement information during an active run. Your runs, run data, routes and story progress are private. Publication does not occur automatically.

This Privacy Policy applies to the RUNLINE app for iOS and Android, the runline.eu website, beta tests, TestFlight tests, Google Play beta tests, voluntary app feedback and—as described below—crowdfunding and supporter data.

1. Data Controller

The controller responsible for processing personal data is:

FitCode-XR GmbH
Grasserstrasse 10
80339 Munich
Germany
Represented by the managing directors: Benjamin Best and Christopher Lance
E-mail: info@runline.eu
Website: runline.eu

2. Data protection officer

We have not currently appointed a data protection officer. If you have any questions about data protection, you can contact us at any time: info@runline.eu.

3. Minimum age, age groups and age determination

RUNLINE is generally designed for users aged 8 and over, as long as use is permitted according to the App Store age rating, device settings, family approvals and legal requirements. People under 8 years of age are not allowed to use RUNLINE. However, the current technical age prompt offers birth years corresponding to an age of approximately 6 or older and does not reliably enforce the minimum age of 8. The legal age limit therefore applies regardless of the technical selection available.

4. Principle: Your Data Is Private

RUNLINE has no public profiles, no friend lists, no groups, no public leaderboards, no comments and no direct messages within the app.

Your runs, routes, story progress, achievements and usage data are private. They are not published automatically. You can actively share certain content on other platforms. This will only be passed on if you initiate this yourself.

For underage users, we pay particular attention not to store location and route data unnecessarily in the cloud. Under 16 years of age, individual runs, location data, routes, distance and speed of individual runs generally remain local on the device.

5. No analysis or advertising tracking in the app that requires consent

We do not use analysis and advertising tracking that requires consent in the RUNLINE app.

We do not analyze for advertising purposes how you move individually through the app. However, for every run RUNLINE stores the technical user identifier, a timestamp and the duration in minutes in a Firestore collection used for story statistics. This processing takes place for all age groups and regardless of the cloud-sync setting for running data. It does not use the Firebase Analytics product and is described further in sections 6.6, 8.8 and 14.1.

6. What data we process in the app

Depending on how you use RUNLINE, we process different categories of data. Not all data is processed in the same way for all users. There are restrictions on cloud storage of location and running data, particularly for those under 16 years of age.

6.1 Account and login data

When you create a user account, we process in particular:

You can log in with email and password or via Google Login or Apple Login, if these options are offered. If you log in via Google or Apple, we receive the login data provided by Google or Apple, in particular your email address and a technical user ID. Depending on the settings of your Google or Apple account, additional information such as a name or profile picture may be transmitted.

Own accounts with email and password may also be possible for underage users, as long as this is legally permissible and the App Store, family sharing and parental control settings allow this.

6.2 Age and Release Information

In order to display content in an age-appropriate manner and to control the cloud functions, we may process the following data in particular:

This data is generally not used for advertising, profiling or the creation of personality profiles. The year of birth entered as a fallback is linked to the user account, stored in Google Firestore and retrieved from there for age checks. It is therefore available in the cloud and not only on the device used.

6.3 Technical data

When using the app, technical data may be processed, for example:

We use this data to provide the app, detect errors, ensure security and improve the stability of the app. We do not use Advertising ID, IDFA or similar advertising identifiers for advertising or tracking purposes.

6.4 Location and Running Data

During an active RUNLINE run, the app processes in particular:

This data is required for interactive running mode. RUNLINE uses it to track your activity, determine speed and distance, and trigger story events based on your running behavior. If you disable or do not allow location access via your operating system, the RUNLINE interactive running mode may not work or may only work to a limited extent.

The age-dependent rules in Section 7 apply to the cloud storage of this data. Under 16 years of age, the location, route, distance and speed of individual runs are generally not saved in the cloud, but remain on your device.

6.5 Movement and sensor data

RUNLINE uses sensors from your smartphone during an active run, in particular:

This allows RUNLINE to recognize certain movement patterns, for example accelerating or slowing down, jumping, turning around, standing still or different step frequencies.

The raw data from the motion sensors is not stored permanently. The evaluation takes place locally on your smartphone. Only derived results are saved to the extent that they are necessary for the story logic, the run history, the later display of your activity or cloud-side progress functions in accordance with this data protection declaration.

6.6 Story, Progress and Achievement Data

So that you can use and continue stories, we process in particular:

This data is used to help you track your progress, continue stories, unlock content, maintain streaks and records over time, and use RUNLINE as a cohesive app experience.

For users under 16, story progress, minutes heard, streaks, records and total distance can be saved in the cloud. The location, route, distance and speed of individual runs are not stored in the cloud. Date and duration may be processed indirectly to the extent necessary for story progression, billing, activation or creator compensation.

In addition, after every run we write the technical user identifier, a timestamp and the run duration in minutes to a shared Firestore collection for story statistics. This personal-data record is created for all age groups before any check of the cloud-sync setting for running data takes effect. It cannot currently be disabled using the cloud-sync toggle. Location or GPS route data is not stored in this statistics record.

6.7 Base Speed

RUNLINE can save a base pace. Base pace is a technical estimate of your usual running pace. It helps to tailor story mechanics and running events to your running behavior.

The base pace is not intended for medical evaluation and is not used to create a health profile. For underage users, the base speed can be processed locally. Cloud-side storage only takes place if this is necessary for the respective function in accordance with the app settings and this data protection declaration.

6.8 Purchase and activation data

RUNLINE is offered as a freemium app. You can purchase individual stories, training courses, subscriptions or other content in the app, if such offers are available.

Payment is generally made via the Apple App Store or Google Play. We ourselves do not store any credit card, bank or full payment details.

However, we process information necessary to manage purchases and activations, in particular:

We use RevenueCat to manage in-app purchases and activations. Purchase and activation data can also be stored in the cloud for underage users so that purchased content can be activated and restored correctly.

6.9 Push Notifications

RUNLINE can use push notifications, for example for training or running reminders, story updates, notifications of new content or important app notifications.

We do not send any personalized advertising pushes or marketing pushes via the app. You will only receive push notifications if you allow them on your device. You can deactivate push notifications at any time in your smartphone's settings.

6.10 Profile picture

You can voluntarily use a profile picture. The profile picture doesn't have to be of yourself; you can also use an icon, avatar, or other suitable image.

The profile picture is currently not publicly visible, is only used for private display in your account, is not biometrically evaluated and can be deleted or changed. For underage users, the profile picture is voluntary.

6.11 Support and feedback data in the app

When you contact us or voluntarily provide feedback, we process the data you provide to us, such as your name or username, email address, message, technical information about the problem, and voluntary responses to surveys or feedback forms.

We use this data to process your request, understand errors and improve RUNLINE.

7. Age-sensitive cloud sync and local processing

RUNLINE distinguishes between local running data on your device and data stored in the cloud. This allows us to particularly protect younger users and at the same time provide important progression and activation functions.

7.1 Under 8 years

RUNLINE may not be used by people under 8 years of age. If an account or usage is found to be associated with a person under the age of 8, we may limit or terminate usage and delete data as required by law.

7.2 Users aged 8 to 15

For users under 16 years of age, location data, running route, start and end points, distance and speed of individual runs are generally only processed locally on the device and are not stored in the cloud.

The app can fully display individual runs on the device, including route, distance, duration, speed and other running details. This local display does not mean that this data is stored in the cloud. If the device is lost, changed, or local data is deleted, such running details that are only stored locally may be lost.

On the cloud side, account data, purchase and activation data, story progress, minutes heard, streaks, records, total distance, stars and comparable progress or success data can be saved for 8 to 15 year olds. Date and duration may be processed indirectly to the extent necessary for story progression, billing, activation, or aggregated creator compensation.

7.3 Users aged 16 and over

For ages 16 and up, cloud sync for run data can be enabled by default so that runs can be backed up, restored on new devices, and you can retain your running history long-term. In particular, the running date, duration, location data, route, distance, speed and other running details can be saved in the cloud.

We will inform you about this cloud synchronization in the app. You can disable cloud sync for running data in the app where this feature is offered. If you deactivate it, new location and route data for individual runs will no longer be saved in the cloud. Certain cloud-side progress data such as streaks, records, total distance, story progress, minutes listened, purchases and unlocks may continue to be saved to keep RUNLINE working across devices and reliably.

Cloud data is not automatically published, is not used for advertising and is not passed on to advertising partners, sports brands, health insurance companies, creators or other third parties for their own purposes. Technical service providers such as Firebase/Google Cloud or RevenueCat may process data as a service provider or under their own responsibility, insofar as this is described in this data protection declaration.

7.4 Restricted Mode

If reliable age assignment is not possible or no age statement is provided, RUNLINE may function in a restricted mode. In this mode, no 16+ content is displayed and no sensitive running data such as location, route, distance or speed of individual runs is stored in the cloud.

7.5 Age changes and previous local runs

As you move into a new age group, such as 12 or 16, content and cloud features can be adjusted for the future. Previous local runs are not automatically uploaded to the cloud when you reach a new age group or come of age.

7.6 Deletion of individual runs and account deletion

You can delete individual runs if this function is provided in the app. You can also delete your account. When deleting an account, personal data will be deleted or anonymized in accordance with legal requirements, provided there are no legal retention obligations or legitimate reasons for further storage.

8. What we use your data for

8.1 Provision of the app and your user account

We process account, login and technical data so that you can log in, use RUNLINE, access content and associate your data with your account.

8.2 Age-appropriate content and data protection features

We process age and clearance data so that RUNLINE only displays age-appropriate content, excludes those under 8 years old, only makes content 16 and over accessible to suitable users and controls cloud functions based on age.

8.3 Conducting interactive runs

We process location, walking and movement data to enable interactive audio adventures. Your real movement influences the course of the story. To do this, RUNLINE must be able to detect how you move, how fast you are, whether you stop, turn around or complete certain challenges during an active run.

8.4 Saving your runs and progress

We store run data, story progress, minutes listened, and challenge results so you can later view your activity, continue stories, and track your achievements. For those under 16, the cloud storage restrictions in Section 7 apply.

8.5 Cloud sync and backup

RUNLINE may store data in the cloud so that your data is secured, associated with your account and available across devices. For ages 16 and up, cloud sync for running data can be enabled by default. Under 16 years of age, individual running details such as location, route, distance and speed are generally not saved in the cloud.

8.6 Activation of paid content

We process purchase and activation data so that paid content, stories, training or subscriptions are correctly activated and restored.

8.7 Troubleshooting and Security

We process technical data, bug reports and crash information to detect technical problems, keep the app stable, prevent misuse and ensure the security of the app.

8.8 Run-related statistics and aggregated analysis

RUNLINE can work with authors, speakers, musicians or other creators. To compensate or evaluate content, we use aggregated statistics, for example minutes heard per story. We do not pass on any personal running data, routes or individual usage profiles to creators.

For the internal analysis, an initial personal-data record consisting of the technical user identifier, timestamp and run duration in minutes is stored in Firestore for every run. The purposes are evaluating story usage, making internal product decisions and producing aggregated statistics. Only the consolidated reports derived from those records contain no personal data.

9. Legal basis for processing

We process your data on the basis of the General Data Protection Regulation.

9.1 Performance of the contract

A lot of data processing is required so that we can provide you with RUNLINE. This includes, in particular, creating and managing your account, login and authentication, age control of the app, conducting interactive runs, processing location data during an active run, processing movement patterns during an active run, storing story progress, storing minutes listened to, storing progress data, unlocking paid content and managing purchases. The legal basis is Article 6 Paragraph 1 Letter b GDPR.

9.2 Legitimate interest

Some processing is carried out on the basis of our legitimate interest. This includes, in particular, local error logs, security measures, misuse detection, technical stability of the app, technical age control, internal run-related statistics and aggregated creator billing. The legal basis is Article 6(1)(f) GDPR. Our legitimate interest lies in operating RUNLINE safely, reliably, appropriately for different ages and economically, evaluating story usage and accounting for content.

9.3 Consent

If we base processing on your consent, the legal basis is Article 6(1)(a) GDPR. This may in particular concern optional features, such as device-level push notifications, the voluntary connection to Strava, voluntary website cookies, website analytics, marketing pixels or embedded external content on the website. A run export initiated by you also serves to provide the function you requested in accordance with Article 6(1)(b) GDPR.

For children under 16, we obtain the necessary consent from their legal guardians in accordance with the legal requirements or do not provide the relevant function. Cloud storage of location, route, distance and speed of individual runs is generally deactivated for users under 16 years of age.

9.4 Legal Obligations

If there are statutory retention, proof or cooperation obligations, we process data to fulfill these obligations. The legal basis is Article 6 Paragraph 1 Letter c GDPR.

10. App permissions

10.1 Location

RUNLINE requires access to your location during an active run. Without location access, RUNLINE cannot reliably record distance, speed, route and story-relevant running events. Location access is not used for advertising.

10.2 Motion and Sensors

RUNLINE uses motion sensors on your smartphone to recognize certain movement patterns. This recognition is part of the interactive story experience. The raw data from the motion sensors is not stored permanently.

10.3 Push Notifications

Push notifications are optional and can be enabled or disabled via your operating system. RUNLINE does not use push notifications for personalized advertising.

10.4 Photos and Media

If you voluntarily upload a profile picture or share content, the app may require access to photos or media. This access only occurs if you actively allow it.

11. No health app

RUNLINE is a sports entertainment app. RUNLINE is not a medical app, not a health app and does not replace medical advice.

We currently do not request health data such as illnesses, injuries, weight, heart rate or fitness status. RUNLINE does not create individualized medical training plans and is currently not connected to Apple Health, Google Fit, Garmin, Polar or Fitbit. An optional connection to Strava is offered solely for run exports initiated by you; details are provided in section 14.3.

If RUNLINE introduces health data, wearables or health-related features in the future, we will update this privacy policy accordingly and obtain additional consents as necessary.

12. AI-powered content

We use AI tools to support internal content production, for example for storywriting, image generation, voice production, sound design as well as music and audio ideas. Services such as OpenAI, Anthropic, ElevenLabs, Midjourney, Suno or Google can be used for this.

We do not transmit any personal user data, running data, location data or training data to these AI providers. Your RUNLINE user data will not be used to train external AI models. AI-generated or AI-assisted content may be marked as such.

13. Sharing Runs and Content

Your runs, routes, progress and story data are private. You can actively share certain content on other platforms or social networks. Publication only occurs through your active action. If you share content on external platforms, the data protection regulations of the respective platform also apply. RUNLINE does not publish a running route automatically.

14. Service providers and recipients

We only pass on personal data if this is necessary for the operation of RUNLINE, to fulfill a contract, to fulfill legal obligations or to protect legitimate interests.

14.1 Google Firebase / Google Cloud

We use Firebase and Google Cloud for technical app functions, including authentication, the Firestore database, cloud storage, storage of account data, year of birth, story and progress data, purchase and activation information, profile images, and the run-related story statistics consisting of a technical user identifier, timestamp and run duration.

Running data is only saved in accordance with the age-dependent cloud rules. Under 16 years of age, we generally do not store the location, route, distance and speed of individual runs in Firebase or Google Cloud. For ages 16 and up, cloud sync for running data can be enabled by default unless disabled.

We do not use Firebase for advertising tracking or Firebase Analytics. Data is stored in the European Union as long as the respective Firebase services support regional storage and are configured accordingly.

14.2 Local error logs

The app currently uses neither Firebase Crashlytics nor another external crash-reporting service. Technical errors and crashes are recorded only in local app logs on the device. These logs are not automatically transmitted to Google or another crash-reporting provider. If you voluntarily send us logs or error details as part of a support request, we process them in accordance with section 6.11.

14.3 Strava

You can voluntarily connect your RUNLINE account to Strava through OAuth in the settings. RUNLINE requests the activity:write permission. When you initiate an export, RUNLINE transmits the relevant running activity, including the data contained in the GPX file—particularly time, location, route and, where available, elevation information—to Strava.

For users in the EU/EEA, the recipient is Strava Ireland Ltd., Making it Work, Magennis Court, Pearse Street, Dublin 2, D02 FK76, Ireland. Strava processes the received data for its own service under its own responsibility as a controller. Data may also be transferred to, processed and stored in the United States. Strava states that it uses appropriate legal mechanisms, such as Standard Contractual Clauses, for international transfers. The Strava Privacy Policy also applies.

You can disconnect Strava in the RUNLINE settings and revoke access in your Strava account. This prevents future transfers; activities already exported to Strava are not automatically deleted from Strava.

14.4 RevenueCat

We use RevenueCat to manage in-app purchases, activations and entitlement. RevenueCat processes in particular technical user ID, product ID, purchase status, store information, activation status and technical transaction information. RevenueCat does not process full payment data such as credit card or bank details for us.

14.5 Apple and Google

If you download the app via the Apple App Store or Google Play, test it via TestFlight or Google Play Beta, make purchases, use Apple Login or Google Login, or age range signals are provided, Apple or Google process personal data under their own responsibility. The data protection regulations of Apple and Google apply to this processing.

14.6 Other technical service providers

We may use other technical service providers, for example for hosting, security, app operation, support or error analysis. These service providers only process personal data to the extent necessary.

15. No distribution for advertising purposes

We do not sell personal information. We do not share location data, running data, story data or account data with advertising partners.

We do not pass on personal data to sports brands, health insurance companies, authors, speakers, musicians or other creators for their own purposes. We only use aggregated statistics for creator billing or internal reporting.

16. Third Country Transfers

We strive to process personal data in the European Union. However, some technical service providers, particularly international technology providers, may process data outside the European Union or the European Economic Area.

When data is transferred to countries outside the EU/EEA, we ensure that appropriate safeguards are in place, for example an adequacy decision by the European Commission, standard contractual clauses or other safeguards provided for by law.

17. Storage period

We only store personal data for as long as necessary for the respective purposes. The following storage periods generally apply:

For inactive accounts, we may send a reminder after 24 months of inactivity. If there is no response within 3 months, we can delete or anonymize the account, provided there are no legal retention obligations to the contrary. Statutory retention obligations remain unaffected.

18. Your privacy settings

You can manage certain settings yourself in the app. Specifically, you can delete individual runs, delete your account, turn off cloud sync for run data where available, and turn off push notifications from your device.

The cloud-sync toggle does not currently control the run-related story statistics consisting of the technical user identifier, timestamp and run duration. These data are stored in the cloud for every run. You can disconnect the voluntary Strava connection in the settings.

Location access during an active run is required for interactive story mode. If you deactivate location access via your operating system, RUNLINE cannot be used or can only be used to a limited extent.

For users under 16 years of age, cloud storage of location, route, distance and speed of individual runs is generally deactivated. For ages 16 and up, cloud sync for running data can be enabled by default, but can be disabled.

19. Data Security

We use technical and organizational measures to protect your data. These include in particular:

Only persons who need this access for operations, development, support or security are granted access to personal data. These are in particular managing directors and authorized developer admins.

20. Your rights

You have the following rights in accordance with legal regulations:

If you want to exercise your rights, you can contact us at any time: info@runline.eu.

21. Objection to processing based on legitimate interests

To the extent that we process personal data on the basis of legitimate interests, you can object to this processing for reasons relating to your particular situation. You can submit your objection info@runline.eu direct.

22. Additional information about the runline.eu website

When you visit our website, we process personal data that is technically necessary to provide the website, as well as data that you voluntarily provide to us.

22.1 Provision of the website and server log files

When you access our website, the web server automatically processes technical access data. This may include: IP address, date and time of access, page or file accessed, referrer URL, browser type and browser version, operating system, amount of data transferred and HTTP status code.

This processing is necessary to technically provide the website, detect attacks, analyze errors and ensure the security of the website. The legal basis is Article 6 Paragraph 1 Letter f GDPR. Our legitimate interest lies in the secure and stable provision of our website.

22.2 Contacting us via email or contact form

If you contact us by email or via a contact form, we process the data you provide, in particular your name, email address, content of your message, time of the request and, if necessary, other information provided voluntarily. We use this data to respond to your request.

The legal basis is Article 6 Paragraph 1 Letter b GDPR if your request is related to a contract or pre-contractual measures, and otherwise Article 6 Paragraph 1 Letter f GDPR. Our legitimate interest lies in processing your request.

22.3 Newsletter, waiting list and app updates

You can sign up for RUNLINE information, app updates, launch information, beta information, or similar communications on our website. In particular, we process email address, time of registration, confirmation status in the double opt-in procedure, IP address during registration and confirmation, unsubscribe status and, if applicable, source of registration, for example website, beta list or crowdfunding context.

We use the double opt-in procedure to ensure that you have registered yourself. The legal basis is your consent in accordance with Article 6 Paragraph 1 Letter a GDPR. You can revoke your consent at any time with future effect, for example via the unsubscribe link in every email or by sending a message to info@runline.eu.

22.4 Cookies and similar technologies on the website

Our website may use cookies and similar technologies. Technically necessary cookies are used for the website to function, for example for security, language settings, form functions or storing your cookie settings.

We only use non-essential cookies or similar technologies, especially for analysis, marketing or external media, if you have given your prior consent. You can change or withdraw your consent at any time via the website's cookie settings.

22.5 Website Analytics

If we use website analysis tools, we only use them with your consent. Website analysis can help us understand how visitors use our website, which pages are particularly relevant and how we can improve our content.

Depending on the tool used, a shortened or full IP address, device and browser information, visit duration, pages visited, clicks, referrers, approximate location information and technical identifiers may be processed. The legal basis is your consent in accordance with Article 6 Paragraph 1 Letter a GDPR. If we do not use website analysis that requires consent, this processing will not take place.

22.6 Online marketing and pixels

If we use marketing or advertising technologies such as Meta Pixel, TikTok Pixel, Google Ads Conversion Tracking or similar tools on the website, this will only happen with your consent. Such tools can be used to measure the success of campaigns or to display advertising on external platforms in a more targeted manner.

Depending on the tool, IP address, device and browser information, pages viewed, clicks, campaign information, technical identifiers, referrers and, if necessary, interactions with forms or buttons can be processed. The legal basis is your consent in accordance with Article 6 Paragraph 1 Letter a GDPR. If you do not consent, these technologies will not be activated.

22.7 Embedded Content and External Links

Our website may contain external content or links, for example to App Store, Google Play, Startnext, Instagram, TikTok, YouTube or other social media or partner sites. If you click on an external link, you will leave our website. The respective providers are responsible for the processing of personal data on external websites.

If external content is embedded directly on our website, for example videos, maps or social media content, it will only be loaded if this is technically necessary or if you have given your prior consent.

22.8 WordPress

Our website is based on WordPress. WordPress may process technical data necessary for the operation, security and administration of the website. If WordPress plugins are used, they can process additional data depending on their function. We make sure to only use plugins that are necessary for the operation of the website or that are only activated with your consent.

22.9 Storage period for website data

The following storage periods also apply to website data: website server logs usually up to 30 days, unless longer storage is required to clarify security incidents; Newsletter data until you unsubscribe or revoke your consent; Contact requests via the website up to 3 years after completion of the request; Cookie consents as long as necessary to demonstrate consent.

23. Additional information about the beta phase

If you take part in a RUNLINE beta phase, we will test with you a version of the app that has not yet been finally released. The aim of the beta phase is to find technical errors, obtain user feedback and improve the app before the official launch.

23.1 Participation in the Beta Phase

For participation in a beta phase, we can process the following data in particular: name or username, email address, beta access or invitation link, platform used, TestFlight or Google Play beta participation status, voluntary feedback, answers from feedback forms or surveys, technical error descriptions and, if necessary, screenshots or voluntarily submitted attachments.

The legal basis is Art. 6 Para. 1 lit. b GDPR, insofar as the processing is necessary to carry out the beta participation. Article 6 (1) (f) GDPR may also apply to voluntary feedback. Our legitimate interest lies in improving RUNLINE before publication.

23.2 Use of the app during the beta phase

During the beta phase, the app generally processes the same data as described in the app sections of this data protection declaration, in particular account data, technical data, age and approval data, running data, location data, story progress and error data. The age-dependent restrictions on cloud storage also apply in the beta phase.

Beta versions may contain additional technical logs, bug reports, or debug information if necessary to find bugs and improve the app. Even in the beta phase, we do not use any personal data for advertising tracking or personalized advertising in the app.

23.3 Feedback, surveys and interviews

When you voluntarily provide feedback, participate in surveys, or talk to us about your experience, we process the information you provide. This may include answers to questions about the app, assessments of user-friendliness, error messages, suggestions for improvement, information about the devices used and voluntary information about your running or usage behavior.

We only use this feedback to improve RUNLINE, fix bugs and make product decisions.

23.4 TestFlight and Google Play Beta

If you test RUNLINE via Apple TestFlight or Google Play Beta, Apple or Google also processes personal data under their own responsibility. Depending on the platform, this may include technical data, device information, crash reports, installation data and usage information. The data protection regulations of Apple and Google apply to this processing.

23.5 End of beta phase

After the beta phase ends, we can delete beta-related data or transfer it to the regular RUNLINE account if this is necessary for later operation or if you continue to use the app. We may reuse voluntary feedback and survey results in aggregated or anonymized form.

23.6 Storage period for beta data

The following additional storage periods apply to beta data: Beta participation data until the end of the beta phase and thereafter only to the extent necessary for further use, evidence or support; voluntary beta feedback for up to 3 years or permanently in anonymized form; Technical error reports from the beta phase usually last up to 90 days, unless they are needed longer to correct specific errors.

24. Additional information on crowdfunding and supporters

If you have supported RUNLINE via a crowdfunding platform, the respective platform initially processes your data under its own responsibility.

We may receive information from the crowdfunding platform that is necessary to process your support, in particular your name, support amount, chosen consideration, email address, if provided by the platform, and, if applicable, shipping or contact details if required for consideration.

We use this data to track support, provide compensation, grant beta access, or send project-related updates. We only send newsletters or promotional emails if you have given your consent.

25. Revocation of consent

If processing is based on your consent, you can revoke this consent at any time with future effect. This applies in particular to newsletters, unnecessary website cookies, website analysis, marketing pixels or embedded external content if such services are used. The lawfulness of processing until revocation remains unaffected.

26. Changes to this Privacy Policy

We may adapt this privacy policy if RUNLINE, our website, our technical systems, age or parental controls, cloud functions or legal requirements change. You can find the current version in the app and on our website. If there are significant changes, we will inform you in an appropriate manner.