Privacy policy

This policy describes how deload ("we", "us") collects, uses, stores, and shares information when you use our marketing site, web apps, and mobile app (together, the "Service"). We've tried to keep it in plain English. If anything is unclear, reach us through the contact page.

Who this applies to

deload is used by two kinds of people: coaches, who write training programs, and athletes, who follow those programs and log their sessions. Coaches invite athletes into the product; athletes accept that invitation and create an account to participate. This policy applies to both.

What we collect

We collect only what's needed to run the product and support you:

• Account information. Name, email address, and authentication identifiers from our login provider (Clerk). If you sign in with Google or Apple, we receive your name, email, and a stable user ID — not your password.
• Coach content. The programs, blocks, sessions, exercises, notes, and cues you create inside the app.
• Athlete content. Session logs, weights, reps, RPE/RIR, "how did it feel?" check-ins, mood and effort ratings, personal records, and any free-text notes you write.
• Roster relationships. Which athletes belong to which coach, and any tags or labels a coach applies to an athlete.
• Email check-ins. If a coach enables check-in emails, we send athletes a periodic message and record whether and when it was opened or replied to.
• Device and usage data. Basic logs (IP address, browser or device type, timestamps, pages or screens viewed, errors) so we can keep the Service running and debug problems.
• Support correspondence. If you contact us, we keep the message and your reply address so we can respond.

We do not knowingly collect data from anyone under 13. If you're a coach working with minor athletes, you are responsible for getting the consent required in your jurisdiction before inviting them into the product.

What we don't collect

We don't collect health information beyond what you choose to type into the app (weights, reps, soreness notes, etc.). We don't track your location. We don't use advertising trackers or sell our analytics to third parties.

How we use it

• To operate the Service — show your roster, render the program calendar, save your session logs, send check-in emails, and so on.
• To generate suggestions inside the product (for example, when a coach asks the assistant to draft or rewrite a block). The model providers we use process this content on our behalf under contract and do not train their models on it.
• To support you when you write in, and to investigate bugs or abuse.
• To improve the product — for example, looking at aggregate, de-identified usage to understand what's working.
• To communicate service messages (security notices, material changes to these terms, account-related email).

We do not sell coach or athlete data. We don't share it with advertisers. We don't use athlete logs to train public AI models.

Who can see what

• A coach can see the programs they wrote and the session data logged by athletes on their roster.
• An athlete can see their own training history and the programs assigned to them by their coach.
• Athletes cannot see other athletes on the same roster.
• A small number of deload staff can access production data when strictly necessary to operate the Service or respond to a support request, under confidentiality obligations.

Service providers we use

We rely on a short list of vendors to run the Service. They only process data on our behalf and under contract:

• Clerk — authentication and session management.
• Neon / managed Postgres — primary database.
• Replit — hosting and deployment.
• Resend — transactional and check-in emails (once enabled).
• Stripe — payment processing (once paid plans launch). Card details go directly to Stripe; we never see them.
• OpenAI and Anthropic — model providers that power the in-app assistant. Content we send for inference is not used to train their models.

We may add or change providers as the product evolves. When we do, we'll keep this list current.

Payments

deload is free during the private beta. If and when paid plans launch, payments will be processed by Stripe. Stripe collects and stores your card information directly under its own privacy policy. We receive billing metadata (the last four digits of the card, plan, country, status) — not the full card number.

Where data is stored

Production data is stored in the United States with our managed-database provider. If you use the Service from outside the US, you understand and consent to your information being processed in the US.

How long we keep it

• Active accounts. We retain coach and athlete data for as long as your account is active, so the product works the way you expect.
• Deleted accounts. When you delete your account, we remove your personal data and content from production systems within 30 days. Encrypted backups roll off within 90 days.
• Logs. Operational logs (errors, request traces) are kept for up to 90 days.
• Support correspondence. Kept for up to 2 years so we can reference past tickets.
• Legal holds. We may retain specific records longer if we're required to by law.

Your choices

• Access and export. You can view your data inside the app at any time and request an export by writing in.
• Correction. Most fields are editable inside the app. If something isn't, write in and we'll fix it.
• Deletion. You can delete your account from inside the app, or by writing in.
• Email opt-out. You can turn off check-in and product emails in your settings; we'll still send essential service messages (security, account, billing).

If you're in the EEA, UK, California, or another jurisdiction with specific data rights, those rights apply to you, including the right to object to or restrict certain processing. Write in and we'll help.

Security

We use TLS in transit, encrypted storage at rest, scoped access controls, and audit logs. No system is perfect; if we ever have a security incident that affects your data, we'll tell you promptly and explain what we know.

Changes to this policy

If we make material changes, we'll update the "last updated" date above and notify you inside the product or by email before the changes take effect.

Questions or requests? Reach us via the contact page.