ORTB
中 / EN
Chapter navigation

USPrivacy String (GPP §6, legacy)

opt-outdeprecated · 2024-01

Role & classification

Four plaintext characters (version · explicitNotice · optOutSale · lspaCoveredTransaction), not base64-encoded — a ready-made counter-example to the assumption that section payloads must be bit-encoded. Support ended 2023-09-30, superseded by Global Privacy Platform (GPP) §6 in 2024-01; legacy traffic and some platform parameters still pass it directly, so it is honestly kept for debugging.

GPP section
§6 (uspv1)
Status
2024-01
Format
4 plaintext chars · no base64
Superseded by
GPP §6

String & field layout

Four plaintext characters (version · explicitNotice · optOutSale · lspaCoveredTransaction), not base64-encoded — a ready-made counter-example to the assumption that section payloads must be bit-encoded. Legacy traffic and some platform parameters still pass it directly, so it is honestly kept for debugging.

4 characters: version · explicitNotice · optOutSale · lspaCoveredTransaction
#FieldTypeDescription
1version1String specification version (always 1).
2explicitNoticeY / N / -Explicit notice/opportunity provided: Y yes, N no, - not applicable.
3optOutSaleY / N / -User opted out of sale/sharing: Y opted out, N did not, - not applicable.
4lspaCoveredTransactionY / NTransaction covered by the IAB Limited Service Provider Agreement.

Carriage & access

  • GPP §6 As a section payload it stays four plaintext characters with no bit encoding — a ready-made counter-example to the assumption that section payloads must be base64.
  • OpenRTB the regs.us_privacy field, the string passed directly.
  • URL the us_privacy parameter; legacy traffic and some platforms still pass it directly.

Version deltas

2023-09-30 停止支持 · 2024-01 由 GPP §6 承接

New integrations should no longer produce a USPrivacy string and should carry it in GPP instead: for the US national signal see the Multi-State Privacy Agreement (MSPA) US National chapter (§7), and for per-state signals see §8–§27.

Invalid forms

  • Does not match the regex 1[YN-][YN-][YN] (must be exactly 4 characters)
  • The leading version character is not 1
This chapter's body is migrated from the legacy /protocol/gpp-tcf single page; the material matches the official specification.