Privacy Policy

This privacy policy (“Privacy Policy“) provides You with information regarding the collection, use, retention, storage and disclosure of Your Data and any Personal Information by My Strength Book Inc. (“MyStrengthBook“).

MyStrengthBook may amend this Privacy Policy from time to time. Your continued use of the System constitutes Your acceptance to any such modifications. If You do not agree to any such modification, then You must discontinue use of the System. All capitalized terms used herein and not defined shall have the meanings ascribed to them in the Terms of Use.

Mobile Applications Scope

Collection of Data

(a) In the course of Your use of the System, MyStrengthBook will collect, process and store information about You and Your use of the System. This information will consist of Your Data and may include Personal Information.

• Registration: Name, gender, location, weight, sport federation, and date of birth.
• Performance: Historic performance results, competition data, and forecasted training metrics.
• Third Party: Information from linked social media or external services.

(b) MyStrengthBook does not collect Personal Information from children under the age of twelve (12).

User Data Management & Deletion

We provide you with full control over your data. You can easily manage your data through the app’s settings. To delete your account and all associated data, email info@mystrengthbook.com (Attn: Privacy Officer). All health data will be permanently removed from our servers within 30 days. Copies an AI assistant already received through a coach’s connection are held by its AI provider under that provider’s own terms, and MyStrengthBook cannot delete them (see AI Assistants).

AI Assistants (Claude and ChatGPT)

MyStrengthBook (MSB) offers a connector that lets a coach connect their MSB account to an AI assistant they use: Claude, made by Anthropic, ChatGPT, made by OpenAI, or another AI application the coach runs on their own computer, which passes what it receives to whatever AI service it uses. This section explains what the connector shares with the assistant, what it can change in MSB, what it keeps and for how long, and how a coach disconnects.

What the connector does

Once connected, a coach can ask the assistant about the clients they coach in MSB, such as how their training, check-ins or nutrition went, and, where the assistant asked for permission to work on programs when it connected, have it prepare training programs and save them in MSB. From a check-in in MSB’s web app, a coach can also have the assistant prepare insights on that check-in: it reads the check-in and the data around it and, with the same permission, saves its insights onto the check-in for the client’s coaches, never for the client. Only coach accounts can connect: an athlete who signs in is turned away, and the assistant receives nothing for that sign-in.

Who is responsible

The coach decides whether to connect an assistant, which one, and what to ask it. MSB runs the connector, which answers the assistant’s requests with the coach’s own MSB access, and about clients only for those on that coach’s roster; it sends the assistant no MSB data except in answer to those requests. The AI provider behind the assistant (Anthropic for Claude, OpenAI for ChatGPT, or whichever provider an AI application on the coach’s own computer uses, which the connector cannot see) receives those answers through the coach’s own account with it, and handles them under its own terms and privacy policy.

What the assistant can receive

When the coach asks, the assistant can receive:

• About the coach: name, email, role, MSB permissions, account status, time zone, and how many clients the coach has.
• The client list: each client’s name and MSB id, whether they are active, their groups, join date, last login and units, their recent activity (sessions, adherence, scheduled training, programming left, current program, latest body weight, days with food logged) and why a client may need attention.
• One client at a time: their name, MSB id, status, units and time zone, and the part of their MSB data the request is about: training (programmed and logged sessions and sets with loads, RPE, set comments and velocity, and whether the coach reviewed a set video, with its description), body metrics (body weight, sleep, heart rate and HRV, steps, session RPE, water, body fat, readiness and body measurements), nutrition (assigned plans, macros, calories, targets and how many meals were logged), check-ins (questionnaire answers, habits, client and coach notes, workout and exercise notes, and pain mentions found in them), programs, personal records, the plan (phases, events, goals, check-in dates, habits and meal plans), lift trends, comments on training videos and on progress and meal photos (the text only) and, where the client logs it, menstrual-cycle data.
• When the coach works on programs: previews and summaries of programs, with the client a program is for and the name of the file it came from, and the coach’s exercise library, including the links to the coach’s own exercise videos stored with it.
• For check-in insights a coach starts in MSB: the check-in’s answers and how many body photos it holds, the answers of up to three earlier check-ins and the client’s onboarding answers, which parts of MSB the coach turned on for the client and which measurements they track, up to the last 100 messages of the coach’s chat with the client, from the coach, the client or anyone else in the conversation, and the Loom videos MSB stores for the client, as their links and, where Loom has one, a transcript. Those are the videos recorded by the coach or another of the client’s coaches: MSB does not filter them by who recorded them, so in an organization, or after a change of coach, other coaches’ videos are included.
• Record identifiers the assistant’s next request needs, such as client and program ids, and links into MSB.

Notes, check-in answers, comments and chat messages reach the assistant as they were written, and transcripts as they were spoken, links included; some long texts are shortened. The assistant receives each answer whole, and Claude and ChatGPT may show it as a card in the conversation.

What the assistant never receives

The assistant never receives, as data of its own:

• The coach’s MSB password or MSB sign-in. The coach signs in on the connector’s own page, the password goes once to MSB to be checked and is not stored, and the assistant receives only the connector’s own tokens.
• A client’s email address or birthday, billing details, or the names of foods a client logged.
• Photos, videos or audio, or links to a client’s photos or videos. A progress-photo answer in a check-in says only which of front, side and back hold a photo; for check-in insights, other photo answers and a check-in’s body photos say only how many there are, and a chat message only that it had an attachment. Loom videos recorded for the client, by the coach or another of the client’s coaches, reach it only as their links and transcripts.

Text a coach or client wrote, such as notes and check-in answers, reaches the assistant as written and can contain any of these.

What the connector can change in MSB

Apart from the records at the end of this section, the connector changes MSB only in the ways below, and only when the assistant asked for permission to work on programs when it connected and the coach allowed it on the consent page; the same permission covers saving check-in insights.

• Save a program the assistant prepared in draft, as one of the coach’s templates, in a client’s program, or both; a client sees a draft only once the coach pushes it in MSB.
• Add blocks to one of the coach’s templates or client drafts that was not pushed or published itself; the added blocks stay unpushed until the coach pushes them in MSB.
• Delete a template or client draft the coach created that was never pushed. A delete cannot be undone.
• Add the movements a program uses to the coach’s exercise library when they are missing, at most 30 at a time, and fill in details left blank on movements already there.
• Save the insights the assistant wrote onto a check-in, for a check-in insights request the coach started in MSB. They replace any insights already on that check-in (coaches cannot edit insights, only have them generated again); MSB shows them to the client’s coaches, never to the client.

Each program change starts from a preview: the connector saves or deletes only what a preview the same coach made in the last 30 minutes showed, and tells the assistant to show that preview to the coach and to go on only on the coach’s yes. Check-in insights are saved without a preview, once per request the coach started. The connector sends no messages or notifications, and changes no check-in answer, training log, nutrition or body-metric record.

Signing in through the connector is an MSB sign-in like any other, and MSB records it on the coach’s account as it does every sign-in. MSB also records, whatever the coach allowed, when a coach connects Claude or ChatGPT, uses it (at most once an hour) and disconnects (once the assistant tells the connector), so that MSB’s web app can offer to start check-in insights there, and when the assistant first reads a check-in insights request. MSB keeps these records, and the insights saved on a check-in, until they are deleted from MSB’s database, with no expiry.

Health data

Some of what the assistant can receive is health data: body weight and measurements, body fat, sleep, heart rate and HRV, readiness, nutrition, check-in answers and notes, which arrive as written and can hold any health information (pain mentions in the free-text answers and workout notes are flagged), and, where a client logs it in MSB, menstrual-cycle data (cycle settings, period dates, the predicted next period, and cycle answers in check-ins such as symptoms and flow). For check-in insights, a client’s chat with the coach and the transcripts of the Loom videos recorded for the client are free text that can hold any health information too. The connector reads it only for clients on the coach’s roster and only when the assistant asks for it on the coach’s behalf. It keeps it only in memory, where it expires after a minute, and never stores it at rest or writes it to its logs; MSB stores the check-in insights an assistant writes from it on the check-in. MSB can turn menstrual-cycle data off for the whole connector; a coach cannot turn it off for one connection.

Minors

MSB can set an age below which clients are hidden from the connector. A hidden client is left out of the client list and its counts, and requests to read their data, or to save, add to or delete a program or save check-in insights for them, are refused; the client list says how many clients are hidden, never who. While no age is set the connector reads no birthdays and treats clients of every age alike, and when one is set it reads a client’s birthday only to apply the age, never passing it to the assistant or its logs. The filter has limits: notes, check-in answers, comments, chat messages, Loom transcripts and program names and descriptions can still mention a hidden client, an assistant that varies the part of a name it asks about can learn that someone matching it is hidden, and the prompt MSB’s web app starts check-in insights with names the client. Athletes cannot connect at all.

What the connector keeps, and for how long

The connector keeps what a connection needs, not a copy of MSB:

• The connection: the coach’s MSB sign-in, MSB user id, email and role, and what the coach allowed. The connector’s own tokens are stored only as hashes, and what it keeps of a connection outside the server’s memory is encrypted. An access token expires after an hour. The connection lasts until the coach disconnects and the assistant tells the connector, until it goes unused for 30 days, or until MSB no longer accepts the coach’s sign-in.
• A sign-in in progress: the coach’s MSB sign-in, MSB user id, email, name and role, for at most 5 minutes before the coach answers the consent page and 5 minutes after.
• Program and delete previews: the coach’s email, the program, the client’s id and name, and the name of the file a program came from, for 30 minutes.
• MSB data, health data included: only in memory and per connection, where it expires after a minute (personal records after 10 minutes).
• The assistant’s registration: the assistant app’s name and callback addresses, with no personal data, kept with no end date.
• Connection reports: the coach’s MSB user id and the assistant (Claude or ChatGPT), in memory, so that MSB is told of a use at most once an hour; a mark past its hour stays until that coach’s next request through that assistant or until the connector restarts.
• Logs, kept for 30 days: a line per event with the coach’s MSB user id, the assistant app’s name, the client ids a request names, counts and timings; the assistant app’s callback addresses, browser and app user agents cut to 80 characters, and up to 300 characters of an error MSB returned; the coach’s email on each program preview, save or delete, and a program’s name, which may name a client, when it is previewed or saved; the coach’s email, the request, the client, the check-in and the assistant on each check-in insights save; and the IP address when a request comes without a valid token or one address sends too many requests. Logs never hold an answer the assistant received, a password, a token, a birthday, or a client’s name as the assistant asked for it.

Disconnecting and other controls

• Read-only without the permission to work on programs. Unless the assistant asked for it when it connected, the connector sends MSB no change apart from the sign-in MSB records and the connection and first-read records described above; MSB’s own checks on each request still apply, as they do in MSB’s apps.
• Disconnecting. A coach can disconnect at any time in the assistant’s connector settings. Access through the connector ends within an hour of a disconnect at most, once the assistant tells the connector about it; an assistant that does not leaves the connection stored until it goes unused for 30 days.
• When MSB ends the sign-in. A connection also ends when MSB no longer accepts the coach’s sign-in. Changing the MSB password does not end a connection while MSB’s check of the coach’s sign-in applies no session cutoff; to end one, the coach disconnects in the assistant.

Clients of a connected coach

A coach’s clients do not use the connector themselves. A client with a question or request about their data can contact their coach or MSB’s Privacy Officer (see Contact Privacy Officer). Data deleted from MSB can no longer be read through the connector once its copy in memory has expired.

Where data is processed

The connector, the connection data it keeps and its logs are hosted in Germany. An AI provider processes what it receives under its own terms. Loom receives the id of each Loom video MSB stores for the client whose transcript the assistant reads.

Contact

Questions about this section, and requests about data the connector handles, go to MSB’s Privacy Officer at info@mystrengthbook.com, with “Attn: Privacy Officer” in the subject, as for the rest of this policy.