marathon.dateBack to your plan ↗Your plan is yours. Calendar access is optional. AI receives planning context when needed. We do not sell your information.
Your rights and choices ↗Who is responsible
This notice explains how marathon.date handles personal information when you visit the website, create an account, build a training plan, use chat or connect a calendar. It applies to users worldwide, with additional rights described for the European Economic Area (EEA), United Kingdom and other places where local privacy law applies.
For privacy requests and questions, contact hello@marathon.date. marathon.date is currently operated as an individual project, rather than an incorporated company. The operator’s full legal identity and contact address have not yet been added to this preview notice and must be completed before public launch. This notice does not identify a separate data protection officer or EU/UK representative.
Information we collect
| Category | Information and source | Why it is used |
|---|---|---|
| Account | Account identifier, email address, name, profile image and sign-in information supplied through Google and Supabase authentication. | Sign you in, associate your plan with your account and secure access. |
| Training profile | Training start and race dates, running days, weekly kilometres, preferred running time, weight, and optional height and age, supplied by you. | Build sessions, calculate approximate fueling needs and remember your preferences. |
| Plan and chat | Run dates, times, durations and types; unavailable dates; coaching preferences; your messages and assistant replies. | Show, adjust and save the plan and respond to your requests. |
| Connected calendar | Event titles, dates, start/end times and all-day status from the primary Google Calendar you choose to connect. Google may return additional event fields before the app reduces the response to the information it needs. | Display meetings and arrange runs around busy times. Calendar connection is separate from Google sign-in. |
| Device and service operation | IP address and connection metadata received by infrastructure providers; browser/time-zone information; sign-in/session information; request status, latency, model and token counts. | Deliver the website, protect accounts, limit abuse, diagnose errors and understand service usage. |
| Payments, when enabled | Selected pass, currency, price, payment status, transaction references and entitlement dates; billing/contact information collected by Stripe at checkout. | Take payments, provide access, handle refunds, prevent fraud and meet accounting obligations. |
| Contact requests | Your email address, message and any information you choose to send to our contact inbox. | Answer questions and handle support or privacy requests. |
We do not request GPS location, contacts, Gmail message contents or a Google password. Avoid including other people’s personal details, confidential meeting titles, medical records or information you do not want processed in your chat messages.
Purposes and legal grounds
Where the EU GDPR or UK GDPR applies, ordinary account, plan and chat processing necessary to deliver the service you request is based on performance of a contract or steps you request before entering one (Article 6(1)(b)). Security, abuse prevention, essential troubleshooting and proportionate service-operation measurements are based on legitimate interests (Article 6(1)(f)): running a reliable service and protecting users. We consider the impact on your rights when relying on those interests.
We rely on consent where legally required for optional access or processing. You separately authorize Google Calendar access and may revoke it. OAuth authorization gives technical permission; it does not replace any additional consent required by privacy law. Accounting, valid legal demands and other mandatory records may be processed to meet a legal obligation (Article 6(1)(c)).
Information such as injuries, health conditions or fitness details may reveal health data depending on its content and use. A separate Article 9 condition is required if information is processed as special-category health data; a service contract alone is not enough. The legal basis and any explicit-consent mechanism for such processing must be finalized before a public launch involving that data. Please do not submit diagnoses or medical records. The planner is not a medical service.
You need an account for cloud saving and authenticated AI chat. Without the necessary training inputs, some planning or fueling features will not work. Connecting Google Calendar and providing optional profile fields are choices; you can use calendar planning without connecting Google Calendar.
AI chat and your information
AI chat is provided using the OpenAI API. When a request requires AI, our backend sends your message, up to 24 recent conversation messages, saved coaching preferences, training dates and sessions, unavailable dates, time zone and relevant calendar busy intervals. Some straightforward requests are handled by app rules without an OpenAI request.
Structured weight, height and age fields, Google event titles, your account email and credentials are excluded from the chat context sent to OpenAI. However, anything you type into chat—including body details, health information, names or copied event descriptions—can be included in messages sent to the provider. Busy intervals can still be personal information even without event titles.
We request responses with store: false. This setting does not mean zero retention: OpenAI documents default API abuse-monitoring retention of up to 30 days, subject to exceptions and account settings. API inputs and outputs are not used to train OpenAI models by default. See OpenAI’s API data controls for its current terms and exceptions.
AI proposes training changes that the application validates. You can inspect, change or undo your plan. We do not use the planner to make solely automated decisions producing legal or similarly significant effects, such as employment, insurance or credit decisions.
Google sign-in and Calendar
Signing in with Google does not connect Google Calendar. Sign-in shares the identity information needed for your account. Calendar access is requested only when you choose to connect it, using read-only event permission for your primary calendar.
The current app fetches events for the training period to show commitments and adapt sessions. Imported event titles and the Calendar access token are held in browser memory, rather than saved with your cloud plan. A page reload ends this in-memory connection; a token may expire earlier. The resulting run schedule is saved, and busy intervals may be sent to our backend and OpenAI when you request an AI scheduling adjustment. If you type meeting details into chat, those messages follow the chat retention rules.
We do not use Calendar permission to create, edit or delete Google events. Downloading an exported run calendar and importing it into your calendar app is a separate action you control. You can revoke access in Google Account connections. Revoking Google access stops future access but does not automatically delete a saved marathon.date plan or account.
marathon.date’s use and transfer of Google API information follows the Google API Services User Data Policy, including its Limited Use requirements. Google data is used to provide the user-facing planning features you request, not advertising or training general-purpose AI models. Human access is limited to circumstances permitted by that policy, such as your specific permission, security investigation or legal requirements.
Providers and other disclosures
We do not sell personal information, share it for cross-context behavioural advertising, or run advertising profiles in the current app. Providers receive information necessary for their role:
- Supabase: authentication, account identifiers and cloud storage of profiles, plans, saved chat and preferences. See Supabase’s privacy information.
- OpenAI: AI chat and scheduling context as described above.
- Google: identity, Calendar authorization and event retrieval. Google-hosted fonts and the Google sign-in/authorization components may receive technical connection information when loaded. See Google’s privacy policy.
- Stripe, when payments are activated: hosted checkout, payment processing and fraud prevention. We do not receive or store full payment-card numbers or security codes. Stripe may act as a processor or independent controller depending on the activity; see Stripe’s privacy policy.
- Website hosting and email providers: delivery, infrastructure security, operational logs and messages sent to our contact address. HOSTiQ is the selected hosting provider; the VPS production configuration is still being arranged.
We may disclose necessary information to professional advisers, competent authorities or other recipients where required by law, to protect rights and safety, or in a business transfer with appropriate confidentiality protections. This does not permit unrelated reuse of Google API data. We do not give other marathon.date users access to your plan or chat by default.
Where information is processed
Service providers and their subprocessors may process information outside your country, including outside the EEA or UK. A selected database region does not by itself guarantee that all support, authentication, AI, payment or infrastructure processing remains in that region.
The final production hosting location, Supabase project region and applicable contractual transfer arrangements have not yet been recorded in this preview notice. We do not currently claim EU-only storage or that a particular transfer safeguard has been put in place for every provider.
Before public launch, applicable international transfers must be assessed and supported by a lawful mechanism, such as an adequacy decision, EU Standard Contractual Clauses and any necessary supplementary measures, or the relevant UK transfer addendum/agreement. Contact hello@marathon.date for information about locations and applicable safeguards.
How long information stays
| Information | Retention approach |
|---|---|
| Account and saved plan | Kept while the account and saved plan are maintained, until you request deletion or the information is no longer needed to provide the service. A race ending does not automatically delete your account. No automatic inactive-account deletion period is currently implemented. |
| Saved chat | The app’s saved state contains up to 80 recent messages. New saves can replace older messages; this is not a promise of immediate removal from backups or third-party abuse-monitoring systems. |
| Calendar events and Calendar token | Current browser memory until reload, the connection is cleared, or the token expires, as applicable. Events are not saved in the cloud plan. Saved runs and any meeting information you type into chat remain subject to their own retention rules. |
| Operational AI usage records | Request status, latency, model and token-count records are pruned on a rolling 90-day basis when new usage records are written. These records do not contain prompts, saved profiles, emails or tokens. |
| Local browser copies | Remain until replaced, removed by the app or cleared through browser settings. Clearing browser storage does not delete a cloud account; deleting an account does not clear every browser’s local storage. |
| Support and privacy correspondence | Kept as necessary to resolve the request, document our response and address reasonably anticipated disputes or legal obligations. We consider the sensitivity and age of the information. |
| Payment, tax and legal records | If payments are enabled, kept for applicable accounting, tax, fraud-prevention and legal-claims periods. Those periods depend on the operator’s jurisdiction; a final schedule will be established before paid public launch. |
Provider backups, security logs and legally required records may be retained separately under their applicable schedules. We will not promise that deletion from an active account instantly removes every backup. You can request the applicable retention details and deletion at our contact email. Backup and infrastructure log schedules must be confirmed for the production configuration.
Cookies, local storage and preferences
The app uses browser storage to keep a plan or account cache, appearance preferences, onboarding-tour state and authentication information. This is not limited to cookies: local storage and session storage also store information on your device.
Keep me logged in controls whether authentication is stored persistently in local storage or in session storage, which normally ends with the browser session. It does not turn off the separate local plan cache or appearance preferences. Sign out and clear site data if you use a shared device.
The current app does not install advertising pixels or third-party behavioural analytics. We have not added a blanket “accept all cookies” banner because no optional advertising or analytics tools are currently configured. Authentication providers, payment checkout and other external services may apply their own storage practices. Any future non-essential tracking will require updated information and any legally required choice before activation.
Security and access
The app uses authenticated account access, per-account database rules, backend validation, private server-side API credentials and usage limits. The owner dashboard shows aggregate service information rather than a list of users’ conversations or body profiles. Authorized administration, support, security or legal work may still require access to relevant data; we do not promise that stored information is inaccessible to every administrator.
No system or transmission can be guaranteed completely secure. Production HTTPS, access controls, backup settings and incident procedures must be verified before the website is publicly deployed. If a personal-data breach occurs, we will assess notification duties and notify affected people and regulators when required by law.
Your choices and privacy rights
Depending on your location and the applicable law, you may request:
- Access: confirmation of processing and a copy of your personal information.
- Correction: changes to inaccurate or incomplete information.
- Deletion: removal of information where there is no continuing lawful reason to keep it.
- Restriction or objection: limits on certain processing, including objection to processing based on legitimate interests. You may object to direct marketing at any time.
- Portability: a machine-readable copy of qualifying information you supplied where processing is automated and based on consent or contract.
- Withdrawal of consent: stop consent-based processing, without affecting processing that was lawful before withdrawal.
- A complaint: contact your competent privacy regulator without first contacting us.
Email hello@marathon.date with your request and the account email concerned. We may reasonably verify your identity, using the least additional information necessary. Do not email passwords, card details or copies of identification unless a specific secure verification method has been agreed. There is currently no self-service account deletion page; requests are handled by email.
For GDPR requests we normally respond within one month. Where legally permitted because a request is complex or numerous, this may be extended by up to two further months; we will explain the reason within the first month. Exceptions, identity checks and legally permitted limitations may apply. Requests are normally free; any legally permitted fee or refusal will be explained.
EEA users can find their regulator through the European Data Protection Board’s authority directory. UK users can contact the Information Commissioner’s Office. Users elsewhere may have additional local rights, including access, correction, deletion, appeal and protection against unlawful discrimination for exercising rights. We assess those requests under the applicable law rather than assume that every regional law applies to this project.
Adults and children’s information
The service is intended for adults aged 18 and over. It is not directed at children, and we do not knowingly seek information from children. If you believe a child has provided information, contact us so we can investigate and remove it where appropriate. A minimum age in a profile field is not a complete age-verification system.
Changes and how to contact us
We will update this page when the service or our processing changes. The revision date appears at the top. Material changes will be brought to users’ attention through an appropriate notice, and we will obtain fresh permission where required rather than assume that continued use supplies consent.
For privacy, data-rights requests, questions or general contact: hello@marathon.date.