Privacy Policy
Effective July 16, 2026
RunnersGarage (“we”, “us”) is a running-coaching product: chat-based shoe recommendations, training plans, race search, nutrition guidance, and recovery protocols. This page explains what personal data we collect, why, who we share it with, and the choices and rights you have over it. It's written to describe what the product actually does today, not aspirational future functionality.
Account data. Your email address and authentication credentials, handled by Supabase Auth (including Google/Apple sign-in and magic links, where enabled). We never see or store your password directly.
Profile data. Anything you tell us or the AI coach about yourself that we use to personalize recommendations: age, weight, height, gender, experience level, weekly mileage, training days, shoe width and budget preference, and injury history (type, date, recovery status). Injury history is health-adjacent information — we collect it only to tailor training and recovery guidance, never to profile you for any other purpose, and it is never sold or shared with advertisers.
Location data.If you tell us (or it's inferred from a race search), your city, state, country, and approximate coordinates, used to find nearby races.
Conversation content. The messages you send the AI coach, and its responses, stored so you can revisit past conversations and so the coach has context across a conversation.
Saved items. Shoes, races, training plans, nutrition plans, and recovery plans you save to your Garage.
Billing data.If you subscribe to Pro, our payment processor (DodoPayments) handles your payment details as merchant of record — your card number never touches our servers. We store only your subscription status and DodoPayments' own customer/subscription identifiers.
Technical data. Standard request metadata (IP address, user agent) processed transiently for rate limiting and abuse prevention, and error/exception data captured by our error-monitoring tool when something breaks.
To generate personalized shoe recommendations, training plans, nutrition guidance, and recovery protocols; to find races near you; to remind you before a saved race's registration window closes; to remember your conversation history; to run and secure the service (rate limiting, fraud/abuse prevention, error monitoring); and to process Pro subscription payments.
We do not use your data to train third-party AI models, and we do not sell your personal data to anyone.
We use a small set of third-party services (“processors”) to run RunnersGarage. Each only receives the data it needs to do its job:
| Service | Purpose | Data involved |
|---|---|---|
| Supabase | Database, authentication, file storage | Account, profile, conversation, and Garage data; exported PDFs |
| Google (Gemini API) | Powers the AI coach | Your chat messages and profile context, sent per request |
| Tavily | Web search tool used by the AI coach | Search queries the AI issues on your behalf |
| Upstash (Redis) | Caching and rate limiting | Cached responses, request counters |
| DodoPayments | Pro subscription billing (merchant of record) | Payment and billing details |
| Resend | Transactional email (race reminders) | Your email address, race reminder content |
| Sentry | Error monitoring | Error reports, which may include request context |
We do not use any advertising, analytics-tracking, or session-recording tools, and we do not share your data with data brokers.
We may also disclose data if required by law, to enforce our Terms, or to protect the rights, safety, or property of RunnersGarage or our users.
We use one first-party functional cookie, a session identifier, so an anonymous visitor's conversation stays linked to them for up to 7 days (or until they sign in, at which point it's replaced by an auth session). If you sign in, Supabase Auth sets a session cookie/token to keep you logged in.
We don't currently use advertising or analytics cookies, so we don't run a cookie consent banner — every cookie we set is strictly necessary for the product to function. If that changes (e.g. we add product analytics in the future), we'll update this policy and add a consent mechanism before doing so.
Conversations. Free accounts keep your 3 most recently active conversations; Pro accounts keep 15. Older conversations are hidden (not permanently erased) once that cap is exceeded. Deleting a conversation yourself works the same way — it disappears from your history immediately, but its content is retained internally rather than immediately purged from our database.
Account deletion.Deleting your account (Profile → Delete Account) permanently and irreversibly removes your login and cascades to delete your profile, conversations, messages, and saved items. Two exceptions: aggregated usage logs and affiliate-link click records are retained in a form no longer tied to your account, for financial auditing and revenue reporting. Account deletion has no grace period — there is no “undo.”
Depending on where you live (including under the GDPR if you're in the EEA/UK, or similar state privacy laws), you may have the right to access, correct, delete, or export your personal data, and to object to or restrict certain processing.
- Access & correction — view and edit most of your data directly from your Profile page.
- Erasure— delete your account at any time from Profile → Delete Account (see retention notes above for what's retained).
- Export / portability— we don't yet have a self-service data export button. Email us (below) and we'll get you a copy of your data manually.
- Objection / restriction— contact us (below) and we'll work with you on it.
Our infrastructure providers (Supabase, Google, Railway, Vercel, and others listed above) may process and store data outside your country of residence, including in the United States. Where that applies to data originating in the EEA, UK, or Switzerland, we rely on the safeguards each provider makes available (such as Standard Contractual Clauses) — see each provider's own privacy/data-processing terms for specifics.
RunnersGarage isn't directed at children, and we don't knowingly collect data from anyone under 16. If you believe a child has given us personal data, contact us and we'll delete it.
We'll update this page if what we collect or how we use it changes, and update the effective date above. For material changes, we'll make a reasonable effort to notify you directly (e.g. by email).
Questions, data requests, or concerns: arnav.vyas06@gmail.com