A business model in which organisations monetise personal data, behavioural signals, and metadata rather than only charging for a product or service. The security concern is not simply collection, but the way pervasive data harvesting reduces user control, obscures tradeoffs, and creates long-lived privacy exposure across platforms and partners.
What surveillance capitalism means in practice
Surveillance capitalism describes a business model that treats personal data, behavioural signals and metadata as economic assets. The security problem is broader than collection alone: once data is continuously harvested, combined and re-used, people lose meaningful control over how it is interpreted, retained and shared across systems and partners.
That makes the model different from ordinary advertising or analytics. The core issue is not a single dataset, but an ecosystem of persistent observation, inference and resale that can turn routine product telemetry into long-lived exposure.
How data harvesting becomes a security concern
Security risk emerges when collection is pervasive enough to create detailed profiles, sensitive inferences or cross-context tracking. Even when individual records seem innocuous, behavioural aggregation can expose habits, relationships, location patterns, device fingerprints and other signals that users never expected to be durable or portable.
This also changes the attack surface. The more organisations and intermediaries that hold or derive value from the same data stream, the more opportunities there are for misuse, unauthorised access, accidental disclosure or secondary exploitation.
Why control over data is hard to preserve
Surveillance capitalism weakens control because users usually cannot see the full chain of collection, enrichment and onward transfer. Consent notices often describe categories of processing without making the downstream implications obvious, especially when metadata and inferred attributes are reused for new purposes.
The problem is compounded by opacity across platforms. A dataset may be shared with ad tech, analytics, brokers or service partners, then recombined with other sources to create profiles that are technically lawful in some contexts but difficult to challenge or revoke in practice.
What long-lived exposure changes for organisations and users
Once behavioural data is retained or replicated broadly, its impact can outlast the original session or service interaction. Historical data may remain useful for targeting, scoring or prediction, but it also creates a persistent privacy footprint that can be re-identified, breached or repurposed later.
For users, that means the harm is often cumulative rather than immediate. For organisations, the issue is not only trust, but the lifecycle of the data itself, including retention, transfer, secondary use and the difficulty of undoing exposure after the fact.
Risk and Threat Considerations
Surveillance capitalism creates privacy and trust risk because the same monetisation machinery that values data at scale can also concentrate sensitive signals, expand sharing paths and normalise retention beyond what people reasonably expect. The longer and wider the data flows, the more likely it is to be misused, breached or combined into revealing profiles.
Failure mechanism: Persistent collection, enrichment and onward transfer turn ordinary product telemetry into a durable dossier, then make it hard to trace who received it, how it was re-used and whether the original purpose still applies.
Impact: Users can lose meaningful control over personal information, organisations can inherit long-tail privacy exposure, and compromised or repurposed datasets can support profiling, targeting, discrimination or other downstream harm.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5 and NIST CSF 2.0 set the technical controls, while GDPR defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| GDPR | A.5.15 — Access Control | Surveillance capitalism depends on broad data sharing and access governance. |
| A.5.12 — Classification of Information | Behavioural data and metadata need classification to govern retention and reuse. | |
| A.5.34 — Privacy and Protection of PII | The term centers on persistent personal-data exposure and user control. | |
| Recommendation — Limit access to personal data and restrict onward sharing to defined purposes. Classify personal and inferred data so handling rules match sensitivity. Apply privacy controls to collection, sharing, retention and downstream processing. | ||
| NIST SP 800-53 Rev 5 | AC-6 — Least Privilege | Minimizes who can access or repurpose harvested data and derived profiles. |
| AU-2 — Event Logging | Visibility into collection, transfer and reuse is central to this data-exposure model. | |
| Recommendation — Constrain access to collected data and derived records to the minimum required. Log collection, sharing and profile-building activity for review and accountability. | ||
| NIST CSF 2.0 | PR.DS-01 — Data-at-Rest is Protected | Long-lived retained data must be protected to reduce exposure from persistence. |
| GV.OC-01 — Organizational Context is Established | Business-model decisions around monetized data require explicit governance context. | |
| Recommendation — Protect stored personal data and derived profiles against unauthorized exposure. Define how data monetization, privacy expectations and partner sharing fit organizational context. | ||
Practitioner Guidance
Why practitioners should care: The practical question is not whether data can be collected, but whether the business model depends on sharing more detail than the user would reasonably expect. Treat behavioural data, metadata and inferred attributes as high-consequence information when they can reveal identity, habits or intent.
Governance implication: Ownership should extend beyond collection to retention, transfer, enrichment and secondary use. A service that monetises data needs clear decisions on purpose limitation, partner access, deletion expectations and what happens when signals are recombined into new profiles.
Practitioner takeaway: If the organisation cannot explain the full data lifecycle in plain language, it likely cannot demonstrate durable user control either.
Related resources from NHI Mgmt Group
- Who is accountable when a compromised official account is used for fraud or surveillance?
- How should organisations control access to frontier AI systems without creating surveillance risk?
- Why do on-chain inflows matter for market surveillance?
- Who should own escalation when market surveillance suggests manipulation?
Deepen Your Knowledge
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.
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org