Terms
The agreement between you and Brick, in plain words.
Last updated 10 September 2026
These terms apply when you use Brick — the app at app.trybrick.io, the API at api.trybrick.io, the MCP server, and this site. Using any of them means you accept them.
The most important thing on this page
Brick is a planning tool, not a coach and not a medical service. It arranges training you decide to do, using numbers you give it. It does not know your history, your injuries, your sleep, or how you actually felt on Tuesday.
Endurance training carries real risk of injury and, rarely, of serious harm. You are responsible for what you do. Get medical advice before starting or substantially increasing training, and stop if something is wrong — a plan on a screen is not a reason to keep going. A ceiling Brick draws is a number you set, not a safety limit anyone verified.
Your account
- You need to be 16 or older to have an account.
- Give a real email address — it is how you recover access, and there is no other route back in.
- Keep your password and API tokens to yourself. Anything done with your credentials is treated as done by you, so revoke a token the moment you suspect it has leaked.
- One account per person. Sharing one means sharing a training history, which serves nobody.
Your data is yours
You own everything you put into Brick. Brick stores and processes it to run the service and for nothing else — it is not sold, not shared for advertising, and not used to train models. You can export all of it or delete all of it at any time from Account → Data, without asking.
Brick owns the software, the design and the name. These terms don't give you rights to those beyond using the service.
What you agree not to do
- Try to reach another athlete's data, or to get around the boundaries between accounts.
- Hammer the API hard enough to degrade it for anyone else. There are rate limits; treat them as the intent, not as a target.
- Resell Brick or run it as a service for other people without agreeing that first.
- Use it for anything illegal, or to harm anyone.
Agents and the API
You can point an AI agent at your plan over MCP, using a token you create. Everything that agent does is your action under these terms — it is acting with your credentials, on your data, at your instruction. Brick records which changes came from an agent so you can always tell them apart, and you can revoke the token at any time. Check what an agent proposes before applying it; that is exactly why every change is shown as a diff first.
Availability
Brick is early software run by one person. It will have bugs and it will occasionally be down. There is no uptime guarantee, and features may change or be removed while the product finds its shape. Anything that would lose your data or change what it means gets told to you first.
Your data is backed up, but keep your own export if a season matters to you. That is true of every service and it is honest to say so.
Payment
Brick is free while it is in beta. If paid plans arrive, existing accounts get clear notice before anything is charged, and nothing you have already put in gets locked away because you chose not to pay.
Ending it
You can delete your account whenever you like, from inside the app, and everything goes with it. Brick may suspend an account that is breaking the rules above — with an explanation, unless the account is actively attacking the service.
Liability
Brick is provided as it is. To the extent the law allows, Brick is not liable for injury, lost training, missed races, or indirect losses arising from using it. Nothing here limits liability for death or personal injury caused by negligence, for fraud, or for anything else that cannot lawfully be limited.
Law
These terms are governed by the law of England and Wales, and its courts have jurisdiction. If you are a consumer, this does not take away rights you have under the law of where you live.
Changes
These terms may change as Brick does. The date at the top moves when they do, and a material change is emailed to you rather than left for you to find.