Privacy policy
Also called a privacy notice.
A privacy policy is a public notice describing how an organization collects, uses, shares and retains personal information, and what rights people have. Publishing one does not, by itself, give permission to collect or use that information.
This page focuses on US businesses and their public-facing notices, not internal rules for employees.
Key takeaways
- Write the policy around actual data practices, including analytics tools, advertising pixels and service providers.
- A small business is not automatically exempt from privacy-notice requirements.
- Misleading privacy promises can trigger Federal Trade Commission action for deceptive practices.
- A template is a starting point, not evidence that your product complies with the law.
How a privacy policy works
Start with a data inventory: what enters the business, where it comes from, who receives it and when it gets deleted. Check the product, website, payment systems, customer support tools and third-party software.
Turn that inventory into a notice people can find and understand. Depending on the applicable law, some disclosures must also appear where information is collected. A footer link alone is not always enough.
Keep the notice current when practices change. Adding an advertising SDK, collecting location data or using customer content to train models deserves a privacy review before launch, not just a wording change afterward.
Question absolute claims. Before saying "we collect no personal information," check IP addresses, cookies and device identifiers.
A three-month deletion promise with twelve months of data
Consider a subscription app with 200 account closures every month. Its policy promises to delete closed-account profile data from its production database within three months. The actual deletion job runs after twelve months.
The following figures are illustrative. They cover only profile records, exclude separately retained invoices and use steady monthly closures, with deletion at the end of each retention period.
| Practice | Retention period | Closed-account profiles retained at steady state |
|---|---|---|
| Policy promise | 3 months | 200 × 3 = 600 |
| Actual system | 12 months | 200 × 12 = 2,400 |
| Difference | 9 months | 1,800 extra profiles |
Three months is not a legal default here. It is the company's own commitment.
The mismatch leaves 1,800 more profiles in production than the promised process would retain. Changing the policy does not erase earlier misleading statements. The company needs to address the system, the notice and any consequences of the mismatch.
For a startup raising money, this can become remediation work during diligence. Investors may compare the current policy with data-flow records and vendor agreements. Check that those materials agree before sharing them.
What the law says the notice must contain
California's Online Privacy Protection Act, or CalOPPA, provides a useful concrete example. California Business and Professions Code section 22575 requires covered commercial websites and online services to conspicuously post a privacy policy.
The statute calls for disclosures including:
- Categories of personal information collected and categories of third parties receiving it.
- How users can review or request changes to information, if the operator maintains such a process.
- How users will be notified of material policy changes.
- The policy's effective date and specified tracking disclosures.
These are disclosure duties, not permission to use data however the business wants. Separately, Section 5 of the Federal Trade Commission Act prohibits unfair or deceptive practices. A privacy promise that contradicts the product's behavior can create risk under that rule.
Privacy policy versus terms of service
| Document | Main purpose |
|---|---|
| Privacy policy | Explains personal-information practices and applicable rights |
| Terms of service | Sets rules for using the product and the contractual relationship |
| Internal privacy policy | Tells staff how to handle personal information |
Putting a privacy-policy link beside an "I agree" checkbox does not automatically create valid consent for every data use.
Questions people ask
What do you write in a privacy policy?
Identify the business and a contact method, then describe data categories, sources, purposes, recipients, retention and applicable rights. Explain how people exercise those rights. Add disclosures required for your activities and audience; do not copy promises your systems cannot support.
Is it illegal to collect data without a privacy policy?
It can be. CalOPPA requires a notice for covered commercial sites and online services collecting personal information from California residents, without a revenue threshold. Other laws impose their own notice or consent requirements. Having a policy does not make otherwise unlawful collection lawful.
What are the new privacy laws in US states?
States have separate privacy laws with different coverage, exemptions and rights. Examples include Delaware's Personal Data Privacy Act, effective January 1, 2025, and New Jersey's privacy law, effective January 15, 2025. Check the relevant state's current requirements rather than treating a California notice as a nationwide template.
