YOUR DATA / YOUR CONTROL

A personal number.
A private experience.

SpinTribe uses the information needed to calculate your own SpinKM and show your progress.

What is stored

Your account email, time zone, monthly and annual targets and imported activity summaries: activity name and type, source identifier, start time, distance, elevation gain, indoor indicator and moving time when available. A road-reference eligibility indicator and timing-check timestamp support private SpinRate and Terrain Pace. Connection credentials are encrypted on the server. SpinTribe does not request GPS streams, routes, heart-rate streams or power data.

Who sees your rides

Your imported history is visible only to your signed-in account. V1 has no public activity leaderboard. Supabase hosts the account and database; Vercel hosts the application and Resend delivers account confirmation emails. The public calculator runs in your browser and does not save the measurements you enter. No advertising analytics or tracking pixels are included.

SpinRate and Terrain Pace use only your own imported history. They are never shared in organisation reporting. Terrain Pace inputs stay in your browser and are not saved; average speed and estimates are derived, not stored as authoritative activity values.

Pace Your Race

Route uploads and rider inputs are processed locally in your browser. Choosing to share creates an anonymous public summary with your goal, distance, climbing when available, kilometre splits and feed quantities. The file, geometry, mass, FTP and heart-rate values are excluded. Anyone with the link can open it for 30 days. Shared plans are excluded from search indexing and expired plans are unavailable even if cleanup is delayed.

Daily counters record plan creation, successful sharing and paid-ride link clicks without rider identifiers, retained for 30 days. Abuse prevention uses a daily rotating one-way address key retained for 24 hours. Raw addresses are not stored in these tables. This tool collects no email addresses in this release.

Your Ride Joburg goal and debrief

If you save a Ride Joburg 2026 goal, SpinTribe stores your target finish time and, after the event date, the actual finish time and optional reflection you enter. These details are visible only to your signed-in account and are kept until you delete them on your event page or delete your account. The debrief compares only your entered times. It uses no Strava data or AI, and does not require an activity connection.

Organisation ride operations

Ride Ready stores organisation membership, the name used in that organisation, ride details, RSVPs, ride availability and role assignments. These are shared only with current members of that organisation. Organisers manage membership and riding roles. Your imported Strava history stays private to your account and is never used to report on other members.

Removing membership or deleting your account removes your membership, responses and assignments. Shared organisation and ride details remain for the other members. Arrange another organiser before deleting your account if you are the only organiser.

Connecting Strava

Strava is an optional import source. Creating an account and participating in Ride Ready do not require a Strava connection. The app requests activity:read permission for activity summaries available through that scope. Activities marked “Only You” on Strava are not imported with this permission. Your SpinKM is based on the available imported history and may not match all rides in Strava.

Ride Stories

Ride Stories can add a short description to your own authorized cycling activities. Stories use prewritten templates, supported recorded facts and context you choose to supply. No Strava data or derived information is sent to AI models. Your activity visibility is not changed. Activities marked “Only You” remain outside this release.

Auto Ride Stories is off by default. It publishes on new activities only after you separately enable it and grant Strava activity update permission. Connecting Strava alone never starts historical publishing. You can pause automatic stories in your dashboard. An update already sent to Strava may still finish after you pause.

Updating historical rides is a separate action. You choose the previous completed Monday-to-Sunday week in your account time zone, or a rolling seven-day window. You see which activities qualify and each complete proposed description before confirming the batch. Optional historical context is used for that preview, not for future automatic stories. Brand attribution and pacing-tool references are independent choices and are unavailable until cleared for the service.

Ride Stories keeps your account choices until you change them or remove your account. Unconfirmed previews of existing and proposed descriptions expire after ten minutes and are cleared when you confirm a batch. Generated text and minimal processing records are temporary, retained for no more than seven days. Completed jobs discard generated text and description hashes, while their status remains until expiry. These records support retries and prevent repeated updates; they are not a permanent archive of your historical descriptions.

Your notes outside the marked Ride Story section are kept in the proposed text. SpinTribe checks the current description before writing and skips or requests a new preview when it detects changed notes. Simultaneous edits from another app can still conflict, so review the result in Strava if you edit a description while an update is running. Published text remains in Strava until you edit or remove it there, including after you disconnect or delete your SpinTribe account.

Disconnecting and deleting

Disconnecting removes the connection and imported Strava activities including their timing and reference indicators from SpinTribe. Removing imported data also stops the connection, so new syncs do not immediately restore it. Your account, monthly and annual targets remain until you delete the account. Deleting your account removes your profile, goals, connections and imported activities. These actions do not delete activities from Strava itself.

Strava deauthorization and activity deletion are processed through the configured webhook lifecycle. Service backups may retain deleted records until the hosting provider’s retention period expires; they are not available in the application.

Sessions and service records

An encrypted, essential, httpOnly session cookie keeps you signed in. Server logs record operational errors without intentionally including passwords, provider tokens or raw activity payloads.

Operator and contact

SpinTribe is operated by spera. For account access, correction or deletion, contact ssdidiza@gmail.com. Account information remains while your account is active; imported records are removed when you disconnect or delete them. Completed webhook event metadata is retained for up to seven days. Legacy records from the previous app are retained separately during the replacement and are not shown as new SpinKM activity history.

SpinTribe is an independent application. It is not developed, sponsored or endorsed by Strava.

Manage your data ↗