Terms of Service Review Template

Review the ToS at least quarterly and after every major feature launch. Any feature that changes data collection, adds third-party integrations, modifies pricing, or introduces AI-generated content should trigger a review. Most legal teams will appreciate a structured list of changes rather than a vague "can you check the ToS?" request.

No. Legal owns the terms of service. The PM's role is to flag when product changes create gaps between what the ToS says and what the product does. This checklist helps you surface those gaps in a structured way so legal can update the language efficiently.

Terms of service govern the relationship between the company and the user: what the product does, what users can and cannot do, liability limits, and dispute resolution. The privacy policy specifically covers how user data is collected, stored, shared, and deleted. Both documents should be consistent. If the ToS says "we do not share data" but the privacy policy allows third-party analytics, you have a conflict. Use the [Privacy Policy Checklist Template](/templates/privacy-policy-checklist-template) to audit your privacy policy separately.

Yes. Beta features should be explicitly excluded from service guarantees, uptime [SLAs](/glossary/sla-slo-sli), and support commitments. Without this exclusion, a customer could argue that a beta feature failure violates your service agreement. Most SaaS companies add a "Pre-Release Services" section that limits liability for beta functionality.

The standard approach is to notify users via email and in-app banner at least 30 days before changes take effect. For material changes (pricing, data rights, liability terms), most legal teams require affirmative consent rather than passive notice. Your product should track which ToS version each user has accepted and surface re-acceptance prompts when the terms change. Use [feature flags](/glossary/feature-flag) to gate ToS-dependent features until users accept updated terms. ---