Beta Addendum
What's different during Brewstiller's invite-only, hobby-only, free beta.
Last updated: July 4, 2026
Plain-language summary
Brewstiller is launching with a limited beta before the v1.0 production release. If you've been invited, here's what's different from the main Terms of Service:
- Beta is invite-only, hobby-only, and free. No commercial workspaces, no payments, access by invitation only.
- No compliance filings in beta. The regulatory-filing feature is not available during beta, and nothing the beta produces is intended for regulatory submission.
- You're responsible for the legality of what you make — especially distilling. Home distilling remains prohibited by federal law in most of the US, and the law is unsettled. We don't determine what's legal for you; you do, with your own counsel if needed. Read §4 below and §8.6 of the Terms before you fire up a still.
- Beta software breaks. Export your data. No uptime commitments, no warranties, and while we intend to carry your data into production, we can't promise it. If losing something would hurt, export it — the export button exists for you.
- We may ask for feedback. No NDA — you're free to talk publicly about your experience, good or bad.
- Beta is free and provided as-is; our liability is capped at $100 (aside from things the law won't let us exclude). You're getting early software for free; that's the trade.
- The beta ends. At production launch this addendum stops applying and the main Terms take over.
The main Terms of Service still apply except where this addendum modifies them; in conflict, this addendum controls during the Beta Period.
1. Relationship to the Terms of Service
This Beta Addendum ("Addendum") supplements and, where stated, modifies the Brewstiller Terms of Service ("Terms") for the duration of your participation in the Brewstiller beta program (the "Beta Period"). By accepting an invitation and using the Service as a Beta Participant, you agree to both the Terms and this Addendum.
In any conflict during the Beta Period, this Addendum controls. Where it is silent, the Terms apply unchanged. When the Beta Period ends for you (§11), this Addendum stops applying.
Acceptance versioning. Your acceptance is recorded against the version identifier of this Addendum and of the Terms as published at the time of acceptance. Brewstiller will not present an acceptance action for any document that is not published and readable at the link presented.
2. Definitions
Capitalized terms have the meanings in the Terms, plus:
- "Beta Participant" — a person invited by Brewstiller, who has accepted the Terms and this Addendum and holds an active beta Account.
- "Beta Period" — per §3.1.
- "Beta Service" — the Service as offered during the Beta Period.
- "Feedback" — per §10.4 of the Terms, with the beta-specific provisions in §6.
- "Production Launch" — the date Brewstiller publicly transitions the Service from beta to v1.0 production availability.
3. The Beta Period
3.1 Definition
The Beta Period begins on the date Brewstiller invites you and ends on the earliest of: the Production Launch (transition per §11); Brewstiller's termination of your participation (§10); or your termination of your Account.
3.2 Beta restrictions
- Invite-only. Invitations are personal and non-transferable.
- Hobby workspaces only. Commercial Workspaces are not available.
- Free of charge. No Fees, no payment method, no invoices; Stripe is not engaged for Beta Participants.
- No Filing Feature. The regulatory filing-preparation feature (Terms §8.4, Compliance Filing Terms) is not available during the Beta Period. Any compliance-related surface visible in beta is a preview: its outputs are samples, are marked as such, and must not be submitted to any regulator.
- Limited features. Features may be missing, partial, differently-behaving, or removed before Production Launch.
3.3 Age and eligibility
Terms §1.2 applies without modification (21+ in the US).
4. Your production activities during beta — legality and safety
Because the beta audience includes home distillers, the following provisions of the Terms are specifically called to your attention and apply in full during the Beta Period:
- Terms §8.6 (Legality of your production activities). You are solely responsible for determining whether your production activities — including home distillation, which remains prohibited by federal law in most of the United States and by many states' laws, under legal rules that are currently unsettled and changing — are lawful for you, where you are. Brewstiller does not determine legality, does not verify permits, does not geo-restrict features, and the presence of a distilling feature is not a statement that using it is legal anywhere. If you are not certain an activity is lawful for you, consult your own counsel, and do not do it until you are.
- Terms §8.7 (Safety). The Beta Service's sensor readings and alerts — including still-monitoring views and temperature/threshold alerts — are informational conveniences under active development. They are not safety instrumentation, and in beta they are even more likely to lag, drop, or misreport. Never rely on them to detect or prevent a hazardous condition; supervise your equipment physically and follow safe operating practices.
- Terms §11.1 (AUP). Unlawful production is a violation of the AUP whatever tools you use.
Your beta attestation at signup includes your acknowledgment of this §4.
5. Modifications to specific Terms provisions during beta
5.1 Fees (Terms §5)
Suspended. The Beta Service is free; no billing mechanics are engaged.
5.2 Grandfathering anchor (Terms §6.4)
Your grandfathering anchor is the date you first subscribe to a Plan after Production Launch, not your beta invite date. Beta is not a Plan version to which grandfathering attaches. If you select a paid Plan at Production Launch, the §6.4 protections run from that subscription on that Plan version; if you land on Hobby Free, they run from that transition on Hobby Free as it stands that day.
5.3 Availability (Terms §17)
Superseded. The Beta Service is provided "as available" with no availability target, no service credits, and no maintenance-notice requirement. We use commercially reasonable efforts to keep it up and to announce planned downtime, but beta software is deployed, fixed, and restructured frequently; expect interruptions.
5.4 Support (Terms §18)
Best-effort only. No response-time targets apply. Priority goes to issues affecting multiple participants or platform stability. Reports with reproduction steps and screenshots genuinely help.
5.5 Limitation of liability (Terms §22)
Because Beta Participants pay no Fees, they are non-paid-commercial users under Terms §22.2. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, BREWSTILLER'S TOTAL CUMULATIVE LIABILITY TO A BETA PARTICIPANT ARISING OUT OF OR RELATED TO THE BETA SERVICE AND THIS ADDENDUM WILL NOT EXCEED ONE HUNDRED US DOLLARS ($100), REGARDLESS OF THE FORM OF ACTION OR THEORY OF LIABILITY (INCLUDING NEGLIGENCE). AS WITH TERMS §22.2, THIS CAP IS SUBJECT TO THE §22.4 EXCEPTIONS AND DOES NOT APPLY TO LIABILITY THAT APPLICABLE LAW DOES NOT PERMIT TO BE EXCLUDED — INCLUDING GROSS NEGLIGENCE, WILLFUL MISCONDUCT, FRAUD, AND DEATH OR PERSONAL INJURY CAUSED BY BREWSTILLER'S NEGLIGENCE. Terms §22.1 (no indirect damages), §22.3 (excluded amounts), §22.4 (exceptions), and §22.5 (all theories) apply during the Beta Period.
Assumption of risk. You acknowledge that beta software is provided for evaluation, that defects, outages, and data loss are inherent risks of pre-release software, and that you accept those risks as the price of early access to a free service.
5.6 Warranties (Terms §24)
Terms §24.1 (limited warranties) is suspended. THE BETA SERVICE IS PROVIDED "AS IS" AND "AS AVAILABLE" WITH NO WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, OR THAT IT WILL BE ERROR-FREE OR UNINTERRUPTED. Terms §24.2–24.5 apply with full force.
5.7 Data retention and termination (Terms §9.4, §20)
Beta data is Hobby Workspace data under the Privacy Policy, including that policy's deletion provisions (and their publication gates): full deletion within 30 days of termination of your participation or Account, with no commercial regulatory carve-outs — the 30-day outcome is the commitment; at beta scale, deletion may be performed manually rather than by an automated process. If your participation ends and you do not establish a post-launch subscription within 30 days, your beta data is deleted on that timeline; if you do, it carries forward per §7.
5.8 Changes during beta (Terms §26)
Because the Beta Service is actively developed, Brewstiller may modify the Beta Service, the Terms as applied to Beta Participants, and this Addendum on as little as 7 days' notice where reasonably necessary for operational, security, regulatory, or stability reasons; at least 14 days where reasonably practicable for changes that substantially affect participants. If you object, you may terminate per §9.
6. Feedback
6.1 Feedback as a participation expectation
Beta Participants are expected to engage in good faith with feedback mechanisms: surveys, optional interviews (typically 30–60 minutes; voluntary), in-app feedback widgets, and bug reports. No specific volume is required.
6.2 No NDA — discuss your experience freely
Beta Participants are under no non-disclosure obligation regarding their experience of the Beta Service. Blog it, post it, screenshot it, criticize it, talk to press — no prior approval needed. We deliberately run an open beta because authentic public feedback serves the platform's credibility better than a closed-doors beta.
6.3 Brewstiller's Confidential Information
§6.2 covers your experience as a user. It does not cover Brewstiller Confidential Information (Terms §16) that we share with you privately and mark confidential at disclosure (e.g., an early feature preview under an explicit confidentiality ask). Unmarked information is not Confidential Information.
6.4 Feedback license
Terms §10.4 applies to all Feedback during and after the Beta Period.
7. Data continuity
7.1 Intent
Brewstiller intends to carry Beta Participants' Customer Data forward to v1.0 production so continuing users find their recipes, batches, sensor history, notes, and attachments intact.
7.2 No contractual commitment — and your standing export duty
Brewstiller cannot contractually commit to data continuity during beta. Schema and storage changes between beta and production may make clean migration impracticable. If a migration cannot be made cleanly, we will notify affected participants as soon as identified, provide a complete export in a reasonable format before anything is lost, and work in good faith to preserve continuity.
Independent of any migration event: export regularly. You are responsible for your own copies of anything you cannot afford to lose (Terms §9.5); the export functionality is available throughout the Beta Period for exactly this purpose.
7.3 No data-loss compensation
Beyond the §7.2 export commitment, Brewstiller has no obligation to compensate Beta Participants for loss of Beta Service data, however caused. This reflects the inherent risk of beta software and is part of the consideration for the free, no-Fee structure of the Beta Period.
8. Confidentiality of Beta Participant identities
Brewstiller will not publicly identify Beta Participants without consent. Aggregate program statistics ("120 hobby brewers in our beta") may be shared. Quotes, testimonials, and case studies are published only with the participant's permission. Not wanting to be identified requires no action — it is the default.
9. Termination by you
Any time: close your Account in settings, or ask support. Effective immediately; data deleted per §5.7.
10. Termination by Brewstiller
10.1 For cause — immediately and without prior notice
If you materially breach the Terms, this Addendum, or the AUP; misuse the Beta Service in ways affecting stability or other participants; provide false information (including the §1.2 eligibility attestation); or attempt to circumvent invite-only access.
10.2 For any reason
With reasonable notice (typically ≥7 days where practicable; immediately when circumstances warrant). A beta program needs flexible management; this is part of the deal.
10.3 Effect
Access ends per the notice; you may export per §7.2 within a reasonable window (typically ≥14 days for non-cause terminations; shorter for cause terminations involving security or integrity concerns); data is deleted per §5.7 after the export window.
11. End of the Beta Period — transition to production
11.1 Notice
At least 30 days before Production Launch, participants receive: the launch date; the available post-launch Plans and pricing; instructions for selecting one; and a clear statement that this Addendum stops applying at launch.
11.2 At Production Launch
- This Addendum stops applying; the Beta Service becomes the production Service.
- Participants who selected a Plan transition automatically; data carries forward per §7.
- Participants who have not selected a Plan are placed on Hobby Free with a 30-day grace period to choose, export, or terminate; after grace, the Account continues as Hobby Free.
- Grandfathering (Terms §6.4) anchors per §5.2.
11.3 No obligation to go paid
Continuing on Hobby Free is always an option. If your beta usage exceeds Hobby Free limits, you'll be notified during transition and asked to reduce usage or subscribe to a fitting Plan.
11.4 Opt-out before launch
Terminate per §9 at any time before launch; data is deleted per §5.7 with no automatic transition.
12. Contact, governing law, miscellaneous
Beta program: [email protected]. Other matters: the contacts in Terms §28.
Terms §21 (Utah law; Salt Lake County exclusive jurisdiction; no mandatory arbitration; no class-action waiver) and Terms §27 (miscellaneous) apply to this Addendum. In conflict during the Beta Period, this Addendum controls; after the Beta Period it has no further effect.
Effective date: July 4, 2026 · Document version: v1.1
| Version | Effective date | Summary of changes |
|---|---|---|
| v1.0 | — (never published) | Initial draft. |
| v1.1 | July 4, 2026 | Production-legality/safety acknowledgment (§4); no-filing-in-beta (§3.2); assumption-of-risk and export-duty prominence (§5.5, §7.2); acceptance-versioning (§1). |