Terms of service and privacy policy basics for your website
What terms of service and a privacy policy do, what to include in each, how CCPA, COPPA and the Consumer Review Fairness Act affect them, and a simple routine to keep them accurate.

If your business has a website that takes orders, collects email addresses, runs a contact form or lets people create accounts, you probably need two documents: terms of service and a privacy policy. They are often lumped together, and many owners paste in a template and forget it. That is risky, because a privacy policy is a set of promises, and a promise you do not keep can become a legal problem.
This guide explains what each document does, what to put in them, which US laws shape them, and how to keep them accurate. It is general information, not legal advice. Privacy law changes quickly and varies by state, so have an attorney review your documents, especially if you handle sensitive data or serve children.
Two documents, two jobs
| | Terms of service | Privacy policy | | --- | --- | --- | | Purpose | Sets the rules for using your site or service | Explains what personal information you collect and what you do with it | | Audience | Visitors, customers, account holders | Anyone whose data you handle | | Legal nature | A contract between you and the user | A disclosure and a set of promises | | Required by law? | Not generally, but strongly advisable | Often yes, depending on your data practices and location | | Typical home | Footer link, sign-up page, checkout | Footer link, forms, sign-up page, checkout |
Terms of service may also be called terms of use or terms and conditions. Think of them as the house rules. The privacy policy is the honest description of what happens to people's information.
Part 1: Terms of service
What to include
- Who you are and what the service is. Your business name, contact details and a short description.
- Acceptable use. What users may not do, such as breaking the law, attacking the site or abusing other users.
- Accounts. Who may register, keeping passwords secure, and your right to suspend accounts.
- Payments and refunds. Prices, billing, renewals, cancellations and refund rules, matching what your checkout and invoices say.
- Intellectual property. You own your content and brand; what users may do with them; what license you need for content users upload.
- Disclaimers and limits on liability. Plain statements that the service is provided as described, with caps on liability where permitted. Courts and states treat some limits differently, so this section deserves legal review.
- Termination. How either side can end the relationship.
- Governing law and disputes. Which state's law applies and how disagreements will be handled.
- Changes. How you will tell users when the terms change.
Make acceptance clear
For terms to work as a contract, users should have a clear chance to agree. A checkbox or "I agree" button next to a visible link to the terms is a stronger signal than a link buried in a footer. Keep a record of acceptance, such as the date and the version shown. Our guide to e-signatures and their legal standing explains why electronic agreement generally counts, and how to keep evidence of it.
One clause to check: reviews
Many standard templates include a line stopping customers from posting negative reviews. Federal law makes that kind of clause void in a form contract. The Consumer Review Fairness Act voids provisions that prohibit or restrict reviews and ratings, impose a fee or penalty for them, or force people to hand over intellectual property in their review content. Exceptions allow you to remove content that is, for example, clearly false, harassing or obscene, and to protect trade secrets. Employer and contractor agreements are not covered by this rule. If your terms contain a "no bad reviews" clause, remove it. Our guide on getting customer reviews ethically covers the broader rules.
Part 2: Privacy policy
Why you need one
Even if no single federal law requires every website to post one, privacy policies are expected by customers, payment processors, advertising platforms and app stores, and state laws such as California's require one for many businesses. More importantly, the Federal Trade Commission has said that businesses that make privacy promises, stated or implied, must keep them, and that policies should describe actual practices. The FTC also warns that even a business with no explicit privacy claims must keep security appropriate to the sensitivity of the data. Deceptive claims can violate Section 5 of the FTC Act.
The practical lesson: write what you actually do, not what sounds good.
What to include
- What you collect. Names, emails, payment details, IP addresses, cookies, analytics identifiers, support messages, files, and anything from forms.
- How you collect it. Directly from users, automatically through cookies and analytics, or from third parties.
- Why you use it. Providing the service, billing, support, marketing, security and legal compliance.
- Who you share it with. Payment processors, email tools, analytics and hosting providers, advisers, and authorities when required.
- Whether you sell or share it for advertising, and how people can opt out.
- How long you keep it. And what happens when someone closes an account.
- How you protect it. At a general level, without exposing security details.
- People's choices and rights. How to see, correct or delete their information, unsubscribe, or opt out.
- Children. A statement about whether your site is meant for children.
- Contact details for privacy questions, and the date the policy was last updated.
Laws that may apply
California. The California Attorney General's page on the California Consumer Privacy Act says the law applies to for-profit businesses that do business in California and meet any one threshold: annual gross revenue above $25 million; buying, selling or sharing the personal information of 100,000 or more California residents or households; or earning 50 percent or more of revenue from selling personal information. A covered privacy policy must describe collection, use, sharing and sale practices, explain consumer rights and how to use them, and include a "Do Not Sell or Share" link where relevant. A notice at collection must list the categories of information collected and why. Consumers can ask to know, delete, correct, opt out and limit use of sensitive data. A small business below those thresholds may not be covered, but California also has a separate law requiring online privacy policies for operators collecting personal information from its residents, and other states have comprehensive privacy laws with different thresholds. Check each state where your customers live.
Children. The Children's Online Privacy Protection Act makes it unlawful, under 15 U.S.C. section 6502, for operators of sites directed to children, or that actually know they collect a child's personal information, to do so in violation of FTC rules. Those rules require notice and verifiable parental consent, access for parents, reasonable security, and limits on collecting more than is necessary. According to the FTC's COPPA guidance, the rule protects children under 13 and applies to commercial operators of child-directed sites and services, as well as general-audience sites with actual knowledge that they collect children's data. If you might attract children, get legal advice before collecting anything.
Other rules. Email marketing, payments, health or financial data, and other sectors have their own obligations. Our guides on email marketing rules and AI and customer data privacy cover two common areas.
A review process you can repeat
- Map your data. List every form, cookie, analytics tool, plugin and app, and what each collects.
- Draft or update the documents to match the map, using plain language.
- Have a lawyer review the first version, then reuse it.
- Place links clearly. Footer on every page, plus sign-up, checkout and forms.
- Date and version them. Keep old copies.
- Re-check twice a year, and whenever you add a tool or change practices.
- Train your team to send privacy requests to one named person.
Common mistakes
- Copying another company's policy. It will describe their practices, not yours.
- Promising what you do not do, such as "we never share data" while using ad trackers.
- Forgetting new tools. Every added analytics or chat plugin may change your data flows.
- Burying the links. If people cannot find the documents, they are less useful as evidence.
- Including a no-reviews clause.
- Ignoring data security. A policy does not protect data; passwords, access controls and backups do. See our cybersecurity basics.
- Not updating the date after changing the document.
Keeping your documents consistent with WorkBOS
If you collect leads or requests through your website, WorkBOS forms and the CRM keep submissions in one place, roles and permissions limit who can see customer data, and the audit log shows who touched a record. Software does not write your legal terms, but it helps your practices match your promises. See the docs and pricing; the Free plan needs no card.
Frequently asked questions
Q: Do I need both a terms of service and a privacy policy? A: If you run a website that collects any personal information or sells to the public, a privacy policy is expected and often required, and terms of service are strongly recommended because they set the rules and limit your risk.
Q: Can I use a free template? A: A template is a reasonable starting point, but you must edit it to match your actual practices and the laws of the states where you operate. An inaccurate policy can be worse than none.
Q: Does the CCPA apply to my small business? A: Only if you do business in California and meet one of the thresholds in the law: more than $25 million in annual revenue, handling data of 100,000 or more California residents or households, or earning half your revenue from selling personal information. Other state laws have their own thresholds.
Q: Do I need a cookie banner? A: It depends on your tools, your audience and the laws that apply. If you use advertising or tracking cookies, check the state rules where your visitors live and consider a clear choice for opting out.
Q: How often should I update these documents? A: Review them at least twice a year and whenever you change tools, services, pricing or data practices. Update the date and keep earlier versions.
Sources are linked in the text above: Cornell Law School Legal Information Institute (15 U.S.C. 45b, 6502), California Attorney General (CCPA). Also referenced: Federal Trade Commission privacy and COPPA guidance.
Run it all from one place
Projects, clients, finance, people and AI employees in one system. Start free, no card needed.
Start free →