Privacy

Ozees is the training app at ozees.app. Questions about this policy or your data go to contact@ozees.app.

• Your account: your name and email address, and the one-time sign-in codes we email you, which expire after 15 minutes.
• Your signed-in devices: each sign-in records the device’s IP address and browser details, so you stay signed in for up to 90 days.
• Your training: the program you run, every session and set (weight, reps, time, notes, substitutions), activities like walks or runs, bodyweight, starting weights and the equipment you have.
• Check-ins: your answers to your coach’s questions, including a photo if a question asks for one.
• Meals: the photos, the meal, the time, any note, and the foods you add with their calories, protein, carbs and fat. Also the hunger and energy you rate a day, and the food plan your coach writes for you.
• Comments between you and your coach on check-ins and meals.
• Invites: the email address a coach invites, and who sent the invite.
• Train-with-me links: if you make one, anyone who opens it sees your first name and the program you run, nothing else.

Before a meal or check-in photo is stored, it is resized and re-encoded on our server. That drops the location and camera details your phone attaches to a picture. Only the re-encoded copy is kept. Photos are never public: each one is served only to you and your coach, after checking who is asking.

So training works with no signal, your phone keeps a copy of your training record and any changes not yet sent, in the browser’s storage, plus photos waiting to upload. We set a sign-in cookie, a cookie that remembers whether you were in the coach view or the training view, and on the coach screens one that remembers whether the sidebar was open. Signing out clears the copy on the phone.

• No ads, and no advertising or analytics trackers on any page.
• We don’t sell, rent or trade your data, or give it to data brokers.

• You.
• Your coach, if you joined a coach’s team: your name, email, training, bodyweight, check-ins, meals and photos. That is the point of having a coach.
• Nobody on another team. Every coach’s team is kept apart in the database itself, with row-level security, so one team’s queries cannot return another team’s rows.
• The service providers below, only to run Ozees for us.
• Anyone a court or law requires us to tell, and only what is required.

• Railway hosts the app’s servers.
• Neon runs our Postgres database, in the United States (Ohio).
• Cloudflare runs our domain and stores photos in its R2 storage.
• Resend sends our sign-in and invite emails, so it sees the address and the email.
• USDA FoodData Central and Open Food Facts answer food searches and barcode lookups. Our server asks them, so they see the search words or the barcode and never your name, account or phone.

All traffic between your phone and Ozees is encrypted (HTTPS).

In the app, Settings has an export: a JSON file of your whole training record and CSV files of every set and weigh-in. Photos aren’t in the export yet; email contact@ozees.app and we’ll send them.

We keep your data while you have an account. Some deletes in the app, like removing a session or a weigh-in, hide the item but keep it in the database. Deleting a meal removes its photo.

There is no delete-account button yet. To delete your account and everything in it, email contact@ozees.app from the address you sign in with. We’ll delete it within 30 days and tell you when it’s done. Copies in our database provider’s backups expire on their own schedule.

Ozees isn’t for anyone under 16, and we don’t knowingly keep their data.

Bodyweight, check-ins and meal photos are health-related, so they get their own notice: how we handle health data.

When this policy changes, the date at the top changes. If a change matters to how your data is used, we’ll email you before it takes effect.