- Is this legal advice?
- No. This tool produces a template, not a finished legal document, and using it does not create an attorney-client relationship. Have a qualified attorney in your jurisdiction review the output before you publish it on your site. State and country laws differ — consumer protection rules in the EU, California, and Brazil all add requirements a generic template cannot anticipate.
- Do I need a Terms of Service?
- If you run a website, app, or store that accepts users or money, you should have one. The Terms set the rules of use, limit your liability, and give you grounds to remove a misbehaving user. They don't have to be public-facing to be useful — but most companies link them in the footer.
- What is the difference between Terms of Service and Privacy Policy?
- Terms of Service govern what users can and cannot do on your site, your liability, payment terms, and dispute resolution. A Privacy Policy describes what personal data you collect, how you use it, and how users can request access or deletion. Most sites need both. Some jurisdictions (GDPR in the EU, CCPA in California) legally require a Privacy Policy regardless of whether you have a ToS.
- Should I require binding arbitration?
- It is common in US consumer contracts because it caps litigation cost and waives class actions. It is restricted or unenforceable in many other countries (most of the EU treats class-action waivers as void in consumer contracts). If you sell to consumers outside the US, the arbitration toggle may be unenforceable for those customers even if the document includes it.
- What refund window should I pick?
- There is no single right answer. 'No refunds' is enforceable in most jurisdictions for digital services but is increasingly disfavored. A 14- or 30-day window is the most common SaaS standard; e-commerce sellers often offer 30 or 60 days. EU consumers have a 14-day statutory right of withdrawal that applies regardless of what your Terms say.
- Does this document cover the EU GDPR or California's CCPA?
- Not directly — those are privacy frameworks, not Terms-of-Service frameworks, and they require a separate Privacy Policy plus operational disclosures (cookie banners, opt-out flows, data-subject-access procedures). The Terms produced here mention privacy by reference but do not draft the privacy disclosures themselves.
- Can I use this for a mobile app?
- Mostly yes — most of the clauses apply to apps, too. But Apple and Google have their own developer agreements that override yours in some areas (in-app purchase refunds, account closure procedures). Your app's Terms of Service supplement, not replace, those store policies.
- Why does the output have 'AS IS' and 'WITHOUT WARRANTIES' in all caps?
- US contract law often requires that warranty disclaimers and limitations of liability be 'conspicuous' to be enforceable, and the established practice is to render them in all caps so they cannot be missed in skim-reading. The capitalization is not stylistic — it is a legal-effect convention.
- Is my information stored or sent anywhere?
- No. The widget runs entirely in your browser. Nothing you type is sent to a server, saved to a database, or logged. Once you close the tab, the values are gone — copy or download the document if you want to keep it.
