Paragraph match score 81.1%
Page A-018
Troubleshooting consent-token deployments
Symptom: services keep processing data after a user withdraws consent. Fix: look for long-lived JWTs that embed consent flags, shorten their lifetime, and ensure the gateway re-evaluates consent against the ledger for each call that touches personal data rather than trusting stale snapshots.
Page A-039
Troubleshooting consent issues in production
Symptom: Users continue to receive marketing messages after withdrawing consent in the app. Likely cause: one or more outbound channels read local "opt_in" flags instead of central consent decisions. Fix: remove local flags from ESP or CRM integrations, require a real-time check_consent call or event-driven subscription before each batch, and backfill revocation events by querying the central consent ledger.