Privacy Policy

BeeOn is a workout planning and tracking app. This policy explains what the app records, where it is kept, who else can see it, and what you can do about it. It covers the BeeOn app and the pages on beeon.app.

Everything you record in BeeOn belongs to an account, and one is created for you the first time you open the app. That first account is a guest account: it has no email address, asks you for nothing, and is not tied to your name. It exists so your workouts have an owner and can be backed up before you have decided whether to sign in.

You can sign in later with a code sent to your email address, with Sign in with Apple, or with Google. Signing in adds your email address to the account so the same data can be reached from another device. If you use Sign in with Apple and choose to hide your address, we only ever receive Apple's relay address.

Your workouts, exercises and sets, completed sessions, planned days, logged activities, body fat readings, notes and preferences (units, theme, language, reminders) are written to a database on the device. So are two things that never leave it: your profile photo, and what the app reads from Apple Health. All of it is available offline and is removed when you delete the app.

So your records survive a lost phone and follow you to another device, the app copies the following to our database, which is hosted by Supabase:

• Workouts you build or save — their exercises, sets, target weights and reps, and any notes you write.
• Completed sessions and their history, including any calories or heart rate you enter yourself.
• Planned days in your calendar, and sports activities you log yourself — type, date, duration and the figures you enter.
• Body fat readings you take — the date, your sex, height and weight, the neck, waist and hip measurements, and the body fat percentage worked out from them — and the sex, height and weight on your profile.
• Your display name, if you set one or Sign in with Apple supplies it; your weight and length unit preference; and your daily step goal, if you set one.
• Your email address, once you sign in, and the app's language, so the codes we email you arrive in it.
• The day you last opened the app, recorded at most once a day.

This data is used to run the app — to sync it, back it up and show it back to you. It is not used for advertising and not sold.

With your permission, BeeOn reads from Apple Health: your workouts — the activity type, when it started, how long it lasted and, where recorded, the distance, energy burned, heart rate, elevation gained and steps — and your daily step count and walking and running distance. BeeOn only reads this data; it never writes to Apple Health.

What BeeOn reads from Apple Health stays on your iPhone. It is not uploaded to our servers, never used for advertising or marketing, never sold or shared with third parties, and never stored in iCloud. Earlier versions of the app copied imported workouts to your account; those copies are deleted with it.

You can stop the import at any time under Profile → Settings → Preferences → Apple Health, and revoke access entirely under iOS Settings → Privacy & Security → Health → BeeOn. Stopping the import keeps what was already read on the phone until you delete the app.

BeeOn Pro is an optional, auto-renewing subscription sold through the App Store. Apple takes the payment; we never see your card or your Apple ID.

To know whether your account has Pro, the app uses RevenueCat, a subscription service. RevenueCat receives your account's random identifier and the App Store's record of your purchases — which plan, when it started, and whether it is active or in a free trial. It does not receive your name, your email address or anything you record. You can manage or cancel the subscription in your Apple ID's subscription settings.

The app records usage statistics with Firebase Analytics, a Google service, so we can see which parts are used and where people get stuck. What is sent: the names of the screens you visit; events such as a workout created, a session finished, a body fat reading taken or the Pro screen opened, together with counts and durations; and a few properties describing the app — the kind of account (guest, Apple, Google or email), your weight and length units, the app language, the theme, and whether you have Pro.

What is never sent: your name, your email address, the names of your workouts or exercises, your notes, your body measurements, anything read from Apple Health, share codes, or the identifier of any record. Firebase gives the installation a random identifier, which is not your name and is replaced if you delete and reinstall the app.

When the app crashes or hits an error, Firebase Crashlytics receives a report: what went wrong, where in the code, and the device model, operating system version and app version. The reports are read to fix the fault and nothing else.

The app asks Firebase Remote Config for a few settings, such as the oldest app version still supported and when it may ask you for a review. This is a request to Google's servers; it carries none of your content.

Workout reminders, body fat reminders and rest timers are scheduled by your device, on your device. BeeOn sends no push notifications and collects no notification token.

You can share a workout as a six-character code and a beeon.app link. Anyone holding that code can see the workout's name, description, exercises, sets and notes, and your display name if you have one, without an account — that is what the code is for. Do not put anything private into a workout you share, and revoke the code from the app when you no longer want it read.

“Contact us”, in the app or at beeon.app/contact, sends what you write, along with the name and email address you choose to give, to a table only we can read; sent from the app, it also carries your app version and platform. It is used to answer you and to fix what you reported.

• No advertising, and no ad networks in the app.
• No tracking of you across other apps or websites, and no advertising identifier.
• No sale or rental of your data to anyone.
• No profiling for marketing.

Your records stay until you delete them. Deleting a workout, a session, an activity or a body fat reading removes it from the device at once. On our servers it is marked as deleted, so your other devices learn of it, and is no longer shown anywhere, share codes included; it is erased for good when you delete your account.

“Delete account”, under Profile → Settings, deletes the account and everything stored under it on our servers — guest accounts included — and clears the app's local data, apart from what was read from Apple Health, which stays on the phone until you delete the app. It cannot be undone. Deleting the app removes what is on the device but not what has already been synced, so delete the account first if you want both gone.

Messages you sent us are kept after your account is deleted, no longer linked to it, so we can still answer them. Write to us and we will delete them.

Crash reports and usage statistics are held by Google under Firebase's own retention periods (analytics events for up to 14 months by default) and are not linked to your name.

You can see, correct and delete everything from inside the app, and export your records as a file under Profile → Settings → Export my data. Depending on where you live — the EU and EEA and the UK under the GDPR, Türkiye under the KVKK, and several US states — you may also have the right to ask what we hold about you, to receive a copy, to have it corrected or erased, and to object to some processing. Write to us and we will answer.

Where the GDPR applies: we process your workout and account data, and your subscription status, to provide the app you asked for (performance of a contract); body measurements you choose to enter on the basis of your consent, which you can withdraw at any time by deleting them; and usage statistics and crash reports on our legitimate interest in keeping the app working and understanding how it is used.

Our database and sign-in run on Supabase; usage statistics and crash reporting run on Google Firebase; subscription status runs on RevenueCat; and app updates are delivered by Expo. Each may process data on servers outside your country, including in the United States, under the safeguards set out in their own terms.

BeeOn is not directed at children under 13, and we do not knowingly collect their data. If you believe a child has given us data, write to us and it will be deleted.

When this policy changes, the new version is published on this page with a new effective date.

Questions about this policy, or about your data, go to beeonapp@gmail.com.