A policy governing data privacy
A privacy policy is the public statement of what a product does with personal data: what it collects, why, who it shares with, and how long it keeps it. Regimes like GDPR and CCPA make it mandatory rather than optional. The honest version describes what the product actually does; the gap between the policy and the practice is where most privacy trouble starts.
The privacy policy became a legal obligation, not a courtesy. Under GDPR's transparency duty, a controller must tell people, at the point of collection, who is collecting their data, for what purposes, and on what legal basis. California's CCPA, as amended by the CPRA, requires a "notice at collection" that lists the categories of personal information collected and how each is used, shared, or sold, and it permits that notice to be delivered as a linked section of the privacy policy (TermsFeed, CCPA Notice at Collection).
The bar has risen past mere disclosure. Current CCPA regulation expects the notice to state retention periods, whether data is sold or shared, and the named third parties controlling collection, and to be accessible to users with disabilities under WCAG (CPPA, General Notices). The drift across regimes is toward specificity: a vague "we value your privacy" page no longer satisfies a regulator, because the policy is now read as a list of verifiable claims.
That shift makes the policy-versus-practice distinction the one that matters. A privacy policy is a promise about data handling. If the product collects a field the policy omits, or retains data past the period it states, the document is not protecting the company; it is a written admission of the gap.
A consumer app's policy says it collects email and usage events, keeps them for twenty-four months, and shares nothing with advertisers. An engineer adds a marketing SDK that quietly ships device identifiers to an ad network. The product now does something the policy denies. A regulator or a researcher reading the policy against the actual network traffic finds the contradiction, and the document that was meant to be a shield becomes evidenceEvidenceValidationData supporting or refuting a hypothesisView reference →. The fix is to model the policy against the real data sourcesData SourceData & AnalyticsA data source or integrationView reference →, so that adding a new collector flags the policy that has to change before the featureFeatureProduct SpecificationA product capability or featureView reference → ships, not after a complaint.
compliance_framework_requires_privacy_policyCompliance FrameworkrequiresPrivacy Policyhierarchy connects them.privacy_policy_governs_data_sourcePrivacy PolicygovernsData Sourcecross-domain makes checkable.In the Unified Product Graph the privacy policy lives in the legal domain, with three defining edges. Productgoverned byPrivacy Policyhierarchy ties it to the product it speaks for; product_governed_by_privacy_policyCompliance FrameworkrequiresPrivacy Policyhierarchy records the regime that mandates it; and compliance_framework_requires_privacy_policyPrivacy PolicygovernsData Sourcecross-domain bridges into the data and analytics domain to name exactly what the policy covers. The domain's standing warning is the privacy policy with no scope, because a policy that connects to no data source is a promise no one can verify.privacy_policy_governs_data_source
Type-specific fields on BaseNode
versionstringVersion identifier of the policy
last_updatedstringDate the policy was last updated (ISO format)
effective_datestringDate the policy takes effect (ISO format)
urlstringURL where the policy is published
regulationsstring[]Regulations this policy addresses (e.g. "GDPR", "CCPA")
idstringrequiredUnique identifier (UUID)
typeNodeTyperequiredDiscriminator for the entity type
titlestringrequiredDisplay name
descriptionstringOptional detailed description
statusstringLifecycle status
tagsstring[]Freeform tags for filtering
5 phases — initial: proposed · template: APPROVAL
3 edge types connected to this entity.
product_governed_by_privacy_policycompliance_framework_requires_privacy_policyprivacy_policy_governs_data_source