Disclosure · 119 filers

Privacy Compliance

119 companies wrote this into a filing in the last 14 days, up from 78. Below: which of them, and what the corpus says they now owe.

Data measured , page built 22 September 2026 at 16:18 UTC.

119filers, current period
78the period before
6controls it touches
5frameworks
first appears Feb 2008 2008 2026 116 filings in the busiest month
Privacy Compliance in 10-K and 10-Q filings, by month. The marked line is the first month any public company in our record used the phrase; everything left of it is nobody writing it down.
Companies disclosing it 119 wrote this into a filing with the SEC
What it obligates 6 controls across 5 frameworks whose text speaks to it
Employers hiring for it 2,655 open US roles name it, and the ones below are hiring now

The long view, in annual and quarterly filings

A 10-K or 10-Q is a periodic report, so this counts how often the phrase appears in routine annual and quarterly reporting. It moves far more slowly and the numbers are larger. Every month since 2008. The last point is the current month and is still filling, so it always looks lower than it will be.

 
058116
2008 peak 116 in February 2026 2026

Who disclosed it

From SEC full-text search over 8-K filings. Every row links to the filing itself.

CompanyFormFiled
TANDEM DIABETES CARE INC TNDM8-K2026-08-06filing
Four Leaf Acquisition Corp8-K2026-09-02filing
Data443 Risk Mitigation, Inc. ATDS8-K2026-09-02filing
Chiron Real Estate Inc.8-K/A2026-08-17filing
Golub Capital Direct Lending Unlevered Corp8-K2026-08-07filing
GOLUB CAPITAL DIRECT LENDING CORP8-K2026-08-13filing
Golub Capital BDC 4, Inc.8-K2026-08-06filing
REGIS CORP RGS8-K2026-09-01filing
Bluerock Acquisition Corp.8-K2026-08-03filing
8X8 INC /DE/ EGHT8-K2026-09-09filing
WHIRLPOOL CORP /DE/8-K2026-08-03filing
GOLUB CAPITAL BDC, Inc. GBDC8-K2026-08-03filing
OCULUS INC. OVTZ10-Q2026-08-06filing
Meta Platforms, Inc. META10-Q2026-07-30filing
Intapp, Inc. INTA10-K2026-08-14filing
Sports Entertainment Gaming Global Corp10-K/A2026-07-31filing

The full search on EDGAR

Who is hiring for it

A sample of the open roles naming this phrase. An employer paying a salary against something is the least ambiguous demand signal there is, and every row links to the posting so the claim can be checked rather than believed. The total above is the whole US market; these are the ones we hold the posting for.

RolePosted
Lead Security Compliance Engineer
Klaviyo, Inc. · Boston, MA
2026-09-22
Lead Security Compliance Engineer
Klaviyo, Inc. · Denver, CO
2026-09-22
Recruiting Coordinator (12 months contract)
Pure Storage, Inc. · Bangalore, India
2026-09-10
Senior Software Development Engineer L4
Inovalon Holdings, Inc. · Remote- United States
2026-09-09
Compliance Manager (Data Protection Officer, Regulatory Compliance & Privacy)
Affirm Holdings, Inc. · Remote UK
2026-09-03
Marketing Technology Lead
Lyft, Inc. · Toronto, Canada
2026-09-03
Sr Privacy Compliance and Ops Manager
INTUITIVE SURGICAL INC · Peachtree Corners
2026-09-02
Sr Privacy Compliance and Ops Manager
INTUITIVE SURGICAL INC · Sunnyvale
2026-09-02
Senior Privacy Counsel
PINTEREST, INC. · Dublin, IE
2026-08-31
Solution Architect
Akoya Biosciences, Inc. · Boston, MA. New York, NY. Raleigh, NC.
2026-08-25
Head of Compliance
Astra Space, Inc. · Remote - US Only
2026-08-24
Marketing Operations Manager
MongoDB, Inc. · Dublin, Ireland
2026-08-24
Associate General Counsel, Privacy Compliance
Cloudflare, Inc. · Hybrid
2026-08-21
HR System Admin
Pure Storage, Inc. · Bangalore, India
2026-08-21

Which industries file it

Companies grouped by the industry classification on their own filing. A count, not a survey.

IndustryCompanies
Chemicals and pharmaceuticals79
Software and IT services73
Not classified64
Banking22
Holding and investment offices21
Instruments and medical devices18
Electronics and electrical equipment18
Health services17
Services and entertainment17
Insurance16

What it obligates

Our corpus holds 6 controls across 5 frameworks whose text speaks to this. Not a judgement: these controls say so, and each is one lookup from its source document. Ordered by how much each framework has to say about it, so the one that will cost you the most work is first. Every name opens that framework in the corpus.

FrameworkControls
ISO/IEC 29100:2024
International
2
HKMA SPM
Hong Kong
1
NIST SP 800-181 verified
United States
1
Global Cross-Border Privacy Rules (Global CBPR) Forum verified
International (Global CBPR Forum)
1
GS1 Global Standards verified
International (GS1 — 116 countries)
1

What an auditor will ask you to produce

The artefacts named on those controls, most frequently cited first.

How it usually fails

Recorded when each control was verified against its source. This is where programmes that think they are covered turn out not to be.

GDPR Evidence & Implementation Kit

40 controls sit behind GDPR, and this is the documentation set for them: an adopt-ready artifact per control, and the evidence an auditor asks for against each.

See what is in it, $249

The same set every buyer of this kit receives. Nothing here is produced on request.

GDPR ISO 27701:201990 shared controlsAPEC Cross-Border Privacy Rules…90 shared controlsNIST SP 800-53 Rev 574 shared controlsSOC 272 shared controlsAICPA Privacy Management Framewo…66 shared controlsAPPI65 shared controlsCloud Security Alliance Cloud Co…63 shared controlsSwitzerland New Federal Act on D…49 shared controlsAustralia My Health Records Act…49 shared controlsFederal Decree-Law No. 45 of 202…47 shared controls
GDPR holds 40 controls. They appear again inside 268 other frameworks in our corpus; the 10 strongest are shown. Thickness and size both carry the number of controls shared, so work done once counts in every framework on this diagram.
40If you already run GDPR, that is the 40 controls behind this disclosure, already evidenced.
138And ISO 27701:2019 is not a separate programme. 138 of its controls are the same controls. If it is on next year's plan, that part of it is already done.
35And ISO 27002:2022 is not a separate programme. 35 of its controls are the same controls. If it is on next year's plan, that part of it is already done.
34And ISO 27001:2022 is not a separate programme. 34 of its controls are the same controls. If it is on next year's plan, that part of it is already done.

Run as two programmes

178 controls

GDPR and ISO 27701:2019 scoped separately, each with its own evidence, its own owner and its own budget line. This is how almost everybody does it.

Run once, counted twice

138 already done

138 of ISO 27701:2019's controls are controls you evidenced for GDPR. Same artefacts, same owner, no second effort. The mapping is the only reason anybody knows.

first appears Feb 2008 2008 2026 116 filings in the busiest month
Privacy Compliance in 10-K and 10-Q filings, by month. The marked line is the first month any public company in our record used the phrase; everything left of it is nobody writing it down.

What this actually means

Why now
119 public companies wrote this into an 8-K in the last seven days, 53% more than the seven before. That is not sentiment or a survey. It is a count of companies choosing to put a phrase into a document they are legally accountable for.
Who already cares
2,655 open US roles name this work today, which suggests increased attention to it beyond what any filing says. A job advertisement clears a budget holder and a filing clears legal, so the two answer to different people. We have not measured which moves first, only that both are moving.
What comes into scope
Once the phrase is on the record it maps to obligations within GDPR, CCPA/CPRA, AICPA Privacy Management Framework (PMF). 140 controls behind those, and the difference between asserting them and evidencing them is the whole of the work.
Who is quietly ahead
Anyone already running GDPR has done 138 of the controls that carry ISO 27701:2019 too. Same evidence, second standard. Most organisations run those as two programmes with two budgets because nobody told them the mapping existed.
Who is exposed
13 companies disclosed this for the first time in the last ninety days, out of 457 in total. A first mention is a company deciding it can no longer not say it. Whoever has not yet is either genuinely unaffected or has not looked, and nothing here distinguishes the two.

What this obligates

The instruments in our corpus that govern this disclosure, and how many controls sit behind each. This is not a filing count. It is what applies once a company has written the phrase down.

7 frameworks, 140 controls between them.

GDPR ISO 27701:201990 shared controlsAPEC Cross-Border Privacy Rules…90 shared controlsNIST SP 800-53 Rev 574 shared controlsSOC 272 shared controlsAICPA Privacy Management Framewo…66 shared controlsAPPI65 shared controlsCloud Security Alliance Cloud Co…63 shared controlsSwitzerland New Federal Act on D…49 shared controlsAustralia My Health Records Act…49 shared controlsFederal Decree-Law No. 45 of 202…47 shared controls
GDPR holds 40 controls. They appear again inside 268 other frameworks in our corpus; the 10 strongest are shown. Thickness and size both carry the number of controls shared, so work done once counts in every framework on this diagram.

What closing it also moves

The same controls appear in other frameworks through mappings held in our corpus. Work done here is already progress there. This is the part that is not in EDGAR and not in any public dataset: it comes from mappings built and verified by hand, control by control.

ISO 27701:2019138
ISO 27002:202235
ISO 27001:202234
NIS2 Directive23

Counted as controls reached through cross-framework mappings. It measures overlap of work, not compliance with the named framework.

Run as two programmes

178 controls

GDPR and ISO 27701:2019 scoped separately, each with its own evidence, its own owner and its own budget line. This is how almost everybody does it.

Run once, counted twice

138 already done

138 of ISO 27701:2019's controls are controls you evidenced for GDPR. Same artefacts, same owner, no second effort. The mapping is the only reason anybody knows.

40If you already run GDPR, that is the 40 controls behind this disclosure, already evidenced.
138And ISO 27701:2019 is not a separate programme. 138 of its controls are the same controls. If it is on next year's plan, that part of it is already done.
35And ISO 27002:2022 is not a separate programme. 35 of its controls are the same controls. If it is on next year's plan, that part of it is already done.
34And ISO 27001:2022 is not a separate programme. 34 of its controls are the same controls. If it is on next year's plan, that part of it is already done.

If that number surprised you, the same measurement across every topic we track:
What changed this week →

This is what it looks like when the same failure is named by standards bodies who never spoke to each other:
How compliance programmes fail →

And the companies that have already written this into a filing:
Privacy Compliance filers →

Tell me when Privacy Compliance files something new

One email when a public company newly discloses this, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

Where this comes from

The left half is public record: SEC full-text search over 8-K filings, counted across a 14 day window against the equivalent window before it. You can check every row.

The right half is ours: 723 frameworks and 20,473 controls, 531 of those frameworks verified against their source documents, with the auditor evidence and common failure modes recorded control by control. Controls appear here because their own text names this term.

Cite this

The Art of Service Signals. Privacy Compliance corporate disclosure activity: 119 filers against 78 in the prior period, in 10-K and 10-Q filings, this quarter against the same quarter last year. Accessed 23 September 2026. https://signals.theartofservice.com/t/privacy-compliance/

Free to use with attribution, no permission needed. The chart downloads as an SVG with the source printed on it. If you cite it we would like to know, but you do not need to ask.

Today's edition · How programmes fail · The obligation index