Legal
The terms governing use of huzlly.com and the closed-beta product. Huzlly is in closed beta, and these terms are being finalized alongside it.
This page lays out the sections a terms-of-service agreement like Huzlly's typically needs and what each one is for. It does not contain finished legal language, and nothing here should be read as an actual obligation, warranty, or liability term. Every section below has a dashed placeholder block marking exactly where real legal copy needs to go — have that copy reviewed before this page goes live.
A statement that using huzlly.com or the product means agreeing to these terms, and what happens if someone doesn't agree.
Your legal language goes here
Standard acceptance clause and effective date.
A plain description of what Huzlly does — connecting proposal approval, contract signing, invoicing, and project setup into one flow — and a note that it's currently pre-launch and evolving during closed beta.
Your legal language goes here
Service description and any "as-is during beta" framing you want to formalize.
Who can sign up (e.g. minimum age, acting on your own behalf as a freelancer or solopreneur), and the account holder's responsibility for their login credentials.
Your legal language goes here
Eligibility criteria and account-security obligations.
Terms specific to being in a limited cohort — that access is invite-based, that features, availability, and pricing may change before general availability, and how feedback given during the beta may be used.
Your legal language goes here
Beta-specific disclaimers, cohort access terms, and feedback-license language if you want one.
A note that pricing isn't public yet (see the pricing page), that Huzlly will be a free tier plus one flat-rate paid upgrade with no per-seat fees, and how billing and cancellation will work once pricing launches.
Your legal language goes here
Billing cycle, cancellation, and refund terms once pricing is set.
What's expected of a user running client work through Huzlly — accurate information, lawful use, and not using the flow to defraud or misrepresent terms to their own clients.
Your legal language goes here
Acceptable-use rules and prohibited conduct.
Who owns what — the user's proposals, contracts, and client data stay theirs; Huzlly's product, branding, and code stay Huzlly's.
Your legal language goes here
Ownership and license terms for user content vs. the Huzlly product/brand.
A note that parts of the flow (payment processing, e-signature) run through third-party providers, and that their terms apply alongside Huzlly's.
Your legal language goes here
Name the actual providers once they're locked in, and how responsibility is split.
The standard disclaimer that the service is provided without certain warranties, especially relevant while it's in closed beta.
Your legal language goes here
Warranty disclaimer language — get this reviewed rather than drafted casually.
The cap on what Huzlly is liable for if something goes wrong — this is one of the highest-stakes clauses in the whole document.
Your legal language goes here
Liability cap and excluded damages — strongly recommend a lawyer draft this one specifically.
How and when an account can be closed, by the user or by Huzlly, and what happens to data on termination.
Your legal language goes here
Termination triggers and post-termination data handling.
Which jurisdiction's law applies and how disputes get resolved.
Your legal language goes here
Governing jurisdiction and dispute-resolution method (courts vs. arbitration).
How updates to these terms will be communicated, and how someone can tell when they were last changed.
Your legal language goes here
Notice method and where the "last updated" date will live.
Huzlly