Privacy Policy

1. The short version

In plain language

Become collects what it needs to coach you: your email address, your body stats, what you train, what you eat, how you feel, and photos you take of your meals.
We do not sell your personal information, we do not share it for advertising, we do not use it to track you across other companies’ apps or websites, and there are no third-party ad trackers in the app.
A small number of named service providers process data for us. They are listed in section 8, and there are six of them.
One of them is an AI provider, Google Gemini. We ask for your permission before anything you submit is sent to it, we do not send anything until you give it, and you can withdraw it in Settings. Section 7 says exactly what is sent.
We never see your card number. Stripe handles payment.
You can ask for a copy of your data, ask us to correct it, or delete your account yourself from Settings — in the app or on the web. Section 12 covers the rest of your rights and section 13 covers deletion.

2. Who we are, and what this covers

Become LLC is a New York limited liability company formed on August 1, 2026, and is the controller of the personal information described here. This policy covers the Become app and website at becomeurbest.com and become.redbtn.io, including the installable version you can add to your home screen, and the Become apps on the App Store and Google Play.

On the App Store, the Become app is distributed under the seller name REDBTN LLC, which operates the platform Become runs on. Become LLC is still the company responsible for your information as described here.

It does not cover anything you reach by leaving Become, such as Stripe’s own checkout pages or Apple’s and Google’s sign-in screens. Those are governed by their own policies.

3. What we collect

Account: Your email address, your name, the account identifier we assign you, which sign-in method you use (an email link, Google, Sign in with Apple or a passkey), the Apple or Google account identifier if you sign in with one of them, the public key and identifiers for any passkey you register, and the session token that keeps you signed in. We do not store a password for any of these sign-in methods.
Profile and body data: Height, current weight, goal weight, age or date of birth, biological sex, experience level, training days per week, available equipment, and your unit preferences. These set your training and nutrition targets, and the calculations do not work without them.
Injury and limitation notes: Anything you type about injuries, restrictions, or movements and equipment you cannot use, so programs and generated sessions can work around them.
Training data: Workouts logged, sets, reps, load, rest, personal records, session notes, your schedule, streaks, and any custom exercises, sessions and programs you build.
Nutrition data: Meals and foods logged, portions and macros, custom foods, meals and recipes, meal plans, barcode scans, and the photos of meals you scan. Recipes you create are private to you by default.
Mind and mood data: Mood ratings, journal entries, mindset session progress, non-negotiables, goals and reflections.
Photos and images: Meal photos, profile and progress photos, and images you attach to programs, recipes or custom exercises.
Device and notification data: Your browser push subscription (an endpoint and keys, if you turn notifications on), your time zone offset, your device and browser type, and your in-app settings.
Native push token: If you use the Become app from the App Store or Google Play and allow notifications, we store the push token your device issues. On iPhone it is a device token from the Apple Push Notification service (APNs), and on Android a registration token from Firebase Cloud Messaging (FCM). It is the address Apple’s and Google’s push services use to reach that one installation. It identifies the installation, not you, and we hold it only to send the notifications you turned on. Turning notifications off in Settings or in the operating system, or deleting your account, removes it.
Usage and diagnostic data: Which features you use, how much of an AI allowance you have used, error and diagnostic logs, and the IP address and timestamps recorded in server logs.
Payment metadata: Become never sees, receives or stores your card number, CVC or bank details. Stripe does. What we hold is your Stripe customer identifier, your plan and subscription status, your billing period dates, and whether each charge succeeded or failed.
Communications: Emails you send us, in-app feedback and support messages you submit, and anything you post to a community group or event. Feedback sent from the app also carries the diagnostics needed to look into it: the app version and build, your operating system and version, your device model, and any screenshots you attach.

4. Where it comes from

From you, when you sign up, fill in your profile, log a workout or a meal, write a journal entry, or take a photo.
From your device, for your time zone offset and, if you turn them on, push notifications: a browser push subscription in the web app, or a native push token issued by Apple’s push service (APNs) or Google’s (FCM) in the App Store or Google Play app.
From your device, if you register a passkey: its public key and identifiers. The private key stays on your device or in your password manager and never reaches us.
From Google, if you choose to sign in with Google: your email address, your name, your profile picture and a Google account identifier.
From Apple, if you choose Sign in with Apple: an Apple account identifier and, the first time only, the name and email address you choose to share. That address can be a private relay address Apple creates, which forwards to your real one.
From Apple Health on iPhone or Health Connect on Android, only if you turn on Health sync in Settings → Profile. Each direction is its own switch and both start off. With reading on, we import your weigh-ins and the workouts another app actually tracked (an Apple Watch run, a Strava ride, a Whoop or Oura session), each with its type, start and end time, duration, distance, energy and the name of the app that recorded it. We do not read any other type of health data. With writing on, we save the weigh-ins you log in Become and the workouts you finish in Become to the same store. Turning a switch off, or revoking Become’s access in the Health app or Health Connect, stops it the next time you open Become.
From Stripe, for the outcome of a payment and the state of your subscription.

5. Why we use it, and our legal bases

The legal bases below are the wording used in the EU and UK GDPR. If you are elsewhere, they still describe honestly why we hold what we hold.

To run the Service: Your account, your programs, your logs and your history. Basis: performance of our contract with you.
To personalise targets and recommendations: Calorie and macro targets, training load, suggested sessions. Basis: performance of our contract, and, for health-related data in the EU and UK, your explicit consent (see section 6).
To produce AI estimates and generated sessions: Only on the input you submit for that request, and only once you have given the separate AI permission described in section 7. Basis: your consent, which you can withdraw in Settings at any time, and performance of our contract for the feature itself.
To take payment and manage subscriptions: Basis: performance of our contract, and legal obligation for financial records.
To send transactional email: Sign-in links, receipts and account notices. Basis: performance of our contract.
To send push notifications and reminders: Only the ones you turn on. Basis: your consent, which you can withdraw in Settings at any time.
To keep the Service secure and stop abuse: Rate limits, allowance counting, fraud and abuse signals. Basis: our legitimate interests in a working, non-abused product.
To fix bugs and improve the product: Error logs and aggregate feature usage. Basis: our legitimate interests.
To comply with law and defend claims: Basis: legal obligation, and our legitimate interests.

6. Health-related data, and HIPAA

Become is not a HIPAA covered entity

Become is not a healthcare provider, a health plan or a healthcare clearinghouse, and it is not a business associate of one. HIPAA does not apply to the data you put into Become.
That does not mean the data is unprotected. It means the rules that protect it are this policy, our contracts with our processors, and applicable state and international privacy law, rather than HIPAA.

Weight, body measurements, biological sex, injury notes, mood ratings, journal entries and photos of your meals are personal, and in some places they are treated as sensitive or health-related information. We collect them because the product cannot set your targets or build your program without them.

You decide how much to write. You can use Become without injury notes or journal entries, though some features will be less useful. In the EU and UK, where our basis for this category is your explicit consent, you give that consent by choosing to enter the data, and you can withdraw it by deleting the data or your account.

Apple Health and Health Connect. If you turn on Health sync, the weigh-ins and tracked workouts we read from Apple Health (HealthKit) or Health Connect are stored with the rest of your history and used for one thing: to show your progress and count the day you trained. We never use data from Apple Health or Health Connect for advertising or marketing, we never sell it, and we never disclose it to a third party except the processors in section 8 that host and run Become for us. Nothing we read from either store is used to train an AI model. Deleting your account deletes our copy; the data in Apple Health or Health Connect itself is yours and stays there.

Washington and Nevada treat this category as consumer health data and require a separate policy for it. Ours is the Consumer Health Data Privacy Policy. It describes the same practices as this document, in the shape those laws ask for, and it applies to every member wherever they live.

7. AI processing, and the permission you give for it

Nothing goes to the AI until you say it can

Become asks you, separately from the Terms, before anything you submit is sent to Google Gemini. Until you agree, no meal photo, no description, no workout input, no injury note, no Mind session input and no message you write to the coach leaves Become for the AI provider.
The request is refused rather than sent, and the feature falls back to its non-AI version. That is enforced on the server, on every AI route, and it is checked for each request rather than cached.
You can withdraw the permission at any time in Settings → AI features. Withdrawing stops the next request; it cannot recall a request already answered.
Saying no is a complete answer. Become still logs your food, builds your sessions and runs your Mind work from its own non-AI versions.

With your permission, and only then: when you scan a meal, generate a workout or run a mindset session, the input for that request is sent to Google Gemini, which Become reaches through the redbtn platform it runs on. Only what the request needs is sent: for a meal scan, the photo or description and the context needed to interpret it.

What that covers, in full:

Meal photos and the descriptions you type with them, when you scan or describe a meal.
The inputs behind a generated workout or program, which can include your injury notes.
The inputs for a Mind session, and what you write to the coach in chat.
A short summary of your profile and progress, assembled by Become, so the answer fits you.

We record that you gave the permission, which version of this disclosure you gave it against, and when — the same way we record your agreement to the Terms. A withdrawal is recorded with its own date.

What comes back is an estimate. The Terms explain what that does and does not mean.

No automated decision in Become produces a legal or similarly significant effect on you. AI output sets suggestions and estimates. It never decides your eligibility, your price or your access.

9. What we do not do

We do not sell your personal information.
We do not share it for cross-context behavioural advertising.
We do not run third-party advertising or advertising trackers in the app.
We do not use your information to track you across other companies’ apps or websites, and we do not share it with data brokers.
We do not post anything to your social accounts.
We do not read your journal entries or your injury notes except where you ask us for support and it is necessary to answer you, or where the law requires it.

10. How long we keep it

Account, training, nutrition and mind data: kept while your account exists, so your history stays useful to you.
After a deletion request: your account is scheduled for deletion immediately, you have 7 days to undo it, and everything is then removed — always within the 30 days we commit to, except for copies sitting in routine backups until those backups age out on their normal schedule.
Sign-in links: deleted automatically 15 minutes after they are created, whether or not they were used.
Payment records: Stripe keeps its own transaction records for its legal and tax obligations, and we keep the minimum billing metadata we need for accounting. Financial and tax records are kept for 6 years, as New York law requires.
Server logs: kept only as long as they are useful for diagnosing problems and spotting abuse.

11. Security

What we actually do, stated without decoration:

Traffic between your device and Become is served over HTTPS.
Sign-in is passwordless, so there is no password of yours to be stolen, guessed or reused somewhere else.
Session tokens are signed and expire.
Card details never reach our servers, because Stripe collects them.
Access to production data is limited to a small number of people who need it.

We do not hold SOC 2, ISO 27001, HIPAA or any other security certification, and we do not claim one. No system is perfectly secure, and we cannot guarantee that a determined attacker will never get in. If you find a vulnerability, please email us before telling anyone else.

12. Your rights, and how to use them

Wherever you live, you can ask us to:

Tell you what personal information we hold about you, and why.
Give you a copy of it in a portable format.
Correct anything that is wrong.
Delete your account and the information attached to it.
Stop sending you notifications, or withdraw a consent you gave.
Restrict or object to a particular use, where the law gives you that right.

To do any of these, email [email protected] from the address on your account and say what you want. Emailing from the account address is how we verify it is you; we will not ask you for identity documents unless there is no other way to be sure. We aim to answer within 30 days, and we will tell you if we need longer.

We will never treat you worse, charge you more or give you less because you exercised a privacy right.

13. Deleting your account

How deletion works

You can delete your account yourself, from inside the app. Open Settings, scroll to Delete account, and confirm. It is two taps, on the web and in the App Store and Google Play builds alike.
Confirming signs you out on that device and stops notifications to every device straight away.
We email you a link that undoes it. You have 7 days to change your mind; after that the account and the data attached to it are permanently deleted, which is well inside the 30 days we commit to.
If you cannot sign in, email [email protected] from the address on your account and ask us to delete it. The public page at become.redbtn.io/delete-account says the same thing without a login.
Cancel your paid plan first, or ask us to cancel it as part of the same request, so a renewal is not charged while the deletion is in progress. Deleting your account does not by itself refund a payment.

Deletion covers your account record and the data attached to it: your profile and body stats, injury notes, training logs and schedules, nutrition logs and custom foods, meals and recipes, mind and mood data and journal entries, uploaded photos, push subscriptions (web push endpoints and the push token your phone issued to the app), and posts you authored in groups and events.

Some things do not simply disappear, and you should know which:

Billing records that Stripe and we are required to keep for tax and accounting.
Entries in the shared food and exercise catalogues that other members’ logs already reference. Those are separated from you rather than deleted, so that other people’s history does not break.
Copies in routine backups, until those backups age out on their normal schedule.
Anything we are required to keep to comply with a legal obligation or to defend a legal claim.

14. Children

The Service is not directed to children under 13, and we do not knowingly collect personal information from them. If you believe we have, email [email protected] and we will delete it. The minimum age for an account is in section 4 of the Terms.

15. California

This section is for California residents, and covers both CalOPPA and the CCPA as amended by the CPRA.

This policy is linked from the Become home page and from the sign-in screen, in both cases with the word "Privacy". Section 3 lists the categories of personal information we collect, section 5 says why, section 4 says where it comes from, section 8 says who receives it, and section 18 says how you will learn about changes.

In CCPA terms, the categories we collect are: identifiers (email address, account identifiers, device push tokens, IP address); customer records (name); commercial information (your plan and subscription status); internet or network activity (feature usage and diagnostics); sensitive personal information (health-related information you enter, such as weight, biological sex, injury notes, mood and meal photos); and inferences drawn from the above (such as your calculated calorie and macro targets).

We have not sold or shared personal information in the preceding 12 months, including the personal information of anyone under 16. We use sensitive personal information only to provide the Service you asked for, which is a purpose the CCPA permits without a separate right to limit.

Californians may exercise the rights to know, delete, correct, opt out of sale or sharing (which does not arise here), limit the use of sensitive personal information, and not be discriminated against. Use the process in section 12.

Do Not Track: browsers send this signal in inconsistent ways and there is no agreed standard for responding to it, so we do not respond to it. We do not track you across other websites in any case. Under California’s Shine the Light law, we do not disclose personal information to third parties for their own direct marketing.

We do not sell or share personal information, so there is no sale or sharing for a Global Privacy Control signal to opt out of. You can still exercise the rights in section 12 at any time.

An authorised agent may make a request for you if they can show they are authorised, and we will confirm it with you directly.

16. Europe and the United Kingdom

Become is reachable worldwide, so this section applies if you are in the EEA, the UK or Switzerland. Become LLC is the controller. Our legal bases are in section 5.

You have the rights to access, rectification, erasure, restriction, portability and objection, and the right to withdraw a consent at any time without affecting what was done before you withdrew it. You can also complain to your local supervisory authority, or to the Information Commissioner’s Office in the UK.

17. International transfers

Become operates from the United States and its processors are principally United States companies. If you use Become from outside the United States, your personal information is transferred to and processed in the United States, which may not give it the same protection as the law where you live.

18. Changes to this policy

We may update this policy. The version and the date at the top of this page always show what is current. If a change materially affects how we handle your personal information, we will tell you by email or in the app before it takes effect.

19. Contact

Privacy questions, requests and complaints: email [email protected], or write to us at the address at the bottom of this page. For help using the app, see Support.