Privacy

Last updated: 22 October 2026 · Deutsche Fassung

In short

Controller

Codex Consulting GmbH, Bahnhofstrasse 21, 6300 Zug, Switzerland.
Contact: see the legal notice.

Route planner on this website

Route: Waypoints you set and your routing settings are sent to our routing server for calculation. With “Secure the tour”, a simplified route outline is transmitted in order to find fuel stations along the way.

Address search: The search text you enter is transmitted to our server and resolved there against our own place database.

Map and sharing: Map tiles come from our own service. A shared plan is held in the fragment of the link; that fragment is not sent to the server when the page is requested.

Optional website access, profile and accommodation reports

These features become available only after technical activation. The route planner remains usable without an account. Access requires no email or password: you explicitly connect the browser in AuraCurve. This website QR is not a group or route QR.

Access: We store a random account identifier, device label, device and session identifiers, hashes of access and recovery secrets, and creation, expiry and revocation times. The device secret is stored securely on the phone. The browser receives a necessary HttpOnly session cookie for at most 30 days; it is not used for advertising. A connection QR is valid for five minutes and can be used once. Recovery replaces the recovery key and revokes previous devices and browser sessions. Access credentials are not public.

To safely retry an interrupted recovery, the service keeps an encrypted copy of its response, including the new access and recovery values, for up to 24 hours. A retry is bound to the original recovery attempt. The response is no longer issued after another key rotation or device revocation. The app also keeps the pending attempt in protected storage until it is completed or you explicitly discard it.

Profile: Your display name, biography and optional links are associated with your account. Profiles are private by default. Only after you explicitly enable public visibility can these details be accessed through the public profile link. Local rides, travel plans and accommodation reports are not part of a public profile.

Accommodation reports: We store the chosen accommodation, your parking observation, visit date, comment, optional source link, account association and review status with review notes. Only you and authorised reviewers have access. A report does not publish your visits or automatically change accommodation facts. Do not enter other people's names, contact details or booking references.

Purpose and legal basis: The access and private profile management you request provide these optional functions (Art. 6(1)(b) GDPR). Public profile visibility and use of your accommodation observations for review rely on your separate consent (Art. 6(1)(a) GDPR). Refusing or withdrawing this consent does not prevent you from using the route planner.

Storage and deletion: Account, profile and report data are processed in a non-public database at Cloudflare, separate from the public accommodation dataset. Profile details remain until you change or delete them; you can disable public visibility at any time. Reports remain for review and traceability until withdrawn or deletion is requested. Withdrawal removes the comment and source link; a non-public status record remains. “Delete profile” does not delete access or separately stored reports; reports remain withdrawable afterwards. For complete account deletion or access requests, contact us via the legal notice. You can revoke devices and sessions yourself. Expired codes and sessions no longer grant access; their technical records are removed through protected operational maintenance.

Network features of the app

Live group

The live group is off by default. You switch it on per ride and can leave at any time. A group holds up to 50 riders. What is then transmitted is your precise position, the time of measurement and — where available — speed and heading. Added to that are the short name and the colour you chose yourself. The creator is the group leader and additionally transmits the destination and its display name, a line for the group display simplified to at most 160 points, and the complete current navigation plan with the route geometry and turn instructions. Guests adopt this plan; if they deviate, the app calculates a way back to the shared route.

Rider missing: From the transmitted positions, the relay works out the order along the route and detects when a rider has not sent a position for several minutes, is standing still while the others ride on, or falls clearly behind. The group then sees that rider's status, since when it applies, and the last position; only the group leader and the two neighbours in the order get an announcement. If your connection drops, you therefore stay in the group as missing, with short name, colour and last position, for up to three hours. If you leave the group, you are removed at once and the others see that you have left. With “Short break” you announce 15 minutes of quiet; the group sees this status and does not report you as missing meanwhile.

Break and shared stop: If you request a break, your short name and — only if you pick one — the reason (break, fuel, toilet, problem) go to the group; a request is possible at most once every ten minutes. If the group leader agrees, the leader's app looks for a stop along the route and sends its location and name to everyone as the shared stop; it is valid for at most three hours. The group leader can also remove riders, renew the code or close the group for everyone. When the code is renewed, the group state is handed over in memory to the group with the new code.

Crash alert to the group: If you have switched on crash detection and its countdown runs out, the whole group learns of it at once — with short name, colour and location. An all-clear lifts the alert.

The recipients are the participants of the same group. Access works through the six-digit code, QR code or link that was passed on. There is no account and no persistent device identifier; the relay assigns the rider identifier at random and only for this group, so that you keep your place after a connection drop.

The relay at gruppe.auracurve.app keeps the last position of each rider, the destination, the simplified route, the current navigation plan, open break requests, the shared stop, ongoing crash alerts and the auxiliary values for the order and “rider missing” in memory only. The only things stored persistently per group are the time of creation, the time since which it has been empty and, where applicable, the marker that it has been closed or moved — without code, short names or positions. The group ends after inactivity, and after twelve hours at the latest; this entry is then deleted as well. Join attempts are rate limited per IP address in volatile memory for about one minute, the creation of new groups for about one hour. Group processing is technically pinned to Cloudflare's EU jurisdiction.

Received positions can be stored locally together with your ride so that the shared ride can be replayed later. They disappear when you delete the ride.

The legal basis is your consent (Art. 6(1)(a) GDPR). Leaving the group withdraws it with effect for the future and ends the transmission.

Emergency: crash detection and emergency SMS

Crash detection is voluntary and off by default. You switch it on in the settings after the app has explained which data goes to whom. The legal basis is your consent (Art. 6(1)(a) GDPR). Switching it off withdraws it with effect for the future.

On the phone: Only during navigation or recording does the app evaluate the accelerometer and GPS speed on the device. As long as no alarm is triggered, these values do not leave the phone. If the app detects a crash, a 60-second countdown with an alarm sound starts. If you tap “I'm OK” — also on the watch — nothing is sent. The names of your emergency contacts stay on the phone.

Emergency service: When you switch the feature on, the app registers with our emergency service at notfall.auracurve.app. It runs at Cloudflare; its storage is technically pinned to Cloudflare's EU jurisdiction. What is stored is a random device identifier, a hash of the device secret and two timestamps. For each contact — at most three, numbers from the EU, EEA, Switzerland and the United Kingdom only — the phone number, its hash, status, message language, channel and an unsubscribe token are added. The names of the contacts, your name and your position are not stored. Your name (letters only, at most 30 characters) is sent with every request and only inserted into the messages.

Alarm: When the countdown runs out, the app sends position, accuracy, time, time zone, language and your name. From this, every registered contact receives an SMS with your name, the time, the accuracy and a map link to your location. The link leads to Google Maps; if the contact opens it, Google processes the location under its own terms. For 24 hours the service stores only the alarm identifier, time, time zone and which contacts (as a hash) were notified — so that a retry never messages anyone twice and the all-clear reaches the same contacts. The position is not stored. With “Send all-clear”, these contacts receive an all-clear. A test SMS contains only your name. If you are riding in a live group, the group also learns of it when the countdown runs out.

Emergency contacts, only with their consent: Every newly entered contact receives one SMS with your name and the question whether they want to be an emergency contact, together with a link. Only once they choose “Yes, I agree” there do they receive alarm, all-clear and test messages. The legal basis is their consent (Art. 6(1)(a) GDPR); as proof, the service stores the time of the consent. We send the one-time request SMS so that the contact can be asked at all (legitimate interest, Art. 6(1)(f) GDPR). Until they answer, the service stores only the number, the language and the status “waiting”. If the contact chooses “No, thanks” or later withdraws their consent through the same link, they receive no more messages, not even from other devices. For that purpose their number remains blocked permanently as a hash; they can change their mind through the same link. If you remove a contact, it is deleted at once. The SMS are sent by seven communications GmbH & Co. KG (seven.io, Germany) as our processor; seven.io receives the contact's number and the text of the SMS.

WhatsApp, only with the contact's consent: Where we offer WhatsApp as an additional channel, the page behind the link offers WhatsApp in addition after the consent. Only if the contact chooses “Yes, also on WhatsApp” there do alarm, all-clear and test go to their number on WhatsApp in addition to the SMS; the SMS is always included. The legal basis is the contact's consent (Art. 6(1)(a) GDPR), which is confirmed on WhatsApp. As proof, the service stores the hash of the number, the time and the source of the consent. The contact can withdraw at any time on the same page (“SMS only”), by replying “STOP” on WhatsApp or by unsubscribing. Incoming WhatsApp messages are only checked for “STOP” and are not stored. The consent also lapses as soon as no rider has the number entered any more. Sending runs through seven.io to Meta's WhatsApp Business Platform (Meta Platforms Ireland Ltd. and Meta Platforms, Inc., USA). What is transmitted is the number, the message content (rider's name, time, accuracy, map link) and technical delivery details. For the transfer to the USA we rely on the EU-US Data Privacy Framework (Art. 45 GDPR), supplemented by standard contractual clauses (Art. 46 GDPR).

Abuse protection and deletion: To prevent abuse, the service counts messages per device and per number; these counters are deleted after 48 hours. When a device registers, the IP address is noted only as a hash, counted for one hour for the rate limit and deleted together with the other counters after 48 hours. If you switch crash detection off, the service deletes the device and its contacts at once; without a connection, the app catches up at the next sync. Devices that have not checked in for 365 days are deleted automatically together with their contacts. The emergency service writes no access logs; numbers, names and positions are not logged.

Important: Crash detection is not an emergency call system and no substitute for the emergency number 112. It only works with a mobile network and during an ongoing ride. Not every crash is detected, and not every alarm is a crash.

Storage, logs and service providers

Routing, search, traffic and weather content is not combined into a user profile. The routing server keeps no general access log. Technical error logs may contain the IP address and the path and are deleted after 14 days at the latest. Our application services write no group positions, emergency positions, phone numbers, weather coordinates or traffic areas into content logs.

These providers process technical connection data under their own terms. The required agreements are in place with our processors.

Permissions and backups

Location serves navigation, recording and — once activated — the live group and the emergency SMS; the camera serves the QR code, and notifications serve visible background operation, the emergency countdown and the group's alerts. On Android you can additionally allow full-screen notifications so that the countdown appears above the lock screen.

Motion sensors serve ride data: lean angle and pitch, including wheelie, stoppie and jump, are calculated on the device and stored with the ride; a GPX export that you trigger yourself contains them. With crash detection switched on, the accelerometer also serves crash detection. You can pick emergency contacts through the system's contact picker; the app then receives only the chosen name and number, no access to your address book.

Device backups by Apple or Google may contain local app data; you control that in your system settings. The device credential for the emergency service is excluded; a new phone registers afresh by itself.

Your rights

You have, in particular, the rights of access, rectification, erasure, restriction, data portability, objection and to lodge a complaint with a supervisory authority. You delete local rides in the app. You delete the data held by the emergency service by switching crash detection off; as an emergency contact, you unsubscribe through the link in your information SMS. For any other request, contact us via the legal notice.

Language

This is a translation of the German original for convenience. In case of any discrepancy, the German version prevails.