Rider Society Privacy Policy
Version: 2026-11-22-v12 · Effective: [PUBLICATION DATE]
This policy explains how Rider Society handles personal data in the Rider Society mobile app and on ridersociety.app, including the waitlist at ridersociety.app/join. It is written to meet the EU General Data Protection Regulation (GDPR) and similar laws. If you are in Türkiye, our Turkish notice under Law No. 6698 (KVKK) also applies and prevails: ridersociety.app/gizlilik.
Rider Society is for adults only. You must be 18 or older to use it.
1. Who we are
The controller is [FULL NAME], the individual who runs Rider Society, in Türkiye. Rider Society is not a company today.
Address: [ADDRESS]
Email: info@rider-society.com
EU representative (GDPR Art. 27): [EU REPRESENTATIVE, or: We have not yet appointed a representative in the EU.]
2. Summary
- We collect what the app needs to work: your account, a verified phone number, your profile, the rides you record, and your location only when you use location features.
- Live location is shared only with riders in a group ride session you joined, only while it runs. We never publish your precise or live location.
- No advertising, no analytics or tracking tools, no data sales, no speed or distance leaderboards.
- You can delete your account in the app at any time and ask for a copy of your data.
3. Data we collect
Waitlist (ridersociety.app/join)
- Name, email address and mobile number.
- Whether you join as a rider or club organiser; your province and district; optionally your Instagram handle and motorcycle make and model. Club organisers: club name, province and district, rough member-count band, club Instagram handle.
- Your declaration that you are 18 or older (no date of birth).
- The source tags in the link you came from (utm_source, utm_medium, utm_campaign).
- Optionally, a suggestion for the community and the app (free text, at most 1000 characters). Please do not include other people's names, phone numbers or other personal details.
- Language, time, the policy version shown and the boxes you ticked.
- IP address and request time.
App
- Account: if you sign in with Apple or Google, that account's identifier and your email address (possibly Apple's private relay address); your username and display name.
- Phone number: required and verified by SMS code on every profile. If you sign in by phone, it is also your sign-in. Codes are kept only while you verify.
- Profile: confirmation that you are 18 or older (your date of birth is checked on your phone and never sent to us); optionally your province and your motorcycle's make, model and year; your language.
- Ride recordings: the track of rides you record, start and end time, duration, distance and elevation gain. No speed.
- Live location during a group ride session you joined (section 6).
- SOS: your location, its accuracy and the time when you press SOS, and the ride session if any.
- Emergency contacts: name, phone number and relationship of up to three people you add (section 7).
- Clubs and group rides: memberships, roles, admission status, sessions you joined and when, which version of the Group Ride Terms you accepted and when, and records of any suspension or removal for unsafe riding, with its reason and any appeal.
- Academy: content you read and quiz results.
- Consent records: which version of which text you accepted, and when you gave or withdrew consent.
- Technical data: IP address, device and OS type, app version, request times in server logs.
- Push token: if you allow notifications, your phone's push notification token and its platform.
We do not ask for sensitive data such as health information. Please do not enter any in free-text fields.
4. Why we use it, and our legal bases (GDPR Art. 6)
| Purpose | Data | Legal basis |
|---|---|---|
| Keep the waitlist and plan the launch and first rides | Waitlist data | Legitimate interests, Art. 6(1)(f): knowing who is interested and where |
| Contact waitlist sign-ups one to one about joining, and organisers about setting up a club | Name, contact details, club details | Art. 6(1)(f); for a requested club set-up, Art. 6(1)(b) |
| Keep the community adults-only | Age declaration and confirmation | Art. 6(1)(b) in the app; Art. 6(1)(f) on the waitlist |
| Measure in aggregate which channels people come from | Source tags | Art. 6(1)(f) |
| Read and consider waitlist suggestions to improve the community and the app (not published, not shared under your name) | Suggestion text | Art. 6(1)(f) |
| Provide the app: account, profile, routes, solo ride recording and ride list, clubs, group rides, Academy, account deletion | Account, profile, ride, club and Academy data | Performance of our contract with you, Art. 6(1)(b) |
| Verify your phone, keep one account per person, secure your account, contact you about rides or safety incidents | Phone number, codes | Art. 6(1)(b) and Art. 6(1)(f) (preventing fake and duplicate accounts) |
| Share your live location with the participants of a group ride you join, and your location with that ride's leads and members when you press SOS | Live location, SOS location | Your consent, Art. 6(1)(a), asked separately and once, before your first group ride; withdrawable in Settings at any time. Where you cannot act, for example if you are unconscious during an SOS you started, also vital interests, Art. 6(1)(d) |
| Let the ride's leads and members reach your emergency contact during an SOS | Contact's name, phone, relationship | Art. 6(1)(f) (your and the contact's interest in your safety); Art. 6(1)(d) where you cannot act |
| Record your acceptance of the Group Ride Terms; suspend or remove group ride access for unsafe riding and handle appeals | Acceptance record, safety decisions | Art. 6(1)(b); Art. 6(1)(f) (other riders' safety, defending claims) |
| Send you a push notification when someone in a group ride you joined presses SOS (SOS alerts only for now; no names, location or emergency contacts in the notification, details load when you open the app) | Push token | Art. 6(1)(b). You can turn notifications off in your phone's settings; the app works without them |
| Email announcements | Name, email | Your consent, Art. 6(1)(a), only if you ticked the box on the waitlist |
| Prove we informed you and recorded your choices | Consent records | Legal obligation, Art. 6(1)(c), and Art. 6(1)(f) |
| Security, abuse prevention, fixing faults | Technical data | Art. 6(1)(f) |
| Answer your requests and lawful requests from authorities | Request data | Art. 6(1)(c) |
Where we rely on legitimate interests you can object (section 10). We make no decisions about you based solely on automated processing (Art. 22), and we do no profiling for advertising.
5. Who we share it with
- Other riders. Your live location, display name and username go to the participants of a group ride session you joined, while it runs. During an SOS, your location and your emergency contact's details go to that session's leads and members. Your profile card (username, display name, primary motorcycle) is visible to other signed-in riders. Your phone number, ride recordings and province are shown to nobody.
- Club staff. Owners and Marshals of a club you belong to see your membership and role there.
- Service providers acting on our instructions under data processing terms (Art. 28):
- Supabase, Inc.: database, authentication, storage, live location delivery; data stored in Dublin, Ireland.
- Hetzner Online GmbH: servers for the site and API, [HETZNER LOCATION].
- Mapbox, Inc., USA: in-app maps; receives your IP address and device details when map tiles load. Mapbox's map-improvement telemetry is switched off.
- [SMS PROVIDER], Türkiye: delivering SMS verification codes.
- [MAILBOX PROVIDER]: our info@rider-society.com mailbox.
- Apple Inc. (Apple Push Notification service, USA; iPhone) and Google LLC (Firebase Cloud Messaging, USA; Android): delivering SOS notifications; they receive your push token and a short notification text with no name or location.
- An email delivery provider, once announcement emails start, for people who agreed to them.
- Apple and Google, if you choose their sign-in, as independent controllers under their own privacy policies.
- Authorities, only where the law requires.
We do not sell your data or share it for advertising.
6. Location
- Map. While the app is open, your location shows your position on the map. It stays on your phone.
- Solo ride recording. Starts when you tap Start and stops when you finish. While it runs, location is also collected when the app is closed or not in use, and your phone shows an indicator or a persistent notification. Only you see the track.
- Group rides. Your live location is sent only during a ride session you joined that is running, only to its participants, and stops when the session ends or you leave. It is not stored; any "last known location" is deleted when the session ends, within 12 hours at most.
- SOS. Only when you press SOS is your location shared with your current ride's leads and members. The push notification they receive does not contain it; they see it in the app.
- We never ask for "Always" location and never collect location in the background unless you started a recording or a session.
- You can refuse location permission and still use routes, your ride list and the Academy. Your consent for group rides and SOS is asked once, before your first group ride. You can withdraw permission in your phone's settings and that consent in the app's Settings at any time.
SOS is not an emergency service and does not contact emergency services. In an emergency, call your local emergency number (112 in Türkiye and the EU).
7. Emergency contacts
When you add an emergency contact you give us their details. Tell them first and share this policy with them; the app asks you to confirm this.
If you are someone's emergency contact: your name, phone number and relationship are stored in that rider's account and shown only when they press SOS during a group ride, to that ride's leads and members, so they can reach you. We do not message you. Your details are deleted when the rider removes you or deletes their account. You can ask us to remove them, or exercise any right in section 10, at info@rider-society.com.
8. International transfers
The controller is in Türkiye. Our database and servers are in the European Union, our map and push notification providers are in the USA and our SMS provider is in Türkiye. Türkiye and the USA are not covered by an EU adequacy decision for this processing.
- Where the GDPR applies to you, data you send us is held in the EU by our processors, and is accessed from Türkiye by the controller. Transfers out of the EU or EEA rely on the European Commission's Standard Contractual Clauses (Art. 46(2)(c)) in our providers' data processing terms, or on the EU-US Data Privacy Framework where the US provider is certified. Ask us for a copy of the safeguards at info@rider-society.com.
- Data of people in Türkiye leaves Türkiye under the standard contracts required by KVKK Art. 9, as described in our Turkish notice.
9. How long we keep it
| Data | Period |
|---|---|
| Waitlist signup, including any suggestion | 12 months after the app's public release on the App Store and Google Play; at most 24 months after signup if it is not released |
| Account, profile, phone, rides, clubs, Academy results, emergency contacts, consent and terms-acceptance records, safety decisions | Until you delete your account; rides and contacts can be deleted sooner |
| Live location | Not stored; any last known location deleted when the session ends, within 12 hours at most |
| SOS location | 30 days after the SOS closes; the SOS record without location, 1 year |
| SMS codes | Only while you verify |
| Push token | Deleted on sign-out, account deletion or uninstall (when the notification service reports it invalid), and after 90 days unused |
| Server logs (with IP address) | At most 30 days |
| Backups | Deleted data expires from backups within [BACKUP DAYS] days |
| Record of email consent | For the period Turkish law requires after the consent ends |
| Privacy requests and our replies | 3 years |
10. Your rights
Under the GDPR you have the right to access your data (Art. 15), correct it (Art. 16), erase it (Art. 17), restrict its processing (Art. 18), receive it in a portable format (Art. 20), and object to processing based on legitimate interests (Art. 21). You can withdraw consent at any time without affecting earlier processing (Art. 7(3)).
- Delete your account: in the app, Settings, Delete account. Deletion starts at once and removes your data immediately, except server logs and backups, which expire within the periods in section 9. You can also ask at ridersociety.app/delete-account or by email.
- Get a copy of your data: Settings, Request my data, or email us. You get a JSON file, with GPX files for ride tracks.
- Anything else: email info@rider-society.com, preferably from the address on your account.
We answer within one month (Art. 12(3)); if a request is complex we may extend this by up to two more months and will tell you why. Requests are free unless manifestly unfounded or excessive.
You can complain to the data protection authority where you live or work, or where you think the law was broken (Art. 77). In Türkiye this is the Personal Data Protection Board (KVKK Art. 14).
11. Security
Data is encrypted in transit (TLS). Access to the database is restricted by row-level security so each rider reaches only what they are allowed to. No system is perfectly secure; if a breach is likely to put you at high risk, we will tell you without undue delay.
12. Changes
We will update the version and effective date when this policy changes, and tell you in the app before a change that adds a purpose or needs your consent.
13. Contact
info@rider-society.com · [ADDRESS]