YOUR DETAILS, WITH CARE

Privacy Policy

Updated October 11, 2026

Rithm helps you run with friends. Here’s what you share and who can see it.

Your account and sign-in

We use your sign-in email to manage your account. If you sign in with Google, Google provides your account identifier, email address, name, and profile picture, if available. Supabase, our authentication provider, stores this information to identify and authenticate your account. We use your email for account access and the run notifications you choose. Signing in with Google does not grant access to your Gmail messages, Google Contacts, or Google Calendar.

Apple sign-in provides an account identifier and the email address you choose to share, which may be an Apple private relay address. Apple may provide your name on first sign-in. We use these details for account access. You choose your Rithm profile details separately: full name, username, city, optional bio and photo, and confirmation that you’re 18 or older and based in the USA. Other members can find your profile to add you as a friend. Your sign-in email is not shown in search or on your profile.

Your runs, photos, and comments

When you agree to the Terms and community rules during profile setup, we store the version and acceptance time with your account. This record is private and is removed when your account is deleted.

You choose who can see each run: friends and their friends, friends only, close friends, a saved list, individual friends, or Just me. New runs default to friends and their friends; you can change this before posting. If you allow forwarding, people invited through a shared link can also access it. People with access can see the run’s details, meeting address, photos, and attendees. A signed-out invitation preview shows limited details, without the address or attendee list.

Run conversation messages and reactions are visible to the host and people who have joined. Blocking hides messages between the blocked accounts. Joining a run does not send a conversation message.

Your accepted friends can browse your ordinary Rithm friends to find people they know and send friend requests. Close-friend designations, saved lists and your phone’s contact list remain private. Blocked and suspended accounts are excluded from friend browsing.

Friend suggestions use invitations, shared-run participation, optional contact matches and mutual friends. Recency, frequency and Close-friend choices help rank eligible suggestions. Suggestions show profiles without revealing private run details, contact matches or Close-friend designations.

Optional contact discovery

During iPhone setup and in Profile → Account settings → Contact discovery, you can choose to find people you know. With your permission, Rithm reads email addresses and phone numbers from the contacts you allow. We do not read contact names, photos, notes or postal addresses. Normalized email addresses and phone numbers are hashed on your iPhone and sent over HTTPS to our services to match existing members’ verified account email addresses or verified mobile numbers. Hashes are identifiers, not anonymous data.

We retain matching Rithm account identifiers and a matching hash privately for your suggestions. Unmatched contact details and hashes are not saved in our database. Contact discovery does not send invitations or friend requests, upload your address book for marketing, or reveal your private contact list to other members. Members who already know your verified email or number may find your Rithm profile this way; we do not display that email or number in results. Apple private relay addresses and different sign-in details may prevent a match.

While enabled on this iPhone, Rithm checks for changes when you reopen the app and refreshes unchanged matches at most daily. You can refresh manually, change allowed contacts in iPhone Settings, or turn discovery off in Rithm to remove your saved matches. Revoked or reduced access is applied when Rithm next opens with an internet connection. Turning discovery off does not remove existing friendships or change SMS consent. Deleting an account removes its contact-discovery preferences and matches from the live database; provider backups follow their retention schedule.

Notifications

Choose push notifications on iPhone, texts, email, or in-app updates in Profile → Account settings → Notifications. Push registration stores an Apple device token and an installation identifier associated with your signed-in account; Apple delivers the notification. Signing out disables that registration until you sign in again. Five switches control cancellations and changed attendance, time and meeting-place changes, reminders, invitations, and run conversations. Conversation alerts use your selected supported channel after a message has remained unread for one hour and before the run starts. We do not send the same update through multiple selected delivery channels. Authentication emails remain separate.

Optional SMS notifications

Rithm offers optional SMS notifications to enrolled beta members. Recurring texts can include run invitations, planning responses, friends joining, cancellations, changed attendance, time and meeting-place changes, reminders, and unread run comments. SMS consent is separate from account registration and is not required to use Rithm. Your mobile number is private and is not shown on your profile or shared with other runners.

If you enroll, we collect your mobile number, consent records, notification preferences, opt-out requests, and message delivery information. We use this information to send the run updates you request, manage your preferences, honor opt-outs, and troubleshoot delivery. Twilio processes the phone number, message content, and delivery information needed to provide SMS messaging on our behalf.

We do not sell or share your SMS opt-in data or personal information with third parties for marketing purposes.

Message frequency varies with invitations and run activity. Message and data rates may apply. Reply STOP to unsubscribe or HELP for assistance. You can also contact bryce@rithm.run. We will retain the consent and opt-out records needed to respect your choices and meet applicable obligations.

Run suggestions are a separate, optional push setting, off by default. If you turn them on, we send a reminder after 14 days without creating or joining a run and one follow-up at least 14 days later, only when you have no upcoming runs. Then reminders stop until you create or join another run. We keep your choice, consent time, latest planning activity time, and reminder delivery times with your account. Turn them off in Notifications at any time. These reminders use Apple push notifications, never email or text, and do not use your contacts, location, or run performance to personalize the message. Their private preference and activity record is removed when you delete your account.

Services, sharing, and security

Supabase stores account and app data, Vercel hosts the website, and Resend receives your email address to deliver run emails. These providers process information needed to operate those services, including network and delivery information used for security and troubleshooting.

Cloudflare R2 stores private, encrypted backup copies of profile and run photos for recovery. Backup snapshots are configured to expire after seven days; provider deletion processing can take additional time. Deleting an account removes its photos from live storage, while older backup copies expire on that schedule.

Google Places receives address searches to provide suggestions. Google Maps displays maps, and Google Routes processes route requests. If you tap the current-location control and allow permission, your device location is used to help choose a meeting point; Rithm does not continuously track your runs or request background location. A saved meeting point or route is shared with people who can access the run.

Member and place searches are sent to the services that provide results. Hosting logs can retain member-search terms with request information for operation, security and troubleshooting. Google may retain place-search terms and related request information to provide and improve its services under its privacy policy. Rithm’s separate internal activity-event records exclude search text.

The native Google Maps and Places SDKs also collect device identifiers and usage or diagnostic information. See Google’s Maps and Places privacy disclosures. Our maps and address features use Google Maps Platform and are subject to the Google Maps terms and Google Privacy Policy.

We use HTTPS and account-based access controls to protect data. Browser storage and cookies support sign-in and app functionality; the separate sample app stores demo data in your browser. Rithm does not use advertising identifiers or track you across other companies’ apps and websites for advertising.

We do not sell Google user data or use it for advertising. Rithm’s use of Google data follows the Google API Services User Data Policy, including its Limited Use requirements.

Keeping and deleting your data

We keep your account and app data while your account exists. You can edit your profile and use the app’s controls to remove content. In the app, open Profile → Account settings → Delete account to verify your sign-in and request permanent deletion. Your profile, hosted runs, messages, friendships and active notification registrations are removed immediately; photos, authentication records and Apple authorization are cleaned up automatically, usually within a few minutes. Upcoming hosted runs are cancelled with one summary per affected friend. Other people’s independently saved data remains theirs. If Apple access was connected before token revocation was available, we also show how to remove that access in Apple settings. For access requests or help with deletion, email bryce@rithm.run from your sign-in address. We retain SMS opt-out records to honor STOP requests. A deletion receipt contains no account identifier once cleanup finishes and expires after seven days. Temporary cleanup records contain only what is needed to finish deletion and retry provider failures.

Service-provider logs and backups can remain after account deletion under each provider’s policies and settings. Twilio is configured to make our SMS records accessible for 90 days, with indefinite backup storage disabled. Provider deletion processing can extend beyond that access window. In-app account deletion does not automatically erase those provider records. Support and appeal emails are stored separately in our Google-hosted support mailbox and are not automatically removed when you delete your Rithm account. Contact bryce@rithm.run for help with these records.

You can also remove Rithm’s access in your Google Account connections. This stops Google access but does not itself delete your Rithm account or previously stored data.

Drafts and optional calendar syncing

Unfinished run and message drafts stay in private storage on your iPhone, excluded from cloud backup. Drafts expire 48 hours after the last edit and are removed when Rithm next checks its storage. Signing out or deleting your account clears this phone’s drafts. They are not shared with other members or synchronized between devices.

If you choose calendar syncing, a private subscription link lets your chosen calendar provider retrieve runs you host or join, including their names, times and meeting points. Rithm does not read your other calendar events. Anyone with the link can read that feed, so keep it private. Changes appear when your calendar provider refreshes. We retain minimal identifiers and times for delivered events to remove outdated entries, with operational cleanup after 30 days past their end time.

You can stop syncing in Rithm to disable the link. Account deletion also disables it. Copies already saved by your calendar provider may remain; unsubscribe from Rithm in your calendar app to remove them.

Safety and moderation

When a reviewer removes content, they can separately restrict its author from reposting selected text or an identical photo. We store a digital fingerprint, account, scope and review record. Restrictions expire after 90 days and can be lifted sooner; their records are erased with the source report when either reporting or reported account is deleted. To verify photo uploads and detect identical files, we also retain an account-linked fingerprint and upload path until account deletion. These checks do not send content to an AI moderation service or assess the meaning of every message or photo.

In-app reports contain the reason, optional details, and a snapshot of the reported content, including a reference to a reported photo. Only designated Rithm reviewers can access reports and private review notes. Reports are not shared with the reported member. Block lists are private; shared attendance remains visible on runs hosted by other people, while messages between blocked members are hidden. Report evidence and its attached review history are erased when either the reporting account or the reported account is deleted. An active account suspension can remain after the reporter deletes their account. Restoration records created after that deletion are associated with the reported account and are removed when that account is deleted. Contact bryce@rithm.run for help or to appeal a moderation decision.

We record limited app activity, such as opening Home and publishing or joining a plan, to improve the beta. These internal events exclude message content, phone numbers, precise locations, and search text. Raw activity events are retained for up to 90 days and are available only to authorised administrators.

Questions and updates

Contact bryce@rithm.run with privacy questions. Updates will appear here with a revised date. We will notify you and request consent before using Google data for a new purpose.