This is a translation for convenience only. The German version is legally binding: Datenschutzerklärung der App.
Privacy Policy (App)
This page describes the data processing in the Curvalia app. A separate policy applies to the website. Information pursuant to Art. 13 and 14 GDPR.
1. Controller within the meaning of the GDPR
Jan Bittner
Sole proprietorship (small business)
Heinrich-Budde-Str. 29
04157 Leipzig
Germany
Email: kontakt@curvalia.app
Contact form: curvalia.app/en/kontakt.html
For data protection matters and all requests under section 8: datenschutz@curvalia.app
No data protection officer has been appointed: the requirements of § 38 BDSG (German Federal Data Protection Act: at least 20 persons constantly engaged in the processing) are not met by a sole proprietorship.
2. What data Curvalia processes
On your device
Ride book, recorded routes, saved routes, settings, the summary of your preferences from the help chat (if you use it) and your identifier are stored in the app's storage on your device. The secret part of your account is stored in the operating system's protected key store (Keychain or Keystore). This is strictly necessary for the operation of the app (§ 25 (2) no. 2 TDDDG, German Telecommunications Digital Services Data Protection Act). On the iPhone, up to app version 1.3.23 the app's storage is part of your iCloud backup, if you have switched it on. Apple holds the key to this backup, unless you use "Advanced Data Protection for iCloud". From version 1.3.24, Curvalia takes its storage out of the backup – if you have rides but have not yet backed up your account key, only after the app has pointed this out to you once. This is a hint to Apple, not a guarantee; older backups keep the old state until Apple replaces them. Android backup is disabled for Curvalia.
Location (GPS)
The app needs your location for the map display and navigation. With background permission, location tracking continues even when the screen is locked (voice guidance). In the following cases, your position is sent to our own routing engine:
- when planning a route, the points you set – so with "My location" as the start, your current position;
- when recalculating during navigation, your current position as the new start;
- when ending a recording, the recorded track, once, in order to match it to the road network;
- when loading points of interest and gas stations, the map area around you.
The engine answers the request and does not store the points. Only if a request fails can it appear in the server's error log; we delete this log after 7 days at the latest. In addition, the app sends your position during a group ride you have actively joined (see "Group rides").
Ridden routes
Recorded tracks (ride book, conquest map, statistics) remain on your device. Only when you back up your account key are they backed up on our server – end-to-end encrypted. The key for this never leaves your device, unless you store it somewhere yourself (see below); we are technically unable to read the contents of the backup. After each ride, the app also reports which dream roads you have ridden (a counter per road), so that you and your friends can see the progress.
Account key with Apple or Google
Only if you switch this on yourself does the app store your account key in your iCloud Keychain (iPhone) or in your Google account (Android, Google Block Store). Only this key is stored there, no rides. It is end-to-end encrypted there: Apple or Google cannot read it, and we receive nothing. On Android this only works with end-to-end encryption, i.e. with a screen lock set up. Any device with your Apple ID or Google account and your device passcode can read it. Apple or Google may see that an entry exists and when it changes. The entry remains until you switch off the switch under Settings → Account or delete your account in the app. Deleting the app is not enough. If your iCloud Keychain happens to be off when you switch it off, an encrypted copy remains in iCloud until you switch the keychain back on.
Account & friends
On first launch, the app creates a random identifier without a name (no email, no password, no real name needed). This identifier is your friend code. Friend list, display name and – only for tours actually ridden – km, points (including those of the current calendar year, the season points, and the points and kilometres of the current month) and level are stored on our server for as long as your account exists. Friends also see the season and month figures, so that your list can be sorted by season and month; a past month is overwritten by the next one. Friends only see which dream roads you ride once you have also added them. You appear in the global leaderboard only if you switch this on yourself (switch at the top of the global leaderboard); it shows display name, rank, points, kilometers and number of tours – never your identifier. On iPhone, the app also stores your referral code (ten characters, derived from your identifier) in your account. It goes only to whoever adds you as a friend with your friend code – so that you can both get your free month – and appears nowhere else. If you add bikes, friends see brand, model and the figures from your ridden tours per bike (km, tours, elevation, best curve score). The leaderboard shows your most-ridden bike (brand, model, km) only if you agree to that there separately. The photo of your bike stays on your device and in your encrypted backup – unless you allow sharing on the bike sheet. There are two separate switches for that, both off until you switch them on: "for friends" and "in the leaderboard" (the second applies only if you take part there). If you switch one on, the app uploads a reduced copy of the photo of your currently active bike (JPEG, at most 480 pixels on a side, without capture data such as the location – the server strips it) to our server. Only your photo, never your name with it. Friends see it only if you have added them yourself – not merely because they entered your code – and only with the "for friends" switch; the leaderboard shows it only with the "in the leaderboard" switch. It is not part of the list rows; the app fetches it individually when someone opens your profile. If you switch bikes, the shared photo switches too; if the new one has none, nothing is shared. If you switch both off or remove the photo, we delete it immediately. Anyone who sees your photo can report it; we look at the report within 24 hours and remove the photo if it breaks the rules. If you choose a profile picture and showcase, our server stores up to three achievements along with the style and two colours of your bike. Friends always see them, the leaderboard only if you take part there. Your ridden tracks are never included.
Season and Hall of Fame
The global leaderboard has two views: all-time and season (one calendar year). For the season, the app reports the points of this year with every score update; our server stores one number per account together with the year – even if you do not take part. It is only visible if you take part in the leaderboard: then in the season view, to all users of the app – and, if you are among the top five, after the season in the Hall of Fame (see below). The row shows the same details as in the all-time view, plus the season points, and carries an opaque list code: calculated from your identifier with a value that only we have, always the same for your account and not traceable back to the identifier. With it, other people can send you a friend request (see below).
After the turn of the year, the server records the top five of the past season in the Hall of Fame, namely among those who take part in the leaderboard at that moment and have season points. It shows display name, season points and – if you have chosen one – profile picture and showcase, plus your list code; that only serves to find the entry again when your account is deleted. All users of the app can view the Hall of Fame. An entry is a snapshot: it does not change any more, not even if you change your name or switch the leaderboard off. It stays until your account is deleted.
Friend requests
From the leaderboard you can send a friend request to someone who takes part there. The request is stored on our server in the record of the person you ask: your identifier and the time. The person you ask receives from our server your display name, your profile picture including showcase and your identifier (your friend code); the app shows them the name and the picture. A friendship is only created if they accept; if they decline, the request is deleted. A request is valid for 30 days. On your device the app also remembers the list codes of the people you have sent a request to (the last 200), so that it shows you the next time you open their profile that the request has already been sent. This list goes neither to our server nor into your encrypted backup.
Shared routes
If you share a route, it is stored on our server and can be retrieved via its code – that is the purpose of sharing. These routes are therefore NOT encrypted, unlike your backup: anyone who has the code can view the route and ride it. If you also add them to your profile, your friends see them too. What is stored is the course of the route, a name, the length and your identifier as the owner. You can delete them yourself at any time in your profile.
Preview of a shared link
When you send a link to a route, a group ride or yourself, the recipient’s messenger shows a small preview, and the recipient’s app asks by name (“Add Micha as a friend?”). For that, our server hands out the following for the code in the link, without sign-in: for a route its type, length, curves, elevation gain and the name you gave it yourself, and your display name only if it was included when sharing; for a group ride whether it is still running, the display name of whoever started it, the route’s name, its length and how many are riding; for your friend link your display name, your level and your profile picture (sticker and colours). Never included are positions, the exact course of the route (at most the simplified line, see below) or your account identifier. Blocked and deleted accounts show nothing.
Follow-along link and the line of a shared route
With "Share my location" you send a link to people who don't have the app. Whoever has it sees in a browser, without signing in, your last position (rounded to about ten metres), how old it is, your display name and the line of your route – only yours, never the others' in a group ride. For this the app reports your position to our server about every 30 seconds; as in a group ride, only the latest is kept, in memory. The link is valid until 10 minutes after the ride ends, for 12 hours at most, and you can stop it at any time; after that it shows nothing. When you share a route, the app also sends a simplified line without the first and last kilometre and, if you like, a preview image (line, name, length), so the link's web page and the messenger preview can show it – without a map background. For routes that are not on your profile we delete the line and image after 180 days; otherwise together with the route.
Group ride album and photos on your rides
After a group ride, everyone who rode along can add up to three photos to a shared album. Only those who rode along can see it. We store the photo reduced in size and without metadata (so without place, time or camera), along with your identifier as the sender; your display name is shown. You can remove your photos at any time, and anyone can report someone else's photo. After 7 days we delete the album and its photos. Photos you add to your own ride stay on your device only; they go neither to us nor into the backup.
Your own dream roads
If you publish your own dream road, we store its points, the name, your note and opening times as well as your identifier as its creator; if you wish, also your display name as a visible label. If you vote on a road or have ridden it, we store this under your identifier – only the total is shown, never who. You delete all of this together with the road or with your account.
Group rides
You join a group ride actively – with a code or QR code shown to you by the creator. While the ride is running, the app sends your position to our server: in the foreground, with fellow riders visible, about every 2 seconds; in the background, depending on the setting, about every 2 seconds (“Precise”) or every 10 seconds (“Battery saver”); if nobody else is visible, the interval can be longer. Only your LAST position is stored there, never a history – and it is visible exclusively to the participants of the same ride, as is how old that report is. Your display name is visible to the participants of the same ride; if you invite a friend who has added you themselves and allowed notifications, it also appears in that friend's notification and passes through Expo and Apple or Google for this (see "Notifications"). Your position is never part of it. Instead of your account identifier, the others see a pseudonym that applies only to this one ride. Whoever navigates additionally transmits the planned route and, continuously, the track ridden so far, so that fellow riders can navigate along and get credit for the part they rode. Positions and the ongoing track are kept only in the server's working memory, never on disk; they are deleted 30 minutes after the end of the ride, at the latest 12 hours after the start. The planned route and the track shared at the end, on the other hand, are stored on the server under a code like any shared route (see above) and remain there until the person who shared them deletes them or closes their account. The proofs of presence from which your credited part is calculated remain on your device.
Fixed groups
You found a fixed group yourself, or you join it with an invitation code someone from the group sends you. We store the group's name and symbol, the identifiers of its members with the time they joined, who founded it, the invitation code (valid for 14 days) and the announced rides: time, time zone, a meeting point if chosen and the code of a shared route, who announced it and who answered how. Only the members of the same group can see this – including your display name, your profile picture and your answers. When someone announces, changes or cancels a ride, or starts a group ride for the group, the other members get a notification via Expo and Apple or Google (see "Notifications") with the group's name, the time and, where applicable, the route's name or the display name of whoever is heading out – never with the meeting point. Whoever you have blocked (or who has blocked you) gets no notification from you. The reminder 90 minutes before a ride you said yes to is scheduled by the app on your device; our server does not know about it. Without an invitation code, nobody outside the group sees anything; with it, only the name, symbol and the number of members.
Respect and challenges
Between friends who have each other in their lists (and where neither has blocked the other), you can give respect to a ride or a shared route. We store it with the recipient: your identifier, what it refers to (the day of the ride or the route's code) and the time. Only the recipient sees it, with your display name and profile picture; on a shared route, other friends only see the number. You create a challenge for yourself and up to five friends: what counts (kilometres, curve points or dream roads), until when, who said yes and the figure at that moment. Only what has been added since then is compared, from the figures your friends see anyway – never speed, lean angle or location. The invited friends get a notification (with your name only if they added you themselves). Only the participants can see the challenge. Which friends rode how much lately is worked out by the app on your device from what it saw the last time you opened it; our server stores nothing for this. A dream road shows how many riders have ridden it – only as a number and only from three.
Reported road closures
If you report a closed road, we store the marked area, the time of the report and an expiry date. Other riders see only the area and how long the report is valid – never who reported it. Your identifier is stored internally, solely so that you can withdraw your own report; it is never disclosed. Every report deletes itself after 14 days.
Notifications (push)
Only if you switch on "Receive notifications" does the app store a device identifier of the push service (Expo/Apple/Google) with your account, together with the platform, the app language (so the notification arrives in it) and the time – per device, at most five. If you sign in on the same device with another account, the identifier moves there. We use it to tell you that a new version is available, to forward invitations from friends to group rides and to tell you when someone has ridden a dream road you published or has sent you a friend request; the notification about a friend request never names anybody. The notification about an invitation names the display name of the person who invited you ("Jan is heading out"), but only if you added that person as a friend yourself; otherwise it names nobody. For this the name passes through Expo and Apple or Google and appears on your device's lock screen. It contains no code, no identifier and no location; the notification about a ridden road contains neither a name nor the road. The app shows what is behind them. If you switch the switch off in the settings, we delete the identifier from the server; likewise if the push service reports that it has become invalid. Navigation notifications on your device are independent of this and do not leave the device.
Bug reports
We store voluntary bug reports with your text, a technical status report (app version, platform, screen, running function), optionally a screenshot and your identifier – the latter so that the app can show you the processing status. The screenshot shows what was on the screen at that moment and can therefore contain names of friends or routes; if your account key is on the screen, no image is attached.
Contact form
If you write to us via the contact form on curvalia.app, we store your name (if given), your email address and your message on our server in order to reply to you.
App updates
On launch, the app asks Expo (u.expo.dev) whether a new version is available. In doing so, your IP address, platform, app version and a random installation identifier are sent to Expo.
Help chat with AI
Purpose: In the "Help & questions" sheet you can ask an AI questions about the app and get an immediate answer. The chat exists where available and only if you expressly tap "Agree" there; there is no default setting. No data goes to Anthropic before your consent. If you do not consent, the way without AI remains (see "Support requests") and you lose nothing. What goes to whom: Your messages go to Anthropic PBC (USA, model Claude Haiku). So that the answer fits your case, the AI also reads, and only about you: the number and kilometres of your rides, your achievements and progress, your Plus status, your motorcycles in the garage, your own bug reports with their status, and app version and platform. It never sees other users or our internal notes. Anthropic processes this on our behalf. Route planning: With every message the AI also sees your current route planning: the names and the order of the waypoints (these can be places or addresses), your settings for it (riding style, round trip, avoid), the length and duration of the route and dream roads nearby - of the planning, or of your approximate location if you have planned nothing - without coordinates. This also goes to Anthropic (same processor, USA, standard contractual clauses, same retention at Anthropic). Curvalia does not store the planning separately; it only passes through our server for the answer. If the AI mentions something from it in its answer or on a card, it stays in the conversation history (30 days, up to 90 days if handed over to the team). The app carries out a change to your planning only once you tap the AI's card. Preferences: The app remembers a short summary of your preferences on your device (riding style, typical duration and length, dream roads, stops, avoid settings, answer style, up to five short notes). It goes to the AI with every message and is updated from your conversations; it is stored only on the device, in the app's storage. To update it, the conversation together with the previous summary goes to Anthropic once more (same processor, USA, standard contractual clauses, same retention at Anthropic): on "New chat" and, once you have written several messages, when you close the chat. Curvalia does not store the summary; it only passes through our server and comes back to your device. If the AI mentions something from it in its answer, it stays in the conversation history (30 days, up to 90 days if handed over to the team). It lives on the device per account, stays after "New chat" and is not part of the account backup; whether the app's storage is part of your phone's device backup is explained above under "On your device". In the settings under "What the AI knows about you" you switch on and off whether the app may remember anything; there you also see what is remembered and can delete it. Screenshot: You can open the chat from a button on every screen. The app then takes a picture of the current app screen - the map is always left out - and shows it as a preview above the input. It is sent only with your next message, if you leave it there; one tap removes it. Like the message text, it goes to Anthropic (same processor, USA, standard contractual clauses, same retention at Anthropic). Curvalia does not store the picture, only a note that one was attached. We also tell the AI which app screen you came from (its name only). Limits: Without Plus you can write the AI 10 messages per day (the day begins at 00:00 German time) and have it plan one route per week; for this we count only the current week per account, and the counter is gone when the account is deleted. With Plus there is no limit per account. Its answers are visibly marked as AI answers in the app. We do not read your AI conversations; we only see a weekly count of topics and the cases that the AI or you hand over to us. How long: We delete the conversations after 30 days. If you withdraw your consent in the settings, we delete your stored AI conversations immediately, and the summary of your preferences on your device with them; open cases remain without the AI history. The summary itself lives only on your device until you delete it, withdraw your consent or delete your account.
Support requests
With "Ask the team" you write to us without AI. The text, your account identifier and app version and platform go to our server as a case, so that we can reply in the same sheet (at most 3 such questions per day and at most 3 open cases per account). If the AI hands a conversation over to us, we see the case with the history needed for it; a screenshot is not stored here either, only the note about it. Only we read handed-over cases; our replies are marked "from the Curvalia team". A case stays until 14 days after it is resolved, at most 90 days.
3. Who else receives the data
The app calls these services. In each case your IP address is technically transmitted (this is the case with every internet connection), together with whatever the request needs:
- Our server at IONOS (Germany), reachable via engine.curvalia.app – routing (GraphHopper, self-hosted), address search (Photon, self-hosted; your search term or the point you tap on the map), weather, account, leaderboard including season and Hall of Fame, friend requests, backup, group rides, road closures, bug reports. IONOS is our processor.
- MET Norway (Norwegian Meteorological Institute, api.met.no) – weather. The request is made by our server, not by your device: MET Norway only receives points of your route rounded to about 1 km, not your IP address.
- Cloudflare (Cloudflare, Inc., USA) – forwards all requests to engine.curvalia.app to our server and protects it against attacks. Cloudflare sees the IP address and the request.
- OpenFreeMap (map tiles) – tiles.openfreemap.org; plus which map area is being loaded.
- Open-Meteo (weather, only as a fallback when MET Norway does not respond) – api.open-meteo.com; plus individual points of your route for which the weather is shown.
- Expo (650 Industries, Inc., USA) – app updates (u.expo.dev) and, only with your consent, the push service (exp.host). It forwards notifications to Apple or Google; what is transmitted is the device identifier and the text of the notification (for invitations to group rides, with the display name of the person who invited you) – no location or ride data.
- Anthropic PBC (USA) – answers in the help chat; only with your consent (see "Help chat with AI"). Anthropic is our processor. By its own statement, Anthropic deletes inputs and outputs of its API within 30 days; if abuse is suspected or legal obligations apply, it can take longer (by Anthropic's statement up to 2 years).
- Apple (iCloud Keychain) or Google (Google Block Store) – only if you store your account key there yourself (see "Account key with Apple or Google"). Only this key is transmitted, end-to-end encrypted; Apple and Google cannot read it, and we receive nothing.
Transfer to the USA: Cloudflare and Expo are based in the USA. The transfer is based on the European Commission's adequacy decision on the EU-US Data Privacy Framework, insofar as the provider is certified under it, and otherwise on the European Commission's standard contractual clauses. For Anthropic (help chat with AI only), the European Commission's standard contractual clauses apply, which are part of the data processing agreement.
Map data © OpenStreetMap contributors, subject to their copyright (www.openstreetmap.org/copyright).
4. Legal basis
- Map, routing, navigation, address search, weather, account, friends, friend requests, leaderboard (including the season view and the Hall of Fame), dream roads, shared routes, group rides and road closures: Art. 6(1)(b) GDPR – these are the functions you use in the app.
- Notifications (push), the account backup and the account key with Apple or Google: Art. 6(1)(a) GDPR – only with your consent, which you can withdraw at any time with effect for the future (Art. 7(3) GDPR). You switch off notifications and the account key with Apple or Google in the settings. For now, you withdraw consent to the backup by deleting your account (Settings → Legal); a separate switch for it will follow.
- Shared bike photo: Art. 6(1)(a) GDPR – only because you switch on one of the two switches on the bike sheet; switching off withdraws consent for the future and deletes the photo immediately (Art. 7(3) GDPR). If we remove a reported photo, that is our legitimate interest (point (f), see the moderation below).
- Help chat with AI: Art. 6(1)(a) GDPR – only with your express consent, which you can withdraw at any time with effect for the future (Art. 7(3) GDPR), in the settings. Withdrawal deletes your AI conversations and the summary of your preferences on your device.
- Support requests ("Ask the team", handed-over cases): Art. 6(1)(b) GDPR – we answer your question.
- Bug reports and contact form: Art. 6(1)(b) or (f) GDPR – to process your report and to reply to you.
- App updates, protection of the server against abuse and attacks (Cloudflare, error logs): Art. 6(1)(f) GDPR – our legitimate interest in a secure, up-to-date app.
- Operation and moderation (blocks, reset display names, removed dream roads, the mark "Test account", the recycle bin for accounts we delete, the deletion journal and the operator log): Art. 6(1)(f) GDPR – our legitimate interest in protecting the leaderboard and the services against abuse, in separating test accounts from real use, in being able to undo an accidental deletion, in being able to prove what we did to accounts as the operator, and in preventing a deleted account from coming back after the server is restored.
- Storing and reading on your device: § 25 (2) no. 2 TDDDG, insofar as it is strictly necessary for the app; for notifications and the account key with Apple or Google § 25 (1) TDDDG with your consent.
5. Storage period
- Local data: until you delete it or uninstall the app.
- Account, backup, friend list, season points: as long as your account exists. Accounts that have not been used for 24 months are deleted automatically, including the backup.
- Shared routes and your own dream roads: until you delete them or delete your account.
- Hall of Fame: your entry stays as long as your account exists – even if you switch the leaderboard off or change your name. If you delete your account (or we delete it after 24 months without use), it is gone.
- Friend requests: until the person you asked replies. After 30 days a request expires and is no longer shown; it disappears from the record the next time that person retrieves their requests or a new request reaches them, at the latest with their account.
- Push identifier: until you switch off "Receive notifications", it becomes invalid or you delete your account.
- Shared bike photo (only if you allow it): until you switch off both switches, remove the photo or the active bike has no photo (then we take it off the server with the next score update); immediately if your account is deleted – it does not sit in the recycle bin either, and an account that is restored starts without a photo. A photo we remove after a report is deleted immediately, and a new one cannot be uploaded until we release it.
- Account key with Apple or Google: until you switch off the switch or delete your account in the app. Deleting the app is not enough.
- Bug reports including screenshots: 12 months after receipt, immediately if your account is deleted.
- Messages via the contact form: until the request has been dealt with, at most 12 months.
- AI conversations in the help chat: 30 days; immediately if you withdraw your consent or delete your account.
- Summary of your preferences (help chat): only in the app's storage on your device until you delete it; immediately if you withdraw your consent or delete your account in the app. Our server never stores it as a summary; what the AI mentions from it in an answer stays in the conversation history (30 days, up to 90 days if handed over to the team).
- Support cases (handed over or "Ask the team"): until 14 days after resolution, at most 90 days; immediately if you delete your account.
- Group rides: 30 minutes after they end, at the latest 12 hours after the start.
- Follow-along link: 10 minutes after the ride ends, at most 12 hours, or as soon as you stop it. Line and preview image of a shared route: 180 days, for routes on your profile together with the route.
- Group ride album: 7 days after the ride; your photos in it right away when you remove them or delete your account.
- Fixed groups: until the last person leaves or after 180 days without activity; announced rides 24 hours after their start; invitation codes after 14 days. If you leave a group or delete your account, your membership, your answers and the rides you announced are removed immediately.
- Respect: 60 days. Challenges: 30 days after they end. If you delete your account, the respect you gave and your participation are removed immediately, and challenges you created entirely.
- Road closure reports: 14 days.
- Dream roads removed by us: 14 days, then they are deleted.
- Server error logs: at most 30 days, those of the routing engine at most 7 days.
- Accounts that we delete as the operator (for example orphaned installations or test accounts): first 30 days in a recycle bin on our server so that a mistake can be undone; then permanently deleted and at most another 30 days in the backup copies. This applies to accounts without content. If an account has content (shared routes, dream roads, bug reports, a backup or images), we only delete it permanently once we have successfully tested a restore from the backup; until then it stays in the recycle bin, beyond the 30 days as well – we currently state no fixed period for this.
- Deletion journal: after every final deletion of an account – including your own in the app – a line stays for 30 to 32 days with the day and a code derived from your identifier (calculated with a key that only we have; no name, no identifier in plain text). It prevents a deleted account from coming back if we have to restore the server from a backup. Without our key it cannot be traced to a person.
- Operator log: if we, as the operator, use our admin tool to view or change something on your account, your bug reports, your dream roads or your road closure reports (for example a block, a reset name, a deletion), a line is written to the log: time, type of action, for a single account a code derived from its identifier (for a bug report, dream road or road closure report its own number), for interventions the reason as a category, the result and technical details (access, key used, number of entries affected, checksums against later changes, for a note to you a checksum of the note) – no name, no account identifier in plain text, no content. Access outside this tool, for example directly on the server, is not recorded there. We keep it for 12 to 13 months (we clear out month by month), beyond the deletion of your account as well, so that we can prove what we did as the operator (Art. 5(2) GDPR).
- Server backup copies: encrypted, at most 30 days; so whatever you delete also disappears from there after 30 days at the latest. The deletion journal and the operator log are included in these copies; their periods are extended there by up to 30 days.
6. Deletion – one tap is enough
Under Settings → Legal & version → "Delete account and all data" you remove, yourself and immediately: all local data, the record including the encrypted backup, your push identifier, your bug reports including screenshots, the routes and dream roads you have shared, your shared bike photo, your votes, your place in the Hall of Fame, the friend requests from and to you and – if you stored it there – your account key with Apple or Google (see section 2). Reported road closures remain visible to others until they expire, but lose the link to you – they warn about the road, not about you.
This path is deliberately built into the app because it is the only one that works reliably: your rides are end-to-end encrypted, so we can neither read them nor look them up on request.
If we delete an account as the operator (section 5, recycle bin), you do not have to wait for the period to end: "Delete account and all data" in the app takes effect immediately in that case too and removes the copy in the recycle bin. If your device contacts our server again during that time, the account is restored.
Apart from the backup copies (section 5, at most 30 days), only two pseudonymous traces remain after the deletion, both without name or content: the deletion journal (30 to 32 days) and – if we did something to your account as the operator – the operator log (12 to 13 months). Both carry only a code derived from your identifier, the operator log also the number of a bug report, dream road or road closure report that can no longer be traced to a person without your account, see section 5.
7. Security
The connection to our server is encrypted (HTTPS). The server can only be accessed with keys, the services on it are shielded from the outside, and your backup is end-to-end encrypted. With every request, you prove your identifier with a proof derived from your secret key.
8. Your rights
You have the right of access (Art. 15 GDPR), rectification (Art. 16 GDPR), erasure (Art. 17 GDPR), restriction of processing (Art. 18 GDPR) and data portability (Art. 20 GDPR).
Right to object (Art. 21 GDPR): Insofar as we process data on the basis of our legitimate interest (Art. 6(1)(f) GDPR), you can object to this at any time on grounds relating to your particular situation.
You can withdraw consent at any time with effect for the future – for notifications and the account key with Apple or Google directly in the settings, for the backup, for now, by deleting your account (section 6).
You also have the right to lodge a complaint with a supervisory authority, for example the one responsible for us: Saxon Data Protection and Transparency Commissioner (Sächsische Datenschutz- und Transparenzbeauftragte), Maternistraße 17, 01067 Dresden.
For everything else, contact datenschutz@curvalia.app. Most things are faster in the app itself, though – deletion and export need no request, see section 6 and the note on data portability below.
Access (Art. 15): On our server, your account holds exclusively the identifier, your self-chosen display name, verified km, points and number of tours, your level, your season points (number and year), your points and kilometres of the current month (number and month), your decision whether you take part in the leaderboard, the counters of dream roads ridden, the identifiers of your friends, with a note of whom you added yourself (only they see which dream roads you ride), and of those you have removed, so that they do not add themselves again on their own (whom you have blocked, with the time of the block), of those whose request you declined or whom you removed without blocking (identifier and time, for 90 days), the code of the friend QR you are currently showing (valid for 15 minutes), and of those you added before they had stored their referral code (until it has been delivered to you or you are no longer friends), up to three bikes (brand, model and the figures from your tours) together with your decision whether one of them appears in the leaderboard, your profile picture including showcase (up to three achievements, style and two colours), if you have allowed sharing your bike photo (a reduced JPEG without capture data, as a file next to the record) together with the two switches for who may see it, and, as a limit, the times of your photo changes in the last hour, the friend requests to you (identifier of the requesting person and time; including expired ones until they drop out of the record, see section 5), the times of creation, last report, last backup, last registration for notifications and last notification, the proof with which you identify yourself, the details of your backup (size, counter, time), an encrypted data block that we cannot open, and – if you have switched on notifications – the device identifier of the push service with the platform (up to five devices, each with the language of the notifications and the time of registration); on iPhone also your referral code, and the identifiers of the fixed groups you are in (up to eight; for what they contain, see "Fixed groups"), and the respect you received (who, for what, when; 60 days). In addition, the routes and dream roads you have shared yourself, your votes, your bug reports and your road closure reports until they expire. If we, as the operator, have noted something on your account, that is stored there too: a block (with the day and the state of your leaderboard switch before it), a reset display name (together with the old name and the day, so that your device does not enter it again), a bike photo we have removed (then no new one can be uploaded until we release it), for a dream road we have removed, the time of removal and the reason as a category (14 days, then it is deleted), a note from us on one of your bug reports, which you see in the app, and – if we have marked your account as a test account – the operator mark "Test account" with the day of marking. It only serves to separate test accounts from real use and is not visible to other users. During an ongoing group ride, additionally – temporarily – your last reported position. No name, no email, no address – we never ask for them in the app. Your place in the Hall of Fame, if you have one, is not in the account but next to it: display name, points, profile picture including showcase and your list code. A request you have sent is stored not in your record but in the record of the person you asked (your identifier and the time). Outside the account we keep two logs that carry a code derived from your identifier: the deletion journal and the operator log (section 5).
As a rule, our license server holds nothing about you: referring friends is paused, and Curvalia Plus is billed by the app store. If an older app version created something there, it is at most: a recognition counter for your referral code, which drops out again after 24 months at the latest without a new redemption; earned referral days not yet collected – they remain until you redeem them, because they are your entitlement and not a counter; and the information that your account has already redeemed a referral code once. Who referred whom is NOT stored there – the server keeps counters, not connections. The legal basis is our legitimate interest in detecting abuse of the referral program (Art. 6(1)(f) GDPR).
Curvalia Plus: purchase, payment, renewal and cancellation are handled by your device's app store – you are their customer there. We receive no payment data. The app only asks the store whether a subscription is active and remembers the answer on the device.
Data portability (Art. 20): Every ride can be exported individually from the ride book as a GPX file – an open format that any other navigation app can import.