Legal

Privacy Policy

Last updated: November 13, 2026

This version takes effect on November 20, 2026. What's changing: ODDS Running is opening in more cities, starting with Istanbul. The app and website show the city you're in, or one you choose. If you choose a city in the app, we save which city you chose (not your location) on your account so your other devices open on it, and if you tap "Notify me" on a city we haven't opened yet, we keep that request so we can tell you when it opens. It also carries the version that takes effect on November 3, 2026: ODDS Running is coming to Android. The Android app draws its maps with Google Maps and looks up place names with Google's geocoding service on your phone, so Google sees the map area shown and the point or text being looked up. It also carries the changes announced for October 30: friend codes, a QR code on your profile that other runners scan to add you (anyone who scans it sees your display name, username and profile photo, whatever your Profile visibility, and you can reset it at any time); run-partner posts can say what you're doing after the run; and we now say plainly that the apps use one strictly necessary sign-in cookie. It also carries the changes announced for October 28: the app and website can show clubs, runs and run requests near you, using an approximate location (rounded to about 1 km) or an area you choose, which we don't store; the website can use your IP address to guess your city; run club leaders can sign their club up on the website; and an optional, off-by-default saved home area lets us tell you about new clubs nearby. Until October 28, 2026, the September 22, 2026 version applies; from October 28 until October 30, the October 28, 2026 version; from October 30 until November 3, the October 30, 2026 version; and from November 3 until November 20, the November 3, 2026 version; ask privacy@oddsrunning.com for a copy.

1. Who we are

ODDS Running is a social product for run clubs, operated by Goc Ventures Group LLC, a Florida limited liability company. The service consists of an iOS app, an Android app, this marketing website, and a backend hosted on InsForge. For EU and UK users this entity is the data controller under GDPR / UK GDPR.

2. What we collect — account & identity

Email address (required), password (hashed by InsForge, never stored in plaintext), and if you sign in with Apple or Google, the stable identifier and email returned by that provider. Optional profile fields: username, display name, bio, Instagram handle, gender, avatar image, and the optional Running fields — a running goal, your next race, a Strava handle, and a home club. Optional fields can be removed at any time in Settings. Profile visibility is a setting you control in Settings → Privacy: Public (anyone can see your activity, runs, and badges), Friends (the default — only your friends can), or Private (no one can). Whatever the setting, your display name, username and profile photo are visible to every signed-in runner — in Search, in a run's going list, and at the top of your profile — so people can find you and send a friend request; the setting decides what is behind them. It also governs what run club organizers see about you (section 9). Search and “Runners you may know”: signed-in runners can find any profile — Public, Friends or Private — by username or display name in Search, and may see it suggested under “Runners you may know”. Before you're friends they see a card — your display name, username, profile photo, and the clubs you follow; on a Friends or Private profile your activity, runs, run partner posts and badges stay hidden. Runners you've blocked (or who blocked you) never see you there. Suggestions are ranked only on things the app already shows: clubs you both follow and how many friends you have in common — never on which runs you went to. Turn off Settings → Privacy → Suggest me to other runners to stay out of suggestions while remaining findable by name; swiping a suggestion away hides that runner from your own list. Your friends list: on a Public profile, any signed-in runner can open your friends list (display name, username and profile photo of each friend); on a Friends or Private profile, a runner who isn't your friend sees only the friends you have in common, and your friends see the full list. Blocked runners (either way) never see it and are left out of lists they view. To keep your friends list to your friends, set Profile visibility to Friends. Friend code: the QR code under the QR button on your profile, which other runners scan to add you. Anyone who scans it, or opens its link, sees your display name, username and profile photo, whatever your Profile visibility setting — you're the one showing it; nothing else about your profile is revealed by the code. Scanning sends you a friend request that you still accept or ignore. You can reset your code at any time (My code → Reset code), and the old code stops working immediately. To add someone, you can scan their code with your phone's camera app or with Scan a friend's bib in My code. On iPhone and Android, that screen uses your camera only while it's open: the picture is read on your phone by the app itself, with no outside scanning service, isn't uploaded or stored, and only the friend code it finds is sent to us, to send the request. Consent record: when you create an account, and each time you accept an updated version of the Terms or this Policy, we record the timestamp and the document version you accepted plus an append-only history entry (version, when you acted, when our server recorded it, which screen it came from, and the app version and OS that rendered it). We keep a copy of every published version of both documents so the text you agreed to can be reproduced. The history is kept for 5 years after account deletion. Email list preferences: two optional marketing lists (weekly runs digest; ODDS news & updates), both off by default, each with its own opt-in and opt-out timestamps.

3. What we collect — location

Two precisions, both foreground only. Exact latitude and longitude only when you create an event, pick a meeting point on the map when posting a run partner request, or check in to a run with your location. Approximate location, rounded to about 1 km, for showing what's near you. We do not request 'always' permission and we do not run background location. Showing what's near you (app): if you allow location, your phone rounds a rough reading to about 1 km before anything uses it. Or you can choose an area by name instead. The app sends that rounded point (or, on the map, the area on your screen) and a distance to our server with each request to load the feed, the map and open run requests near you. The server uses it to find what's nearby and doesn't store it or link it to your account. The rounded point, chosen area and distance setting are kept on your phone. Place-name suggestions come from Apple's MapKit: what you type is sent to Apple under Apple's privacy policy, and we receive only the place you pick. Distances to run requests are measured from each post's meeting point rounded to about 1 km and rounded to 100 m. Showing clubs near you (website): oddsrunning.com uses a city-level location our host Vercel derives from your IP address on each request, and doesn't store it. If you tap Use my location, your browser asks first and the page puts your location, rounded to about 1 km, in the page address (for example ?near=25.80,-80.20). It isn't saved in a cookie, in browser storage or to an account, but it can appear in our host's request logs (about 30 days), and anyone you share the link with sees that rough area. Saved home area (optional, off by default): only if you choose Save my home area (we ask first, and you can say no), we store an approximate area around where you are, rounded so it never points to your home or street, together with your time zone. We use it to tell you about runs and clubs near you at a sensible local time and to order your weekly digest, never show it to anyone, and delete it when you remove it in Settings → Notifications or delete your account. Coordinates are stored on events you create and on run-partner posts (the meeting point you drop on the map); approximate 'near you' locations are transient, and a run-partner post's coordinate is deleted when the post auto-expires after 4 hours or you cancel it. Checking in to a run: a run club chooses which ways its runners can check in, and can change them at any time — holding your phone to the club's NFC sticker, confirming you're at the meeting point with your location, a one-tap check-in, or the host marking you present. We record that you checked in, when, which way was used, and who did it (you, or the host who marked you present), and we keep a history of check-ins and undone check-ins for each run. Sticker check-in reads only the sticker's link and serial number; no location is read. Location check-in happens only when you tap it, and only at clubs that have turned it on: your phone reads your location once and sends it to our server, which works out how far you are from the run's meeting point. We keep only that distance and how accurate your phone said the reading was. Your coordinates are discarded straight away and never stored, logged, or shown to anyone. We also check whether your phone reports the reading as simulated. Cities: the app and this website are organised by city (Miami, Istanbul, …). The city you see is worked out from the same approximate location — the city you're in, or else the nearest one — or it's the city you choose. Choosing a city in the app saves which city you chose (not a location) on your account so your other devices open on it; choosing "Use my location" clears it. This website takes the city from the page address (for example /istanbul) or a guess from your IP address, and stores nothing. If you tap "Notify me" on a city we haven't opened yet, we record that request (your account and the city) so we can tell you when it opens.

4. What we collect — device data

Push notification token (APNs on iOS, FCM on Android) so we can send notifications you opted into — run reminders (including a safety tip before a run you posted or joined, and a notice when a run you RSVP'd to is canceled or back on), vibe checks on your event, friend requests, announcements from clubs you follow or run with, badges you earn, and a heads-up when your weekly check-in streak ends that Sunday; each category has its own toggle in Settings → Notifications. Notification engagement: for each push we send you, we record whether it was sent or skipped (and why), whether it reached your phone, and whether you opened it, swiped it away, or turned that category off soon after, with your device platform and app version. We use it only to decide what is worth sending and when; it's linked to your account, stays with us (no third-party analytics), and is kept for 13 months. Club organizers see only totals for their own club's sends, never who received or opened them. A random per-install UUID stored locally — this is not Apple's IDFA or Google's AAID; we use it only to dedupe anonymous search analytics. App and OS version with API requests for bug fixes. IP and User-Agent on public web forms (event proposals, waitlist) for rate-limit and abuse prevention. We do not collect IDFA / AAID and we do not show an App Tracking Transparency prompt because we have nothing to track across apps.

5. What we collect — your content

Events, RSVPs and check-ins, vibe checks (comments and emoji reactions), club ratings, direct messages, friend relationships, badges you earn, event proposals, and waitlist signups. If a club's organizer cancels a run, the reason (weather, safety or other) and any short note they add are shown on that run to anyone who can see it, including after its start time. When you RSVP "going" to an event, your display name, username and profile photo (if you set one) are shown to other signed-in ODDS users on that event — friends first, then everyone else — whatever your Profile visibility (Settings → Privacy). Tapping your name opens your profile, where that setting still decides whether they see your runs, run partner posts, badges and activity. Your friends also see that you're going in their Activity feed; people who aren't your friends never do. Signed-out visitors see you only if your profile is Public. The first time you tap "I'm going" the app tells you who will see it, and you can change the setting before anything is saved. Separately, the organizers of the club hosting that run see your RSVP and check-in on their roster regardless of this setting — exactly what they see is in section 9. Club ratings: If you've checked in at one of a club's runs, you can rate the club: 1–5 stars, tags from a fixed list, and an optional note to its organizers (up to 280 characters). We store the rating against your account so you can edit it. Other runners see only the club's totals — the average, how many ratings it has, and the most-picked positive tags — and only once the club has 5 ratings. The club's organizers see those totals, every tag count, and the notes, without your name or which run it was about, grouped by week and shown only after that week ends. In a small club, an organizer may still be able to guess who wrote a note. Direct messages are stored on our servers and are not end-to-end encrypted — treat them as private email, not as a sealed letter. Club sign-ups: if you use Set up your club on the website, we collect your name and email, the club's name, area and Instagram handle, its weekly run (name, day, time, meeting point, distances, pace groups, whether walkers are welcome), how you'd like runners to check in, how many check-in cards you want, and any note, plus your IP and User-Agent for abuse prevention. We use it to confirm you run the club (for example by messaging the club's Instagram account), to set it up and give you organizer access, and to arrange check-in cards. We ask for a postal address by email only if a card needs one. Reports about club and run listings: if you use Report wrong info on a club or run, we collect which club (and run) it's about, the reason you pick, any note you add, whether you say you showed up, and your account, so we can follow up and tell you when it's fixed. The club doesn't see your report or who sent it. Run confirmations: after a run you RSVP'd "going" to, the app may ask whether it happened as listed; we keep your yes or no with your account and the run, and other runners see only a club-level line such as "Runners confirmed a run 3 days ago", never who answered. Run edit history: if you lead a run club (or are one of our admins) and create, edit or delete one of its runs, we record your user ID, when, which fields changed (for example the start time or the photo), and their values before and after. Admins and that club's organizers can see it, so a club can tell who moved or changed a run.

6. What we do NOT collect

No Google Analytics, Meta Pixel, Sentry, PostHog, Mixpanel, Amplitude, Segment, or Vercel Analytics. No advertising SDKs, retargeting pixels, or data brokers. No access to your contacts, mic, SMS, or camera roll, and we never read your calendar. After you RSVP to a run you can choose Add to Calendar; it's optional. On iPhone the app asks for add-only calendar access, which can't see the events already in your calendar (if you say no, the system's Add Event screen opens and you confirm there); on Android your calendar app opens and you confirm there. Either way it adds only that run, with a reminder before it starts, and nothing about your calendar is sent to us. The app asks for camera access (on iPhone and Android) only when you open Scan a friend's bib, and only to read a friend code. You can pick photos yourself (your avatar, a club photo, or a photo you send in a message), or a photo or video to put behind a run's share story, and the app receives only the ones you pick. A story background is put together on your phone and never uploaded to us; it only goes where you send the finished story. If you lead a run club and tap Save Image on its QR code, or tap Save on a run's share story, the app asks to add those images or videos to Photos. In both cases it can't see the rest of your library. No background or 'always' location. No Apple Health, HealthKit, Google Fit, Health Connect, or any other health or fitness data — the app never asks for that permission. No IDFA / AAID. No sale of personal information, ever.

7. How we use your data

Operating the service (sign-in, RSVPs, feed, messaging) on the basis of our contract with you. Letting runners find each other by name and suggesting “Runners you may know” (username, display name, photo, club follows, friend counts — never RSVPs or check-ins), also on the basis of our contract with you, limited by Suggest me to other runners. Showing a runner's friends list on their profile (everyone on a Public profile, friends in common otherwise), on the basis of our contract with you, limited by Profile visibility. Sending transactional email (verification, reset, RSVP confirmation) as part of the contract. Showing who's going to an event (display name, username and profile photo of "going" RSVPs, friends first) as part of the contract; what's behind the name is limited by your Profile visibility setting (default: Friends). Giving a club's organizers the roster, check-ins, and attendance history for their own runs (section 9) as part of the contract — the club's run is the thing you RSVP'd to. Sending push notifications you opted into, including announcements from clubs you follow or run with (Settings → Notifications → Club announcements). Showing clubs, runs and run requests near you, from an approximate location you allow or an area you choose, neither of which we store. Showing clubs near you on the website from a city-level location derived from your IP, as a legitimate interest (or from Use my location, with your permission). If you turn on a saved home area, telling you about new clubs and runs near you, on the basis of your consent. If you opt in to the weekly runs digest, picking the one run it leads with from the clubs you follow, your friends' RSVPs, the clubs you've checked in at and how many people are going (or the biggest run near your saved home area, if you set one), on the basis of your consent — nothing new is collected for it. Reviewing a club sign-up and setting the club up, at your request. Recording that you checked in to a run, how, who did it, and a history of check-ins and undone check-ins, as part of the contract. Confirming you're at the meeting point when you choose to check in with your location — read once at your tap and reduced on our server to a distance and accuracy — as part of the contract; you can use another way the club offers instead. Keeping club and run listings accurate — reviewing reports about a listing, fixing it, telling the person who reported it, and showing when runners last confirmed a club's run — as a legitimate interest in a catalog runners can rely on. Preventing abuse on public forms as a legitimate interest. We do not make automated decisions that produce legal or similarly significant effects on you.

8. Who we share with

Infrastructure providers acting on our instructions only: InsForge (backend host — auth, database, file storage), Vercel (web hosting; sees request logs, which can include a page address holding a location rounded to about 1 km if you tapped Use my location, and derives an approximate location from your IP), Apple Maps / MapKit (map display and place-name search in the app; sees the map area shown and the text you type when choosing an area), Google Maps Platform (map display and place lookup in the Android app; sees the map area shown, the point or text being looked up, and request data such as your IP address), Resend (email delivery — account notices and the marketing lists you opt into; sees your email address, message content and delivery events), Apple APNs (iOS push delivery), Google FCM (Android push delivery), and Apple / Google as OAuth identity providers if you choose them. Run club organizers are a separate case, described in section 9. We do not share with advertisers, ad networks, data brokers, or attribution providers. We may disclose data when required by law (subpoena, court order); we will not disclose more than necessary and will notify you unless legally prohibited.

9. Run club organizers

Run clubs on ODDS Running are run by independent organizers — not our employees, and not processors acting on our instructions. When you interact with a club, its organizers see some of your data through the organizer tools in the app and the web console. This is the complete list. For a club run you RSVP to (whatever your Profile visibility setting): your username and profile photo, your RSVP status (going / thinking / not going) and when you set it, whether and when you checked in and how (sticker, location, one-tap, or host) — for a host check-in, which host; for a location check-in, your distance from the meeting point rounded to 10 m — the history of check-ins and undone check-ins for that run, how many of that club's previous runs you RSVP'd to and checked in at, and whether this is your first run with them. In the club's people list (their view of everyone who has run with the club or follows it): the same identity fields, your total runs (and how many of them were checked in each way), RSVPs, and no-shows with that club, when you first and last ran with them, whether you follow them, and a label we compute from that history — newcomer (first run within 30 days), regular (3+ check-ins in the last 60 days), lapsed (2+ RSVPs and nothing in 45 days), follower (follows, never RSVP'd), or occasional. The web console lets an organizer download this list as a CSV file. Only if your Profile visibility is Public: the running goal and home club you entered in Settings → Running; for Friends and Private profiles these are hidden from organizers. If your Profile visibility is Private: you are left out of the club's people list, its CSV, and its history-based announcement audiences (regulars, lapsed, everyone); you still appear on the roster of any run you RSVP to, and you still receive announcements sent to a run you RSVP'd to or a club you follow unless you turn off Club announcements in Settings → Notifications. From club ratings: the club's average star rating and number of ratings, how many ratings picked each tag, and the notes runners left for them — never who rated or wrote what, or which run it was about. Organizers never see your email address, phone number, location (a location check-in shows them only your rounded distance from their own meeting point), direct messages, or activity with other clubs. Organizers may use this only to run their club and communicate with their runners on ODDS Running, and are bound by Terms section 7. Deleting your account removes you from every organizer view, but not from a CSV an organizer already downloaded — that copy is theirs to delete under the same Terms. Report misuse to privacy@oddsrunning.com.

10. International transfers

Data is stored and processed in the United States. If you access the service from the EU, UK, or elsewhere outside the US, your data is transferred to the US. We rely on the EU–US Data Privacy Framework (where applicable to our processors) and Standard Contractual Clauses with processors that have not self-certified.

11. Retention

Account, profile, events, RSVPs, check-ins and check-in history, messages, friends, vibe checks, club ratings, listing reports and run confirmations are retained while your account is active and deleted when you delete your account. A check-in history entry naming a host who later deletes their account keeps the entry but drops the host. Activity pings auto-expire after 4 hours. Anonymous search logs aggregate into a 7-day rolling view; raw rows are kept up to 90 days for abuse detection. Push tokens are replaced on every device re-registration. Event-proposal and club sign-up IP and User-Agent are kept 90 days for rate-limit then nulled; the submission is kept for admin audit. Approximate 'near you' locations are not stored by us (the app keeps your last rounded location, chosen area and distance setting on your phone; the website's rounded location lives only in the page address and our host's rolling request logs). A saved home area is kept until you turn the setting off or delete your account. Run edit history is kept with the run's record; the editor's user ID is cleared when they delete their account. Server logs roll on a ~30-day window. Backups are purged on the same cadence after account deletion (excluding any rolling backup window — typically ≤30 days residual). Organizer CSV exports (section 9) leave our systems when downloaded; the organizer must delete them when they stop leading the club or when we ask. Your chosen city and any "Notify me" requests for a city are kept until you change them or delete your account; a "Notify me" request can also be removed by emailing us.

12. Your rights

You have the right to access, correct, delete, restrict, port, and object to processing of your data, and to withdraw consent at any time — revoke location or push permission in your device settings, or turn off any push category in Settings → Notifications. Account deletion is available in-app under Settings → Account → Delete account. Request other rights at privacy@oddsrunning.com. EU and UK users can lodge a complaint with their local supervisory authority — we'd appreciate the chance to address concerns directly first.

13. California (CCPA / CPRA)

Categories collected: identifiers (email, username, OAuth subject, device UUID, IP on web forms), customer records (profile fields), internet/network activity (search queries, request logs), geolocation (precise, only with foreground permission; for a location check-in we keep only the derived distance from the meeting point, not the coordinates; approximate location rounded to about 1 km to show what's near you, not stored; a saved approximate home area, never street-level, only if you turn it on — we treat all of it as sensitive), sensory data (avatar photos), and sensitive personal information (precise geolocation). We use sensitive PI strictly for the purposes in section 7 and do not infer characteristics about you. Disclosed for a business purpose to run club organizers (section 9): identifiers (username), customer records (profile photo; goal and home club if your profile is Public), and your RSVP, check-in (including how you checked in, which host checked you in, and for a location check-in your rounded distance from the meeting point), and follow activity with that club. No sale. No share for cross-context behavioral advertising. Rights honored at privacy@oddsrunning.com or via in-app account deletion. Authorized agents accepted with verified power-of-attorney.

14. Security

All traffic is TLS-encrypted in transit. Passwords are hashed by InsForge. Auth tokens are stored in iOS Keychain (hardware-backed where available) and Android EncryptedSharedPreferences. The database is encrypted at rest. Access to production data is restricted and logged. Direct messages are not end-to-end encrypted. No system is perfectly secure; if we become aware of a breach affecting your data we will notify you and the relevant supervisory authorities within the windows required by law (72 hours under GDPR).

15. Children

ODDS Running is for adults. You must be 18 or older to create an account. We do not knowingly collect data from anyone under 18. If we learn that we have, we delete it immediately. Parents and guardians who believe a minor has registered should contact privacy@oddsrunning.com.

16. Cookies

The marketing site sets no cookies, and a location you share with Use my location is kept only in the page address, not in a cookie or browser storage. We do not use analytics, advertising, or tracking cookies and we do not show a consent banner because there is nothing to consent to. The staff-only /admin area keeps its session token and UI preferences in localStorage; it is only set for signed-in staff. The apps use one strictly necessary, first-party cookie to keep you signed in. It carries a login refresh token between the app and our backend, and we use it only for that purpose, not for tracking or advertising. Other session state is kept in OS-secure storage. If you sign in with Google, Google may set its own cookies during that sign-in, under Google's privacy policy. Full inventory at /cookies.

17. Marketing email

Transactional email (verification codes, password resets, RSVP confirmations, event reminders you opted into) is sent on the basis of our contract with you. Marketing email is opt-in only, in two lists you control separately: the weekly runs digest and ODDS news & updates. The digest leads with one run picked for you, using the clubs you follow, the runs your friends are going to or interested in, the clubs you've checked in at and how many people are going, or, if none of those apply, the biggest run near your saved home area, if you set one. It names a friend only to you, and only a friend who is going to that run, which is what you'd see on the run's page in the app; it never names anyone else. If nothing fits, we don't send you a digest that week. Its I'm in and Maybe buttons open a confirmation page on our website: your RSVP is saved only when you confirm there, and the links stop working after 10 days. Every marketing email carries a one-click unsubscribe link scoped to that list, standard one-click unsubscribe headers, our postal address, and a line saying why you're receiving it. Opt-outs take effect immediately in our system and within 10 business days at the very latest; you can also toggle each list in Settings → Email. Service notices (a material change to these documents, account-deletion confirmation, security or breach notification) go to every account and cannot be unsubscribed from. We comply with the US CAN-SPAM Act, EU ePrivacy Directive, and Canada's CASL.

18. Changes to this policy

Every version of this Policy and the Terms is published with a version (its effective date), the date it was announced, and a plain-English summary of what changed. For material changes (new data category collected, new third party, new use that changes the legal basis) we publish the new version at least 30 days before it takes effect; during that window you'll see an in-app banner with the summary and we email it to the address on your account. When it takes effect, the app asks you to review and accept the new version before you continue, unless you've already accepted it: whenever the app asks you to accept a version, it also lists any newer version already announced, and accepting covers those too, as does creating an account. We record which version you accepted and when. If you don't accept, you can stop using ODDS and delete your account; the version you last accepted governs until then. We never treat continued use alone as acceptance. For non-material changes (clarifications, typo fixes, address updates, a rename) we update the 'Last updated' date above without changing the version. Past versions are available on request.

19. Contact

Privacy questions: privacy@oddsrunning.com. Postal: Goc Ventures Group LLC, 92 SW 3rd St Apt 2907, Miami, FL 33130, United States. DMCA notices: /dmca.