Privacy

Privacy policy

Last updated: 16 November 2026.

Shredder World is the map of places to ride, and the sessions: who's riding where, and when. This page says what we know about you, why, who else sees it, how long we keep it, and what you can do about it.

The short version

  • Browsing needs no account. No cookies to browse, no ads, no tracking across other sites.
  • An account is public by default: your handle, your name, what you ride and your picture are public, and so are your Instagram link if you add one, who you follow and how many follow you.
  • Sessions are public too, unless their host makes one Private or a crew's: a session's day, time, meeting point, spot and note, its host, and the riders going, by name and picture. Whoever has a session's link can open it, whatever its host picked. Taking your answer back deletes it: nobody ever sees who left.
  • No account? You can still say you're in from a session's link, by first name or just counted. Its host reads a guest's first name, and on a private session so does whoever holds its link; it's deleted once the day after the session is over (10 days after, if someone dropped a file in its album).
  • "I'm here" is kept for three hours after your last tap. It shows only as a mark beside your name on a session's own list. No page says who is at a spot, or how many.
  • A session's album (opening soon) is for the people who were on it, never public, and deleted 10 days after. A clip someone said no to or took down goes after three days (a reported one can stay with the moderators up to 30 days more).
  • A rain notification comes only if you ask for one, and at most once for a session.
  • A spot photo you send shows only once the founder approves it, then with your name. We remove where and when it was taken, and keep no original.
  • Never shown to anyone: your email, your date of birth, your gender, your city and your country.
  • Under 13, a parent or a coach runs the account. The kid is counted, never named.
  • From 13 up to the age your country sets (13 to 16), a parent says yes once.
  • Your account lives in the EU, in Frankfurt. We never sell your data.
  • Anyone can report a profile or a session, signed in or not. The founder reads every report.
  • Questions, or delete it all: write to hello@shredder.world.
On this page
  1. 1. Who we are
  2. 2. When you just browse
  3. 3. When you make an account
  4. 4. What's public, and what never is
  5. 5. Reports and moderation
  6. 6. Kids and teens
  7. 7. Who else handles your data
  8. 8. How long we keep it
  9. 9. Your rights
  10. 10. Cookies, and what's kept in your browser
  11. 11. Security
  12. 12. No machine decides about you
  13. 13. Changes to this page
  14. 14. Contact

1. Who we are

Shredder World is run by its founder, in Belgium. The company is being registered: its name, address and number go here once it is.

That makes the founder the "controller" in the law's words: whoever decides what happens with your data. The founder is also the person who answers you. There's no backup yet: it's one person for now.

Write to hello@shredder.world for anything on this page.

We have no data protection officer: the law asks for one only for big or risky processing.

2. When you just browse

You can use the map, the search and every spot page without an account. Here is what happens then.

  • Our host sees your connection. Every page comes from Vercel, our host. Like any website, it gets your IP address and your browser's usual details with each request, to send you the page and to keep the site safe from attacks. If Vercel's firewall thinks a visitor might be a bot, it may run a quick check in the browser first.
  • The map opens near you. Vercel turns your IP address into a rough position, city and country, and the map opens there. We don't keep that guess.
  • Times on your clock. Sessions show their place's time and, when your clock differs, yours beside it. Your browser tells the page your time zone; before it does, Vercel guesses it from your IP address. We don't keep either.
  • The map itself comes from MapTiler. Your browser asks MapTiler for the map's tiles, the aerial view and place names, so MapTiler sees your IP address and the part of the map you look at.
  • Search. Spot names are searched on our own server (on Vercel). The same text also goes to MapTiler as you type, to find places by that name. Each search carries your area or the map's centre, rounded to about 10 km, so results come out near you.
  • The weather comes from Open-Meteo, asked by our server with the spot's position only. Your IP address never reaches them.
  • Spot photos are our own copies, sent to you by our host from our own address. The sites they first came from don't see you. The store that keeps them (Cloudflare, section 7) is asked by our host, not by your browser, and most photos come from our host's own copy.
  • "Use my location" only runs when you tap it, and your browser asks you first. We round your position to about a kilometre and keep it in your browser, as your area. It isn't stored anywhere else; your searches carry it rounded to about 10 km, as above.
  • Directions open Google Maps, Apple Maps or Waze with the spot's position. What they do with it is up to them and their own privacy policies.
  • We count visits with Vercel Web Analytics: which pages are seen, and an address that doesn't exist. Analytics sets no cookie and stores no IP address: it tells one visitor from another for 24 hours with a code made from the request, then drops it. Each count comes with its time, the page's address (with any session or crew code, and any rider or crew handle, taken out), the site you came from, your country, region and city (from your connection), and which device, system and browser you use. We also count, in fixed words and never what you typed (a search, and an address that doesn't exist, are the two exceptions):
    • Spots: which spot was opened and how (from the map, a list, a search, a link, its own page or a reload). On a spot's page: whether its lower part came on screen, whether the page stayed in view for 30 seconds, which of its keys you tapped and how soon (within 10 seconds, a minute, or later), and "Say how it is": that it came on screen, and the word said (dry, puddles, wet, closed) or taken back.
    • The map: which types of spot it was set to show, and what your browser answered to "Use my location".
    • Search: what was searched, and the kind of result picked. A search is recorded in lower case and without its numbers; one with an @ in it, or only numbers, is recorded as "(hidden)".
    • Buttons and links: the kind you used, like a town in a list or the search field in the bar. The click itself never says which town, spot or rider. For a link to another site: directions (to which spot, and in which maps app), a spot's listing, Instagram, or the other site's name.
    • Signing up: how far a sign-up got (the step, and what stopped it, like "code wrong or expired" or "under 13"), who it was for (you, your kids or riders you manage), how you signed in (an email code, a password or Google), and whether you were new, coming back or already signed in.
    • Sessions: what you did with one (posted it, changed it, called it off, joined it, said you're in or coming later, took that back), and what stopped it if it didn't go through. For a weekly session: that it was posted, and whether its repeat came from your sentence or from the switch.
    • A session's link, and the planner: that you opened it, and what you tapped there (an answer or Post before signing in, "Not now", a share or a copy of the link or the message, "Add to calendar"). On a session's link, also whether you were its host, had already answered, were signed in or signed out. From someone with no account: that they opened it, and whether they came on its list or went off it (by name, counted, or kids only), never the name. On a weekly session, that the one-tap key ("I'm in as …") was used. The rain key: that it was shown, tapped, refused by your browser, turned on or turned off. A parent's read of a link (opened, and by which way; a kid put in or taken off), and "Send it to a parent" (shared, WhatsApp or copied). In the planner, how much of your sentence was understood (all, some or none) and which field you then set by hand, never the sentence.
    • A run of spot photos: where it was opened from, how far it got and how it ended.
    • A trip: how long it is, whether you made it or opened its link, and whether its route was opened in a maps app or its link sent, with how many stops; never its towns.
    • With some counts, a word for where on the site it happened (the kind of page, or the part of it) or how you got there.

Why we're allowed to: our legitimate interest in running a useful, fast and safe map and in knowing which parts are used, done in a way that doesn't identify you (GDPR Art. 6(1)(f)).

Saying you're in without an account

From a session's link you can say you're in with no account. Here is what that keeps.

  • By first name, or counted. A guest who taps that they're at least the age their own yes counts from (13 to 16, by the session's country; 16 where we don't know it) can give a first name. We rely on that tap and don't check it, and we keep the age tapped beside the name. Anyone else is counted, with no name. A phone can also count up to three kids in: kids are a number, never a name.
  • What we keep with the answer: the first name, if given, and the age tapped; going or joining later, and from when; whether you said you film that day; how many kids; and when you answered.
  • Who reads a first name. The sheet says it before you answer. The session's host, always. On a private session, whoever holds its link too. On a session that is public, or was ever listed, the host alone: everyone else sees a number. A crew's session that isn't open to public takes no guests. Away from the session's own link, guests are only ever part of a number. A guest has no picture and no page.
  • Your phone's key. Your browser makes a random key and keeps it (sw:me, section 10), with the first name you last gave. It goes only to our own site, inside the request. We keep a scrambled form of it (a hash), never the key itself, and show it to nobody: it tells us the same phone again on the sessions it answered, so you can change your answer or take it back; it also keeps a rain notification, a weekly session's one tap and your album files yours. It isn't an account, and it isn't a cookie.
  • How long. A first name can be read until the end of the day after the session's last day, on the session's clock. Within twenty minutes after that we delete the name, the age tapped and the phone's scrambled key: the guest stays in the count, a number with nobody in it. "Take me off" deletes your answer at once. If someone dropped a file in the session's album, the album keeps its own copy of your first name and your phone's scrambled key, and shows the name there to the same people, until the album is deleted, 10 days after the session's last day (section 4).
  • If you clear your browser's storage, your phone no longer holds its key and can't take its name off. The host can, and the name goes after the day after the session anyway, or with the album (section 4).
  • The host and our moderators can remove any guest. That phone can't come back to that session: we keep its scrambled key for that, until the names go; on a weekly session, 8 weeks (below). Since 16 November 2026, every removal of a guest is also noted, whether albums are open or not: the phone's scrambled key, the sign-in if there was one, and when, kept until 10 days after the session's last day, so that the session's album hides that person's clips from the others (section 4). A host can also close a session to new guests.
  • If you sign in or make an account on the same phone, a session you answered by first name offers "Move it to my profile". Tapped, your coming answers by first name move to your account where it may answer (elsewhere they're deleted), and those guest names are deleted; past ones lose their name and your phone's key. Signing in alone moves nothing. An answer you gave counted stays as it is.
  • On a weekly session (one link, a new date every week), when your phone answers by first name we keep a note for that weekly session: your phone's scrambled key, the age your last answer by name there stated, and its day. It makes the next week one tap ("I'm in as …"), and the sheet shows you that day. The note holds no name: your phone keeps it (sw:me), and each tap sends it again for that date's list, like any guest's answer. We delete the note 8 weeks after your last answer by name there, or, once the host ends the weekly session, when the day after its last date is over; within twenty minutes after either. Sooner, and at once, when you take an answer back there, answer without your name, are removed, or tap "Move it to my profile", which forgets your notes on every weekly session.
  • Removed from a weekly session. The phone is taken off its other coming dates too, and can't answer as a guest on any of its dates for 8 weeks from the removal. So is the sign-in that was on that answer, if one was, from any phone. For those 8 weeks we keep, with the weekly session, the phone's scrambled key, that sign-in, the account that removed it, and when. Nobody reads it on the site.
  • A parent signed in who counts kids in from a session's link: the count is kept with that sign-in until the names go, and nobody reads it.
  • Stopping floods. Each new answer is noted for a day: your phone's scrambled key (or your sign-in), the session, the time, and a scrambled form of your connection's address. That form is made with a key the database doesn't hold and a code that changes every day, so the database alone can't turn it back into the address. The address itself is never stored.
  • No account means no email of yours here. To ask about a guest answer, write to hello@shredder.world with the session's link and the first name you gave.

Why we're allowed to: our legitimate interest in letting a host know who's coming, done with the least we can keep (GDPR Art. 6(1)(f)).

"I'm here", and how a spot is

At a spot, or from a session's link, you can tap "I'm here" and say how the spot is. Signed in or not.

  • "I'm here". We keep the spot, the time of your last tap and how many times you tapped, with your account or, without one, your phone's scrambled key (the one above). Three hours after your last tap we delete them, within twenty minutes. We don't read your phone's location for it: the tap is your word.
  • Nobody can read who is at a spot, or how many. No page says it.
  • "Here" on a session. Tapped from a session's link, it shows as a mark beside your name on that session's own list, with no time, from thirty minutes before the start to the end, and for three hours after your last tap at most. Who reads it: the session's host and the riders with an account who are on it; on a private session, the guests on it too. Anyone else holding the link reads nobody "here".
  • How a spot is. A word (dry, puddles, wet or closed) shows on the spot's page with no name, its time rounded down to the quarter-hour and kept so. Only the two newest show. It shows until the end of the spot's day or for six hours, whichever comes first, and is deleted within twenty minutes after. Saying a spot is closed needs an account.
  • What ties a word to you. While your "I'm here" lasts, the word is tied to it. Three hours after your last tap it is nobody's, and stays until its end. For a day it can still be matched, by spot and time, with the record below. It also carries a mark, so one phone can't fill a spot's two words, that only a key the site alone holds can match.
  • "Not here" deletes your "I'm here" and the word it carries at once.
  • Stopping floods. A record of each tap is kept for a day, then deleted within twenty minutes: your account; or, without one, your phone's scrambled key and the scrambled form of your connection's address (as for guests, above); the spot; and the time.
  • Deleting your account deletes at once your "I'm here", the word it carries, and every record the limits kept of your account.
  • A spot's usual week ("usually ridden Wednesdays around 16:00") is worked out only from public one-day sessions at that spot in the last twelve weeks that three or more riders with an account said they were going to, and only for a time that came up in three different weeks. Nothing done without an account goes into it, and no "I'm here". Nobody is named. A spot's page reads the same for everyone.

Why we're allowed to: our legitimate interest in telling riders how a spot is right now, and in letting the people on a session find each other, kept for hours and shown to as few as we can (GDPR Art. 6(1)(f)).

A rain notification

Opening soon; this is what it does from the day it opens. On a session you're in, signed in or not, "Tell me if rain moves in" sends you one notification if rain is forecast for it.

  • Your browser asks you first. The key asks your browser to let us show you notifications; if you already allowed the site, it asks nothing. If you allow it, your browser gives us its address at its push service and two keys. We keep a copy with that session, under your account or your phone's scrambled key (the one above), with the answer it goes with and the time. Nobody else is shown that you asked.
  • What it says. Only from what hour rain is forecast and when your session starts, never where or with whom; a phone may show it on its lock screen. A tap opens the session's page. It goes in the two hours before the start, never between 21:00 and 08:00, and on a school day not before 15:30 (13:00 on a Wednesday in Belgium); at most once to each person who asked, and only if rain is forecast.
  • It goes through your browser's push service: Google's, Mozilla's, Apple's or Microsoft's. Your browser picks it; we work only with these four. The line is encrypted for your browser alone, and every line is the same length. The push service sees which browser a message is for, that it came from us, when, and how long to keep it, which tells it when the session starts (to the quarter-hour at worst, often to the minute); never what it says. It can tell that two of our lines went to the same browser.
  • One push address for the site. Your browser has one: we keep it with each session you asked about, so those requests are linked to each other while they wait, as they are by your account or your phone's scrambled key.
  • If you answer for your kids, the line goes to the phone that asked, never to a kid.
  • How long. We delete the address and the keys when the line goes out, when you take it back ("Don't tell me if rain moves in"), when you and any kid you answered for leave the session, or early on the day after the session's day, whichever comes first. A note that your line went (your account or your phone's scrambled key, no push address) is kept until early on the second day after the session's day, so it goes only once.
  • Signed out, your connection counts toward a limit for the sessions that start on one day. We keep a fingerprint of its address (for IPv6, of its network), mixed with a key only our server holds and with the session's start day, never the address itself. It is kept with your request and, once your line went, with that note.
  • The forecast is asked by our server from Open-Meteo with the spot's position only, as for any page. Nothing about you reaches them.
  • In your browser: a service worker and your browser's push subscription (section 10).

Why we're allowed to: your consent, given in your browser's own question and taken back with "Don't tell me if rain moves in" (GDPR Art. 6(1)(a)).

A trip

A trip finds the spots along the way between two towns. It needs no account.

  • A trip is its address. The two towns, the kinds of spot, how far off the way to look and the stops you keep are written in the page's address, nowhere else. We store no trip, so there is none to delete. Whoever gets the link opens the same trip. Like any page's address, it passes through our host's logs of requests (section 8). Our visit counts get the address without its towns or its stops.
  • The towns you type are looked up on our own site, in our own list of towns. They go to no other service. We store neither the text nor who asked: only the answer to a text can stay in our host's cache for a day, the same for everyone.
  • "From where I am" only runs when you tap it, and your browser asks you first. Your phone rounds your position to about 11 km before it leaves, and our site answers with the nearest town. We don't store the position, and it isn't kept in your browser either; the answer for that rounded point can stay in our host's cache for a day, the same for everyone near it.
  • The route opens Google Maps, Apple Maps or Waze with the positions of the stops you kept and of the town you're heading to. We give them no starting point: the app starts from where your phone is, which it knows itself. What they do with it is up to them and their own privacy policies.
  • Sending a trip hands its link to your phone's share sheet, to WhatsApp, or to your clipboard. We don't learn who gets it.
  • The link's picture, the card a chat shows under the link, is drawn by our own site from the two towns and the stops in the address.

Why we're allowed to: the same legitimate interest as for browsing, above (GDPR Art. 6(1)(f)).

3. When you make an account

You sign in with Google, with your email and a password, or with a 6-digit code we email you. Here is what an account holds, and why.

  • Your email. To send your sign-in codes and to reach you about your account. Never shown to anyone.
  • Your password, if you set one (you can skip it and sign in with a code). Supabase keeps only a scrambled form of it (a bcrypt hash), which can't be turned back into the password: nobody can read it, us included.
  • What Google gives us, if you sign in with Google: your email address, your name and the link to your Google profile picture. Supabase keeps them with your login. We use only the email: your profile shows the name and the picture you pick here.
  • Who the account is for: you, your kids, or riders you manage. It sets the steps that follow.
  • Your gender (woman or man; girl or boy for a kid). It sets which riders our picture pick shows first. It isn't public: only you, and whoever runs the account with you, can see it.
  • Your date of birth. To apply the age rules the law sets: under 13, and the age your country sets for your own yes. It also sets the day a kid's account can become theirs, at 13. Never shown to anyone. It sits in a part of the database the site's public interface can't reach; the people who run an account only learn whether the rider is under 13 or under 18.
  • Your country, and your city if you keep it. Your country sets the age rules. We fill both in from your connection: change them at sign-up, and clear the city if you don't want it kept (it's optional). After sign-up, write to us to change your country. A kid or a rider someone adds takes that adult's country. Your city is there to show you spots, riders and sessions near you, as those come. Neither is ever shown to anyone.
  • Your profile: your name (a nickname is fine), your handle, what you ride, and your picture: a rider from our character set, or your initials. Your own photo comes later. The profile is public, on your page (shredder.world/riders/your-handle): that's what Shredder World is.
  • Your Instagram username, if you add one, from 13: your page links to your Instagram. Public, and optional.
  • Who you follow. You follow riders as your own profile. Who follows whom is public once both profiles are, and your page shows how many follow you and how many you follow, counting public profiles only.
  • Who you block. Only you see it; the rider you block isn't told. Neither of you can follow the other while it lasts, nor say they're going to the other's sessions; a new block takes each of you off the other's sessions to come.
  • Your sessions. When you plan one: the day or the days (31 at most), the time (from and to, and whether you said either roughly: "15:30-ish"; an older plan can also say "till dark", or how you put it then: "after school"), its time zone, where to meet (anywhere you type), the spot (one from our map, or later), your note, the day's word if you give it one (chill, practice, filming, jam, class or contest), and its link. The time zone is the spot's; with no spot yet, it's your browser's (a region, like "Europe/Brussels"), and anyone with the link can read it in the page's data. If you change it, we keep the plan as it was just before, so its page can show what changed. If you call it off, we keep when. And who sees it: Public, Private, or one of your crews, and for a crew's session whether it's open to public and visible to the crew's followers.
  • A weekly session. A session can repeat every week. It has one link, which shows its next date (once you end it, its last one), and until you end it we post each week's date in your name, whether or not anyone opens the link. Each date is a session like any other, with its own list: you're down as going on every one, and nobody else's answer carries over to the next week. We keep the weekly plan itself (its day of the week, times, time zone, spot, meeting point, note, the day's word and who sees it, and when it was made, first made public, changed and ended) as long as your account. Whoever has its link reads that plan and its host, as for any session.
  • Your answers to sessions: going, or joining later (from a time, or from a day of a session over several days), whether you said you film that day ("I film": a camera with you), and when you said it. When a parent or a coach answers for a rider they run, we keep which sign-in answered. Taking an answer back deletes it at once: nothing keeps who left.
  • Counts that stop floods: each time you answer a session or change one, we note your sign-in and the time, for a day, so nobody can send thousands.
  • Since when: the date you joined is kept with your profile; we show the month.
  • "managed by @…" beside a handle, naming the coach, agency or parent who runs the account. On a rider's page from 13 it shows only if it's turned on, and once the rider has their own sign-in, it's their call. A kid under 13 has no page.
  • Who runs which account: the link between a login and a rider (your own, a parent's, a manager's), and the time a parent or a manager confirmed that the right person agreed.
  • When you agreed to our terms, and which version (its date), kept with your profile, to show that you did. For a kid or a rider you add, it's your yes, given for them.
  • A parent's email, for a rider of 13 up to their country's age (section 6).
  • Sign-in records. When you sign in, Supabase, which runs our sign-in, records the time, your IP address and your browser, to keep you signed in and to spot misuse.

What you must give: your email, your gender, your date of birth, your country, a name and a handle, and what you ride (not if you're a parent or a manager who doesn't ride). For a kid or a rider you add: their name, handle, gender, date of birth and what they ride, and your tick. Without them there's no account. Your city and your Instagram username are optional.

Why we're allowed to:

  • Your account, your public profile, your follows, your blocks, your sessions and your answers: to give you the service you signed up for (GDPR Art. 6(1)(b)). Under your country's age, your account rests on your parent's yes instead (Art. 6(1)(a) and Art. 8).
  • Your date of birth and country: to meet the law's age rules (Art. 6(1)(c), with Art. 8), and our legitimate interest in keeping kids safe (Art. 6(1)(f)).
  • Sign-in records, and the counts that stop floods: our legitimate interest in keeping accounts and sessions safe (Art. 6(1)(f)).

The emails we send go out through Resend: your sign-in codes (opening one loads its picture from our site, unless your mail app blocks that), and, from hello@mail.shredder.world, the answers to reports and moderation's decisions (section 5), in plain text with no picture.

4. What's public, and what never is

Everything is public unless decided otherwise. That is the rule Shredder World is built on.

  • Anyone can see, signed in or not: your handle, name, what you ride, your picture, your Instagram link if you add one, the month you joined, who you follow and who follows you (between public profiles), and how many.
  • Never shown to anyone: your email, your date of birth, your gender, your city, your country, a parent's email, who you block, what you report, your sign-in records, and the name and picture Google gives us.
  • Kids under 13 are never public. Only the parent or the coach who runs the account sees the profile. A kid has no page, can't be followed, and is never in anyone's counts: anywhere else they're counted, never named, and never pictured.
  • While a parent's yes is awaited, the profile stays hidden.
  • Who finds a session: a Public one is listed for everyone (at its spot, on its host's crews' pages, in followers' weeks). A Private one is listed only for its host and the riders in it. A crew's session is listed for the crew's members; for its followers too when it's visible to followers; for everyone, with the crew's name on it, when it's open to public. Only the crew's members can join a crew's session that isn't open to public. Signed out, only Public ones are listed. A crew's session whose crew is gone, or whose host left the crew, counts as Private (or Public, if it was open to public).
  • Sessions (shredder.world/s/…), whatever their host picked: anyone with the link, signed in or not, sees the plan (the day, the time and its time zone, where to meet, the spot, the note, the day's word), its host (handle, name, what they ride, picture), what changed since it was posted, and the riders going or joining later, by name and picture, with the time they said and whether they film. A spot's sessions from yesterday on can be listed by anyone too. A rider under 13, or one whose profile is hidden, is counted, never named or pictured. Nobody, the host included, ever sees who took their answer back. Signed out, a session more than a day past shows who went only as a number.
  • A session's link in a chat: when you share it, the app (WhatsApp, Instagram, Telegram, iMessage…) fetches its preview from us once: a picture with the day, the time, the spot and the day's word, over the spot's photo when we have one, and the host's name. Never who's going, a count or the weather. The chat keeps that preview as it was, even after the session changes or is taken down.
  • Rider pages (shredder.world/riders/…) show the public part of a profile. We ask search engines not to list them, for now.
  • Spot photos you send are seen only by the founder until they're approved. Then anyone sees them on the spot's page, with your name if you run your own public profile; a photo from an account a parent, a coach or a manager runs shows no name. The approved photos can be listed by anyone with their riders' names, so the spots you photographed are public too. Before keeping a photo, we redraw it at 1920 × 1080 pixels at most, without what the file says about where and when it was taken or the phone that took it. We don't keep the file you sent.
  • A profile taken down by moderation shows nowhere, until it's put back (section 5).

A session's album

Opening soon; this is what it does from the day it opens. One part runs already: since 16 November 2026, a guest's removal is noted (below). Once a session is over, the people who were on it can drop the day's photos and videos in its album. A session called off has none.

  • Who can open it. Only the people on the session, with an account or without: on a session that was ever listed, those who answered before it ended; on one shared only by its link, those who answered by the end of its last day. It never shows on a public page, on a spot's page, or to anyone with no place on the session.
  • Who sees a clip. On a session that was never listed (an invitation by its link), everyone on it sees every clip, once each person named in it said yes. On a session that is or ever was listed, a clip is seen at first by the one who filmed it and the people named in it; once each of them said yes, the host sees it too. One of the people named in it, or the host, can then share it with the session; the one who filmed it can't, unless they are the host. Before they press, the key says how many it goes to ("Everyone on the session: 14 people"): everyone who answered before the session ended, each account and each phone counted once. Whoever may share it may take the share back, and changing the names in a clip cancels it.
  • Names, yes and no. Only people named on the session's list can be named in a clip: riders with an account, and guests who gave a first name. Kids never are. A clip that names you is shown only to the one who filmed it and the others named in it until each of you said yes. "Not this one" gives it back to the one who filmed it: it isn't shown, it's deleted three days later (How long, below), and we refuse that same file there again (a copy edited or saved again is a new file to us). Once shown, a clip says who is in it and who filmed it, by the names each viewer may read: a rider's name to everyone on the session, a guest's first name as section 2 says (on a session that is public or was ever listed, to the host alone), otherwise "someone on the session". On such a session, only the host can name a guest.
  • Taking a clip down. Anyone else who sees a clip can take it down while the album lasts. It goes back to the one who filmed it for three days, then it's deleted; they're never told who did it, and that same file is refused there. The adult who brought kids can take down any clip they see: signed in with kids counted from the link, until the end of the day after the session; on a session that was ever listed, they see a clip only once it's shared or names them.
  • Saving. Anyone who sees a clip can save it to their phone, and we can't take that copy back.
  • Blocks and removals. Nobody sees a clip whose filmer they blocked, or who blocked them. The clips of someone the host or a moderator removed from the session are hidden from everyone else. So are the clips of a rider the host blocks, or one our moderators suspend. For that, since 16 November 2026, every removal of a guest is noted, whether albums are open or not and whether the session has an album or not: the removed phone's scrambled key, the sign-in if there was one, and when, until 10 days after the session's last day. No removal from before that day is noted this way. A rider the host blocks is off the album too, even once the session is over: only their own files are left to them, to save or delete.
  • What we take out of a file. Before a file leaves your phone, the page blanks where it was made and what made it: the place, the make, model and serial numbers, the software, the owner's and author's names, and any text written into it. A video keeps only its picture and sound. The camera's settings for the shot stay, and so do the day and time it was filmed, with its time zone when the file has one. A kind of file the page can't clean (WebM, a video in pieces, a file it can't read) isn't sent. Some drones and dashcams write the place into the picture or the sound itself: we can't take that out, so don't drop such a file if where it was filmed matters.
  • What we keep with a file: who dropped it (your account, or your phone's scrambled key), its name on your phone (shown to you alone), its size, type and length, a print of it (a code worked out from the file, to know the same file again), the names in it and when each said yes, its small picture, and when it was dropped, kept, shared or taken down. The size and print of a file sent back (a no, a take-down, a report) are kept after the file itself is gone, until the album is deleted, 10 days after the session's last day, so that same file is refused there.
  • Where the files are. At Cloudflare (R2), in a private store of their own. Your phone sends each file straight to Cloudflare and fetches it from there, through links that last a minute (three minutes to send a part), so Cloudflare sees your IP address. The small picture of a file goes through our server, which draws it again from the image alone.
  • Guests. Once someone drops a file, the album keeps its own copy of the session's guests: for each guest's phone, its scrambled key, the first name it gave if it gave one, and when it joined. It's kept while the album has files, after the guest list itself has forgotten them. A first name the guest list forgets sooner (an account made, a leave, a removal) is forgotten by the album too.
  • How long. An album is deleted 10 days after the session's last day, all of it: the clips shown, and the ones still waiting for a yes. Sooner when the session is called off, or an hour after it's taken down (put back within that hour, the album comes back whole; later, it doesn't). While the album holds a file, the session's days can't be moved, so the album's end doesn't move either. A clip sent back to the one who filmed it (a no, a take-down, a report, a name taken off when an account is deleted) is deleted three days after, or with the album if that comes first: until then its filmer still has it, to save or delete, and reads the day it's deleted. An upload left unfinished is deleted after a day.
  • Deleting. You can delete a file you dropped at any time, on the session or no longer on it (if you left it or were taken off it, its link still shows you your own files, to save or delete, and nothing else of the album): it leaves the album at once, and our server deletes it from the store before it answers you; if the store doesn't answer, it's tried again at our next clean-up (every ten minutes), then once a day. A reported file is the one exception (Reports, below). Deleting your account deletes the files it dropped the same way, at our next clean-up; a clip still waiting for your yes goes back to the one who filmed it, and clips you said yes to stay, without your name. Files dropped from a phone with no account stay that phone's until it deletes them or the album does (How long, above), even if you later make an account on it.
  • Reports. Reporting a clip takes it down at once: only the one who filmed it still sees it, for three days, as any clip sent back. Within the limits on reports it also sends a report to the moderators, as for a session (section 5): the report keeps the session as it was then, the file's kind, type and size, and who filmed it. A moderator can then open the file; each look is written down (who, which report and file, when) and kept a year, as the decisions are. While the clip is still in the album, or held for the report after it left (below), a moderator may delete it for good; the decision keeps the file's size and type, and its print if it was still in the album, not the file. An account that dropped it reads that decision on its account page, with the ground, the rule and the facts; a phone is told nothing, since we hold no address for it. If the file would go while the report is open (its three days over, deleted by the one who filmed it, its session taken down, its album over, its account deleted), we hold it, seen by the moderators alone, until the report is decided or 30 days pass. A decision on the whole session, leaving it up or taking it down, doesn't decide a report on a file no moderator has looked at yet. A report the moderators turn down doesn't bring the clip back.
  • Stopping floods. We count what each person does in an album by the hour, for a day: by account, or by the phone's scrambled key and a scrambled form of the connection's address (as for guests, section 2).
  • Signed in on a phone that answered as a guest, the page sends that phone's key along (sw:me, section 10), so your account also reaches the files and clips of that phone.

Why we're allowed to: to give the people on a session the album they use (GDPR Art. 6(1)(b) with an account; our legitimate interest, Art. 6(1)(f), without one); a clip that names you is shown only on your yes.

5. Reports and moderation

Anyone can report a rider's profile or a session, signed in or not: More, then Report, on the rider's page, or "Report this session" on its page.

  • What a report keeps: the profile it's about as it was then (the handle, the name, the picture, the Instagram link), or the session as it was then (its plan, its link, its host's handle and name), the reason you picked, your words if you added any, whether you said it's illegal, and the time.
  • Guests in a report. A report about a session keeps a guest's first name, and the age they tapped, only if anyone holding the session's link could read it when the report was sent (a private session, until the end of the day after it). When we remove a guest, our decision keeps their answer as it stood, first name and age tapped included. Both are kept as long as reports and decisions are: a year after the decision.
  • About you, when you report: signed in, your account, so Your account lists your reports and our answer goes to your account's email. Signed out, nothing unless you give it: your name and your email are optional, except in a report of illegal content, where the EU's Digital Services Act asks for both (not for child sexual abuse material). We use your email to say we got the report and what we decided, and for nothing else.
  • The rider, or the session's host, isn't told who reported.
  • Stopping floods. To limit the reports one connection can send, we keep a scrambled form of your connection's address for a day. It's mixed with a code that changes every day and is deleted after two, so it can't be turned back into the address. The address itself is never stored.
  • A person decides: the founder reads every report and decides whether the profile or the session stays up, comes down, or the account is suspended. A session taken down is gone from every page, the week and the spot's list. No machine decides. Each decision is recorded: what was done, the rule or the law it rests on, the facts, and when the rider was told. That record is the "statement of reasons" the Digital Services Act asks for (Art. 17): whoever runs the account gets it by email, and on Your account.
  • Spot photos are checked before they show. The founder approves or refuses each one, and can take an approved one down. A refusal or a take-down says why, by email and on Your account, and is kept like any decision. A photo can't be reported from its page yet: write to hello@shredder.world.
  • How long: a report and the decisions on it are kept for a year after the decision, then deleted, so a decision can be challenged and we can show what we did. A profile or a session taken down stays in our database, hidden from everyone, so it can be fixed or looked at again, until it's put back or the account is deleted; if the account goes, the report keeps what was reported for that year.
  • Why we're allowed to: the law asks us to handle reports and give our reasons (the Digital Services Act, Art. 16 and 17; GDPR Art. 6(1)(c)), and our legitimate interest in keeping Shredder World safe (Art. 6(1)(f)).

6. Kids and teens

  • Under 13, everywhere: no account of their own and no email of theirs. A parent makes the account from their own ("My kids"), or a coach, team manager or agency does ("Riders I manage"). Only that adult signs in, and only they see the profile.
  • A kid under 13 who tries alone is stopped at the date of birth, and asked to hand the phone to a parent. The login made with their email is deleted as soon as they tap on ("I'm the parent", "Back to the map"); one left open is deleted with the unfinished sign-ups (section 8).
  • The adult's tick. A parent ticks that they're the kid's parent or guardian and agree to the account. A coach ticks that the kid's parents agreed (a club's form counts). We rely on that tick and don't check it, nor the date of birth anyone types. A false tick breaks our terms, and we delete the account as soon as we know.
  • At 13 the account can become the rider's. That step isn't built yet: until it is, the profile stays hidden and the adult keeps running it.
  • From 13 up to the age your country sets (13 in Belgium, 15 in France, 16 in Germany, the Netherlands and Ireland; 16 for a country we don't list), the account is the rider's own, and a parent says yes once, by email. The profile stays hidden until they do. We use the parent's email for that yes and nothing else.
    • The email asking for that yes isn't sent yet: it comes with the next update. Until then the profile stays hidden, and we keep the address only for it. You or your parent can ask us to delete both at any time.
    • Once it's sent: if no yes comes within 14 days, with a reminder at 7, we delete the profile and the parent's email.
  • From your country's age, your own yes is enough.
  • A manager (a coach, a team manager, an agency, 18 or over) can run a rider's account at any age. A rider of 13 or over that a manager adds is public at once, on the manager's tick that they agreed (or that their parents did, under the manager's country's age). We have no way to reach that rider until they get their own sign-in, so the manager must tell them about this page.
  • The rider's last word. From 13 the rider can get their own sign-in beside the manager's (coming soon), and then has the last word: they can remove the manager, and the manager can't delete the account or change how it signs in.
  • Parents' rights. A parent can ask us to see, correct or delete their kid's data, and can take back their yes at any time. We then hide the profile at once and delete the account.
  • Sessions. A parent or a coach can say a rider they run is going. A kid under 13 is counted, never named or pictured: only that adult sees the kid's name on the session's page. A rider waiting for a parent's yes is counted the same way until it comes. A kid can't post a session: its host is a public rider with their own sign-in. Hosts are told to meet somewhere public, never at a home.
  • A session's link, read as a parent. A session's page can be read in a parent's order: who hosts it, the day, the start and the end, where it is and the way there, the rain over those hours, who's in. It is the same page with the same data: it reads nothing more, keeps nothing more, and stores nothing in your browser. Which read you're on is written in the page's address, nowhere else. A kid's name shows only to the sign-in that runs that kid, as above.
  • "Send it to a parent" hands the session's link, and nothing else, to your phone's share sheet, to WhatsApp or to your clipboard. We don't learn who gets it, and no parent's number or email reaches us this way.
  • Without an account. A kid counted in from a parent's or a friend's phone is a number, never a name. A rider who answers by first name taps that they're their country's age or older: we rely on that tap and don't check it (section 2).
  • "I'm here" is a mark on a session's own list, for the people section 2 names, and it lasts hours. No page says who is at a spot, a kid no more than anyone.
  • A session's album (section 4). Kids are never named in a clip. The adult who brought them can take down any clip they see, within the limits section 4 gives.
  • What we never do with kids' data: sell it, show ads with it, rank them, or show their age to anyone.
  • Outside the EU. We're built for Europe.

7. Who else handles your data

We don't sell your data, and we don't share it with advertisers or data brokers. These companies handle it for us, each for its own job:

  • Supabase: our database and sign-in. Your account is stored in Frankfurt, Germany. Supabase's staff and its own suppliers can reach it from outside the EU (the US, Singapore); those transfers are covered by the EU's Standard Contractual Clauses in Supabase's data processing agreement.
  • Vercel Inc. (USA): hosts the site, runs our server code in Frankfurt, and counts visits (Web Analytics). Pages reach you from the Vercel server nearest you, which can be outside the EU if you are. Covered by the EU–US Data Privacy Framework and by Standard Contractual Clauses in Vercel's data processing agreement.
  • Resend (Plus Five Five, Inc., USA): sends our emails (sign-in codes, and the answers to reports and moderation's decisions), from Amazon's servers in Ireland. It handles your email address and the email itself. Covered by the EU–US Data Privacy Framework and Standard Contractual Clauses in Resend's data processing agreement.
  • ImprovMX (USA): passes on the mail sent to @shredder.world addresses. Mail goes through its servers in the EU and is deleted once delivered. Covered by Standard Contractual Clauses in its data processing agreement. It hands the mail on to our inbox at Google (Gmail), which is covered by the EU–US Data Privacy Framework.
  • MapTiler AG (Zug, Switzerland): the map's tiles, the aerial view and the place search, asked by your browser. It sees your IP address and keeps it up to 2 months for security. The EU recognises Switzerland's data protection as equal to its own (an "adequacy decision").
  • Open-Meteo (Switzerland): the weather, asked by our server with a spot's position. It gets nothing about you.
  • Cloudflare, Inc. (USA): stores riders' spot photos (R2): the ones waiting for the founder's check, in a private store only the founder can open, and the approved ones the site shows. And the sessions' albums, in a private store of their own: your phone sends those files to Cloudflare and fetches them from it, so there Cloudflare sees your IP address (section 4). Covered by the EU–US Data Privacy Framework and Standard Contractual Clauses in Cloudflare's data processing agreement.
  • Your browser's push service (Google, Mozilla, Apple or Microsoft, all in the USA: your browser picks it, not us): carries a rain notification to your browser, encrypted, only if you turn one on (section 2). Its servers can be outside the EU. We have no contract with them: each runs its service for its browser, under its own privacy policy.

Sign in with Google (Google Ireland Limited): if you use it, Google checks it's you and tells us your email address, your name and your profile picture's link (section 3). Google knows you signed in to Shredder World; what it does with that is up to its own privacy policy.

Coming: Sign in with Apple (Apple Distribution International Limited, Ireland): if you use it, it tells us your email address, or a private relay address instead. This page will name it before it's used.

The law. We hand data to the police or a court only when the law makes us. We report child sexual abuse material to the police.

8. How long we keep it

  • Your account: as long as you keep it. When you ask us to delete it, we delete your login, your profile and everything linked to them from the live database within 7 days, and they leave Supabase's backups as those roll over, within about a week after that.
  • A kid's account: until the parent or the coach deletes it, or the rider does once it's theirs.
  • Waiting for a parent's yes: until the email asking for it goes out (coming), then 14 days, then deleted (section 6).
  • A kid under 13 who tried alone: the login is deleted as soon as they tap on; otherwise as a sign-up left half-way.
  • A sign-up left half-way (the code typed, no profile made): deleted after 30 days.
  • A session: as long as its host's account, called off or not; a weekly session's plan and each of its dates, the same. Your answers: until you take them back, or your account goes.
  • A spot photo you send: while it waits, until the founder decides; once approved, until you delete it, it's taken down, or your account goes. A refused, withdrawn, deleted or taken-down photo's files are deleted at once and leave the site within minutes; the decision on it is kept a year (section 5).
  • A guest's answer (no account): the first name, the age tapped and the phone's scrambled key until the end of the day after the session's last day, deleted within twenty minutes after; the count they were part of stays. The album's copy of a name: below. A removed phone's bar: the same; on a weekly session, 8 weeks; the record of a removal, since 16 November 2026, until 10 days after the session's last day (below). The day's notes that stop floods of guest answers: a day.
  • On a weekly session, without an account: the note that makes next week one tap, 8 weeks after the phone's last answer by name there, or, once its host ends it, until the end of the day after its last date; a removed phone's bar, 8 weeks from the removal. Both deleted within twenty minutes after.
  • "I'm here": three hours after your last tap. A word about a spot: until the end of the spot's day or six hours, whichever comes first. Both deleted within twenty minutes after. The record of each tap, against floods: a day. The daily code that scrambles a connection's address: until the end of the next day (UTC).
  • A session's album (opening soon; nothing here is kept before the day it opens, except a removal's record, kept since 16 November 2026): its files, until 10 days after the session's last day, or until the session is called off, or an hour after it's taken down; a file sent back to the one who filmed it (a no, a take-down, a report), three days, or until the album goes if that comes first; an unfinished upload, a day; a file you delete, at once from the album and from the store (a delete the store refuses is tried again at each clean-up, then once a day); a reported file that would go, until the report is decided, 30 days at most. The album's copy of the guests: while it has files, so 10 days after the session's last day at most. A removal's record, and the size and print of a file sent back: until 10 days after the session's last day. The hourly counts against floods: a day. A moderator's looks at a reported file: a year.
  • A rain notification's address and keys: until the line goes out, you take it back, you and any kid you answered for leave the session, or early on the day after the session's day, whichever comes first. The note that your line went: until early on the second day after the session's day.
  • The counts that stop floods of answers and changes: a day.
  • Reports and moderation's decisions: a year after the decision (section 5). The scrambled form of a connection's address: a day.
  • Sign-in records: a session lasts until you sign out from Your account (which ends it everywhere) or it runs out; signing out on the sign-in page forgets it on that device only. Supabase's log of sign-ins, which keeps the email address used, is kept for a limited time, as Supabase's plan sets it.
  • Mail you send us: as long as we need it to answer you, and to show what we did with a request (a takedown, a deletion), and no longer than 2 years.
  • Visit counts: the code that tells visitors apart is dropped after 24 hours. The counts stay, with nobody in them.
  • Vercel's logs of requests: kept by Vercel for a short time, then deleted.
  • What's kept in your browser: until you clear it (section 10).

9. Your rights

You can ask us, at any time and for free, to:

  • see what we hold about you, and get a copy (GDPR Art. 15);
  • correct what's wrong (Art. 16);
  • delete it: your whole account, or one thing (Art. 17);
  • take it with you in a file a computer can read (Art. 20);
  • object to what we do on our legitimate interest (Art. 21);
  • pause what we do with it while we sort out a question (Art. 18);
  • take back your yes, or your kid's, where we rely on it. What we did before stays lawful (Art. 7(3)).

How: write to hello@shredder.world from the email on your account. If you write from another address, we send a code to the account's email first, to be sure it's you. We answer within a month; if a request is complex we can take two more months, and we tell you so within the first month. Delete and download keys come to Your account soon.

A parent uses these rights for a kid under 13, and for a rider under their country's age. From 13, a rider can use them too.

Complaints. You can complain to the Belgian Data Protection Authority (Autorité de protection des données / Gegevensbeschermingsautoriteit), Rue de la Presse 35 / Drukpersstraat 35, 1000 Brussels, contact@apd-gba.be, +32 2 274 48 00, autoriteprotectiondonnees.be, or to the authority where you live. Telling us first often fixes it faster, but you don't have to.

10. Cookies, and what's kept in your browser

  • No cookie to browse. No ad cookies and no tracking cookies, ever.
  • Signed in: one cookie keeps you signed in, sb-noooautnmtrzzhifjbon-auth-token (in parts, .0, .1, when it's long). It's set when you sign in, removed when you sign out on that device, and lasts up to 400 days.
  • Vercel's firewall, if it checks your browser for a bot, may keep a short-lived note that it passed.
  • A service worker on session pages, added when you first allow a rain notification (section 2) and kept until you clear the site's data: it shows the notification and opens the link, and stores nothing. With it, your browser's push subscription. Clearing the site's data removes both; blocking notifications stops them; "Don't tell me if rain moves in" stops the line but leaves both in your browser.
  • Kept in your browser, and nowhere else:
    • sw:home: the place you set as your area, or your rounded position if you tapped "Use my location" (searches carry it, rounded to about 10 km: section 2);
    • sw:recent-search: your last six search picks (the spot or the place, with its name and position);
    • sw:data-reload: for this tab only, stops the page reloading in a loop after an update;
    • sw:plan: the session you're planning, so a sign-in or a reload doesn't lose it, for 12 hours at most;
    • sw:held: and the session's link code: the answer you gave before signing in, sent once you're in if that's within the hour, and dropped after;
    • sw:me: the key your browser made for itself and the first name you last gave, so an answer given without an account stays yours to change or take back (section 2). The key goes to our own site, with such an answer, with a rain notification's key, a weekly session's one-tap key and a past session's album (sections 2 and 4), and nowhere else;
    • sw:spoken: what you just said about a spot (the spot, the word and its quarter-hour), for five minutes, so the page shows it at once;
    • sw:said: in the planner, the words you used for a spot ("the bowl") and the spot you picked for them, 30 at most, each dropped after 180 days unused. Never sent anywhere;
    • sw:directions: the maps app you picked for directions (Google Maps, Apple Maps or Waze), one word;
    • shredder-pitch-notes, on /pitch, our pitch deck, only: the presenter's password, if typed;
    • sw:team, on /labs/team, a page for our own team, only: a mark set there by hand, which leaves that browser out of the visit counts.

These are all needed for what you asked for, so there's no banner asking.

11. Security

  • Your account is stored in the EU, and every connection is encrypted (HTTPS).
  • A password, if you set one, is kept only as a bcrypt hash, never as you typed it. A sign-in code works once, within the hour.
  • The database itself enforces who can read what, row by row: the site's public interface can't read an email, a date of birth, a city, a gender, a report, or anything about a kid under 13.
  • Only the founder can reach the database's controls.
  • If a breach puts your data at risk, we tell the Data Protection Authority within 72 hours, and you without delay if the risk to you is high (GDPR Art. 33 and 34).
  • Found a hole? Tell us at hello@shredder.world.

12. No machine decides about you

Nothing about you is decided by a machine alone in a way that affects you seriously, and nothing is profiled for ads. The age rules follow the date of birth you give: if we got something wrong, write to us and a person looks. A person reads every report (see our terms).

13. Changes to this page

When this page changes, the date at the top changes, and the change applies from that day. Shredder World is being built: features open as they're ready, and what a new one does with your data is on this page the day it opens. Rider pages, follows, blocks and reports were added on 25 October 2026, and sessions on 26 October 2026. Answers without an account, "I'm here", trips and weekly sessions were added on 15 November 2026; the rain notification and the session's album, which open soon, are on this page since that day. Earlier versions: on request.

14. Contact

hello@shredder.world. A postal address comes here once the company is registered.