Terms/Privacy Policy Update Review

The first 10 questions

This is where the conversation starts. Each answer shapes what gets asked next.

1. 01What changed — a new feature, a new integration, a new data type you're collecting, a new region you're operating in?
2. 02Do you have your existing Privacy Policy and/or Terms of Service from Groundwork (or elsewhere) to work from?
3. 03Is this change live already, or are you updating the policy ahead of a planned launch?
4. 04Does this change affect what data you collect, how you use it, who you share it with, or how long you keep it?
5. 05Does this change affect what users are allowed to do, your liability, or your service commitments?
6. 06Is this change significant enough to require notifying existing users, or is it a minor update?
7. 07Specific sections affected: which parts of the existing Privacy Policy/ToS need new or revised language?
8. 08New language: draft the specific additions or edits needed for each affected section.
9. 09Notification requirement: does this trigger a legal obligation to notify users (material change), and how would you do that?
10. 10Effective date and versioning: how this update will be dated and how you'll track the change history.

+ 4 more questions across discovery, validation, and the creative brief — each one adapting to what you've already said.

Related legal project types

• Incorporate Now — and As What?Decide whether it's time to incorporate, and what to form — LLC, C-corp, or your home-country equivalent — based on what you're actually doing, not startup folklore.
• Founder AgreementWork through equity, vesting, IP ownership, roles, and what happens if someone leaves — before those conversations become awkward or costly.
• Privacy PolicyThink through what data you collect, how you use it, and who you share it with — and produce a privacy policy tailored to your product, not a generic paste job.