In short
Comeback is one app with three parts:
- Recover (Injury Recovery) helps you organize the recovery plan your athletic trainer, physio or doctor gave you.
- Train (No Excuses) looks at your schedule to find free time and suggests short training sessions that fit.
- Learn (Off the Field) organizes your courses and deadlines and turns course materials you upload into study guides, practice and a tutor that helps you learn.
The Home screen shows your day across the parts you use. To do this we need information about you, your schedule, your training, your recovery and your coursework. We use it to run the app and keep its suggestions safe.
We don't sell your data, we don't show ads, and we don't track you across other apps. Our AI provider processes your data only to answer you and doesn't train its models on it. AI features, product analytics, notifications and sharing between the three parts are all off until you turn them on. You can download your data or delete your account inside the app at any time.
Who we are
Comeback ("Comeback", "we", "us") is run by Comeback Technologies LLC, a North Carolina limited liability company, 121 Richmond Pines Dr, Rockingham, NC 28379. We are responsible for the personal information described in this policy.
You can reach us at comeback@comeback-app.net.
This policy covers the Comeback app and the online services behind it. It doesn't cover other companies' apps or websites, even ones you open or connect from Comeback, like YouTube, Google, Google Calendar or your school's learning system.
Comeback is offered in the United States. Our services run in the United States, so if you use Comeback from somewhere else, your information is stored and processed in the United States.
Things we don't do
- We don't sell your personal information, including your health information.
- We don't show ads, and the app has no advertising or ad-tracking tools.
- We don't track you across other companies' apps or websites.
- We don't share your calendar, check-ins, recovery information or coursework with your school, your coaches or your teammates. Teams only see the few things you choose to share (see "Teams and challenges"), and the community only sees the stories and comments you post (see "Community stories").
- We don't collect your contacts, your precise location (GPS), Apple Health or Health Connect data, or advertising IDs. We only get photos and files that you choose to upload.
- We don't let our AI provider train its models on your data.
- We never see your card or bank details. Apple handles payments.
What we collect
Information you give us
| What | Examples | Why we need it |
|---|---|---|
| Account | Email address; how you sign in (email and password, Sign in with Apple, or Google sign-in) | To create your account and sign you in. Sign-in is handled by Supabase; our own servers never see your password. |
| Athlete profile | First name, last name (optional), sport, position, whether you're a student-athlete or working athlete, competition level, training status, experience level, age range, time zone | To tailor the app to you and schedule things at the right local time |
| Preferences | Bedtime and wake time, buffers, meal and other protected times, daily limits, preferred times of day, weekly session goal | So suggestions respect your sleep, meals and limits |
| Training locations | Names you give places (like "Home" or "School gym"), type of place, equipment, travel minutes, opening hours | To suggest drills you can actually do there. We don't ask for addresses and don't use GPS. |
| Goals | Skills you want to work on and their priority | To choose what to suggest |
| Calendar information | See "Calendar data" | To find your free time |
| Training history | Sessions you plan, start, skip or finish; minutes, effort rating, rating, reps and notes; training load; plans; daily goals; streaks; achievements; weekly reviews | To run Train and show your progress |
| Readiness and activity limits | Daily check-ins (energy, fatigue, soreness, hours of sleep, and whether something hurts); the readiness level we calculate; activity restrictions you add (a label, tags like "no running", dates, where it came from, and notes) | To keep suggestions safe. See "Readiness, pain and injury information". |
| Recovery information | See "Recover and consumer health data" | Only if you use Recover |
| Courses and coursework | See "Learn: course materials and study help" | Only if you use Learn |
| Suggestions and feedback | The sessions and study blocks we suggested; whether you accepted, declined or saved them; any reason or note you give | To explain suggestions and make future ones fit you better |
| Messages to AI features | What you type to the coach, the tutor or the recovery explainer, the replies, and technical details (which model answered, token counts, safety and topic flags) | Only if you use those features. See "AI processing". |
| Community stories | Your display name, sport, level and injury type for each story, the story itself, comments, reactions, and reports or blocks you make | Only if you're 18 or older and choose to post. See "Community stories". |
| Teams and challenges | Teams you create or join, your role, your sharing choices, challenges you join, and whether you appear on leaderboards | Only if you use teams. See "Teams and challenges". |
| Invites | Your personal invite code, whose code you used, and the rewards it earned | Only if you're 18 or older and use invites |
| Your choices | What you agreed to or switched on or off (terms, privacy, analytics, AI processing, consumer health data, sharing between parts), with the version and time | To respect your choices and keep a record of them |
| Notification settings | On or off, categories, quiet hours, daily limit; a push token for each device | Only if you turn on notifications |
| Subscription | Your plan, the store, renewal and expiry dates, and purchase events | To give you the features you paid for |
| Feedback and safety reports | Ratings, reasons from a list, optional comments, safety concerns you report | To improve Comeback and follow up on safety reports |
| Messages to us | Anything you send to our support email | To answer you |
If you used Comeback: Injury Recovery before
If you used the earlier Comeback: Injury Recovery app (version 1), your account stays the same. We move the recovery data you saved in that app (your plan, completed tasks, check-ins, milestones and benchmarks) into the current app, from the copy saved to your account and, the first time you open the new version, from what was stored on your phone. Your earlier subscription carries over.
Information collected automatically
- Server logs. When the app talks to our servers, we log a request ID, the kind of request, which part of our service was called, the result and how long it took. Our logs are built to leave out calendar titles, notes, coach and tutor messages, course material, recovery information, passwords and sign-in tokens. Our hosting provider and Supabase also keep standard technical logs, such as IP addresses, under their own practices.
- Abuse protection. We count how many requests each account makes so no one can overload the service. For a few public features that don't need sign-in, we count by IP address for a short time instead.
- AI usage records. For each AI request we record which feature was used, the model, the number of tokens, the cost and whether the message was on topic, so we can apply the usage limits shown in the app. These records don't contain what you wrote or what the AI answered.
- Security records ("audit log"). We record important account actions, such as connecting or disconnecting a calendar, changing activity restrictions, changing your consent choices, and exporting your data. For restrictions we record only that something changed and how many tags were involved, never the details.
- Crash and error reports. When the app or our servers hit an error, we record a technical report so we can fix it. Reports from the app don't include your account ID, and we scrub reports so they don't contain calendar content, notes, messages, course material or health information. We may use Sentry to collect these reports.
- Product analytics, only if you opt in. See "Product analytics".
Stored on your phone
- Your sign-in tokens are kept in your phone's secure storage (the iPhone Keychain).
- A copy of your schedule, suggestions, training and recovery data, and recent study guides and open assignments is saved on your phone so you can use the app offline. The app clears it when you sign out. Keep a passcode on your phone to protect it.
- Things you do while offline wait on your phone until you're back online.
- If you add the Comeback widget, the app saves your streak, today's progress count and your sport for the widget. It never includes your injury, because the widget can show on your lock screen.
- If you turn on product analytics, the app creates a random ID for that installation.
Calendar data
Where it comes from
Adding your schedule is optional. You can also type events in yourself.
| Source | How it works | What we get |
|---|---|---|
| Apple Calendar and other calendars on your phone (including Google or Outlook accounts added to your iPhone) | With your permission, the app reads only the calendars you pick, on your phone, when you open the app or tap Sync | Calendar names, and busy events from yesterday to 30 days ahead: times, all-day or not, and the title (no title if busy-only is on). Not locations. Events marked "free" are skipped. |
| Calendar feed link (ICS), for example from Canvas | You paste a link. Our server downloads it regularly. | The events in the feed. These links often contain a private key, so we encrypt the link. |
| Calendar file (.ics) | You upload a file once | The events in the file |
| Google Calendar or Outlook connection, where the app offers it | You sign in with Google or Microsoft and give Comeback read-only permission. Our server checks for changes regularly. | Your list of calendars, and events from 7 days ago to 60 days ahead: times, time zone, all-day or not, repeats, busy or free, and the title and location (unless busy-only is on). From Outlook we don't get event descriptions, attendees or attachments. |
| Events you add | You type them in | What you enter: title, time, repeats, category and effort |
We also store a category for each event (like class, practice, game or travel) and an effort level, so Comeback can keep hard training away from games and practices and recognize game and travel days.
Busy-only mode
Turn on busy-only and we throw away event titles and locations as soon as they arrive. We keep only the times.
Read-only
Comeback only reads your calendars. It never adds, edits or deletes events in your calendars.
Keeping calendar access safe
The keys that keep a Google or Outlook connection in sync, and private feed links, are encrypted on our servers. They are never sent to your phone and never included in your data export.
Disconnecting
When you disconnect a calendar in the app, we delete the stored access key and every event we imported from it. For Google, we also ask Google to cancel Comeback's access. For calendars on your phone, turn off calendar permission in your phone's settings.
Information from Google and Microsoft
We use calendar information from Google and Microsoft only to find your free time and show your schedule in the app. We don't use it for ads, we don't sell it, and we never send event titles or locations to our AI provider. People at Comeback don't read it unless you ask us to help with a problem, it's needed for security, or the law requires it. Comeback's use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.
Readiness, pain and injury information
Check-ins and activity restrictions in Train are optional, but they make the app safer.
- What it's for. We use this information only to make your suggestions more careful. Check-ins can make suggestions easier, never harder. If you report pain, Comeback pauses physical activities until your next check-in and suggests you talk to an athletic trainer, physio or doctor.
- It's not medical. The readiness level is a simple app calculation, not a medical score. Comeback is not a healthcare provider, and this information is not a medical record.
- Who sees it. It isn't shared with coaches, teammates or anyone else. It isn't sent to our analytics service and isn't written to our logs. The Train coach doesn't receive your check-in answers or restriction details (see "AI processing" for what it does receive).
- Deleting it. You can delete restrictions at any time. Everything is deleted when you delete your account.
We treat this information as consumer health data and collect it only to provide the feature you're using. See "Consumer health data notice".
Recover and consumer health data
Recover is optional. Before it stores anything, it asks for your separate consent to collect consumer health data.
What it holds: the injury or condition you're recovering from, whether you had surgery and when, your recovery phase, the exercises and restrictions your clinician set, notes from your clinician that you enter, your daily check-ins (how you feel, pain, swelling, confidence, sleep, range-of-motion measures and notes), completed tasks, streaks, milestones and benchmarks, journal notes, appointments and your notes after them, clinician instruction sheets you photograph or upload, and progress photos you add.
What it does: organizes your clinician's plan into a daily checklist, reminds you about appointments, and shows your progress over time. With your permission for AI features, it can draft a day or week of tasks around your plan, turn instructions you paste or photograph into a checklist ("Organize my plan"), and explain them in plain language. It never decides when you can return to play, and it never looks at or grades your progress photos.
How-to videos and searches: when you tap a task to learn how to do it, the app opens YouTube or Google with a search for that exercise's name. That search goes to YouTube or Google under their own privacy policies, not ours.
AI processing: see "Recover coach" and "Recover explainer and Organize my plan" under "AI processing".
Files: recovery files are kept in a private storage area that only our servers can reach, up to 25 MB each. Progress photos are never sent to an AI provider.
Deleting it: you can delete any entry or file, delete a whole recovery plan, or delete your account at any time.
Learn: course materials and study help
Learn is optional. It works with what you choose to add.
What you add
- Courses: term, course title and code, instructor name, a color, and the course's AI policy (which you pick, or which we suggest from your syllabus for you to confirm).
- Assignments: title, type, due date, your time estimate, status, and the requirements and questions we extract from instructions you upload.
- Uploaded materials: assignment instructions, syllabi, lecture notes, slides, readings, photos of handouts or whiteboards, and your own attempts at a problem (for "Explain my mistake"). Accepted types are PDF, JPEG, PNG, WebP, Word (.docx), PowerPoint (.pptx) and plain text.
- Study activity: study sessions (start and end time, mode, how many items you reviewed and got right), practice and flashcard reviews, and tutor conversations.
The app doesn't record audio.
How we process uploads
- Your file goes directly from your phone to a private storage area at Supabase through a short-lived upload link. It isn't public and has no link anyone else can use.
- Our servers check the file's real type and size and its structure, to reject files built to cause harm. Files that fail are rejected and their contents deleted.
- We extract the text. For scanned pages and photos, Anthropic's model reads the text from the image.
- We split the text into short passages so the tutor and guides can find the parts of your material that matter. Passages are tied to your account and are never searchable by anyone else.
- If the file is assignment instructions, we extract the title, due date, requirements and key questions. Due dates stay unconfirmed until you check them, and only confirmed dates are used for planning.
How we generate study help
When you ask for a walkthrough, a catch-up lesson, a tutor reply, an "Explain my mistake" review or practice questions, we send Anthropic the relevant passages from that course's materials, your question, and the course's AI policy. We never send your name, email, school, calendar, recovery information or other courses' materials.
- Citations. Guides mark which parts come from your course materials and which come from general knowledge, and they list materials that seem to be missing.
- Academic integrity. Each course has an integrity mode based on your course's AI policy. Depending on that mode, some features are limited or off. The tutor helps you learn: it won't write graded work for you. You're responsible for following your school's rules; see the Terms of Service.
- Wellbeing. If a tutor message suggests you're in distress, the tutor doesn't answer the coursework. It shows supportive wording and points you to campus resources and the 988 Suicide & Crisis Lifeline. We record that this happened so we can check the safety feature works; people at Comeback don't read your conversation unless you report a problem.
Who can see it
Only you. Your course materials, assignments, guides and tutor conversations aren't shared with your school, instructors, coaches or teammates, and aren't used to help other users.
Sharing between the three parts
Each part keeps its own data. A part can use a small, derived signal from another part only if you switch that signal on in Profile → Privacy & sharing. All of them are off by default, and you can switch each one off at any time.
| Signal | What crosses | What never crosses |
|---|---|---|
| Academic workload (Learn → Train and Home) | For today and tomorrow: minutes of confirmed work due and whether an exam is due. Used to protect study time and reduce optional training. | Course names, assignment titles, materials, grades, tutor conversations |
| Recovery limits (Recover → Train and Home) | Activity-limit codes like "no running" or "light work only" | Your injury or condition, pain and other entries, journal, photos, clinician notes |
| Training load (Train → Recover) | Daily training minutes and effort, so Recover can show your load | Drill details, session notes, check-in answers |
Signals stay inside Comeback and are used only for your own plan and Home screen.
Community stories
People 18 and older can share their comeback story with other Comeback users. If you post:
- Other users see your display name, sport, level, the injury type you pick, and your story. Comments you post show your display name. Don't include your full name, contact details or anything you want to keep private.
- Stories are checked by a person at Comeback before they appear. Comments appear right away, and our filter blocks links, phone numbers, email addresses and slurs.
- Other users can react to, comment on, report or block. Reports are reviewed by a person at Comeback, and we may remove content that breaks the Terms of Service.
- You can delete your stories and comments at any time. They're deleted when you delete your account.
Users 13 to 17 can read stories but can't post stories or comments or set a display name.
Teams and challenges
You can create or join a team with an invite code. Inside a team:
- Members see each other's first name and last initial, and whether each person is a coach or an athlete. They never see your email or account ID.
- Each member chooses what the team sees, and everything starts switched off: training completion (sessions and minutes in recent weeks, active days and current streak), goal names, and your five newest Train achievements. Coaches see the same as teammates, nothing more.
- Teams never see your schedule, calendar events, readiness or pain check-ins, injury details, recovery plan or journal.
- Challenge progress is counted from what you log. Leaderboards show only people who choose to appear; athletes under 18 start hidden.
- When you leave a team, your sharing switches turn off and your challenge entries in that team are deleted.
AI processing
AI features are optional. Before the first AI request, the app asks for your permission and tells you which provider receives what. If you say no, every feature that doesn't need AI keeps working. When you use the coach, the tutor or the explainer, you're talking with an AI, not a person.
| Provider | What it does | What it receives |
|---|---|---|
| Anthropic | The Train coach, the Recover coach, the recovery explainer and "Organize my plan", reading text from images, assignment extraction, study guides, catch-up lessons, tutor replies, mistake reviews and practice questions | Only what each feature needs, as described below |
- No training on your data. We use Anthropic under business terms that don't allow it to use your data to train its models. If we ever add another AI provider, we'll only use one on terms like these, and we'll update this policy and ask for your permission first.
- Only what's needed. Every request is built on our servers from a fixed list of fields for that feature. Requests never include your name or email.
- Provider retention. Anthropic deletes our requests and its replies within 30 days. If its automated safety systems flag a request as breaking its usage policy, it may keep that request for up to 2 years.
- Staying on topic. We check that messages are about training, recovery or school. If an account keeps using AI features for unrelated things, we pause them for that account for a day.
- AI can be wrong. See the Terms of Service.
Train coach
What we send: our instructions for how the coach must behave and internal safety flags; your sport, position and goal names; your local time, your readiness level (like "good" or "low"), today's intensity limit and how much you've trained today; today's suggested sessions and the drills that are safe for you today; a short summary of the last 30 days (sessions completed, extra minutes, current streak); and your message, plus up to 8 earlier messages from the same conversation, leaving out any message about pain, injury, urgent symptoms or a personal crisis and the reply to it.
What we don't send: your email, your name, calendar event titles or locations, your session notes, your check-in answers, or your restriction labels and notes.
Safety. If your message mentions pain, injury, urgent symptoms or a personal crisis, or if physical training is paused for you today, the coach answers with fixed safety wording and doesn't use the AI provider. When AI features are off, a built-in coach on our own servers answers instead.
Recover coach
When you tap "Draft today" or "Draft my week", we send: our instructions for how the coach must behave; the injury name and body area, whether you had surgery, your sport, recovery phase and how many days into your recovery you are; the clinician notes you entered (up to 600 characters); your other recent recovery plans (injury, sport and whether you had surgery); your current activity limits and what your clinician cleared; your notes after recent appointments (up to 300 characters each); your check-ins from the last 7 days (how you felt, pain, swelling and a short note, up to 200 characters each); and today's tasks.
What we don't send: your name, email, school, photos, files or anything from Train or Learn.
Safety. If you logged high pain recently, the draft is limited to recovery work and tells you to contact your clinician. Every draft is checked against your activity limits before you see it, and nothing changes in your plan until you apply it.
Recover explainer and "Organize my plan"
The explainer sends your question, the earlier messages in that conversation, your injury as you described it, your recovery phase, today's tasks and the clinician notes you entered (up to 2,000 characters). "Organize my plan" sends the clinician instructions you paste or photograph. Neither sends your name, email, school, journal or progress photos.
Whatever you type goes to the provider
Please don't type things you don't want shared, like health details you don't need to share or other people's names or contact information.
History
We save coach, tutor and explainer conversations so you can read them again. Tutor conversations are deleted automatically after 365 days. You can delete conversations at any time. Switching AI features off stops new requests going to the provider but doesn't delete past conversations; delete them separately if you want.
AI features can't change your calendar, your sessions or your recovery plan without you.
Product analytics
Analytics are off by default. If we offer product analytics and you switch them on in Profile → Privacy & sharing:
- The app sends a short, fixed list of usage events to PostHog, in the United States, such as onboarding completed, suggestion accepted or declined, session completed, guide opened, or a message sent to the coach or tutor (only that one was sent, not what it said).
- Events carry only small details, such as the reason you picked from a list, a length in minutes, or the plan type.
- Events use a random ID for your installation, not your account ID, email or name.
- We never send calendar data, names, check-ins, recovery information, course material, notes, messages or anything you type.
You can switch analytics off at any time. Because events aren't linked to your account, we may not be able to find them for an export or deletion. They're kept for up to 12 months.
Notifications
Notifications are off by default. They only start if you switch them on in the app and allow them in your phone's settings. You choose which kinds you get, quiet hours (10 pm to 7 am to start with) and a daily limit (4 to start with).
To send push notifications, we store a push token for your device and send notifications through Expo's push service, which passes them to Apple. Notifications can show on your lock screen, so they never include calendar event titles, injury details, pain levels, restriction details, grades or course names. Some reminders, like your Recover morning reminder, are set up directly on your phone.
Subscriptions and payments
Comeback Pro is sold through the Apple App Store. Apple takes the payment; we never see your card details. We use RevenueCat to check and manage purchases. The app identifies you to RevenueCat with your random Comeback account ID, not your email. RevenueCat tells us about purchases, renewals, cancellations and refunds, including the product, price, currency, country code and dates.
Deleting your account does not cancel a subscription. Cancel it in your App Store settings.
How we use your information
We use your information to:
- run your account and the app;
- find your free time, suggest sessions and study blocks that fit, explain why, and re-check booked sessions when something changes;
- keep suggestions safe using your readiness, pain reports, activity limits, team schedule and training load;
- organize your recovery plan, if you use Recover;
- organize your courses and deadlines and create study help from materials you upload, if you use Learn;
- combine signals between the three parts, only for the signals you switched on;
- show your progress for each part separately;
- show the stories, comments and team information you chose to share;
- answer you through AI features, only if you allowed them;
- send notifications, only if you turned them on;
- provide paid features, invite rewards and manage subscriptions;
- move your data over from Comeback: Injury Recovery 1.x, if you used it;
- keep Comeback secure, prevent abuse, review reports, apply usage limits and fix problems;
- read feedback and follow up on safety reports;
- reply when you contact us;
- understand how the app is used and improve it (usage events only if you opted in to analytics);
- follow the law and protect our rights and the safety of our users.
We don't use your information for ads, and we don't use your uploads, messages or health information to train AI models. Comeback makes suggestions automatically, but you always decide what to do.
Who we share information with
We share information only with service providers that help us run Comeback, and only what they need for their job. They may use it only to provide their service to us.
| Provider | What they do | What they get |
|---|---|---|
| Supabase | Sign-in, our database and private file storage | Your email and sign-in details, everything stored in our database, and your uploaded files |
| Resend | Sends account emails (like confirming your email or resetting your password) | Your email address and the email's content |
| Render | Runs our servers and background workers | Everything our servers process, including technical logs |
| Anthropic | AI features, only if you allowed them | The items listed under "AI processing" |
| Apple | Sign in with Apple, App Store purchases, TestFlight test builds, push notifications | What each of those needs |
| Google sign-in; Google Calendar, only if you connect it | What each of those needs | |
| Microsoft | Outlook calendar, only if you connect it | Our requests to read your calendars |
| Whoever hosts your calendar feed | Only if you add a feed link | Our server's request to download that feed |
| RevenueCat | Checks and manages subscriptions | Your random account ID and purchase information from the store |
| Expo | Builds the app and delivers push notifications | Your device's push token and the notification text |
| PostHog | Product analytics, only if you opted in | The events listed under "Product analytics" |
| Sentry | Helps us find and fix errors, if we use it | Technical error details, scrubbed of calendar content, notes, messages, course material and health information |
We may also share information:
- if the law requires it, or to respond to valid legal requests;
- to protect the safety, rights or property of our users, the public or Comeback;
- if Comeback is sold or merged, in which case we'll tell you, and your information stays protected by this policy or one that protects it at least as well (health information is never transferred without the consent the law requires);
- when you ask us to, or when you share it yourself (for example, a story you post or a data export you send).
How long we keep information
| Information | How long |
|---|---|
| Your account and app data | Until you delete it or delete your account, unless a shorter period is listed below. Account deletion removes it from our database right away. |
| Uploaded course materials and their extracted text | 300 days after upload. When you archive a course, its materials are kept until 180 days after the end of the term instead. Then they're deleted automatically. You can delete any file or course sooner. |
| Tutor conversations | 365 days after they start, or sooner if you delete them |
| Study guides, practice items and study sessions | Until you delete them, their course or your account |
| Recovery information and files | Until you delete them, the plan or your account |
| Stories and comments | Until you delete them or your account |
| Things you delete yourself | Removed from our database and file storage when you delete them |
| Feedback and safety reports | Until you delete your account |
| AI usage records (no content) | While your account exists. When you delete your account, the link to you is removed. |
| Temporary data while you connect Google or Outlook | About 10 minutes |
| Security records (audit log) | 365 days. When you delete your account, these records lose their link to you and their details. |
| Records of notifications sent | 30 days, or until you delete your account |
| Purchase records | 7 years, for accounting and tax. When you delete your account, we remove your account ID, email and other details and keep only the product, price, currency, store, country code and dates. |
| Proof that we deleted your account | As long as we run Comeback. We keep only a scrambled code made from your account ID with a secret key, not your email or name. |
| Database backups | Up to 30 days, where our hosting plan keeps backups. Deleted data can stay in backups until they expire. |
| Server logs | Up to 30 days |
| Product analytics | Up to 12 months |
| Support emails | Up to 3 years after your last message |
| Data held by our providers | Under their own terms (for Anthropic, see "AI processing") |
Your choices and rights
What you can do in the app
- See and download your data. Go to Profile → Privacy & sharing → Export my data. You get a file (in JSON format) with what we store about you, including your profile, preferences, calendars and events, sessions and check-ins, restrictions, suggestions and feedback, plans, goals and progress, recovery records, courses, assignments, the list of your uploaded files, guides and conversations, stories and team memberships, consent choices, notification settings, push tokens (shortened) and subscription. For safety it leaves out calendar access keys, feed links and other secrets. The file opens in your phone's share menu, so be careful where you send it.
- Fix your information. Edit your profile, preferences, locations, goals, events, restrictions, recovery plan, courses and assignments in the app. To change the email on your account, contact us.
- Delete pieces of data. Delete events, restrictions, connected calendars, uploaded files, courses, assignments, guides, recovery entries and plans, stories, comments and conversations.
- Change your choices. Switch AI features, sharing between the three parts, team sharing, product analytics and notifications on or off at any time.
- Sign out to clear the saved copy of your data from that phone.
Deleting your account
Go to Profile → Delete account, type DELETE, and confirm. You can also email us at comeback@comeback-app.net from the email address on your account.
When you delete your account:
- we permanently delete your profile, preferences, calendars and imported events, sessions, check-ins, restrictions, goals, progress, recovery records and files, courses, assignments, uploaded files, guides, conversations, stories and comments, team memberships, feedback, notification settings, push tokens and consent records;
- we delete your sign-in account at Supabase, which also deletes anything saved by Comeback: Injury Recovery 1.x. If that can't happen automatically, we remove it by hand within 30 days;
- we ask Google to cancel Comeback's calendar access, if you connected Google Calendar;
- sign-in tokens issued before the deletion can't be used to bring the account back.
What stays afterwards:
- purchase records with your account ID, email and other details removed, for accounting;
- security records and AI usage records, with the link to you and the details removed;
- a scrambled code made from your account ID, as proof we deleted your account;
- anything in backups, until the backups expire;
- product analytics events, if you had opted in (these aren't linked to your account);
- what Anthropic keeps for its limited retention period;
- things outside Comeback, like a data export you shared and what Apple and RevenueCat keep about your purchases.
Deleting your account does not cancel a subscription. Cancel it in your App Store settings.
Your privacy rights
Depending on where you live, you may have the right to:
- know what information we have about you and get a copy;
- correct it;
- delete it;
- get it in a format you can move to another service;
- object to, or limit, some uses of it;
- withdraw your consent;
- appeal if we say no to your request;
- complain to your state attorney general.
The in-app tools above handle most requests straight away. For anything else, email comeback@comeback-app.net. We may need to check it's really you, usually by asking you to write from the email on your account. We'll reply within 45 days. If we say no, we'll explain why and how to appeal: email us with "Appeal" in the subject line. Where the law allows, someone you authorize can make a request for you. We won't treat you differently for using your rights.
Consumer health data notice
This notice is for residents of Washington, Nevada, Connecticut and other places with consumer health data laws. It applies to readiness check-ins, pain reports, activity restrictions, and everything in Recover.
- What we collect: the health information described in "Readiness, pain and injury information" and "Recover and consumer health data".
- Where it comes from: you, documents and photos you choose to upload, and, if you used it, the Comeback: Injury Recovery 1.x app. We don't buy health information or get it from other companies.
- Why: only to provide the features you use: safer training suggestions, your recovery checklist and progress, recovery limits for Train (if you switch them on) and AI help in Recover (if you allow AI features).
- Consent: we ask for your consent before collecting health information in Recover, and for separate consent before sharing it with anyone other than our service providers. You can withdraw consent at any time in Profile → Privacy & sharing.
- Who receives it: only the service providers that run Comeback for you (Supabase, Render and, for the AI features you use, Anthropic), and anyone you choose to share it with. We don't have affiliates that receive it.
- We never sell it and never use it for ads. We don't use geofences around healthcare locations.
- Your rights: to confirm whether we hold your health information and get a copy, including a list of the third parties and service providers we've shared it with; to delete it; and to withdraw consent. Use the in-app tools or email comeback@comeback-app.net. If we refuse a request, you can appeal by email with "Appeal" in the subject line and, if we turn down your appeal, contact your state attorney general.
How we protect your information
- Information between the app and our servers travels over encrypted connections (HTTPS).
- Calendar access keys, private feed links and your recovery notes are encrypted on our servers, and the encryption key is kept separately from the database.
- Uploaded files are kept in private storage; the app reaches them only through short-lived links our servers create.
- Every request is checked to make sure it really comes from you, and you can only reach your own data.
- Our database can't be read directly through Supabase's public data interface; everything goes through our own servers.
- Sign-in tokens on your phone are kept in secure storage.
- We limit how many requests can be made, and our logs leave out calendar titles, notes, messages, course material, health information and tokens.
No system is perfectly secure. If you find a security problem, please tell us at comeback@comeback-app.net.
If there's a breach
If your information is involved in a security breach, we'll tell you and the authorities as the law requires. For health information, we follow the FTC Health Breach Notification Rule: if there's unauthorized access to or disclosure of your unsecured health information, including sharing it without your authorization, we'll notify you without unreasonable delay and no later than 60 calendar days after we discover it, by email and in the app. We'll also notify the Federal Trade Commission and, where 500 or more residents of a state are affected, prominent media, as that rule requires.
Where your information is stored
Our database and files are hosted by Supabase in the United States (Virginia), and our servers are run by Render in the United States (Virginia). Our providers, including Anthropic, process information in the United States and may also process it in other countries under their own safeguards.
Notices for US states
California
This section applies to California residents.
| Category under California law | What it means for Comeback | Disclosed for business purposes to |
|---|---|---|
| Identifiers | Email, account ID, push token, random analytics ID (if you opted in) | Supabase, Render, Resend, RevenueCat, Expo, PostHog (if you opted in) |
| Personal information records | Your name | Supabase, Render |
| Characteristics of protected classifications | Age range | Supabase, Render |
| Commercial information | Subscription and purchase history | Supabase, Render, RevenueCat, Apple |
| Internet or other electronic network activity | How you use the app; analytics events (if you opted in); server logs | Supabase, Render, PostHog (if you opted in), Sentry (if we use it) |
| Education information | Courses, assignments, uploaded materials, guides, tutor conversations, study activity | Supabase, Render, Anthropic (the parts each feature needs) |
| Sensitive personal information | Account sign-in details; readiness, pain, injury and recovery information | Supabase, Render, Anthropic (for the AI features you use) |
| Inferences | Readiness level; training and study suggestions | Supabase, Render, Anthropic (readiness level, if AI features are on) |
| Other information | Calendar events, training history, coach messages, stories and comments | Supabase, Render, Anthropic (coach messages and today's session times, if AI features are on) |
- Sources: you, your phone, the calendars you connect, files you upload, Comeback: Injury Recovery 1.x (if you used it), and Apple and RevenueCat (for purchases).
- Purposes: see "How we use your information". Retention: see "How long we keep information".
- No sale or sharing: we don't sell personal information or share it for cross-context behavioral advertising.
- Sensitive personal information is used only to provide the service you asked for.
- Your rights: to know, delete and correct, and not to be treated differently for using your rights. See "Your privacy rights".
- "Shine the Light": we don't share personal information with others for their own direct marketing.
Other US states
If you live in a state with a comprehensive privacy law (for example Colorado, Connecticut, Oregon, Texas or Virginia), you may have the rights listed in "Your privacy rights", including the right to appeal. To appeal a decision, email us with "Appeal" in the subject line. If we turn down your appeal, you can contact your state attorney general. We don't use your personal data to train large language models.
Age requirement
Comeback is for people 13 and older.
- We ask for an age range, not your birth date.
- If you tell us you're under 13, we don't create your account, and we delete anything already stored. We don't knowingly collect information from children under 13.
- If we learn that we have information from a child under 13 in any other way, we'll close the account and delete it. Parents who think this has happened can email us.
Teens (13 to 17)
Teens can use Comeback, including Recover and Learn. A few things work differently to protect them:
- Community stories: teens can read stories but can't post stories or comments, so adults and teens don't talk to each other there.
- Teams: teens join with a code from a coach. They can't create a team or be a coach or admin, and they start hidden from every leaderboard (they can choose to appear). Teammates see only what a teen chooses to share.
- Health information: a teen gives their own OK before Recover stores health information, the same way adults do. We never sell it and never use it for advertising.
- Invites: invite codes and rewards are for people 18 and older.
We encourage teens to go over this policy with a parent or guardian.
Changes to this policy
We'll update this policy when Comeback changes. Every version has a version number and a "last updated" date at the top, along with a list of changes. Earlier versions are listed at comeback-api-prod.onrender.com/legal. If we make an important change, such as collecting a new kind of health information or using information in a new way, we'll tell you in the app before it takes effect and, where the law requires, ask for your consent again. The app records which version of this policy you accepted.
Contact us
- Email: comeback@comeback-app.net
- Mail: Comeback Technologies LLC, 121 Richmond Pines Dr, Rockingham, NC 28379