Privacy Policy

Information we collect

We collect only what the app needs to work. It falls into three groups.

What you give us

• Account: your email address and a password. The password is stored only in scrambled (hashed) form; we never see it.
• Profile and settings: a display name (it starts as the first part of your email address, and you can change it), your home location (a ZIP code you type, or your phone's location at the moment you choose "use my location"), your time zone, search radius, alert preferences, and the sports, distances and states you pick for race alerts.
• Your races and activity: the races you watch, whether you've registered, dates you confirm yourself, race results, times and notes, and training plans.
• Registration profile (optional): if you choose to save one, the details race sign-up forms usually ask for: your name, date of birth, gender, phone number, mailing address, emergency contact (name, phone and relationship) and shirt size. You can leave any of it blank. This is sensitive, so it is kept separate from the rest and used only as described below.
• Photos: medal photos and photos you attach to a race result.
• Things you send us: race reports, races you add, feature suggestions, and emails to support.

What is collected automatically

• Device and app details: a push notification token (if you turn on notifications), your device model, iOS version and the app version.
• Usage: which screens you open, when you sign in, and actions such as watching a race, using filters or sorting, and tapping a registration link.
• Crash and error reports: when the app hits a problem, a report with the device and app details, what the app was doing, and your account ID (a random number, not your name or email). Some reports also carry occasional performance timings. It never includes your name, email or password.
• Connection details: your IP address and basic request details whenever the app contacts our servers. The same happens when the app checks for app updates (Expo's update service sees your IP address and the app version), loads a race's logo from the race's own site or its registration platform, or shows a map (Apple Maps).
• "Near me" location: if you tap Near me, the app reads your phone's location once, only while the app is open. It's used on your phone to sort races and is not sent to be stored. We never use background location and keep no location history.

What we get from others

Apple and RevenueCat tell us whether your subscription is active, which plan, and when it renews or ends. We never receive your card or payment details. We don't collect information about you from any other source, and we never read your accounts on other sites.

Our website's download link (bibregistry.com/get) counts how many times each link was opened, as a total per day and per campaign name (for example "linkedin"). It stores no IP address, cookie or other identifier.

Camera, photos, location, notifications and calendar are all optional. The app asks only when you use a feature that needs one, can only see the photos you choose, and you can turn any of them off in your phone's Settings.

How we use it

• To run BIB: show races, send the alerts you asked for, sort races by distance, and keep your results, photos, plans and watched races.
• To email you about your account: sign-up confirmation and password reset, and replies to your support messages. We don't send marketing email.
• To improve and fix the app: usage records and crash reports show us which features people use and where bugs are.
• To save you typing: your registration profile is shown only to you, so you can copy or pre-fill the details when you sign up for a race. BIB does not send it to any race website or anyone else, and does not submit registrations for you.
• To manage your subscription: unlock the features you've paid for.
• To keep the service safe: prevent abuse and investigate problems.

We don't use your information for advertising, profiling or automated decisions about you, and we don't sell it.

How we share it

We share information only as described here.

• Service providers that process it for us and may not use it for their own purposes: Supabase (hosts our database, sign-in, file storage and servers), Resend (delivers account emails, so it sees your email address and the message), Expo and Apple (deliver push notifications, so they see the alert text), Sentry (receives crash reports), and RevenueCat (manages subscriptions by reading your purchase status from Apple).
• Apple also processes payments for App Store purchases, and its location service on your phone turns a ZIP code or coordinates into a place name, under Apple's own privacy policy.
• Your registration profile is not shared. It is not given to race websites, advertisers or other users, and we don't use it for anything but showing it back to you. If you copy it into a race's sign-up form, that is your choice and that site's own privacy policy applies.
• Race registration sites. When you tap a registration link, you go to that race's own site (for example RunSignup). What you do there is between you and them, under their privacy policy.
• Other BIB users. Your results, photos, plans and watch list are private to you. The one exception: if you add a race that isn't in BIB yet, its details (name, place, date, website) become a listing other users can see. It isn't labeled with your name or email.
• Legal reasons. We may disclose information if the law requires it or to protect people's safety or our rights.
• If BIB changes hands. If BIB is ever sold or transferred, your information would go with it, and this policy would keep applying until you're told otherwise.

Affiliate links. Registration links to RunSignup carry an identifier that identifies BIB, not you. If you register within 30 days of tapping one, RunSignup pays BIB a small commission at no cost to you. We send RunSignup no personal information about you, though RunSignup may set its own cookies on its site.

We don't sell or rent your personal information, and we don't share it with advertisers.

Where and how we store it

Your information is stored on servers in the United States (Supabase, in Amazon Web Services' Oregon region). It's encrypted when it travels between your phone and our servers, and each account's data is protected by access rules so other users can't read it. Your registration profile is protected by its own access rule that lets only your signed-in account read it; the app's reports, analytics and background jobs don't read it. Your photos are stored privately and only you can open them. Access to the underlying data is limited to the person who runs BIB. No system is perfectly secure, but we take these steps to protect what you give us.

Some things stay only on your phone: your appearance choices (light or dark mode, seasonal themes), a saved copy of the race list so the app opens quickly and works on a weak connection, the home-screen widget's next-race details, and, if you choose to add race dates to your calendar, the calendar events themselves (we save only a reference ID so we can update or remove them).

How long we keep it

• Your account and what you add (profile, registration profile, watches, results, plans, photos, alert history, suggestions): until you delete it or delete your account.
• When you delete your account (Settings → Account → Delete my account), all of that is permanently removed from our live systems right away, along with your device tokens. This can't be undone.
• Usage records: kept for 12 months, then deleted. After you delete your account, any remaining records are no longer linked to you.
• Race reports you sent: kept after you delete your account, with the link to you removed, so we can still fix the listing.
• Crash and error reports: up to 90 days (set by Sentry).
• Connection logs, including IP addresses: about 1 day (kept by our hosting provider).
• Account email delivery records: up to 30 days (kept by Resend).
• Backups: we keep private backups of our database for recovery and delete them after 30 days, so deleted data can remain in a backup for up to that long. Backups include your account record (your email and your password in scrambled form) and your photos, but not your registration profile.
• Purchase records: Apple and RevenueCat keep their own records under their own policies.
• On your phone: until you remove the app or clear its data.

Your choices and rights

• Edit or clear your profile and home location any time in Settings.
• Unwatch races, change alert preferences, or turn race alerts off any time.
• Turn off notifications, location, camera, photos or calendar access in your phone's Settings.
• Delete individual photos, results and training plans in the app, clear any detail of your registration profile (or all of it), or delete your whole account.
• To get a copy of the information we hold about you, or to have it corrected or deleted, email support@bibregistry.com. We'll reply within 30 days.

What we don't do

• We don't run ads, and we don't sell your data.
• We don't track you across other apps or websites, and we don't use your device's advertising identifier.
• We don't submit race registrations for you, and we don't send your registration profile to race sites.
• We don't collect your contacts, health or fitness data, microphone audio, or payment card details.
• We don't use background location or keep a history of where you've been.
• We don't read your photo library beyond the photos you choose to add.
• We don't use third-party advertising or marketing tools in the app.

Children

BIB is not directed at children under 13, and we don't knowingly collect data from them.

Changes

If this policy changes in a way that matters, we'll update the date at the top of this page. Continued use of the app after a change means you accept the update.