Privacy Policy

Run Bud may process the following information: - Authentication data: Email address, password credentials processed by Supabase Auth, account identifiers, and session information. - Runner profile: Display name, one selected primary profile photo, up to four optional additional profile photos, gender, pace ranges, preferred distance, availability, additional details, and preferred activity. - Run area: A user-selected or one-time device-derived geographic point, general city/region/country label, location source, optional device accuracy, selected search radius, and update time. - Social activity: Connection requests, accepted connections, private messages, blocks, and reports, including optional report details. - Support communications: Information you choose to send by email. The app does not automatically attach passwords, tokens, messages, report notes, or location information.

- Discovery information: Completed, discoverable profiles may show display name, the primary profile photo and optional additional profile photos, pace, preferred running distance, availability, additional profile details, a general city/region area, and an approximate distance band to eligible nearby runners. Gender can be used to filter discovery but is not returned on another runner’s discovery profile. - Location information: Run Bud privately stores one current run-area point selected manually or derived from a one-time foreground device-location request. Exact coordinates, device accuracy, and location source are not displayed to other users. The app does not create location history, continuously track location, request background location, share live location, return a bearing, or display an exact distance. - Connection information: Request status and connected-runner profiles are available to the relevant users. - Private messages: Message content is available to conversation participants. Messages are not end-to-end encrypted. - Private account information: Email, credentials, sessions, and account operations are not part of the discovery profile. - Private safety information: Blocks, reports, report details, and moderation snapshots are restricted from ordinary client access.

Run Bud uses information to: - Create and secure accounts and maintain sessions. - Build profiles, find runners within both users’ selected proximity radii and compatible preferences, and operate connection and messaging features. - Prevent unwanted contact, receive reports, preserve bounded evidence, investigate abuse, and enforce the Community Guidelines. - Provide support, troubleshoot failures, protect the service, and comply with applicable obligations.

Run Bud uses Supabase for authentication, Postgres database hosting, public profile-photo storage, realtime messaging delivery, and server-side account deletion. Supabase processes information on Run Bud’s behalf under its own service terms and infrastructure practices. The current app does not implement analytics, advertising SDKs, crash-reporting SDKs, push-notification device tokens, subscriptions, background or continuous GPS tracking, location history, route tracking, or live-location sharing.

Submitting a report creates a private report and a limited snapshot of the reported profile. When available and authorized, the snapshot may include up to 20 recent conversation messages or a reported message with up to 10 messages before and after it. The deployed system assigns this moderation evidence an expiration 180 days after capture. Evidence is removed when the privileged expiry-cleanup operation runs. A trusted operator may change an individual expiration only under a separately reviewed, case-specific policy. Deleting an account does not extend an evidence expiration. It replaces the deleted account ID in retained evidence with an unlinkable pseudonym and clears deleted profile-photo URL and gallery-path metadata while preserving the bounded safety snapshot until cleanup.

Permanent account deletion removes the Auth account, public profile, private current run-area row, profile-photo objects, connection requests, accepted connections, blocks, conversations, and ordinary messages. Successful deletion also clears the local app session and caches. Reports may remain as private safety records. Live profile references are removed, and narrowly retained moderation evidence may remain until its existing expiration and subsequent privileged cleanup. This means account deletion may not immediately erase every safety record.

Run Bud uses access controls such as Supabase Row Level Security and restricted moderation tables. No method of storage or transmission is completely secure, and Run Bud cannot guarantee absolute security.

Run Bud is intended only for users who are 18 years of age or older. Users under 18 are not permitted to create an account or use the service.

Supabase infrastructure may process information in locations selected for the project and through its service operations. Depending on where you live, your information may therefore be processed outside your state, province, or country.