Back to the home page
Privacy

Privacy Policy

Last updated: 25 June 2026

Short version: We operate BOB 600 with data minimisation in mind. The website does not use advertising profiles, cross-site tracking or tracking cookies. For statistics, we evaluate technical events without cookies. For the notification list, we store only the data needed for the notification.
This English version is provided for convenience. In case of discrepancies, the German version of the Datenschutzerklärung shall prevail.

1. Controller

The controller responsible for processing personal data on this website and in the BOB 600 services is:

myITsolutions GmbH
Gatower Straße 197a
D-13595 Berlin
Germany

Represented by: Sven Fröbel, Managing Director
Email: Show email address
Website: myitsolutions.de

2. General Information

We process personal data only to the extent necessary for operating the website, providing app functions, notifying users about the launch of BOB 600, managing participation, support, security and the technical improvement of the offer.

The legal bases arise in particular from Art. 6(1)(a) GDPR (consent), Art. 6(1)(b) GDPR (contract or pre-contractual measures) and Art. 6(1)(f) GDPR (legitimate interests).

3. Hosting and Technical Provision

Our website, app backend and database are operated on servers in Germany. We currently use hosting infrastructure from Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany.

When the website is accessed, the server processes technically necessary data, for example IP address, date and time of access, requested URL, transferred data volume, HTTP status, browser and operating system information and referrer information, insofar as these are transmitted by the browser.

The purpose is delivery of the website, system stability and security, and error analysis. The legal basis is Art. 6(1)(f) GDPR. Our legitimate interest lies in secure and reliable operation of the website.

4. Cookies and Device Access

The public website does not use tracking cookies for reach measurement and does not use cross-site tracking. We do not store a permanent visitor ID in the browser for website statistics and do not create advertising profiles.

If technically necessary app or admin functions later require local storage or session technology, this will be used only to the extent required for the requested function. There is no further use for advertising or profiling.

5. Cookieless Statistics

We want to understand whether BOB 600 is found and used. For this purpose, we plan or use our own data-minimised statistics without tracking cookies and without a permanent browser-side identifier.

In particular, the following may be recorded:

We do not store complete IP addresses for statistics and do not create personal advertising profiles. Evaluation is aggregated in order to assess reach, technical function and interest in the offer. The legal basis is Art. 6(1)(f) GDPR. Our legitimate interest lies in improving, measuring and developing BOB 600 according to demand.

If your browser sends a Do Not Track signal, we will take this into account when implementing our own statistics, insofar as technically possible.

6. Notification List

If you would like to be notified when BOB 600 launches or registration opens, we process your email address and technical proof of your consent.

In particular, we store:

The purpose is notification about the launch, the opening of registration and directly related information about BOB 600. The legal basis is your consent pursuant to Art. 6(1)(a) GDPR.

You may withdraw your consent at any time with effect for the future, for example by email to Show email address. After withdrawal, we delete or block your email address for this purpose, unless statutory retention obligations apply.

7. Rider Account and App Use

A rider account may be required for later use of the BOB 600 app. We process data necessary for the account, login, participation, result determination and support.

Depending on use, this may include:

The legal basis is Art. 6(1)(b) GDPR where processing is necessary to provide the account and app functions. For voluntary additional information, Art. 6(1)(a) GDPR may apply.

8. Checkpoints, Location Data and Track Proof

BOB 600 uses QR checkpoints to document start, intermediate points and finish in a traceable way. When a checkpoint is scanned, the checkpoint, time and GPS location for this scan may be processed.

If you voluntarily activate live tracking, location pings may be processed during an active attempt and displayed in the admin area or via a live link shared by you. Live tracking is not required to visit the website.

After finishing, track proof may be required. We process the GPX or comparable track file provided by you in order to verify compliance with the rules and the route.

Track analysis may also form the basis for result verification, plausibility checks and achievements. In particular, route, times, speed, stop or movement patterns and contextual information derived from external sources, such as weather or daylight conditions, may be taken into account.

The legal basis is Art. 6(1)(b) GDPR insofar as these data are necessary for participation, classification and result verification. Voluntary live tracking is additionally based on your active decision to enable that function.

9. Support, Assistance and Emergency Contact

If you use support, assistance or route-disruption reports, we process the content you submit, time, request status, affected route, attempt, rider account and, where applicable, location data if you transmit them.

The assistance/location-send function does not replace an emergency call. In case of danger to life or limb, the official emergency numbers 112 or 110 must be used immediately. Through BOB 600, we can only try to make contact or inform a stored assistance contact.

The legal basis is Art. 6(1)(b) GDPR for support related to app use and Art. 6(1)(f) GDPR for security, abuse prevention and error handling.

10. Leaderboards, Results and Achievements

If you participate in BOB 600, result data may be displayed in leaderboards, DNF lists or achievement overviews. This includes in particular rider name or alias, route, season, finish/DNF status, time, rough performance data and unlocked achievements.

We recommend not using your real name as a public rider name if you do not want your name to appear in public lists. The display is based on the participation rules and the result presentation required for the challenge, Art. 6(1)(b) GDPR.

11. Email Communication

If you contact us by email or we write to you in connection with BOB 600, we process your email address, message content and technical communication data. The purpose is handling your request or carrying out the relevant function.

We use Hornetsecurity as mail provider for the technical provision and protection of our email communication. In particular, email addresses, message content, technical sending and receiving data as well as security and filter information may be processed. Where Hornetsecurity processes personal data on our behalf, this is done on the basis of a data processing agreement.

12. Recipients and Processors

Within myITsolutions GmbH, only persons who need access for operation, support, administration or development receive access to data. External recipients may be hosting, email, maintenance or IT service providers where this is required for operation.

Data are not disclosed for advertising purposes.

13. Storage Period

We store personal data only for as long as required for the respective purposes or as long as statutory retention obligations exist.

14. Your Rights

Under the GDPR, you have in particular the following rights:

To exercise your rights, you can contact Show email address.

15. Right to Lodge a Complaint

You have the right to lodge a complaint with a data protection supervisory authority if you believe that the processing of your personal data violates data protection law. In particular, the Berlin Commissioner for Data Protection and Freedom of Information may be competent.

16. Changes to This Privacy Policy

We update this privacy policy when functions, technical implementation or legal requirements change. The current version is available on this website.