What a gym owner agrees to when they connect an AI.
Version 2026-08-25. You accept this when you generate a Lamella connect code or approve a connection on the consent page, and it stays in force while any connection on your gym is live.
This is the gym owner document. It is the text your console and the consent page show you, published here in full and unchanged. If you are a coach, trainer or studio connecting your own account rather than a gym you own, the document you accept is the Lamella connection agreement instead.
Who this applies to
This agreement is between Marrow Fitness LLC and you, the gym account owner who generates a Lamella connect code from the gym console or approves a connection on the Lamella consent page. It sits on top of the Marrow Terms of Service and the Marrow Privacy Policy, and it does not replace either of them. By accepting it you confirm you are allowed to bind the gym.
The agreement, as you accept it
These nine points are the agreement. They are reproduced here word for word from the panel in your gym console and the card on the consent page, in the same order, so the text you read before you tick the box and the text published here are one document.
- You choose the AI service. It is your account with them, not ours, and what you send is governed by your settings and their terms.
- Lamella works at owner altitude. Your roster, your locations, your gym's own records, and roll ups across the trainers on your roster.
- It never opens a member's health, body or nutrition records. Attendance and totals yes. One named person's body data never.
- It never writes to a trainer's own site, programs, prices or client records. Your trainers keep their hands on their own work.
- It cannot invite, remove or suspend a trainer. Roster changes stay in this console, because who is on your roster is an owner decision.
- It cannot make a price live, publish anything, or move money. Those stay behind your own hands in this console.
- Nothing here is free. Your gym subscription of $500 a month per location is unchanged, and the 8 percent Marrow takes on every payment it processes is unchanged. Lamella waives none of it, and the AI service you connect bills you for its own use.
- You are responsible for the assistant you connect and for what you do with what it hands back. Anything you type into it yourself is stored the way you wrote it.
- You can disconnect any assistant here at any time, and it loses access immediately.
The sentence you confirm. Before either surface lets you continue, you tick a box carrying exactly this wording.
I understand what Lamella sends to the assistant I connect, that it never opens a member's health record, and that my gym's billing and the transactional split are unchanged.
The version identifier of this text is 2026-08-25, and that is the exact string Marrow stores against your acceptance. The surface section below moved again on 2026-08-18 when the owner connection gained three tools, and the version did not move with it for the reason stated there: that section grants nothing, it describes what the tools reach, and it is kept accurate on the day they ship.
What an owner connection actually reaches
This section describes the shipped surface so the nine points above are read against something concrete. It adds no terms. A gym owner connection has nineteen tools, twelve that read and seven that write, and this is everything they touch. It said thirteen until 2026-08-18, when the owner surface gained the two page tools described below. The terms above did not change and the version identifier did not move, because this section grants nothing: it is a description of what the tools reach, kept accurate on the day the tools ship rather than at the next version.
What it can read.
- The gym record. Display name, city, onboarding state, whether payouts are set up, the brand colours on file, and how many trainers, gym owned plans, fee templates, events and saved reports exist.
- The roster. Each trainer's display name, role, status, location identifier, and invite and join dates.
- Readiness per trainer. Whether an active trainer has a published page, a live price, programs, and payments enabled. Existence only. Never the trainer's own content, and never a price figure.
- Activity roll ups. Counts across the active roster for a forward window of up to 90 days, per trainer and in total: class sessions, class attendees, open booking slots, bookings, pending requests, slot utilisation and active athlete counts.
- Gym owned membership plans. Name, description, price, interval, and whether each is live.
- Trainer fee templates. Label, kind, amount or percentage, and whether each is live.
- Gym events. Title, type, status, times, capacity and price.
- Reports and the change log. The reports Lamella saved for you, and the recent changes it made with the before and after value of every field it touched.
- Your gym page as it is written today. The headline, the description, the list of what you offer and the words on your enquiry form. Your own public copy, and nothing of a trainer's.
- Where your branded app is up to. The step of the build it is on and whether anything is waiting on you. It never claims Apple has approved anything, and it tells you when it could not check rather than saying nothing has started.
- The shape of your month. Counts bucketed over a window so you can see whether the gym is growing. Numbers only. No money figure and no named person.
What it can write. Seven tools, and every one of them lands somewhere a person still has to act.
- Create or edit a gym owned membership plan. It always lands switched off, new or edited, and no tool here can switch one on.
- Stage a proposed gym brand colour, clamped until it clears contrast against the Marrow surfaces. Nothing on your live page changes.
- Save a written report to your console under audit, plan or note. Nothing is emailed, messaged, posted, or shown to a trainer or a member.
- Restore the stored before values of one earlier change, through the same field allowlist as the original write.
- Create or edit a trainer fee template, the thing that decides what a trainer is paid. It always lands NOT IN FORCE, on a new one and on an edit, and no tool here can put one in force.
- Draft a gym event. It lands as a draft, which no member and nobody on the public internet can see, and only you publish it.
- Edit the words on your gym page: the headline, the description, what you offer and your enquiry form. It writes a draft. Nothing your page shows the public changes until you publish it yourself, no tool here can publish, and every field it touches is recorded in the change log with its before value so you can put it back.
What it never receives. These are not settings. There is no tool on the gym surface that returns them.
- An individual member's identity or contact details. No member name, email address, phone number or mailing address, and no member id.
- Any member's health, body or nutrition record. Attendance and totals yes. One named person's body data never.
- A trainer's own content or prices. Not their page copy, not their programs, not their price figures, not their client records.
One honest limit, the same one the coach document names. A count can still point at a person when the number is small. If one trainer has one active athlete, a count of one is about that athlete even though no name was sent. Treat what your assistant tells you about your gym with the same care you would treat the console it came from. The member facing version of this disclosure is in the Connected AI assistants section of our privacy policy.
Acceptance, records, and revocation
- There are two acceptance moments, and both run the same gate. Generating a Lamella connect code in the gym console, and approving a connection on the Lamella consent page. Neither one proceeds without an explicit acceptance of the current version, so a second door is never a cheaper way past the same gate.
- We record it. Marrow stores which gym accepted, the version identifier of the text they accepted, and when.
- A new version means a new acceptance. If we revise this agreement materially, the next code you generate or connection you approve asks you to accept the new version, and we tell you what changed. If the text changes while your console page is open, the console refuses the stale acceptance and asks you to read the current one.
- Revoking is one click. Disconnect an assistant from the gym console whenever you want, and it loses access immediately. Revoking does not reach into your AI vendor and remove what you already sent them.
- We can revoke too. Marrow may revoke a connection, or the whole Lamella surface, if we see abuse, a security problem, or a breach of this agreement. We will tell you when we do.
Questions
Marrow Fitness LLC
Miami Beach, FL
Agreement questions and data questions both go through our contact page.