Trailsy Privacy Policy

DRAFT v0.1 — NOT YET REVIEWED BY COUNSEL. Bracketed items are placeholders. Last updated: [date]

This policy explains what information Trailsy collects, why, who sees it, how long we keep it, and what choices you have. It is written to be read. If anything here is unclear, email [[email protected]].

Trailsy is operated by [Trailsy LLC], [address], Oregon, United States ("we", "us"). The Service is offered only in the United States and our data is stored in the United States.

1. The short version

2. What we collect

Account information. When you sign in with Apple we receive a stable identifier and, if you allow it, your name and email (Apple may provide a relay address). You then give us a display name, birth date (to confirm you are 18+), state of residence, and optionally a handle, bio, and avatar.

Strava connection. When you link Strava we receive an access token, your Strava athlete ID, and basic profile fields. We store the token so we can read your activities.

Ride data. For each cycling activity you upload to Strava after linking (and, on first link, activities from the current and previous riding season), we receive and store: the activity's start time, duration, distance, elevation, sport type (including whether you marked it as an e-bike ride), device name, privacy setting, and the full GPS stream (latitude, longitude, elevation, and time for each point). This is precise location data. We use it exactly as described in Section 3.

Our records about your rides. We create and store our own records: which trail segments each ride completed, the coverage and direction we measured, any fairness flags, and the version of our matching rules used. These records are ours; they are derived from ride data but are not Strava's data.

Payments and payouts. Stripe processes your card payments and pays out winnings. We store Stripe's identifiers for your customer record, payment intents, transfers, and refunds, the amounts, and the status of your Stripe Connect payout account (for example, whether onboarding is complete). If Stripe asks you for identity or tax information, you provide it to Stripe directly on Stripe's pages; we do not receive or store it. We keep a full ledger of every money movement on your account.

Community activity. Rides you schedule, RSVPs, comments you post, and your leaderboard standings.

Notifications. If you enable push notifications we store your device push token and your preferences.

Device and usage data. IP address, device model and OS version, app version, timestamps of requests, crash and error reports, and coarse location inferred from IP for eligibility checks. We do not use advertising identifiers and do not use tracking as defined by Apple's App Tracking Transparency framework.

Fairness and fraud signals. Statistics we compute from ride data (speeds, climb rates, trace regularity), a non-reversible fingerprint of each ride's shape used to detect the same file being submitted from multiple accounts, and signals used to detect duplicate accounts.

Support. Messages you send us and our replies.

We do not collect location from your phone directly. All location data comes from activities you chose to record and upload to Strava.

3. How we use it

Purpose What we use
Run the Service and your account account information, notification tokens
Verify trail completions and pack results ride data, our completion records, trail map
Detect cheating, duplicate accounts, and payment fraud ride data, fairness signals, device data, Stripe signals
Charge entries and pay winnings; keep required financial records payment and payout data, ledger
Confirm eligibility (age, Oregon) birth date, state, coarse IP location
Show leaderboards, packs, rides, and threads to other riders display name, avatar, derived statistics, community activity
Send transactional messages (verdicts, results, payouts, ride updates, security) account information, notification tokens
Send occasional product news (optional, opt out any time) email
Improve matching accuracy and the trail map ride data and completion records, in aggregate wherever practical
Respond to support and disputes support messages, the records relevant to your request
Comply with law (tax reporting, lawful requests) financial records, account information

We do not: sell personal data; share it for cross-context behavioral advertising; use ride data for advertising or marketing measurement; disclose your individual ride data to other riders; or use ride data, or anything derived from it, to train artificial-intelligence or machine-learning models. Our matching system uses fixed geometric rules, not models trained on rider data.

4. Who sees your information

Other riders see your display name, avatar, handle, and bio; your trails-completed count and other derived statistics on leaderboards and the completion map; your enrollment in public packs; rides you schedule or join; and comments you post. Anything visible to other riders can be copied by them. They do not see your GPS tracks, activity names, pace, heart rate, or anything else from Strava.

Service providers that process data on our behalf, under contracts that limit their use of it:

Legal and safety. We disclose information when required by law or valid legal process, to enforce our Terms, to investigate fraud or safety issues, or to protect the rights and safety of riders, the public, or the Company.

Business transfers. If the Company is sold or merged, your information may transfer with it under commitments at least as protective as this policy. We will notify you before your data becomes subject to a different policy.

5. Strava specifically

6. How long we keep it

Data Retention
Account information While your account is open, then up to [3] years for disputes and legal compliance
Raw ride data (GPS streams) While Strava is connected and your account is open; deleted within [48] hours of disconnection or account deletion
Our completion records and fairness flags While your account is open; after deletion, pseudonymized (no name, no email) and retained as pack history
Financial ledger, payment and payout records At least 7 years (tax and financial regulations), pseudonymized after account deletion
Fraud-prevention fingerprints and signals Up to [5] years, to detect repeat abuse
Comments and ride threads Deleted or anonymized on account deletion
Push tokens Deleted on account deletion or when you revoke notifications
Support messages [3] years
Unclaimed winnings As long as needed to administer them under Oregon unclaimed-property law

7. Your choices and rights

Oregon residents. Under the Oregon Consumer Privacy Act you have the rights to confirm whether we process your data, access it, correct it, delete it, obtain a copy, opt out of targeted advertising, sale, or profiling (we do none of these), and to appeal a refusal. Exercise them as described above.

California and other states. Residents of California and other states with comprehensive privacy laws have similar rights. We have not sold or shared personal information for cross-context behavioral advertising in the past 12 months, and we treat GPS ride data and birth date as sensitive information used only for the purposes allowed by law. Because we do not sell or share data, Global Privacy Control signals do not change how we process it.

The Service is not offered outside the United States.

8. Security

Data is encrypted in transit (TLS) and at rest. Access to production data is limited to people who need it to run the Service. Strava tokens and secrets are stored encrypted [confirm implementation]. No system is perfectly secure; if a breach affects your information we will notify you and any regulators as the law requires.

9. Children

Trailsy is for adults. We do not knowingly collect information from anyone under 18. If you believe a minor has an account, contact us and we will delete it.

10. Changes

We will post changes here and update the date. For material changes we will notify you in the app or by email before they take effect.

11. Contact

[Trailsy LLC], [address] [[email protected]] — put "Privacy Request" in the subject for rights requests.