Users notified of material changes before they take effect

GDPR Art. 13(3) requires that when you make material changes to how you process personal data, you re-notify affected users before those changes take effect. GDPR Art. 7(3) requires that withdrawing consent be as easy as giving it — which implies users must know when consent conditions change. CCPA §1798.130(a)(5)(B) requires notifying consumers of material changes to privacy practices. If your Terms of Service states "we will notify you by email" of changes but no email dispatch mechanism exists for legal updates, that statement itself is a misrepresentation — and regulators have cited exactly this gap in enforcement actions. eprivacy Art. 5(3) adds cookie consent re-notification requirements when consent scope changes.

Document your notification procedure explicitly in the Terms of Service, then implement a version-tracking mechanism to trigger notifications when terms change.

In your Terms of Service, add:

## Changes to These Terms

When we make material changes, we will: update the "Last updated" date,
send an email to your registered address at least 14 days before the changes
take effect, and display a notice on our website. Your continued use after
the effective date constitutes acceptance.

In your database, add a terms_version field to the users table and check it on login:

const CURRENT_TERMS_VERSION = 2  // Increment when terms change materially

// On login, after session is established:
if (user.acceptedTermsVersion < CURRENT_TERMS_VERSION) {
  // Show a "We've updated our terms" modal or redirect to /terms-updated
}

Trigger a bulk email via your transactional email provider (Resend, Postmark, SendGrid) whenever CURRENT_TERMS_VERSION increments.