Developers

Decision Schema

Decision records describe requests processed by the GPCGuard endpoint. They help explain endpoint behavior; they do not prove legal compliance or downstream suppression by themselves.

FieldTypeMeaning
signal_idstringUnique identifier for the processed request decision record.
processed_atISO timestampWhen the endpoint processed or recorded the decision.
sitestringConfigured customer domain associated with the decision.
signal_sourceheader | navigator | noneWhether Sec-GPC, navigator.globalPrivacyControl, or no signal was observed.
gpc_enabledbooleanWhether the endpoint observed an enabled GPC preference.
decision_outcomeHONORED | DENIED | FAILED | NO_SIGNAL_OBSERVEDCustomer-facing outcome label for evidence review.
policy.honoredbooleanWhether the configured policy honored the observed signal.
policy.sale_opt_outbooleanWhether the response indicates sale opt-out should be applied.
policy.sharing_opt_outbooleanWhether the response indicates sharing opt-out should be applied.
policy.targeted_advertising_opt_outbooleanWhether the response indicates targeted-advertising opt-out should be applied.
compliance_standardstringCustomer-configured compliance label returned with the decision.
policy_versionstringPolicy or evidence version label, when available.
guard_resultsarrayGuard-stage outcomes used to explain the endpoint decision.
downstream_handoff_notestringReminder that suppression outside GPCGuard depends on customer wiring.

Guard-Chain Table

GPCGuard guard results should identify the stage that passed, denied, or failed. Typical stages include rate limit, site existence, origin, active site, DPA acceptance, circuit breaker, and policy decision.

Downstream Handoff

A HONORED decision should be treated as an input to customer-controlled systems. Customers need to map it into CMP state, tag-manager rules, CDP suppression, server-side event logic, and ad-partner controls.