What you agree to when you connect your AI.

Two documents, so read the one you accepted. This page is the coach document, for an assistant connected to a coach account. If you own a gym and connect an assistant to your gym console, the text you accept is the eleven point gym connection agreement, published in full and unchanged on its own page.

What changed in this version. Your clients now decide for themselves. A client says yes to texts in their own Marrow account, and appears to your assistant by name only after they agree there, even with Client profiles switched on. A texting permission you recorded for a client is paused until that client confirms it. A price increase for an existing client bills only after that client accepts it in Marrow. Marrow is for adults only. Marrow also now records a fingerprint of this text, the account that accepted it and the browser used. Reading keeps working whether you accept or not. Anything that acts waits until you accept this version.

The short version. Marrow connects an AI assistant you already pay for to your own account. You pick the vendor, so you own that relationship and its settings. Once you accept this version, it can read what your dashboard shows you, including your clients' records and your revenue in dollars, and it can act for you, but only in two steps: it shows you exactly what would happen and to whom, and acts only after you say yes. What you say yes to is your decision and your responsibility.

Who this applies to

This agreement is between Marrow Fitness LLC and you, the coach, trainer or studio account holder who connects an assistant to your own coaching account, whether you generate a connect code or approve a connection on the 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. Connecting an assistant to a gym you own is a separate act on a separate surface, and it carries the gym connection agreement. Accepting that one is where you confirm you are allowed to bind the gym.

You choose the vendor, so you own that relationship

Marrow has no model of its own. You connect a client you already pay for, and the assistant runs on your account, your usage, and your bill. Marrow does not resell you a model and has no agreement with the company behind it.

• The choice is yours. You are responsible for which AI vendor you connect and for reading that vendor's terms and privacy policy before you do.
• The settings are yours. Whether that vendor trains on your inputs, how long it retains them, whether a human can review them, and whether your plan offers a no retention mode are settings on your account. Set them the way your business needs them. Marrow cannot see them and cannot set them for you.
• What lands there is out of our hands. Once your assistant receives something from Marrow, it is with your vendor under your vendor's terms. Marrow cannot recall it, delete it, or audit it.
• Verification is narrow. Marrow names a client as verified only after running it end to end ourselves. Any other client that speaks the same open protocol can connect, and connecting it is your call, at your risk.

What Marrow sends, so you know what you are sending

A connected assistant can reach your own business content: your site copy, your programs, your membership tiers and session packages, your community, your schedule, and the reports you save. About your clients, it can reach what your dashboard shows you, on your own account and nobody else's.

• Their programs, and the workouts and sessions they logged.
• Messages between you and them in Marrow, and their check ins.
• Their nutrition: the plans and targets you set and what they chose to log.
• Their measurements and progress entries, and readings from a wearable they connected and shared with you.
• Their bookings and classes with you.
• Their billing with you: what they pay, what they have paid, refunds and payment requests. Never card details.
• Counts of memberships by status, how many members sit on each tier, session pack usage in aggregate, and timestamps such as the date of the last community post.

Clients appear as opaque per client pointers, a one way code standing in for one client that carries no name and no contact detail and that your AI vendor cannot reverse. A client appears by name, with their contact details, date of birth, goals, injury history and your notes, only if you switch on Client profiles for your own account from your dashboard and that client has agreed in their own Marrow account. Until a client agrees, they stay a pointer and are counted, never named, and they can take that agreement back at any time. Message text is the exception to that setting: a message is sent as it was written, so a name or detail typed into it travels with it either way.

It can also read your schedule as a whole, which is a different thing and a narrower one. Counts, clock times, durations and how full the next ninety days look. That read carries no identity field at all, not even an opaque pointer, so it can tell you a session has three seats left and can never tell you whose.

And it can reach your money.

• Your revenue in real dollars over a chosen window: gross taken, refunds issued, the Marrow application fee, what is left after it, a refund rate and a transaction count, plus the previous window of the same length so a direction can be stated.
• The same figures split across your six revenue streams: tips, class registrations, class package purchases, template purchases, booking payments and event tickets.
• A trend, month by month, for up to twelve months.
• Your spend ceiling, the rolling window it applies over, and how much of that window is already held.
• Your own individual payments, and one client's billing with you.

These are Marrow payment rows summed by the date Marrow recorded them. They are not a Stripe report, and Stripe processing fees, payouts, payout timing, disputes, chargebacks and taxes are not read by the revenue summaries, so treat any figure as what clients paid you through Marrow rather than what lands in your bank.

What it can do, only after you say yes

Anything that reaches a person, moves money or changes what a client can see happens in two steps and never one. First your assistant shows you exactly what would happen and to whom, including anything still blank. Then it acts only if you say yes to that exact thing, in the conversation, and your words are recorded with the change. A yes to one thing is never a yes to another, and a confirmation goes stale if what it describes changes. Apart from taking your own public page live or offline, which never waits on this agreement, none of this works until you have accepted this version.

• Reach a client. Send a message in Marrow, an email, or a text from your own connected texting number. A message goes only where that client has given permission for that channel, inside daytime hours where they are and the daily caps, exactly as when you press send yourself. A text goes only to a client who said yes to texts themselves, in their own Marrow account.
• Invite and ask. Invite a client, send a form, or send a review request.
• Publish your own work. Take your public page live or offline, publish a program, and post to your community and your own connected social and review accounts.
• Change the schedule. Book, move or cancel a session or class.
• Handle money. Issue a refund through Stripe, with the same limits the dashboard applies, charge a client or send a payment request, and turn on a price. Turning a price on never changes what an existing client already pays, and a price increase for an existing client bills only after that client accepts it in Marrow. Until they accept, their old price continues.

A message, a post, a refund or a charge cannot be undone once it has gone, so read it before you say yes. A page, a price and a booking can be put back, and putting one back asks you again.

It can never reach another coach's account, score a client's form or grade a person, change Marrow's prices or your own Marrow subscription and billing, change how much it may do on its own, turn off the switch that stops it, change whether it may handle money, see or mint your connection keys, or upload a file, a photo or a video.

One honest limit. A count can still point at a person when the number is small. If you have one member past due, a count of one is about that member even when the count itself carries no name. Treat what your assistant tells you about your members with the same care you would treat the roster it came from. The member facing version of this disclosure is in the Connected AI assistants section of our privacy policy.

What you must not put into it

Marrow controls what the connection sends, and the section above is the whole of it. It cannot control what you type. Anything you put into your chat window, or into the free text of a report you save through the connection, goes to your AI vendor as well, so these stay out of it.

• No card details. Marrow never sends a card number or bank detail. Do not paste one.
• No addresses, photos or videos. Marrow does not send a client's home or mailing address, their progress photos or their form videos. Do not paste or upload them.
• Nothing from outside your own account. Do not paste another coach's clients, records or messages, or details about a person who does not train with you.
• Only what the task needs. When a job needs one client's details, bring what that job needs and nothing more.

If you break this, the details land with your AI vendor, and the exposure is yours. You are the one with a relationship with those members, and depending on where you and they live, you may be the one carrying the legal duty for their health information. Marrow does not scan the free text you save and cannot repair a disclosure you made.

What Marrow holds up on its side

• Your connection is scoped to your account alone. One coach's business never informs another's. We do not pool it and we do not train a model on it.
• Nothing publishes itself, and taking your page live needs you to say so. Your Claude can take your own public page live, and take it back down, only after it has read the whole page and the web address it would live at back to you and you have said yes in the conversation. A program or a post publishes the same way, two steps and never one.
• Nothing acts without your yes. Every action that reaches a person, moves money or changes what a client sees is two steps and never one, and no other request can trigger it. Your answer is recorded with the change.
• A refund is issued only on your yes. Your assistant shows you the payment, the amount and who it goes back to, and the refund runs through Stripe only after you say yes. A refund cannot be undone once it is issued.
• Prices arrive switched off. Tiers and packages your assistant writes land inactive, and one goes live only after you say yes to that price. Turning a price on never changes what an existing client already pays, and a price increase for an existing client bills only after that client accepts it in Marrow. Marrow's own prices to you are not editable by any assistant.
• Messages respect your clients' permission. No message goes to a client on a channel they have not given permission for, outside daytime hours where they are, or past the daily caps. A client says yes to texts themselves, in their own Marrow account, and can take it back at any time. A texting permission you recorded for a client is kept on file and sends nothing until that client confirms it.
• Marrow is for adults. A client record with a date of birth under 18 is refused, and a record that already says under 18 is shown to you so you can sort it out.
• Every write is logged with its previous value, so you can undo what your assistant did.
• You can revoke a connection at any time from your dashboard, and Marrow can disable connected assistants entirely if something goes wrong.

Acceptance, records, and revocation

• There are two acceptance moments, and both run the same gate. Generating a connect code from your dashboard, and approving a connection on the 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. No acceptance, no connection.
• We record it. Marrow stores which account accepted, the person signed in to it, the version identifier of the text they accepted, a fingerprint of that text, the browser used, and when. The version identifier of this text is 2026-10-25, and that is the exact string stored against your acceptance.
• A new version means a new acceptance. If we revise this agreement materially, the next connect code you generate or connection you approve asks you to accept the new version, and we tell you what changed.
• You can withdraw your acceptance. Withdrawing it disconnects every assistant on your account at once and cancels any connect code you have not used. Your dashboard and your clients are not affected. Marrow keeps the record of what you accepted and when you withdrew it, and connecting again means accepting the current version.
• Revoking is one click. Revoke a connection from your dashboard whenever you want. Revoking stops the assistant reaching your account. It does not reach into your AI vendor and remove what you already sent them.
• We can revoke too. Marrow may revoke a connection, or connected assistants as a whole, 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.