Privacy policy
App: Train Personal ("the app"), for iPhone and Apple Watch. Who we are: JGA Ventures LLC, of 30 N Gould St, Ste N, Sheridan, WY 82801, United States ("we", "us"). Contact: support@trainpersonal.app. In force from: 2026-10-21.
The short version
- The app is a strength-training logbook. What you log is kept on your phone, and on your Apple Watch if you use it.
- We receive nothing you log until you do one of three things: create an account ("Save this workout"), agree to use the AI coach, or agree to let AI read a photo of gym equipment. Three other ways it can leave your phone are yours: a copy you export, a list of your gym you share as a file, and your phone's own backup, which goes to Apple if you have iCloud Backup on.
- The app has no advertising, and no analytics or crash-reporting library. We do not sell your data and we do not use it to track you across other companies' apps or websites.
- Our server runs on Google Cloud in the United States. The AI is Google's Gemini. Sign-in is by Apple, through Google's Firebase. Purchases are made through Apple, with RevenueCat. Each is named below with what it receives.
- You can export your logbook and delete your account in the app, in You.
Much of what the app holds says what your body did, so we treat it as health data. The health data policy covers that on its own page.
What the app holds
On your phone, always:
- Your plans: their workouts, exercises, planned sets, reps or seconds, and rest.
- What you did: each workout's start and finish, each set's weight and reps or seconds, how hard you said a set was, exercises you skipped, swapped or added, and the weight chosen for next time.
- Your notes on exercises and on equipment. A note is free text: it holds whatever you type.
- Your gym: its equipment, the weights each piece has, its bars and plates.
- Photos of your gym's equipment, if you add any, and up to 60 photos waiting to be named (see "Photos").
- Your answer to "Have you lifted weights before?", and your settings.
- Your conversations with the coach: up to 100, each with its latest 50 messages.
- On a paired Apple Watch: today's workout as the phone last sent it, with your last results, kept until the next one replaces it; and the workout you run on the watch, with its sets and its place, kept until you tap Done on its last screen.
- Your phone's offset from UTC when a workout starts. It is a rough sign of your time zone.
- A random id the app makes for this install. It is not an advertising id or a hardware id.
- Once you open "The coach plan" or "More questions", RevenueCat's part of the app keeps its own copy of your purchases and the store's prices. We believe it keeps them in the app's storage; we have not confirmed where or for how long.
The app does not ask for your name, email address, date of birth, body weight, precise location, contacts or payment details. Sign in with Apple gives us no name and no email. Sign in with Google gives our sign-in provider the name, email address and photo of your Google Account: see 2 below.
What leaves your phone, and when
1. When the app first opens with a connection
The app signs in to Google's Firebase Authentication with no name: Firebase makes a random id for this install. With it goes proof that the caller is the real app (Apple's App Attest, through Firebase App Check). Nothing you log goes with it. We use the id to count your free uses of the AI features.
On an iPhone this id is kept in the phone's keychain and can outlast deleting the app.
2. If you create an account ("Save this workout")
You sign in with Apple or with Google. Apple tells us only that it is you. Google also gives the name, email address and photo address of your Google Account: Google's sign-in always does. Google's Firebase Authentication keeps them with your account. The app does not read, show or use them, and our own server does not store them. We then keep, on our server:
- A copy of everything listed under "On your phone, always" above, except your coach conversations (they go only if you choose: see 10), photos still waiting to be named, RevenueCat's copy and what is on your watch, as the phone recorded it. It includes changes you later undid and workouts you discarded, and the install's random id.
- The photos of your equipment, as the phone keeps them.
It is kept under your Firebase user id, so that signing in on another phone brings it back. Without an account, neither is sent.
With or without an account, our server keeps a count of your uses of the AI features: which feature and when. No question, photo, note or reply. Without an account it is kept under the install's random id (1, above).
3. If you agree to the AI coach
The app asks first, once, and says what is sent. With each question it sends to our server, and our server to Google's Gemini:
- Your question, and up to 3 earlier ones with their replies.
- The plan you are using, and the names of your exercises with the first 200 characters of each note.
- Your last 10 finished workouts, with each set's weight, reps or seconds and effort, and each exercise's best sets.
- Your gym, when it holds anything: your unit, each piece of equipment, how it loads, its weights and the first 200 characters of its note, and your bars and plates.
- Whether you have lifted before, and today's date.
- When you ask from a workout: that workout, the exercise on screen and its sets so far.
No photo, no account detail and no install id is sent. Our server keeps no copy and writes none of it to its logs. Google does not train its AI on it. Google may hold a request in memory for up to 24 hours, and may log requests to check for misuse; we do not know how long it keeps that log.
"Build a plan with AI" is covered by the same agreement. It sends the days a week you chose, whether you have lifted before, and your gym as above. Our server keeps no copy of the plan; it is kept on your phone.
Some questions never reach the AI. If a question mentions signs such as chest pain, trouble breathing or fainting, the app answers itself and sends nothing.
4. If you agree to let AI read a photo ("Ask AI")
The app asks first, once. Each time, it sends to our server, and our server to Google's Gemini: one or two photos of one piece of equipment as the phone keeps them, its note, your unit, and the type of equipment if you named it. Nothing from your logbook or account goes with them. Our server keeps no photo and no note from the read. Google treats it as it does a coach request, above.
You can pick up to 30 photos at once. Each is kept on your phone as one photo is (see "Photos"), and nothing is sent until you tap "Ask AI about" them. AI then reads them one piece at a time, each read sent and handled as above. Our server counts each read with your other AI uses (2).
5. If you export a copy
"Export a copy" makes one file of your logbook and hands it to your phone's share sheet. It goes where you send it. The app does not learn where. Photos and coach conversations are not in the file.
6. If you tap a link to Google or YouTube
- "Watch a video" opens a YouTube video, or a YouTube search, in YouTube's app or your browser. The app sends YouTube only that video's address, or search words of the app's own for that exercise. It never sends your text. YouTube learns which exercise was looked up.
- "See pictures" opens a Google Images search in the same way, with a search term of the app's own for that type of equipment.
The videos and pictures are not ours. Google sees what it sees of any browser, such as your phone's internet address, and may set its own cookies in that sheet. Google's privacy policy applies: https://policies.google.com/privacy
7. Your phone's own backup
If iCloud Backup is on, or you back your phone up to a computer, the app's files, photos included, are in that backup. That copy is held by Apple or by your computer, under your settings, not by us.
8. If you use the Apple Watch app
- Between your phone and your watch: the phone sends the watch today's workout, with the weights it opens on and your last results. The watch sends the phone what you do on it: the workout's start, each set, how hard a set was, an undo, a skipped exercise and the finish. These go directly between your devices, through Apple's link between them, not through our server. Your sets then join your logbook like any set logged on the phone.
- Apple Health, only if you allow it on Apple's sheet: a workout you do on the watch is saved to Health as a strength training workout, with its start and end and the energy burned, so it counts towards your Activity rings. Health may keep the heart rate your watch measured during it with the workout, as it does for other workouts. No exercise, weight or rep goes to Health. A workout you discard on the phone is discarded in Health too. What is in Health is kept by Apple under your Health settings, and you can delete it there.
- Heart rate and energy are read from Health during a watch workout: heart rate to show it on your watch. The app never writes heart rate to your logbook, the phone's database or our server, and never used for advertising.
- We do not store anything from Apple Health in iCloud.
9. If you look at the coach plan, or buy it
The coach plan and the pack of questions are bought through Apple. Apple takes the payment and holds your payment details; we never see them. RevenueCat, a company that checks purchases for us, tells our server what you bought.
- When you first open "The coach plan" or "More questions", or tap "Restore purchases", whether or not you buy, the app sends RevenueCat your Firebase user id (1, above), and RevenueCat keeps a customer record under it. RevenueCat's part of the app also sends, by itself, your phone's App Tracking Transparency setting. The app never asks to track you, so it says "not determined". We believe it also sends the app's version, your phone's platform and country, and its internet address; RevenueCat's pages we read do not say.
- When you buy or restore, Apple's receipt for the purchase goes to RevenueCat, and our server reads from RevenueCat what you are entitled to.
- RevenueCat receives no health data, no name and no email address.
- Our server keeps whether your plan is live and until when, which store and whether a test purchase, the day your plan's 30-day periods start from, the questions and AI plans you bought and have left, and each pack you bought with its store transaction id, so a purchase is counted once, and whether it was refunded. It counts the plan's questions, AI plans and photo reads you use with your other AI uses (2). No price and no payment detail.
- RevenueCat's dashboard shows us totals of purchases, such as how many people subscribe. RevenueCat counts this as analytics.
10. If you keep your coach conversations on our server
With an account, the Coach tab's list of conversations asks once: "Keep conversations on our server?" Only if you tap "Keep on our server" does the app send them. It then keeps on our server each conversation as your phone holds it, under your Firebase user id, with the time of its last message, so they come back when you sign in on a new phone. The coach never reads this copy, and our logs hold none of its words.
It is kept until you delete that conversation, turn "Keep conversations on our server" off in You, or delete your account. Turning it off asks first, then removes them all from our server; they stay on your phone. A deleted conversation stays in the database's backups for about a week (see "How long we keep it").
11. If you share My gym with a friend
"Share with a friend" on My gym makes a file named "My gym" and hands it to your phone's share sheet, as "Export a copy" does. You send it to whoever you choose, through Messages, AirDrop, Mail or another app. We receive nothing: it does not pass through our server.
- What is in it: each piece of equipment you have said is here, not sure or not yet said: its type or the name you gave it, how it loads, its weights, where its plates go and its own weight; and your gym's bars and plates. The app shows you the names you gave before you send, since a name may name someone.
- What is not: your notes, equipment you said is not here, your workouts, your name and your account.
- Photos, only if you choose: "Include photos" is off each time. Turned on, you see each photo, untick any with a person in it, and must tick "No one is in these photos." before you can send. The file holds new, smaller copies, with no place or time, of up to 30 photos.
- The app writes the file in its own temporary storage and deletes it when the share sheet closes. What you sent is then in the hands of whoever received it.
A file a friend sends you shows what it holds, and you tick what to add. Nothing is added until you tap "Add". Each photo you add is checked for faces again, as your own photos are, and becomes yours, kept like any equipment photo (and on our server, with an account). The app deletes its copy of the file once read.
Photos
- A photo comes from your camera or from the photo you pick. The app asks for the camera only when you tap "Take a photo".
- Before a photo is kept, your phone looks for faces and covers each one it finds (the app calls this blurring), makes the photo smaller, and removes where and when it was taken. This happens on the phone. The photo as it came is deleted.
- The phone can miss a face that is far away or turned aside. You see the photo before it is kept. Please keep other people out of the picture.
- With an account, your photos are also kept on our server so your other phone has them.
- Pick several at once, up to 30: each is kept as one photo is, and you check them all on one screen before any is kept. Photos waiting to be named (up to 60) are kept on your phone only, never on our server; one is sent only when you ask AI to read it (4, above).
- Your photos are used for your own account only, unless you choose to send them to a friend in a gym file (11, above).
Why we use it
- To run the app's features for you: your logbook, your plans, your progress, the coach's replies, plans built by AI, and equipment read from a photo.
- To keep a copy for you and return it on another phone.
- To count free uses of the AI features, and to keep the service's cost within its limit.
- To keep the service secure and working.
- To see totals of purchases, such as how many people subscribe, in RevenueCat's dashboard.
We do not use your data for advertising. We do not use your photos, questions or logbook to train AI, and Google does not train its AI on what we send it.
Where the GDPR or the UK GDPR applies, we rely on our contract with you to run the app, your account and its copy, and purchases; and on your agreement for the AI coach, AI plans, photo reads, keeping conversations on our server, and Apple Health. You can withdraw an agreement at any time (see "Your choices").
Who receives your data
We share data only with the companies that run the service for us, and only what each needs.
| Who | What it receives | When |
|---|---|---|
| Google Cloud (Cloud Run, Cloud SQL, Cloud Storage), United States | The server's copy of your logbook and equipment photos; your coach conversations, if you chose to keep them there; the count of AI uses | The copy: with an account. The conversations: after your yes. The count: from your first use of an AI feature, with or without one |
| Google Firebase (Authentication, App Check) | The install's random user id; once you sign in, Apple's or Google's id for you in this app, and with Google the name, email address and photo address of your Google Account; proof that the caller is the real app | From the first launch with a connection |
| Google Gemini on Vertex AI, United States | What is listed under 3 and 4 above | Only after you agree, each time you ask |
| Apple (Sign in with Apple, App Attest) | That you signed in to this app, and the app's proof request | When you create or delete an account; at launch |
| Google (Sign in with Google) | That you signed in to this app | When you create or delete an account with Google |
| Apple (the App Store) | Your purchase and its payment | When you buy, renew, cancel or ask for a refund |
| RevenueCat | Your Firebase user id; Apple's receipt for a purchase; your phone's tracking setting ("not determined"); see 9 above. No health data, name or email | From the first time you open "The coach plan" or "More questions", or tap "Restore purchases" |
| Apple Health, on your own devices | A watch workout: its type, start, end and energy; Health may keep heart rate with it | Only if you allow it, when you finish a workout on the watch |
| Google and YouTube, as websites | The video's address or the app's own search words | When you tap "Watch a video" or "See pictures" |
| Whoever you send a gym file to | What is in the file (11 above). We do not choose them or learn who they are | When you send it |
Like any internet service, these see your phone's internet (IP) address when the app calls them. Our server's request log keeps, for 30 days, that address and details of each call, such as its time, the address it went to (which can hold a piece's or a photo's id), and the app's version and the phone's system.
We may also disclose data when the law requires it. We have not sold anyone's data.
Where it is kept
Our server and its database are in the United States (Google Cloud). The AI runs in the United States. If you use the app from another country, your data goes to the United States. For people in the UK and the EU, that transfer relies on the standard contractual clauses (and the UK's addendum) in Google's data processing terms.
How long we keep it
| What | How long |
|---|---|
| Everything on your phone | Until you delete it, delete your account, or remove the app |
| The server's copy of your logbook | Until you delete your account |
| The server's copy of a photo | Until you remove or replace the photo, remove its equipment, or delete your account. It is then gone at once: we keep no earlier versions |
| The server's copy of a coach conversation | Until you delete it, turn "Keep conversations on our server" off, or delete your account. Then about a week more in the database's backups |
| A gym file you share | Not kept by the app once the share sheet closes. Not received by us |
| The count of AI uses | Until you delete your account. For an install with no account, it stays: see "What we cannot do yet" |
| A coach request, a plan build, a photo read | Not kept by our server. Google may hold it in memory for up to 24 hours, and may log it to check for misuse for a time we do not know |
| The id of a deleted account | One day, so a phone still signed in cannot save to it. Removed at the next deletion after that |
| Your plan's state and the questions and AI plans you bought | Until you delete your account. Bought questions and AI plans never expire |
| RevenueCat's customer record | Until you delete your account, when we ask RevenueCat to delete it. RevenueCat may keep some records after that for its own obligations; we have not confirmed which |
| An install's Firebase id with no account | Kept. See "What we cannot do yet" |
| Server backups | The database keeps 7 daily backups and, on the live server, its own recovery log, so deleted data stays in them for about a week. |
| Server logs | 30 days. Our own log lines hold no question, reply, photo, note or user id |
| An account nobody uses | Kept until you delete it. We do not delete an account for not being used |
Your choices
- Use the app with no account. Then we keep no copy of your logbook. It still goes to the AI when you ask the coach a question, if you agreed to that, and into your phone's own backup.
- Turn the coach off in You. When it is off, nothing is sent to the AI, and photo reads stop too.
- Export a copy of your logbook in You.
- Delete your account in You, "Delete account". Apple or Google, whichever you saved with, asks you to sign in once more. We then delete the server's copy of your logbook, your photos on the server, the count of your AI uses and your Firebase user (with a Google account, the name, email address and photo address it held), revoke Apple's sign-in token or this app's access to your Google Account, and clear the app's data on this phone. We also delete your coach conversations kept on our server, ask RevenueCat to delete its record of you, and delete the questions and AI plans you bought. It is for good. A copy you exported earlier is yours and is not deleted.
- Deleting your account does not cancel a subscription. Apple bills it until you cancel it. Before you delete, cancel it on the deletion page's "Manage subscription", or in your iPhone's Settings.
- Delete a photo on its equipment's page. It goes from the phone and from your account.
- Delete a coach conversation in the Coach tab's list ("Edit", then "Delete"), or all at once with "Delete all conversations", offered when the coach is off. One kept on our server goes from there too.
- Stop keeping conversations on our server in You, under "The coach". They stay on your phone.
- Ask us at support@trainpersonal.app to see, correct or delete your data, or to withdraw an agreement you gave. We reply within 30 days. If we refuse, reply to our answer to appeal, and we answer the appeal within 30 days.
Depending on where you live, the law may give you more rights, such as to complain to a regulator. We have no separate data-protection officer and no EU or UK representative: write to us at support@trainpersonal.app.
What we cannot do yet
We would rather say these than leave them out.
- An install with no account cannot delete its Firebase id or its count of AI uses from inside the app. Write to us and we will do it.
- "Delete account" does not clear a paired watch, or workouts saved in Apple Health. The watch keeps its copy until its app is deleted from the watch or the next workout replaces it; delete Health's workouts in the Health app.
- Another phone signed in to an account that was deleted keeps what it already holds.
Security
The app talks to our server over HTTPS. Every call that carries your data must prove who is calling and that it comes from the real app. The server's database has no public internet address, and nobody signs in to it with a password. Your photos on the server are private to your account. On your phone, the app relies on the phone's own file encryption.
No system is perfectly secure, and we cannot promise ours is. If a breach affects your data, we will tell you as the law requires.
Children
The app is not for anyone under 16. We do not knowingly collect a child's data. If you believe a child has used the app, write to us and we will delete it.
Changes
We will change this policy when the app changes what it does with data, and put the new date at the top. When a change matters, we tell you in the app and on this page at least 14 days before it takes effect. This policy is published at https://trainpersonal.app/privacy. Where the app asks for your agreement and the text changes, it asks again.