Join our Newsletter — 33% off our NHI Course
Home› Guides› Privacy Notice vs Privacy Policy: Which Document Does…
Guide Privacy & Data Protection

Privacy Notice vs Privacy Policy: Which Document Does Which Job

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 14 November 2026 15 min read
On this page

Many organisations publish one document called a "privacy policy" and assume it covers both what they must tell people and how their own staff must handle personal data, when in law these are two different obligations with different readers, owners and tests. The external privacy notice discharges a transparency duty to individuals: GDPR Articles 13 and 14, and the CCPA notice at collection and privacy policy rules in California. The internal privacy or data protection policy is a governance control: it tells employees and contractors what they must do, and it is part of how a controller demonstrates accountability under GDPR Article 24(2). This guide compares the two in depth, covering legal sources, contents, placement of cookie information, ownership, review cadence and the enforcement patterns that appear when the two are confused. It is written for privacy leads, DPOs, legal counsel, security and GRC teams and product owners who publish or approve these documents.

Key takeaways

  • Different reader, different duty. A privacy notice is written for the people whose data you use and must be concise, intelligible and easy to access; an internal policy is written for your workforce and must be specific, enforceable and auditable.
  • Naming is not the test. California law uses "privacy policy" for a public document, the ICO speaks of "privacy information", and many firms say "privacy notice": regulators judge the content, timing and placement, not the title.
  • Timing is a legal requirement. GDPR Article 13 information is due when the data is obtained, and the CCPA regulations say a business that does not give notice at or before collection must not collect the data.
  • Cookie information can sit in a separate notice. The ICO says consent cannot be shown if cookie information is buried in a hard-to-find privacy policy, so many firms keep a dedicated cookie notice linked from the consent banner and the main notice.
  • Drift between the two is the real risk. When the internal policy, the record of processing and the public notice describe different practices, the public notice becomes an inaccurate statement, which is how transparency enforcement cases often start.

The short answer

You need both. Publish an external privacy notice (or, for California, a privacy policy plus notices at collection) that tells individuals what you collect, why, on what basis, who receives it, how long you keep it and how to use their rights. Maintain an internal privacy or data protection policy that sets rules for staff: who may access what, how to classify and share data, when to run a DPIA, how to handle requests and breaches, and what happens when the rules are broken. The notice is a promise to the outside world; the policy is the mechanism that keeps the promise true.

Comparison table

DimensionExternal privacy noticeInternal privacy policy
Primary legal hookGDPR Articles 12, 13 and 14; 11 CCR 7011 and 7012 in CaliforniaGDPR Article 24(2) data protection policies; Article 5(2) accountability; DPA 2018 appropriate policy document where Schedule 1 requires one
AudienceCustomers, users, applicants, employees as data subjects, the publicEmployees, contractors, managers, internal audit
PurposeInform, so people can understand and exercise rightsDirect behaviour and allocate responsibility
LanguagePlain, concise, layered; CCPA 7003 asks for everyday wording and WCAG 2.1 accessibility onlinePrecise, normative ("must", "must not"), linked to standards and procedures
TimingAt collection (Article 13), within one month or at first contact for indirect data (Article 14), at or before collection (7012)Before staff process data; acknowledged on joining and on change
PlacementWebsite footer, forms, app settings, signage, call scriptsIntranet, policy management system, onboarding
OwnerPrivacy lead or DPO with legal; product owners supply factsPrivacy lead or DPO as author; executive approver; HR and security for enforcement
Change triggerNew purpose, recipient, transfer, retention period or data category; Article 13(3) requires notice before further processingNew law, audit finding, incident, organisational change
Enforcement exposureRegulator fines for transparency failures; GDPR Article 83(5)(b) puts Articles 12 to 22 in the higher fine tierEvidence in investigations of whether controls existed and were followed

What the external notice must contain

GDPR and UK GDPR

Article 13 lists what must be given when data is collected from the individual. The UK text on legislation.gov.uk sets it out as follows.

Article 13 itemContentWhere it usually comes from internally
13(1)(a), (b)Controller identity and contact details, representative, DPO contactLegal entity register, DPO appointment
13(1)(c), (d)Purposes, lawful basis, legitimate interests pursuedRecord of processing, legitimate interests assessments
13(1)(e)Recipients or categories of recipientsVendor register, data sharing agreements
13(1)(f)International transfers and safeguards, how to get a copyTransfer risk assessments, contract clauses
13(2)(a)Retention period or criteriaRetention schedule
13(2)(b), (c)Rights, and right to withdraw consentRights request procedure
13(2)(ca), (d)UK: right to complain to the controller and to the Information Commissioner (EU text: to a supervisory authority)Complaints procedure
13(2)(e), (f)Statutory or contractual requirement; automated decision-making with meaningful information about the logicProduct design records, DPIAs

Article 14 covers data obtained from other sources and adds the categories of data and the source. The ICO summarises the timing as within a reasonable period and no later than one month, with exceptions where the person already has the information or where providing it would involve disproportionate effort. The right column above is the point of this guide: every line of the notice should trace back to an internal record that the internal policy requires someone to maintain. See the Data Mapping and ROPA Guide.

California CCPA

California splits the external duty into two documents:

  • Privacy policy (11 CCR 7011): a "comprehensive description" of online and offline practices, covering categories collected in the past 12 months, sources, purposes, sale and sharing, rights and how to exercise them, how opt-out preference signals are handled, and the date last updated. It must be linked conspicuously with the word "privacy" on the homepage or app page.
  • Notice at collection (11 CCR 7012): a short notice at or before collection listing categories, purposes, whether each category is sold or shared, retention, the opt-out link where relevant, and a link to the privacy policy. Online, it may link straight to the relevant section of the privacy policy, but linking to the top of the policy so the consumer must scroll does not comply.

So in California the public "privacy policy" is not an internal policy at all, which is a common source of confusion for multinational teams. For the wider regime, see CCPA and CPRA and GDPR vs CCPA/CPRA.

What the internal policy must do

UK GDPR Article 24(2) requires appropriate data protection policies where proportionate to the processing. No article lists their contents, so the test is whether the policy makes the controller's measures real and demonstrable. A workable internal policy covers:

  • Roles: DPO or privacy lead, data owners, system owners, line managers, and who approves new processing.
  • Principles in operational form: what lawful basis approval looks like, minimisation rules, retention and deletion duties.
  • Triggers: when a DPIA is required, when a vendor needs a privacy review, when the public notice must be updated.
  • Rights and incidents: how requests are routed and answered, and how breaches are reported internally.
  • Special data: handling rules for special category and criminal offence data, including the appropriate policy document that many DPA 2018 Schedule 1 conditions require, as the ICO explains.
  • Enforcement: monitoring, exceptions, disciplinary consequences.

Use the Privacy Policy Template for internal wording and the Privacy Notice Template for the public document; this guide explains how they fit together rather than repeating them.

Threat model: what goes wrong when they are conflated

  • Internal rules published as a notice: the public sees statements of intent ("we may share data with partners") instead of specific recipients and purposes, which fails the Article 12 clarity test and tells nobody what actually happens.
  • Notice used as the only policy: staff have no binding rules, so practice drifts and the notice becomes untrue without anyone noticing.
  • Single document, single owner: marketing or legal edits the public text without the data owners, so it stops matching the record of processing.
  • Missing collection-point notices: a long policy in the footer, but nothing at the form, app screen or call where data is taken, which California rule 7012(d) treats as a bar to collecting at all.
  • Hidden material changes: a new purpose added silently to a long document, when Article 13(3) requires information before the further processing starts and the ICO says new uses must be brought to people's attention.

Enforcement patterns

Transparency cases tend to turn on what the public document said compared with what the organisation actually did.

CaseRegulator and dateWhat it shows
WhatsApp IrelandIrish Data Protection Commission, 2 September 2021, EUR 225 million after an EDPB binding decision of 28 July 2021The inquiry examined transparency information to users and non-users, including sharing with other group companies; the DPC also ordered remedial actions. Information about sharing between entities is exactly where internal reality and public text diverge.
SephoraCalifornia Attorney General, 24 August 2022, USD 1.2 millionThe business did not tell consumers it was selling personal information through third-party tracking, and did not honour Global Privacy Control signals. Remedies included updating the privacy policy and online disclosures. Tracking technologies set by marketing tools changed practice without the public document changing.

The lesson in both is the same: the notice must be generated from, and checked against, the internal records and controls the policy requires. A well-written notice that describes last year's data flows is still a transparency failure.

Cookie information is a separate obligation under PECR regulation 6 in the UK and the ePrivacy rules in the EU. The ICO says the information must be "clear and comprehensive", consent is needed for non-essential cookies, and consent cannot be shown if the information sits only in a privacy policy that is hard to find or rarely read. Practical placement:

OptionWhen it worksRisk
Separate cookie notice linked from the banner and the privacy noticeMost websites and apps with analytics or advertising tagsCookie list falls out of date unless generated from a scan
Cookie section inside the privacy notice, linked directly from the bannerSmall sites with few non-essential cookiesBanner link lands at the top of a long document
Consent management platform detail layer onlyAs a supplement, showing vendors and purposes at the point of choiceNo durable record of what the user was told if the platform changes

Whatever the layout, the privacy notice should explain the personal data aspects of tracking (purposes, recipients, retention), and the cookie notice should explain the device access and consent mechanics. See the Consent Management Guide and ePrivacy Directive vs GDPR.

Ownership and review cadence

ActivityExternal noticeInternal policy
AuthorPrivacy team, with plain-language reviewPrivacy team
Fact suppliersProduct, marketing, HR, procurement, securitySecurity, HR, records management
ApproverDPO or privacy lead and legalExecutive owner or board committee
Scheduled reviewAt least annually; California's statute requires the privacy policy disclosures to be updated at least once every 12 monthsAnnually, in line with the policy framework
Event reviewEvery new purpose, recipient, transfer, data category, retention change or tracking tagNew law, audit finding, incident, reorganisation
Evidence keptVersion history with dates, what changed, how users were toldApproval record, staff attestation, exception log

The ICO recommends user testing of privacy information and regular review, and its right to be informed guidance notes it is under review following the Data (Use and Access) Act 2025, so check the current version before relying on detail.

Decision criteria

  • Small organisation, one product: one layered public notice, one short internal policy, and a cookie section linked from the banner. Keep the record of processing as the shared source.
  • Multiple products or audiences: a main notice plus audience-specific notices (customers, job applicants, employees, website visitors), each traceable to processing records. Avoid one notice that tries to describe everything.
  • California consumers in scope: a CCPA-compliant privacy policy plus notices at collection on each form, app and offline channel, linking to the right policy section.
  • Heavy indirect collection: plan Article 14 delivery (at first contact or within one month) and document any disproportionate effort reasoning.
  • AI or automated decisions: meaningful information about the logic belongs in the notice; see the AI Transparency Notice Template.

Worked scenario

A software company adds a product analytics tool and starts sharing usage data with a support vendor based outside the UK. Under a combined single document, marketing installs the tag, nobody updates anything, and the public text still says data is "not shared with third parties except as required by law". Under a separated model, the internal policy's change trigger requires a privacy review before the tag goes live. The review updates the record of processing, adds the vendor and transfer safeguard to the register, updates the cookie notice from a scan, revises the notice sections on recipients and transfers, records the version, and informs existing users before the new processing starts, as Article 13(3) requires for a new purpose. The same review asks whether a DPIA is needed. See the DPIA Guide.

Implementing the two-document model

  1. Inventory current documents. List every public notice, cookie notice, form text and internal policy, with owner and last review date.
  2. Make the record of processing the single source. Map each notice statement to a processing record, retention rule and recipient entry; flag statements with no source.
  3. Split mixed documents. Move staff obligations into the internal policy and replace them in the public text with specific facts.
  4. Add collection-point notices. Short notices at forms, apps and offline channels, linking to the right section of the main notice.
  5. Wire change triggers. Product release, vendor onboarding and tag management processes must call a privacy review before go-live.
  6. Test with users. Check readers can find retention, sharing and rights information quickly; fix what they cannot find.
  7. Version and archive. Keep every published version with dates so you can show what a person was told at any point.
  8. Roll back safely. If an update is wrong, restore the prior version, record why and correct the underlying record, rather than editing silently.

Detection and measurement

  • Notice coverage: share of processing records traceable to a notice statement, and share of notice statements traceable to a record.
  • Drift alerts: new tracking tags or vendors detected by website scans or procurement that are not in the current notice.
  • Collection-point coverage: share of forms and app screens that collect personal data with a notice link in place.
  • Change lead time: days between a processing change being approved and the notice being updated (target: before go-live).
  • Policy attestation rate: share of staff who have acknowledged the current internal policy.

For a wider metric set, see Privacy Programme Metrics.

Framework mapping

FrameworkReferenceDocument it supports
NIST SP 800-53 Rev 5PT-5 Privacy Notice; PT-5(1) Just-in-time NoticeExternal notice and collection-point notices
NIST SP 800-53 Rev 5PM-20 Dissemination of Privacy Program InformationPublic privacy programme information
NIST SP 800-53 Rev 5PM-18 Privacy Program Plan; PT-3 Processing PurposesInternal policy and purpose records
NIST CSF 2.0GV.PO-01, GV.PO-02Internal policy established, communicated, reviewed and enforced
NIST CSF 2.0GV.OC-03Legal transparency obligations understood and managed
UK GDPRArticles 12 to 14; Article 24(2)External transparency; internal data protection policies

Practitioner checklist

  • Separate public notice and internal policy, each with a named owner and approver.
  • Every notice statement traceable to a processing record, retention rule or recipient entry.
  • Collection-point notices on every form, app screen and offline channel that takes personal data.
  • California privacy policy and notices at collection in place where the CCPA applies.
  • Cookie information reachable directly from the consent banner, generated from a current scan.
  • Change triggers in release, vendor and tag processes that require a notice review before go-live.
  • Version history kept for every published notice, with how users were told about material changes.
  • Internal policy covers roles, DPIA triggers, rights handling, special data and enforcement.
  • Annual review of both documents plus event-driven updates.

Standards and references

Related NHI Mgmt Group resources: Privacy Programme Guide for Security Teams, Cookie and Tracking Technology Compliance Guide, UK GDPR and Data Protection Act 2018 Guide, DSAR Guide. This guide summarises transparency and policy obligations and is not legal advice.

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 14 November 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.