Copenhagen Cycling Buddies

Your data

What the app stores, where, who sees it, and how you get rid of it. Every sentence here matches what the app does.

Version 41 · 24 October 2026

Who is responsible

Copenhagen Cycling Buddies (CCB) is a project by Ferdinand Drobik, Copenhagen, Denmark. For now it is non-commercial, and no company stands behind it. Using it is free, and it has no ads and no tracking. Danish law and the GDPR apply.

Postal address: Bordeauxgade 4, 2. th., 2150 Copenhagen, Denmark

Contact: info@nordicappstudio.dk.

The short version

What the app stores, and why

Your account

You sign in with Apple. Apple gives the app an account ID and an email address — your real one or the relay address Apple offers. The email is used to sign you in, and only if a data breach puts you at risk does the admin write to it to tell you. No other user ever sees it, and the app never shows it.

Your sign-in is tied to the device you use. A sign-in that hasn't been used for 90 days ends on our server; “Sign out everywhere” in Settings ends it on every device.

Your profile and card

You give a name, usually your first name; the server checks it against a list of words that aren't allowed. A profile photo is up to you; without one, your card shows your initial and a colour. Photos, your profile photo and the cover photo of a group ride, are resized on your iPhone and saved without place or camera details; only users inside can open them, through links that expire after an hour. You can also give your district and a favourite café of the app. Other users inside see your card: your name, your member number, since when you're a member, the role Founder or Ambassador if you have one, how many group rides you've been checked in on, your medals, your pins, the group rides you've posted that are coming up, and, each with its own switch in Privacy settings, your photo, your district, your favourite café, your spot totals and the kit and bikes you put on your card. Your card has no intro, no rides, no followers and no trust level. Someone you blocked, or who blocked you, sees nothing of yours.

With Share profile your iPhone draws a picture of your card, with your photo if your card shows it, your name and up to three pins, never your member number, district or numbers. The picture can also be a story whose background follows the time of day and the season. Nothing goes to our server, and the picture only leaves your iPhone when you share it.

Getting in

To join, two users vouch for you with their codes: each code works once and for seven days, and each of them is asked whether they know you. The server keeps only a fingerprint of each code; the code itself stays on the phone of the user who made it until it's used or runs out. When you enter a code, you see the name of the user it belongs to. While your application is open, the users you asked see your name; afterwards, your name and whether you got in. You see each answer next to their name, a no too. Who vouched for whom is kept while the account exists, also if an application is declined. The admin sees your application with your photo and your confirmation that you're 18 or older, and lets you in or declines it, naming a rule or saying why in a few words. When both codes are confirmed, you can also be let in without the admin's review, as long as the admin keeps that way open; three confirmed codes or the admin's own QR code let you in too. When you join with someone's code, they're told your first name and can say within 48 hours that they don't know you; then your profile and posts are hidden from others and you need two codes again, unless the admin has already decided, and the admin is told either way. So that a code posted in public is noticed, the server counts how often each code is entered on a day, without who entered it, and deletes the counts after 30 days. Send as a card draws your first name and one of your codes on a picture on your iPhone; it only goes where you send it.

You can invite people 14 days after you were let in, or after your first group ride checked in by QR. If someone you vouched for is blocked from the app, your codes rest for 90 days.

You must be 18 or older to use the app, join group rides and crews. Where your iPhone offers it, the app asks Apple's age range whether you are 18 or older; Apple answers only yes or no, and if you'd rather not share it, you tick that you're 18 or older. We store only the moment you confirmed it and whether it came from Apple's age range or from the tick, never a date of birth and never an ID. Everyone confirms it again when they accept the Buddy rules of version 16. If someone reports that a user may be under 18, the admin asks that user in the app; the app never asks for ID documents.

When you accept the Buddy rules, the app keeps which version, when and at which step, so you and the admin can see what you agreed to. You find the list under Settings › Rules and liability; it is in your data export and goes with your account. No location or device is kept with it.

Group rides

Every user who is in can post a group ride; only a step by the admin, such as Restricted, holds posting back. A group ride carries: who posted it (“Posted by” and the first name), the time, a meeting point from the app's list of public places (cafés, studios, spots, and a few squares and stations), a title the app makes from the template and the meeting point, the planned pace and Planned stops as a description, not a promise, the distance, the kind of bikes it suits, a coffee stop at a café of the app, up to three places to join on the way from the same list, a route as the points you tap or from a GPX file, and a cover photo of your own or a picture from the app. A GPX route that doesn't start at the meeting point is cut on your iPhone so that it does. When you draw a route, your iPhone asks Apple Maps for the way between the points you tap; we keep only those points. An online group ride shows its platform and duration, no place. Group rides have no description and no free-text comments. Until every device has version 1.0.14, a ride posted with an older version can still have its own title and description and a meeting point outside the list.

Every user inside sees a group ride, except a ride only for a crew, which only that crew's members see. A crew's logo shows on a ride once a second member of that crew said I'm in. 30 days after the start, a group ride keeps only its place from the list (or the middle of its district), its time and how many signed up; its route and places to join go. You can delete a group ride you posted before it starts, as long as nobody else has said I'm in or reported it; otherwise you can cancel it.

With Every week, the app proposes the next date of a ride you posted, a week later at the same time, to you alone; it only goes up when you confirm it, and a date nobody confirms never appears. You can have two weekly rides, from 14 days after you were let in or after your first group ride checked in by QR. A weekly ride ends when you leave its crew, the crew ends, your account goes or the admin hides its latest ride. To call a ride off, you pick one reason: Weather, Too few users or Something came up. Everyone who said I'm in gets a notification with that reason, and the reason goes 30 days after the ride.

The app keeps the last list of group rides on your iPhone, protected and outside its backup, until you sign out, and a ride you start but don't post as a draft for up to seven days, with a copy in your own iCloud. Add to Calendar opens the calendar sheet of iOS, which gives the app no access to your calendar. If you switch it on in Settings, the app puts group rides you join or post into the calendar you pick and only reads the events it made. From two hours before a ride, your Lock Screen can count down to it as a Live Activity; no token for it goes to our server. None of this goes to our server.

Saying I'm in, invitations and checking in

Before a ride starts, everyone who sees it sees who said I'm in. Which place to join you pick, only you and the poster see. You can say what you'll do on a ride (knows the route, rides at the back, meets newcomers); that is something about you, not a job. Whoever posted a ride and those who said I'm in can invite people they were checked in with on a group ride and people who asked to join their rides, up to 20 a day; the person invited sees your name and the ride. On a card you can ask to join someone's rides next time; only that person sees it, without a notification or a count, and it goes after 30 days.

From 30 minutes before to an hour after the start, you check in by scanning the QR code on the poster's phone, which changes every 15 seconds. It needs a connection and uses no location and no Bluetooth; only the time and the way are stored. Your phone proves a check-in with its own key, which never leaves the phone (it is kept in the iPhone's Secure Enclave); our server keeps only the public half, at most three per account, and a revoked one for 30 days. Without a connection, the poster can mark you as there. Until two weeks after the start, the poster can take off anyone who checked in but didn't cycle and add anyone who cycled with them but didn't check in. From the start, the poster sees the list, those who checked in see each other under Who was there, and everyone else sees how many came.

Your sign-up, your place to join, your role, invitations to the ride and your check-in are deleted 30 days after the ride. What stays is one number for you: how many group rides you were checked in on by QR, with no dates and nothing about who was there. It shows on your card as Group rides, opens inviting, crews and weekly rides, and brings medals at 10, 25, 50 and 100. It was started once from the check-ins already stored when version 1.0.14 came.

After a group ride

From the start until 14 days after, those who were there can pick up to three of twelve fixed comments, like Great ride or See you next time; there is no free text. Only the others who were there see them, and they are deleted 30 days after the ride.

From an hour to 48 hours after the start, those who checked in by QR can answer two questions about the ride's description: Pace as described? and Stops as described? The person who posted it never answers. We keep no answer per person: only a mark that you answered, until the 48 hours are over, and four counts per ride. Only the person who posted the ride sees the counts, once, after the 48 hours and only if at least four answered; with fewer, the counts are deleted unseen. Nobody else sees them, not the admin either, and they never change anything about anyone. The person who posted a ride can switch feedback off for their rides, which deletes the counts at once. The counts are deleted 30 days after the ride.

Crews

A crew is a small circle of users who cycle together, with a name, a logo, a home café and its members. It is not an association, and whoever starts it isn't its leader. You can start a crew 14 days after you were let in, or after your first group ride checked in by QR. A crew stores its name, its logo as a code of a few fixed shapes and colours (drawn on your iPhone, never a picture), its home café, whether it's open or closed, its members and who started it or took it over. A crew has at most 25 members, and you can be in up to 10 crews and start up to three.

Only a crew's members see who is in it, with first names and photos if they show one. Everyone else sees a crew's name, logo, home café and roughly how many are in it once it is listed (with a confirmed name and four members), never who. Rides and times of a closed crew only its members see. Someone you blocked doesn't see you in crew lists or on sign-ups.

Every crew name has a quick look from the admin before others see it. The server compares a new name with a list of words, links, email addresses, phone numbers and the first names of users; a match doesn't refuse it, it only marks it for the admin, and you see the same note as for any name. If the admin turns a name down or resets it, you're told which rule and why, and you can answer once. You can change a crew's name once a season.

You join an open crew from its page; a closed one gets a request without text, which the person who started it answers. A crew link or QR code works for seven days, can be revoked and opens only in the app for users who are in; our server keeps only a fingerprint of it, made with a key of its own. The person who started a crew can remove a member without a reason; that person can ask again after 30 days. You can leave a crew at any time; leaving and deleting your account are never blocked. When the person who started a crew goes, the member who has been in it longest is asked to take it over; if nobody does within 14 days, the crew is archived. A crew with no crew ride for 90 days is archived, and deleted 12 months after its last crew ride; its members see the date. When a crew is dissolved, everything about it is deleted, and its rides stay as open rides without the logo. Groups from before version 1.0.14 became crews; their members see a note with Leave crew once.

For the crew's streak, the server keeps one mark per crew and week in which at least two of its members checked in by QR on a crew ride, never anything per person. To know when a crew league could start, the server counts, only when the admin asks, how many crews had five different members checked in on crew rides in the last 28 days, and stores nothing. At most one notification about a crew's rides goes out per crew and day.

Cafés and studios

Users add cafés and studios and give them a thumb up, one each, no text; others see how many, never who. A café that Apple Maps doesn't know can be set by hand on the map with its name, which the server checks against its list of words. Others see a café or studio set by hand, on the map and as a meeting point for group rides, only once the admin has confirmed it; until then only whoever added it sees it. Such a café keeps opening hours set by whoever added it; who set them isn't stored, and anyone can ask the admin for a change, which only the admin sees and which goes 90 days after the answer. A cyclist deal at a café is reported by a user and shown only after the admin checked it. “Most liked cafés” counts thumbs from the last 12 months, from at least three people. The admin sees who added a café or studio. While the admin has restricted an account, it can't add, rate or ask about cafés. To find a café or studio, your iPhone sends what you type to Apple Maps, never your location. A café or studio you added stays when you delete your account, without your name.

You can check in at a café for 30, 60 or 90 minutes. The check-in stays on your iPhone, nobody else sees it and our server doesn't get it; the café goes on your own list for café medals, kept in your own iCloud. At 5, 15 and 30 different cafés, the app asks our server for a café medal, at most one a week; the server only checks the week and the level.

Spots, medals and pins

Every Saturday at 22:00 new spots show on the map, to collect alone or together. Your iPhone checks the 50 metres itself; your location is never sent or stored. A spot together counts when one of you scans the QR code on the other's phone: only a short random code goes from one phone to the other and to our server, which forgets it within ten minutes. Our server only knows numbers: how many spots you collected each week, alone and together, never which, where or when. Which spots you have stays on your iPhone and in your own private iCloud. With Report a spot you can tell the admin about a wrong spot; who reported is kept for 30 days, then only the report stays. Community spots that are already on the map stay, without a picture; new ones can no longer be suggested.

Others see medals from spots, cafés and group rides you were checked in on. Medals from your own rides in Apple Health are worked out on your iPhone and stay there. Pins say what kind of cyclist you are, in three levels; every night the server works them out from what it already has, such as your group rides, cafés, spot totals and the kind of bike on your card. Others see up to three under your name and all of them on your card; you can hide them.

Your kit and bikes on your card

In your workshop you can put pieces of your kit On my card, with brand and model if you like, and your bikes, with only their kind. Only those are stored with us; users inside see them on your card, never someone you blocked or who blocked you. Show my bikes and kit in Privacy settings hides all of it. If someone says Same here to one of your items, you see who in your inbox. What users wear shows numbers and brands only when five or more users are behind each, never names; since version 1.0.14 no new looks from rides come in, so it empties within 28 days.

Only on your iPhone

From Apple Health the app reads workouts and cycling distance, and whether a workout was indoors; for See more of your ride also that ride's speed, cadence, power, active energy, temperature and humidity, fresh each time. From them your iPhone works out your list of rides, your medals from them, Your year, the kilometres of your bikes and pictures to share. None of it goes to our server, to iCloud or into a backup. Heart rate, routes and weight are never requested, and the app writes nothing to Apple Health. You can turn Apple Health off for the app in the Settings app under Apps › Health › Data Access & Devices.

People I cycled with is your own list of users, in place of following. It stays on this iPhone, with each person's first name as it was when you added them and the day; it never goes to our server or to iCloud and isn't in the backup.

Your workshop (bikes, log, photos, notes, costs, frame numbers, your kit) stays on your iPhone and in your own iCloud, never with us, so your iPad or your next iPhone with the same Apple ID has it too. Which ride counts for which bike and the milestones in kilometres stay only on this iPhone and aren't in its backup. Reminders you set there are notifications your iPhone plans itself.

The bike passport in your workshop holds your own photos of your bike, its frame number, lock, insurance and receipt, with a checklist for the day it's stolen that leads to politi.dk, and Check before you buy. It stays on this iPhone, in its backup if you make one; it never goes to our server or to iCloud. You can use it before you're in.

Weather, maps and your iPhone

When you open the map, and if you allow it, your iPhone takes your location, rounds it to about 1 km and asks Apple Weather for that spot; outside Copenhagen, or without your permission, the map shows the weather in the middle of the city. From the same answer the map shows the lightest wind of the day as a time window, without its direction and without where you live, and in winter the time of sunset. The wind on the map comes from the same request; zoomed in elsewhere, your iPhone asks Apple Weather for fixed points about every 15 km (at most ten a day), the same for everyone. Your iPhone checks by itself whether you are in the Capital Region or Region Zealand. Nothing in the app follows your location in the background, and none of this goes to our server.

For the time by bike and Look Around, your iPhone asks Apple Maps with your location and the place. Home and work for “my way” stay on your iPhone, and Apple sees both when it works out the way between them. Looking for bike shops sends the part of the map you see to Apple. Weather alarms stay on your iPhone with a copy in your own iCloud; to plan them, your iPhone asks Apple Weather now and then, also in the background, for the place you picked, and for “where I was last” it keeps that place, rounded to about 1 km, only on the iPhone. Places you save for a tour stay on your iPhone and in your own iCloud; a tour shared as GPX or posted as a group ride carries only your places.

The bar above the tabs, the widgets and Siri work from what the app already has on your iPhone; widgets show no other people's names and no figures from Apple Health. Notices at the top of the app are the same for everyone and hold no personal data; when you close one, only your iPhone remembers it, for 60 days. Pictures to share (a ride from Apple Health, your month, today's wind, a spot as a postcard, an invite card) are drawn on your iPhone and only go where you send them. Buddy AI uses Apple's model on your iPhone and reads only what the app has; nothing it reads or writes goes to us, to Apple or to any other AI service, and each function has its own switch, which is all our server sends. Translating uses Apple's translation on your iPhone. Codes, QR codes and other users' cards show dark in screenshots. When you open the app, at most once an hour, your iPhone asks the App Store which version is the newest; only the app's ID goes with it.

Notifications

If you allow them, the app stores a device token, tied to your sign-in on that device, so Apple can deliver notifications, and the app's build number, so a text an older version doesn't know only goes to newer ones. A notification can carry first names, the title of a group ride and the name of a crew; Apple sees the text while delivering it. Most have a switch. These have none: a change to or cancellation of a group ride you said I'm in to, and those about getting in, steps by the admin, your reports and the answer in Your rights, which only says “The admin answered your message.” Signing out removes the token; a device whose sign-in hasn't been used for 90 days gets nothing.

Reports, blocks and steps by the admin

You can report a group ride, a crew (its name, its logo or how its members behave), a profile, a café, a studio, a spot or a piece of kit on someone's card: you pick a reason and can add a few words for the admin, which only the admin reads. The admin sees who sent a report and how often you report; the person you report never learns it was you. After two reports, a group ride is no longer shown to those who reported it; after three from people who aren't linked by vouching, or a decision of the admin, it is hidden for everyone. A café, a crew or a studio is held back after two reports until the admin decides. If reports hold back something of yours, you're told what it is, what it was reported as and that the app did this automatically, never who reported it; if you reported something, you hear what came of it. If you block someone, you stop seeing each other at once, also in crews; the admin is told that a block happened and who was blocked, never who blocked.

The admin can send a note, restrict an account (then it can't post group rides, invite, start crews or weekly rides, or add or rate cafés, until a set day or until the admin lifts it), hide or remove content, reset a crew's name and block an account from the app. Each step names the rule and comes with a message from the admin, and you can answer it once. Whether someone stays in the app is always decided by a person. So that deleting the account and signing in again doesn't undo a ban, the server keeps a keyed hash of the ID Apple gives the app for you, not your name or email, for two years or until the ban is lifted. The server checks names of people, crews and cafés against a list of words that aren't allowed and refuses them before they're saved.

Your rights in the app, and email

Under Settings › Your rights you can ask for a copy of your data, to correct or delete it, object to how it is used, hold it while something is checked, or appeal a decision of the admin. Each request is a fixed sentence; only an appeal has one field for your own words, which only the admin reads. Your messages and the admin's answers are encrypted on the device that writes them, for your devices and the admin's, and signed; our server stores only the encrypted text, the time and the public keys, and can't read them. Your private key syncs through your iCloud Keychain if you use it; the admin's never leave the admin's devices. You answer when the admin has asked something; there is no free chat. The admin answers within a month. Requests are deleted three months after their last message, and at once with your account.

For a bug, a question or an idea, write to info@nordicappstudio.dk (see the support page); the app shows no address. By email the admin never deletes, restores or exports an account and never hands out codes, and the admin never asks for your codes or sign-in. A request about your rights by email always gets an answer within a month: the admin confirms it's you through Your rights in the app or, without a device, with a one-time code after you sign in with Apple. Emails are deleted three months after the last message. The mailbox is with Simply.com in Denmark.

Report a bug

Report a bug in Settings sends where and what from two fixed lists, with the app and iOS version, your iPhone model and the language; no text of your own, no screenshot, no ride and no place. Your account is only kept for the daily limit of five, your data export and deleting it with your account; the admin sees the reports without it. They are deleted after 90 days.

Crash reports and performance numbers

When the app closes unexpectedly, your iPhone keeps a note of it. Nothing is sent unless you say yes: you choose Send report, Always send or Never, and can change it under Crash reports in Privacy settings; a note you don't send is deleted unsent after 14 days. If you say yes, the note goes to us at a later start: what kind of problem it was, your iPhone model, the iOS and app version, and where in the app's code it stopped. With Always send, a few performance numbers from Apple's MetricKit also go once a day. None of it holds a name, an account, a ride, a place, a photo or a text, and our table has no column that could name you. The same problem only counts up. Reports are deleted 90 days after the last one of their kind, performance numbers 60 days after we receive them.

Ambassadors

The admin asks a few users personally to help new people find their way in; there's no application, no duty, and nothing shows on a group ride they post. Since when someone is an Ambassador is stored, and when the role ended. New users can ask once, in their first 60 days, to cycle with someone, with a district and a rough time of day; only Ambassadors and the admin see it, for 14 days. Ambassadors see letters and notes from the admin, which hold no one's data. They see no reports and moderate nothing.

App Review

For Apple's App Review, the admin can open a separate review circle. Reviewers join with review codes right after signing in; they see only sample accounts and crews marked “(Example)”, and users don't see them. Review accounts get no member number; a review account ends 30 days after it joined, or when the admin closes the circle, and is deleted a day later.

What changed with version 1.0.14

Since version 1.0.14 the app has no feed and shares no rides from Apple Health, and it has no ride photos, free-text comments, bells, thanks, intros, followers, tips, spot suggestions, leaderboards, city goal, trust levels or cards after rides, guests, welcome chat, coffee or studio meetups, Ambassador chats and ideas, and no feedback with text or screenshots. Our server takes nothing new for any of them. The two guests who were in the app became members once, by a decision of the admin; their guest data was deleted.

Until every device has version 1.0.14 and the old data is deleted, our server still stores what earlier versions saved for these features: rides shared from Apple Health (day, time, duration, distance, climb, source, note and weather marks), their photos, comments, bells and thanks, who cycled with whom, counted days, who follows whom, intros, trust records and cards after rides, leaderboard data, tips, spot suggestions, Ambassador ideas and chats, feedback with screenshots, coffee and studio meetups, medals from Apple Health and the consents to Apple Health. Only an older version can still add to it, with a consent to Apple Health; older versions of the app can still show some of it, and your own insights and stats in the profile are still worked out from rides you shared before. All of it is in your data export until it is deleted. Whatever an older version still sends from Apple Health, our server throws away without storing it.

Until then we also keep, for 12 months after the deletion, a coded fingerprint of the Apple account ID of accounts deleted before version 1.0.14, with two dates and a count of failed code attempts, never the ID itself or a name. It once kept the guest time from starting again; since version 1.0.14 no new ones are made.

Who sees what

WhoWhat
Other users insideYour card with the fields you switched on (see Your profile and card). The group rides you post, and before a ride starts that you said I'm in. Your role on a ride. The crews' names, logos and home cafés, never who is in a crew they aren't in.
The members of your crewsThat you're in the crew, your first name and your photo if you show one, and the crew's rides and times.
Those who were at a group ride with youThat you were there (Who was there) and your fixed comments, for 30 days.
Whoever posted a ride you joinedWhich place to join you picked, your check-in, and, only as counts after at least four answers, how those who checked in answered the two questions about the ride.
The users whose codes you usedYour name while your application is open, afterwards your name and whether you got in.
Users you blockedNothing of yours, and you nothing of theirs.
The admin (one person, with two-factor sign-in: a code at least every three days, and the code or Face ID checked by the server at least every four hours; the admin's app locks after 15 minutes without input or two minutes in the background, also on the server)Applications with photo and 18+ confirmation, reports with your words, crew names waiting for a look, bug reports without your account, your messages in Your rights (readable only on the admin's own devices), steps by the admin, and all profiles. Never your health data, which isn't on our server, and never the feedback counts of a ride.
The public internetNothing.

Who processes data for us

ServiceWhat forWhere
SupabaseDatabase, sign-in, photo storage, server functions. Its own logs keep each request and sign-in with the account (if you're signed in), the IP address and technical details of the request, for seven days.Frankfurt, Germany (AWS eu-central-1). The company is in the USA; a data processing agreement with standard contractual clauses covers that.
Apple — Sign in with Apple and the age rangeSigning you in, and whether you're 18 or olderApple's own terms
Apple — Push NotificationsDelivering notifications to your iPhoneIn transit; Apple sees the message text
Apple — WeatherKit and MapsWeather at a rounded location or the middle of the city, fixed points about every 15 km when you zoom in elsewhere, map tiles, what you type when you search for a café or a studio, the way between points you tap, and the time by bike — requested by your iPhone, not by our serverApple's own terms
Apple — iCloudYour spot collection, your workshop with its photos, your list of cafés for café medals, copies of drafts and weather alarms, your tour and the keys in your iCloud Keychain, if you use iCloud. Never data from Apple Health. Between you and Apple; we can't read it.Apple's own terms
Simply.comThe web server of this page on nordicappstudio.dk, and the mailbox info@nordicappstudio.dk. Sees visitor IP addresses in its logs and the emails you send us.Denmark; a data processing agreement covers it

Nobody else. No analytics, no advertising, no crash reporting service of another company, no mailing service.

Apart from these services, data goes to an authority only where the law requires it. If something in the app suggests a crime that threatens someone's life or safety, the admin tells the police and passes on the relevant information the app holds (Article 18 of the EU Digital Services Act). If a court or another authority orders us to act against content or to give information about a user, we follow the order as far as the law requires (Articles 9 and 10). The legal basis is a legal obligation (Art. 6(1)(c) GDPR).

How long

Everything tied to you stays until you delete it or your account, except: sign-ups, check-ins, places to join, roles, invitations to a ride, fixed comments, feedback counts and the reason a ride was called off go 30 days after the ride, and the ride then keeps only its place, time and number of sign-ups; a request to join next time goes after 30 days; feedback marks go when the 48 hours are over; proposed dates of a weekly ride go an hour before their start. A crew is archived after 90 days without a crew ride and deleted 12 months after its last one; crew links go after seven days or when revoked, decided crew names after 12 months, requests 30 days after the answer. Messages in Your rights go three months after the last one, emails three months after the last one, bug reports after 90 days. Crash reports go 90 days after the last one of their kind, performance numbers after 60 days. A code for a spot together goes within ten minutes, who reported a spot after 30 days. A notification token goes when you sign out on that device or its sign-in ends. Photo links expire after an hour. Supabase backs up the database every day and keeps each backup for seven days; its logs go after seven days too. Until the old data is deleted, the coded fingerprint of an account deleted before version 1.0.14 goes 12 months after the deletion.

Nightly jobs delete: handled reports 12 months after the decision; statements of reasons after reports and steps by the admin 12 months after they end (a restriction never while it lasts); an account without an application 90 days after its last sign-in or, if later, 90 days after someone said they don't know the person; an account that was let in but never accepted the Buddy rules after 90 days, with a notification about two weeks before; an account whose application was declined after 12 months; sign-ins after 90 days unused; the hash kept after a ban after two years. In these automatic deletions there is no Apple token, so the sign-in with Apple isn't revoked at Apple; you can remove the app yourself under “Sign in with Apple” in your Apple ID settings.

Deleting your account

Profile › Settings › Delete account; before you're in, the same is in the account menu. The app first revokes the sign-in with Apple — this only works with the Apple ID your account uses — then our server deletes your photos and every row tied to you at once. If the revocation with Apple fails, nothing is deleted and the app tells you. On the iPhone you delete it from, your spot collection, your workshop and your bike passport go from the iPhone and from your iCloud (if iCloud can't be reached then, the app tries again later), your rides and medals from Apple Health that the app kept and People I cycled with go from the iPhone, and your keys leave your iCloud Keychain. If you started a crew, the member who has been in it longest is asked to take it over; your deletion never waits for that.

What stays: totals without your name; a café, studio or community spot you added, without your name; after a ban, the keyed hash for two years; and a backup at Supabase can hold a copy for up to seven days.

Your rights

You can see, change and delete what the app holds about you in the app: your card, your crews (leave any time), your account. Anything beyond that through Settings › Your rights, or by email if you don't have the app (see Your rights in the app, and email). You can object to feedback on your rides by switching it off. Apple Health is switched off in the Settings app; crash reports with Never in Privacy settings.

Under Settings › Export my data you get a file (JSON) with what the app holds about you: your profile and settings, your 18+ confirmation and where it came from, your rules, vouches and codes, group rides you posted and joined, your sign-ups, fixed comments, the feedback counts of your rides and your own answer marks, your weekly rides, your crews with your role, home crew, crew links you made, names you proposed and handovers, your number of group rides, medals, pins, spot numbers and the spots you reported, cafés, thumbs and cyclist deals, your kit on your card and the Same here you gave, your notification devices and choices, your reports and blocks, steps by the admin and a ban with their messages, your requests in Your rights with their topics, your bug reports, and a list of what the app no longer collects since version 1.0.14. Until the old data is deleted, the file also holds what earlier versions stored about you for the features that ended. What lives only on your iPhone or in your iCloud isn't in it (your spot collection, workshop, bike passport, People I cycled with, rides and medals from Apple Health). Nor are what individual users said about you in reports and the admin's notes, because they would give other people away (Art. 15(4) GDPR).

If you think we handle your data wrongly, you can complain to the Danish Data Protection Agency: Datatilsynet, Carl Jacobsens Vej 35, 2500 Valby, datatilsynet.dk.

Legal bases, in plain words

Your account, your card, group rides, sign-ups, check-ins and the number of your group rides, fixed comments, weekly rides, crews, cafés, spots, medals, pins and your kit on your card: the service you asked to join (Art. 6(1)(b) GDPR). Using check-ins also for your number of group rides, medals and the crew streak fits the purpose they were collected for (Art. 6(4)). Your confirmation that you're 18 or older and its source: the condition of using the app (Art. 6(1)(b)) and protecting minors (Art. 6(1)(f)). Feedback counts on a ride's description: the interest of whoever posted it, and of everyone who relies on a description, that it is right, which the poster can object to by switching it off (Art. 6(1)(f) and Art. 21). Comparing a crew name with users' first names and the admin's look at it, vouching, reports, blocks, steps by the admin, the hash after a ban and bug reports: our legitimate interest in a community without abuse and an app that works (Art. 6(1)(f)). Your rights, statements of reasons and what came of your reports: legal obligations (Art. 12 to 22 GDPR, Articles 16 and 17 of the EU Digital Services Act, Art. 6(1)(c)). Emails: our legitimate interest in answering you (Art. 6(1)(f)), and for requests about your rights a legal obligation (Art. 6(1)(c)). Crash reports and performance numbers: your consent, given by tapping Send report or Always send and taken back with Never (Art. 6(1)(a)). Telling you about a data breach that puts you at risk: a legal obligation (Art. 34 and Art. 6(1)(c)). Supabase's logs: our legitimate interest in a secure service that works (Art. 6(1)(f)). What stays on your iPhone or in your iCloud doesn't reach us. The data from earlier versions that is still stored until it is deleted keeps the legal basis it was collected on, and the consents to Apple Health are kept until then as a record (Art. 7(1)).

Changes

When this text changes, the version number and date at the top change. Earlier versions are kept and can be requested by email.