PRE-LAUNCH / DESIGN SYSTEM   ·   All product, governance, and capability statements describe design targets and require independent verification before deployment.
RIGHTS · DESIGN TARGET

Consumer rights center.

Pseudonymization is not anonymity. The planned system is designed to honor exclusion at the boundary and inspection through documented responses. These are design targets; forms below are non-submitting placeholders.

01 · WHAT YOU CAN ASK

Opt-out, access, deletion, correction.

DESIGN TARGET · RIGHT

Opt-out

A deployed service would stop including the requesting token in cohort construction and propagate suppression within a documented window.

DESIGN TARGET · RIGHT

Access

A deployed service would return a description of cohort-bucket participation at the cohort level, not the user level.

DESIGN TARGET · RIGHT

Deletion

A deployed service would delete the requesting token and associated non-cohort records. Cohort aggregates may persist until they decay.

DESIGN TARGET · RIGHT

Correction

A deployed service would support correction of identity-domain records. Token correctness would remain a separate operation bound by rotation policy.

02 · GPC

Global Privacy Control target behavior.

When a participating surface forwards a Global Privacy Control (GPC) signal, BingBong targets suppression at the boundary rather than at the buyer. GPC is treated as a privilege boundary, not a soft preference. This is a design target until the partner surface roster is operational.

SignalTarget behaviorStatus
Sec-GPC: 1Suppress token issuance; suppress event ingestion.DESIGN TARGET
DNT: 1 (legacy)Documented behavior; not relied upon as the primary signal.DOCUMENTED
Opt-out via this rights formSuppression at ingestion within documented window.DESIGN TARGET
03 · SUBMIT A REQUEST (DEMO)

Forms are non-submitting placeholders.

A real submission path is not deployed in pre-launch. The form below demonstrates the planned shape and does not transmit data.