Event-Driven Notification Platform · View 13 of 26 · 3 · Data

Preference, Consent and Override Policy

Which notifications may ignore a stated preference, and on what authority.

Editable source SVG draw.io All views

The rule this view exists to state

Security and transactional notifications override an opt-out; operational and marketing never do
Every override writes an audit record naming the rule that authorised it, so a regulator can be answered from one query
Classification is set by the rule, not by the producer, so a producer cannot relabel marketing as transactional

Consent basis

Marketing requires explicit opt-in with timestamp and source recorded
Operational runs on legitimate interest and respects preferences in full
Quiet hours and frequency caps apply to everything except security and transactional

Risk

Misclassifying marketing as transactional is a regulatory breach, not a bug — drawn in red on the page
Controlled by requiring a second approver on any rule that sets a P0 class, and by a weekly report of P0 volume per tenant

◀ Core Data Model All views Notification Orchestration ▶