MOKET
Controller
The controller for the Moket app and its website is:
Mirko Genovese
Ziegeleistr. 53B
86199 Augsburg, Germany
Email: info@moket.app
We are not required to appoint a data protection officer. For any privacy question, write to the address above.
In short
- Moket collects your location only during a ride you start yourself. Nobody ever sees where you are.
- Raw GPS points are deleted no later than 72 hours after the ride ends.
- Your private zones stay on your phone, and points inside them never leave it.
- Encounters only show a fuzzy area (about 5 km), the day and a time of day.
- We sell no data, show no targeted ads and use no tracking; the only statistics are the anonymous usage statistics (Aptabase), which you can switch off.
- You can delete your account in the app at any time.
Account and sign-in
To sign in you enter your email and receive a one-time code; there is no password. We store your email, an internal user ID, sign-in times and when you accepted which version of the terms and privacy policy (at sign-up). The code is sent via Brevo (Sendinblue SAS, Paris, France) as our processor.
Legal basis: Art. 6(1)(b) GDPR.
Profile and bike
We store nickname, stated area, riding style, experience, bike (make, model, year, colour, category, look), your settings (e.g. ghost mode, notifications, who may follow you), your records (top speed, estimated max lean angle, with date) and medal levels.
For the place medals we store on the server which mountain passes and meeting points you have reached and in which areas of about 20 × 40 km you have ridden, without date, time or ride. Nobody can read this list, not even you: the app only receives the counts. It is kept until account deletion.
Other riders see only nickname, bike, style, area, your profile description (optional, up to 160 characters; swear words are replaced with asterisks, the server rejects links and phone numbers; after 3 reports it is hidden until reviewed) and, unless you switch it off, your medal levels. Only you see your records, unless you share them. We do not ask for your real name, date of birth or gender.
Profile photo (optional, with Moket Pro): if you upload a photo of yourself or your bike, our server scales it to 512 × 512 pixels (plus a small thumbnail) and removes all metadata such as where it was taken (EXIF/GPS). Everything here applies equally to a cover photo shown instead of the mountains at the top of your profile (1200 × 600 pixels, no thumbnail). It is stored in non-public storage at Supabase in Frankfurt; only people allowed to see it can download it. Before others see it, Amazon Rekognition (Amazon Web Services EMEA SARL, Luxembourg; servers in Frankfurt am Main) checks it automatically for nudity, violence and banned symbols. Amazon receives only the scaled image, without name or email, does not keep it after the check and does not use it to train its own models. A doubtful photo stays hidden until the Moket team has looked at it; a clearly banned one is never stored. We keep the time and result of each check for 2 days to limit abuse. Who sees your photo: you, your friends and anyone on the same group ride (until 7 days after). If you turn it on, also all riders or, while you organise a ride, anyone viewing it. Everyone else sees your bike. After 3 reports the photo is hidden until reviewed. Without active Pro it is not shown. If you replace or remove the photo, we delete the old one immediately; also when you delete your account. Other people or other riders’ number plates may only be recognisable with their permission.
Biker spot photos (optional, with Moket Pro): you can add a photo to a place on the biker spots map (up to 3 per place, one each). Our server scales it to 1200 × 900 pixels (plus a thumbnail) and removes all metadata such as where it was taken (EXIF/GPS); Amazon Rekognition checks it like the profile photo, and only a clean photo is stored. It is kept in public storage at Supabase in Frankfurt and is visible to all riders in the app, without your name; the Moket team can see who uploaded it. It stays visible without Pro. After 2 reports it is hidden until reviewed. Legal basis as for the profile photo.
Legal basis for the profile photo: Art. 6(1)(a) GDPR (consent by uploading; you withdraw it by removing the photo); for the automatic check Art. 6(1)(f) GDPR (protecting users from banned content).
Legal basis: Art. 6(1)(b) GDPR.
Location during a ride
When: only from “Start ride” until the ride ends, with the “While using the app” permission. On Android a visible foreground service with a notification keeps recording while the screen is off. No location is collected outside a ride.
Filtered on the phone: points in your private zones are never sent. Before your first ride you set at least your home zone (minimum radius 500 m). The zones themselves stay on your device only.
On the server: the remaining points (coordinates, time, accuracy) are automatically matched against other rides (about 150 m at the same time). Nobody, not even you, can read raw points or tracks. The server discards implausible points (for example impossible jumps or times in the future). They are deleted 72 hours after the ride ends.
Encounters: we keep only the two accounts and rides, a fuzzy area (about 5 km), the nearest town, the day and a time of day. They become visible only after both riders have ended their ride: someone still riding is never shown. During the ride the app shows at most a count, without names or places. The alert comes at the moment you cross; if the app is not open or the screen is off, it comes as a notification. Whoever gets it therefore knows where they were at that moment and, once you have both ended your ride, sees who they crossed, and so also when and roughly where it happened. If you do not want to appear in any encounter, turn on ghost mode.
Ghost mode: when on, your points do not leave your phone and you take part in no matching.
Help request: if you ask for help during a ride (e.g. fuel, puncture, battery), we notify at most 30 nearby riders (first 20 km, then 40 km after 5 minutes or once everyone has said no; during the first hour also riders who newly come nearby) who are riding or have set a help zone. They see nickname, bike, type of problem and approximate distance. A helper gets your exact location only if you send it yourself. If a rider answers “I can’t”, we store that with the request: the person asking only sees how many said no, not who. Notified riders see how many have already said yes and, only when 5 or fewer were notified, how many were notified. Request, refusals, chat and shared location are deleted 72 hours after closing. If a helper reports a false alarm, we keep only who reported whom and when, for 30 days: with 2 reports from different riders the help feature is blocked for 30 days. For the help zone we keep a point rounded to about 5 km until you switch it off or delete your account.
The track of your rides stays on your phone only. On the server we keep, per ride, start, end, status, bike and the summary (km, duration, top speed, estimated maximum lean, title, group ride), so you get your history back on a new phone and medals are calculated there. Only you see the summary; others see at most your medal levels.
Legal basis: Art. 6(1)(b) GDPR. You can revoke the permission at any time in your phone settings.
Flashes, contacts and chat
After an encounter, or with a rider code/QR code, you can send a contact request (“flash”). We store sender, recipient, time and status. Unanswered requests expire after 7 days without the sender being told.
Only when both accept can you chat. Messages are kept with sender, time and read status until one of you deletes the account or ends the contact. They are encrypted in transit and on the server, but not end-to-end. We only read a chat if a participant reports it to us. To prevent abuse we limit code lookups (30 per hour).
Legal basis: Art. 6(1)(b) GDPR; abuse prevention Art. 6(1)(f) GDPR.
Rides, following and news
Group rides: others see title, description, date, meeting point (a public place), bike categories and your nickname as organiser. Only participants see the participant list. To find rides near you the app sends an approximate position that is not stored. If you turn on alerts for new rides, we store the centre of the area rounded to about 5 km, its name and the radius until you turn them off or delete your account; to avoid duplicates we remember for 7 days which alerts you have already received.
Following: the rider you follow sees that you follow them (nickname and bike, as everywhere in the app) and gets a notification, at most one a day; it can be turned off in Notifications. Others only see the count; you can hide it and choose who may follow you.
News: your followers learn about your new public rides, new medal levels (if visible) and, only with “I’m going too”, the public rides you join. These entries are deleted after 30 days. Places, rides or encounters are never shared.
Polls (e.g. the new logo): we store which designs you voted for and when, linked to your account, so everyone votes only once. Others only see the overall result, never who voted for what.
Legal basis: Art. 6(1)(b) GDPR.
Road reports
During a ride you can drop a report with one tap (road hazard, crash, check). We store type, position, time, expiry and your account. Others see the report nearby but never who made it. Reports expire after 1–4 hours. Your account is kept only to prevent abuse (max 10 reports per hour) and so you can undo a mistaken report. Expired reports are deleted no later than 24 hours after expiry.
Legal basis: Art. 6(1)(b) and (f) GDPR.
Creators and invite codes
For a creator application we store the channel, stated follower count, verification code and our review note. A creator page shows nickname, bio, channels, a “My gear” link marked as an ad, and upcoming public rides, never rides, positions or encounters.
If you sign up with a creator’s invite code we store that link; the creator sees the total plus your nickname and the day you signed up, nothing else, and can send you a friend request you can accept or ignore; they never see your bike code. We tell you this when you enter the code. For the banner we count views and taps per creator and day without storing who. External pages (YouTube, Instagram, shops) are the responsibility of their operators.
Legal basis: Art. 6(1)(b) GDPR; statistics Art. 6(1)(f) GDPR.
Moket Creators (page moket.app/moket-creators): for our Moket Creators we show on moket.app their name or nickname, photo, bike, a short text and links to their channels, only with their explicit consent (Art. 6(1)(a) GDPR). The photo is resized and stored without metadata. Consent can be withdrawn at any time; the card is removed within 7 days. In the app others only see the «Moket-Creator» badge; Moket Pro for Moket Creators is recorded on our server while the partnership lasts.
Push notifications
If you allow notifications we store your phone’s push token. Delivery runs through the Expo push service (650 Industries, Inc., USA) and Firebase Cloud Messaging (Google Ireland Ltd.) or Apple Push Notification Service. The text never contains places, times or chat content. Besides the alerts (encounters, contacts, chats, group rides, help requests) we send the weekly summary “Your week” and, during the trial, a reminder before Moket Pro ends. Turn off single types in the app and all of them in your phone settings. We delete the token when you sign out.
Legal basis: Art. 6(1)(a) GDPR, § 25(1) TDDDG.
Moket Pro and purchases
For Moket Pro we store whether, since when and until when you are Pro and where it comes from (trial, subscription, code, gift). The trial starts when you sign up. On day 12 we send a push reminder if you allowed notifications.
Subscription: payment goes through Google Play (Google Ireland Ltd.). We never see payment details. When you buy, the app passes your internal Moket ID to Google so the subscription can be linked to your account. We store the purchase token, order number, status, expiry and whether it renews, and ask Google for the current status (Google Play Developer API, also for renewals, cancellations and refunds via real-time notifications).
Codes: we store who redeemed which code and when. Wrong attempts are kept for one hour, against guessing codes.
When you delete your account we delete this data. Google Play keeps billing records for the statutory periods.
Legal basis: Art. 6(1)(b) GDPR; abuse prevention Art. 6(1)(f) GDPR.
Reports and moderation
You can report riders, content or creator links. We store reporter, reported user, reason, description and status. The reported user is not told who reported. To review, we may look at the reported content, for chats the reported conversation. Reports and actions are kept up to 12 months after closing, at the latest until account deletion. If an account is deleted while suspended, we keep only an encrypted fingerprint (hash) of its email until the suspension ends, at most 12 months, so the suspension also applies to a new account with the same email.
Legal basis: Art. 6(1)(f) GDPR; Art. 6(1)(c) GDPR with Art. 16 and 17 DSA.
Services the app calls directly
These providers see your IP address and the data listed:
- Apple Maps (iPhone) or Google Maps SDK (Android, Google Ireland Ltd.): only in test versions without the OpenFreeMap map; map area and device data under their terms.
- System geocoder (Apple/Google): address search; search text or coordinates.
- Bright Sky (brightsky.dev, DWD data): temperature; position rounded to about 5 km, at most every 10 minutes.
- maps.moket.app (our web space at IONOS SE, Germany): speed limit files from OpenStreetMap; area of about 10 km, then kept on the phone.
- Overpass API (overpass.private.coffee, Private.coffee, Austrian non-profit association; OpenStreetMap data): speed limit, only when the file is missing; rounded area of about 1 km.
- OpenFreeMap (tiles.openfreemap.org): all maps in the app (ride, summary, meeting points, private zones: map tiles, fonts, symbols) and roads of the area to keep the arrow and line on the road, in tiles of about 2 km; if it does not respond, Overpass API (Private.coffee) for the same tile. What is sent: the tiles requested and the app identifier (name, version, operating system), not your exact position or route. Data © OpenStreetMap contributors (ODbL).
- Expo Updates (650 Industries, Inc., USA): app updates; app version, platform.
- Sentry (Functional Software Inc., servers in the EU, Frankfurt): error reports when the app crashes or hits an error; error message, app version, device model, operating system, without name, email, location or messages; kept 90 days. Legal basis: Art. 6(1)(f) GDPR (a stable app).
- Aptabase (servers in Germany): anonymous usage statistics; individual actions (e.g. “ride saved”) with broad bands (e.g. ride length “30-90 min”), without device ID, cookies, location, routes, names, emails or messages. Legal basis: Art. 6(1)(f) GDPR (improving the app). Turn off in Settings > Encounters and followers > Anonymous statistics.
Camera and photo library are used only when you take or pick a profile photo or a biker spot photo yourself (it is uploaded only after you confirm) and to scan QR codes; a QR image is neither stored nor sent. The calendar is used only when you tap “Add to calendar”: the app writes the group ride into your phone’s calendar and never reads your events. Motion sensors only estimate lean angle on the phone.
Legal basis: Art. 6(1)(b) GDPR; updates Art. 6(1)(f) GDPR.
Hosting and processors
Database and sign-in are run for us by Supabase Inc. (USA) on servers in Frankfurt am Main. Other processors: Brevo (email, France), Amazon Web Services EMEA SARL (profile photo, club logo and biker spot photo checks with Amazon Rekognition, Luxembourg; servers in Frankfurt am Main), Expo (push and updates, USA), GitHub Inc. (USA, encrypted nightly backups). All are bound by a contract under Art. 28 GDPR. For any transfer to the USA we rely on the EU-US Data Privacy Framework where the provider is certified, otherwise on EU standard contractual clauses (Art. 46(2)(c) GDPR).
Backups are encrypted, contain no raw GPS points and are deleted after 30 days.
Website
The website moket.app is hosted by IONOS SE, Elgendorfer Str. 57, 56410 Montabaur, Germany; the servers are in data centres in the EU. A data processing agreement under Art. 28 GDPR is in place with IONOS. The former address moket.app only redirects to moket.app. On each visit the server logs your IP address, date and time, the page requested, your browser (user agent) and the referring page. This serves the security and operation of the site; logs are deleted after 7 days.
The website sets no cookies, uses no tracking or analytics and loads no external fonts or scripts. The invite pages (/c/ and /add/) read the code only in your browser to open the app. Shared ride pages (/e/…) load the title, type, date, duration and organiser name directly from our Supabase server in Frankfurt am Main (see “Hosting and processors”); to do so Supabase technically receives your IP address. These pages never show the meeting point or the riders.
The “Join the beta” button is a plain link to the Moket WhatsApp community. WhatsApp (WhatsApp Ireland Ltd.) only opens if you tap it; from then on its own privacy notice applies. The website itself sends no data to WhatsApp.
Legal basis: Art. 6(1)(f) GDPR.
Retention
- Raw GPS points and tracks: 72 hours after the ride
- Sign-in code: a few minutes
- Contact requests: visible 7 days, kept until account deletion
- Encounters, contacts, chats: until one participant deletes the account
- Road reports: visible 1–4 hours, deleted no later than 24 hours after expiry
- News from people you follow: 30 days
- Profile, bike, rides (start/end), group rides: until account deletion
- Moket Pro (status, subscription data, redeemed codes): until account deletion; wrong code attempts: 1 hour
- Alerts for new group rides (rounded area, radius): until you turn them off or delete your account; alerts sent: 7 days
- Place medals (passes, meeting points, areas of about 20 × 40 km): until account deletion
- Reports and moderation: up to 12 months after closing, at the latest until account deletion; fingerprint of the email of an account deleted while suspended: until the suspension ends, at most 12 months
- Profile photo and cover: until you replace or remove it or delete your account; unreviewed photo: at most 7 days; automatic check result: 2 days
- Biker spot photos: until you remove or replace it, the place is deleted or you delete your account
- Poll votes: up to 3 months after the poll closes, at the latest until account deletion
- Backups: 30 days
When you delete your account (Profile > Settings > Delete account) we delete all linked data immediately, in backups within 30 days.
Your rights
You have the right of access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction (Art. 18), portability (Art. 20) and to object to processing based on legitimate interest (Art. 21 GDPR). You can withdraw consent at any time for the future.
Edit profile and bike in the app; delete your account under Profile > Settings. You get a copy of your data by emailing info@moket.app. Without the app you can request deletion at https://moket.app/delete-account.
You can complain to a supervisory authority, e.g. the Bavarian Data Protection Authority (BayLDA), Promenade 18, 91522 Ansbach, Germany.
Minimum age, ads, changes
Moket is for adults (18+) only. We sell no data, use no ad SDKs or tracking and build no ad profiles; the only statistics are the anonymous usage statistics (Aptabase), which you can switch off. We announce material changes to this policy in the app.