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 nine point Lamella gym connection agreement, published in full and unchanged on its own page.

What changed in this version. Your assistant can now be allowed to see your revenue in real dollars, and to stage a refund or a price change for you to press. None of it is reachable until you accept this version. Everything you already use keeps working whether you accept or not.

The short version. Lamella connects an AI assistant you already pay for to your own Marrow account. You pick the vendor, so you own that relationship and its settings. Marrow controls what leaves your account, and it is counts, opaque pointers and, once you accept this version, your revenue in dollars, never member names, contact details, health data or messages. It never sees who paid. Your own typing is the one path that can carry member details out, and keeping it clean is your responsibility, not ours.

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 Lamella 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

Lamella 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 Lamella, 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 Lamella sends, so you know what you are sending

A connected assistant can reach your own business content, your site copy, your membership tiers, your session packages, your community post drafts, and the reports you save. About members, it can reach only the following.

• Counts of memberships by status, including how many are active, cancelled, or past due, and how many members sit on each tier.
• Session pack credit usage in aggregate, how many credits have been used and how many are left.
• Opaque per member pointers, a one way code standing in for one member so your assistant can flag that someone is close to running out of sessions. The code carries no name and no contact detail, and your AI vendor cannot reverse it.
• Timestamps, such as the date of the last community post.

It can also read your schedule, 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.

New in version 2026-08-18, and only once you have accepted it, a connected assistant can also reach your money at business altitude. None of the following names a member.

• 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.
• On a request that explicitly asks for them, your own individual payments. Each one carries an opaque coach scoped payment pointer, the stream, the amount, how much has already been refunded and how much is still refundable. That pointer stands for a PAYMENT, never for a person, and no client pointer is returned beside it.

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 at all, so treat any figure as what members paid you through Marrow rather than what lands in your bank.

It can never reach member names, email addresses, phone numbers, mailing addresses, health data, body metrics, nutrition detail, workouts, logged sessions, form videos, or messages between you and a member.

And it can never see who paid. This is the line that does not move with a setting, a version or a flag. No revenue tool reads a member name, an email address, a phone number or a client pointer, and none of them accepts an argument that could ask for one. A payment reaches your assistant as an amount, a stream and an age, and nothing that could name the payer travels beside it. When you need to know who a payment belongs to, open it in your Marrow dashboard, which is the only place that answer exists.

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 though no name was sent. 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 Lamella sends. It cannot control what you type. Your chat window and the free text of any report you save through Lamella are the one path that can carry a member's personal or health details to your AI vendor, and you agree not to use it that way.

• No member identities. Do not paste member names, email addresses, phone numbers, addresses, or photos into your AI chat or into a Lamella report.
• No health details. Do not paste injuries, diagnoses, medications, pregnancy status, body metrics, or anything a member told you about their health.
• No private messages. Do not paste conversations between you and a member, or anything a member posted in a private community.
• No payment detail. Do not paste what an individual member pays, their invoices, or anything from their billing record.
• Refer by pointer, not by person. If you need your assistant to reason about one member, use the opaque pointer Lamella gave you. That is what it is for.

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. It is two steps and never one, your answer is recorded with the change, and no other request can trigger it. Nothing else publishes: posts and programs arrive as drafts and a person presses the button.
• Nothing charges anyone. No checkout, no card, no payout is reachable by any Lamella tool.
• A refund is staged, never issued. Your assistant can stage a refund against one of your own payments, and staging writes a pending item and holds the amount against your spend ceiling. It sends nothing to Stripe, and there is no tool on this server that can send it. The refund happens only when you press it yourself while signed in to Marrow, and a refund cannot be undone once it is issued, so read the amount before you press.
• A price change is staged, never applied. Your assistant can stage a change to one of your own membership tiers or session packages. It writes no plan or pack row, your live price is unchanged, and applying it is a press you make yourself in Marrow. Marrow's own prices to you are not editable by any assistant.
• Nothing messages anyone. No email, no text, no push. Drafts come to you.
• Prices arrive switched off. Tiers and packages your assistant writes land inactive, and stay inactive until you turn one on yourself.
• 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 the Lamella surface entirely if something goes wrong.

Acceptance, records, and revocation

• There are two acceptance moments, and both run the same gate. Generating a Lamella connect code from your dashboard, 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. No acceptance, no connection.
• We record it. Marrow stores which account accepted, the version identifier of the text they accepted, and when. The version identifier of this text is 2026-08-30, 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.
• 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 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.