Terms, privacy, and the fine print.
Last updated 28 September 2026
Disclaimers.
1.1 Brix is for people of legal drinking age
Brix is a tool for recording and scaling alcoholic drink recipes. Do not use it, and do not create an account, unless you are of legal drinking age where you live. In the United States that is 21. Elsewhere it varies, and it is your responsibility to know which rules apply to you.
Nothing here encourages excessive drinking. Alcohol carries real health risks, those risks increase with quantity, and some people should not drink at all. Never drive after drinking. If you serve other people, you may be subject to dram shop or social host laws in your jurisdiction, and this page is not a defence to any of them.
1.2 Food safety is your responsibility, and some of these techniques carry real risk
Several Brix tools cover techniques that are not risk-free. Infusions, fat washes, milk punches, clarification, and batching all involve holding food outside its original packaging, often for days, sometimes at room temperature, and sometimes with dairy, oil, or fresh produce in the mix.
Oil infusions containing fresh garlic, herbs, or other low-acid produce are a documented botulism risk: the anaerobic environment is favourable to Clostridium botulinum, and the toxin it produces can be fatal. Dairy-based preparations and anything held warm carry their own hazards. Brix gives you ratios and volumes. It does not, and cannot, tell you whether a particular batch is safe to drink.
Follow tested food-safety guidance for anything you infuse, preserve, or store. In the US, the National Center for Home Food Preservation and your local extension service publish tested methods; the USDA's botulism guidance is a good starting point. When in doubt, refrigerate it, or throw it out.
1.3 Every number Brix shows you is an estimate
ABV, dilution, total volume, batch quantities, and every other figure in the app are calculated from the values you type in. They are arithmetic on your inputs, not measurements of your drink. Real dilution depends on your ice, your technique, and how long you shook it. Real ABV depends on what the bottle actually contains.
Do not rely on these numbers for anything that matters legally or medically: not for labelling, not for licensing or compliance, not for deciding whether someone is fit to drive, and not for managing a medical condition. Measure, do not assume.
1.4 How Brix is built, and what that means for you
Brix is made by a very small team, and much of its code was written with the help of AI coding assistants. That is disclosed here because you deserve to know how the software you are trusting with your work was produced. It is offered as is, without warranty of any kind, and it may contain defects.
To be clear about the other direction: no generative AI runs inside Brix. Nothing you read in the app is machine-generated at the moment you read it, no model is fed your recipes, and the “smart recommendations” in the modifier tools are ordinary arithmetic with rules we wrote, not a language model guessing.
1.5 None of this is professional advice
Brix is not a source of medical, nutritional, food-safety, legal, or licensing advice. Recipes and techniques in the app, including those written by other users, have not been tested or verified by us. If you are cooking for the public, running a bar programme, or managing an allergy or a health condition, get advice from someone qualified to give it.
Terms of use.
2.1 Using Brix
By using Brix you agree to these terms. If you do not agree, do not use it. You must be of legal drinking age where you live, as described in §1.1, and you are responsible for keeping your account credentials to yourself and for everything done from your account.
2.2 Your recipes stay yours
You keep ownership of everything you create in Brix. You grant us only the permission we need to actually run the service: to store your content, back it up, and display it to you and to the people you choose to share it with. That permission ends when you delete the content or your account, subject to §3.5.
Sharing a recipe into a community gives that community its own copy, which its members can edit independently of yours. That is the intended behaviour, it is described where you do it, and it cannot be undone by deleting your original.
2.3 What other people post is theirs, not ours
Communities and public recipes are written by users. We do not review, verify, endorse, or take responsibility for them, and a recipe appearing in a public community is not a claim by us that it is safe, accurate, original, or any good.
Do not post content you have no right to post, content that is unlawful, abusive, or deceptive, or anything that targets or endangers other people. Do not use Brix to market alcohol to people below legal drinking age. We can remove content and suspend accounts that break these rules, and any signed-in user can report a public community from its page.
If you believe something on Brix infringes your copyright, write to work@mixwithbrix.com with enough detail to identify the work and where it appears, and we will look into it.
2.4 No warranty, and limited liability
Brix is provided as is and as available, without warranties of any kind, express or implied, including any implied warranty of merchantability, fitness for a particular purpose, or non-infringement. We do not promise the service will be uninterrupted, that it will be free of defects, or that anything in it is accurate.
To the fullest extent the law allows, we are not liable for indirect, incidental, special, or consequential damages, or for any loss of data, profit, or goodwill, arising out of your use of Brix. Some jurisdictions do not allow these exclusions, in which case they apply to you only as far as local law permits. Nothing here limits liability for death or personal injury caused by negligence, or for fraud, where the law does not allow that limit.
2.5 Changes
We may change the service or these terms. When we change the terms materially, we will update the date at the top of this page. Continuing to use Brix after a change means you accept it. You can stop using Brix and delete your account at any time.
Privacy policy.
3.1 What we collect
Your account. An email address and a password, which is hashed by our authentication provider and never visible to us. A username is generated for you at signup, and you can change it. You can also add a display name and a profile photo; both are optional and shown on your recipes and in communities.
What you create. Recipes, modifiers, communities, memberships, and the invitations you send, including the email address you send an invitation to.
Email delivery records. Whether a transactional email we sent you was delivered, so we can tell a broken address from a broken service.
Aggregate usage. Page views via Vercel Analytics, which we use to see which parts of the app get used. We do not run advertising trackers and we do not sell anything about you.
On your own device. Your unit preference, your light or dark theme choice, your recently viewed items, and a cache of your recipes so the app works offline. This lives in your browser's local storage, not on our servers, and clearing your browser data clears it. When you are signed in, your theme, units and default batch size are also saved to your account so they follow you to other devices.
3.2 Why we collect it
To give you the service you asked for, to keep your account secure, to send you the transactional email the service depends on, and to understand usage in aggregate so we can improve it. We do not sell personal information, and we do not share it for advertising.
3.3 Who else processes it
Running Brix means trusting a few infrastructure providers, each of which processes data on our behalf: Supabase for the database and authentication, Vercel for hosting and analytics, and Resend for transactional email. Their infrastructure may be located outside your country, including in the United States.
3.4 Cookies
Brix sets a session cookie so you stay signed in. That is the whole story: no advertising cookies, no cross-site tracking, and nothing that follows you off this site.
3.5 How long we keep it, and what survives deletion
When you delete your account, we hide it straight away and permanently delete it 7 days later. Sign in during those 7 days and the deletion is cancelled. We also keep 7 days of nightly database backups, so deleted content can persist in a backup for up to 7 more days — about 14 days in total — before it ages out.
Recipe copies you shared into a community stay with that community after you leave, unless you choose to delete them along with your account. Where a credit is linked to your account — your recipes, riffs of them, and community copies — it follows your privacy setting: with "Show my name on shared recipes" off, or once your account is deleted, it reads "A Brix member" instead of your name, and so does your entry in community member lists. A few older credits were saved as plain text before we linked them to accounts; where we couldn't match one to a current username, it keeps the name as it was written. If you want one of those removed, ask us and we will do it.
We keep a short record of each deletion, including the email address and username, for 30 days so we can confirm it ran. After that those details are removed from the record too.
3.6 Your rights
You can ask us for a copy of the personal data we hold about you, ask us to correct it, or ask us to delete it and close your account. Depending on where you live you may also have the right to object to or restrict certain processing, or to complain to your data protection authority. You can export your recipes and delete your account yourself, any time, from your profile. For anything else, write to work@mixwithbrix.com and we will action it.
3.7 Children
Brix is not for children. We do not knowingly collect data from anyone below legal drinking age, and we will delete any account we learn belongs to one.
Contact.
Questions about any of this, a copyright complaint, or a request about your data all go to the same place: work@mixwithbrix.com. You can also reach us through the contact page.