Privacy Policy

Breaking up the privacy policy into machine-readable, schema defined properties that allow for the legal side of an API to be understood programmatically. A privacy policy sets the stage when it comes to consumption, helping consumers with what they can expect when it comes to how their data and usage of digital resources will be shared or sold.

Also known as: Privacy Notice, Privacy Statement, Data Protection Notice

Example

privacy-policy.yaml
- type: PrivacyPolicy
  url: https://example.com/privacy

Standards

HTTP Headers

HeaderDirectionSpecDescription
Link response RFC 8288 May advertise rel="privacy-policy" pointing at the policy URL.
Sec-GPC request Global Privacy Control (W3C CG draft) Signals the user's opt-out of sale/sharing under CCPA/CPRA.
DNT request W3C Tracking Preference Expression (Note) Legacy Do Not Track signal; largely superseded by Sec-GPC.

Status Codes

OpenAPI Expression

Link Relations

Governance Rules

Risk & Compliance

Compliance:

Security: A privacy policy is the consumer-facing surface of the data-protection program. It must accurately describe data collected, purposes, lawful bases (GDPR), retention, sub-processors, international transfers (SCCs/adequacy), security measures (Art. 32), and individual rights with response SLAs. Misalignment between the policy and actual API data flows is itself a regulatory and reputational risk. Version the policy, surface effective_date, and notify users of material changes before they take effect.

Tools

Suggested Metrics

Example Implementations

Related Properties

Tags


All Common Properties