Phase 3: Consent & Privacy (Week 2-3, Parallel)

7.1 Understand Consent Requirements

Before EdgeTag sends any data, users must have consented. This is non-negotiable for:

• ✓ GDPR (EU users)
• ✓ CCPA (California users)
• ✓ CPRA (California users, expanded)
• ✓ Platform terms (Meta, Google require explicit consent)

7.2 How Consent Works With EdgeTag

Simple flow:

1. User visits your site
2. Consent banner appears (your existing popup/banner)
3. User clicks "Accept" or "Reject"
4. You send their consent choice to EdgeTag via a GTM tag
5. EdgeTag only sends data to ad platforms if user accepted

What Your Consent Tag Does

When a user accepts the cookie banner, this tag fires:

Send consent signal to EdgeTag:
- "Marketing/Advertising: YES"
- "Analytics: YES"
- "Share PII with platforms: YES"

For Your Dev/Analytics Team

Integrate your existing cookie/consent banner CMP (like Termly, OneTrust, etc.) with EdgeTag:

1. When user accepts consent, fire EdgeTag consent tag
2. Specify which purposes they consented to (advertising, analytics, share_pii)
3. If consent is missing, EdgeTag won't send data to ad platforms

Critical for compliance: You must capture and respect user consent. If you do not, regulators can fine you 1-4% of global revenue under GDPR. Set this up correctly from day 1.