Privacy Policy
Effective date: 22 September 2026
This policy explains the personal data Runsembly handles when you browse the website, create an account, use the native app, submit race-registration evidence, or take part in private race communities and plans.
1. Who to contact
For privacy questions, rights requests, or concerns about personal data, email privacy@runsembly.com. Other public contact details are on the Legal information page.
2. Data we handle
- Account and authentication data: email addresses, Clerk identifiers, sign-in state, and email-verification state.
- Profile data: name, city, country, date of birth, photo, gender, languages, preferred distances, club, biography, and onboarding or terms-acceptance records.
- Race and registration data: saved races, room-access status, registration confirmation numbers, submission and decision timestamps, and evidence files you upload.
- Community and feedback data: private community access, plans, membership requests, messages, notifications, push-device subscriptions, blocks, mutes, safety reports, and suggestions or app/race reports you submit.
- Technical data: request, error, authentication, and security logs needed to operate and protect the service.
- Map and place data: place searches, selected meeting locations, and map requests when you use location features.
Runsembly does not currently connect to Strava, import running activities, collect pace data, or process payments.
3. Why we use it
- Create, authenticate, and secure accounts.
- Provide race discovery, saved races, registration review, and private community access.
- Show runner profiles and operate plans, conversations, notifications, reporting, blocking, and moderation tools.
- Review registration evidence and investigate misuse or safety concerns.
- Provide place search, meeting pins, maps, and directions.
- Maintain, troubleshoot, and protect the website, API, and native app.
- Respond to support, feedback, and rights requests and comply with lawful obligations.
4. Registration evidence
Evidence is used to decide access to a specific private race community. Uploads are bound to the submitting account and kept in private object storage. The runner who uploaded a file and authorized race-desk users can retrieve it through authenticated routes. Upload links expire after 15 minutes. Files that were uploaded but never attached to a profile or registration review become eligible for cleanup after 24 hours.
Upload only evidence you are authorized to share and remove unrelated sensitive information where possible. Accepted evidence is limited to supported image files or PDF, with a 10 MB maximum.
5. Who can see information
Account controls, saved races, registration submissions, notification settings, blocks, and data exports are account-scoped. Authorized race-desk users can see the registration material needed to make access decisions. Profile information, plan details, and messages are shown within the community surfaces that use them; visibility depends on room access, plan membership, and the relevant feature.
Service providers receive data needed to supply their service. Information may also be disclosed when required by law, to protect users or the service, or as part of a lawful business transfer.
6. Providers and external requests
- Clerk provides account authentication and sign-in storage.
- Replit hosts the application and provides managed PostgreSQL and private App Storage. Published pages also use Replit’s default published-app traffic metrics, which Replit describes as IP-based and separate from Runsembly’s optional Plausible statistics.
- Google receives requests for Google Maps, Places, directions, and externally loaded font files when those features or pages are used.
- Plausible receives an approved public page path plus normal network and device request information only when the integration is configured and you have allowed optional usage statistics.
- Device push services receive a push subscription and notification content when push notifications are enabled.
- Resend processes the email address associated with your account, the information needed to prepare a service message (such as the race name or plan title), and delivery metadata so Runsembly can send registration-decision emails and optional plan notifications. Resend acts as a processor on Runsembly’s behalf for this purpose.
Provider processing can take place outside your country. Provider-specific contracts, locations, and retention rules may apply in addition to Runsembly’s controls.
7. Storage, logs, and retention
Account and application records are kept while needed to provide and secure Runsembly, resolve access or safety issues, and meet legal obligations. The code does not set one fixed retention period for every database record, log, provider record, or backup.
Authorization, cookie, and set-cookie headers are redacted from application logs. The service removes expired push endpoints when a provider reports that they are no longer valid. Browser and app storage, including exact configured lifetimes, is listed on Cookies & storage.
8. Account deletion
On the website, Privacy & data lets you download account data or start permanent deletion by typing DELETE. Processing starts immediately and cannot be cancelled. Runsembly removes application records and tracked files, then removes the Clerk account. Failed steps are recorded for retry.
Messages can remain in other runners’ conversations with the author replaced by “Former member” and profile links removed. Operational backups and provider-held security or legal records can remain until their normal deletion or rotation.
Private safety reports and feedback may remain for moderation and investigation after deletion, but the reporter’s account identifier is removed. Do not include unnecessary personal information in a report’s description.
9. Your controls and rights
You can edit profile details, manage notification categories and push devices, leave plans, block or unblock runners, download account data, change optional analytics preferences, and delete your account. Subject to applicable law, you may also request access, correction, restriction, objection, portability, or deletion by emailing privacy@runsembly.com. We may need to confirm that a request belongs to you.
Registration-decision emails are service messages and cannot be switched off. You can independently turn off emails about approval-plan join requests, accepted join requests, and daily summaries of new plans in race rooms in Notifications, or use the unsubscribe link in the relevant email. Unsubscribing from one type does not change the other email settings or your in-app Updates.
You may complain to the data-protection authority responsible for your circumstances.
10. Age
Runsembly’s community features are intended for adults aged 18 and over. Date of birth is used to apply that age requirement. If you believe a person under 18 has provided data, contact us so we can investigate.
11. Security
Runsembly uses authenticated routes, account and role checks, private file storage, short-lived upload links, and server-side ownership checks. No online service can guarantee absolute security. Contact support@runsembly.com if you believe an account, file, or room has been accessed improperly.
12. Optional usage statistics
Runsembly’s Plausible integration is disabled in the current website build, so it currently sends no event requests. If enabled, optional website statistics will be off unless you make a valid choice to allow them. Approved public page paths are used; race-page identifiers are replaced with a generic race-detail path, and URL parameters are excluded. The website may send “Sign up started,” “Registration submitted,” “Plan created,” “Plan joined,” and “Share clicked” events. Race-related events contain only a race property with the public event key and edition; the signup event has no custom properties. Events do not include user IDs, names, email addresses, plan titles, or free text, and private page paths are not sent. Browser DNT and GPC signals keep web statistics off.
A choice is stored separately in each browser or app installation for up to 180 days and can be withdrawn at any time in Privacy preferences.
Replit’s default published-app traffic metrics and its hosting-layer requests are separate from this Runsembly preference and are not controlled by it.
13. Changes
Runsembly may update this policy when the service or legal requirements change. The effective date will be updated, and material changes will be made visible in the service where appropriate.