Glossary
What are Privacy Nutrition Labels?
Privacy Nutrition Labels are standardised disclosures on app store listings that summarise an app's data collection and usage practices, shown before a user downloads.
The idea
Privacy policies are long, written for lawyers, and read by almost nobody. The nutrition label borrows a format from food packaging: a standardised summary, in a consistent structure, visible at the point of decision.
Categories cover what data is collected, whether it is linked to the user's identity, and whether it is used to track them across other companies' properties. Because the structure is fixed, apps can be compared — which a prose privacy policy makes effectively impossible.
How accurate they are
Self-declared, which is the obvious weakness, and it produced real problems early on. Studies after launch found substantial discrepancies between what apps declared and what they were observed doing, often because developers genuinely did not know what their third-party SDKs collected.
Privacy manifests were introduced largely to address that: the SDK declares its own behaviour in machine-readable form, and the app's label is assembled from verifiable inputs rather than from a developer's assumption.
Accuracy is meaningfully better as a result, and it remains a declaration rather than an audit.
What it means for advertising
A label declaring tracking is visible to every prospective user before download, which puts a real product cost on data collection that would previously have been invisible.
That has changed behaviour in a way regulation alone did not. Several categories of app removed SDKs specifically to keep a cleaner label, and 'data not collected' has become a marketing claim. It is one of the clearer demonstrations that disclosure at the point of decision affects conduct more than disclosure buried in a policy.
Common questions
Do labels affect download rates?
Modestly overall, and more in privacy-sensitive categories. The larger effect has been on developer behaviour, since a visible label creates a reason to reduce collection.
Who is responsible for label accuracy?
The app developer, including for data collected by third-party SDKs they bundle. That responsibility is what makes SDK auditing a release concern rather than a legal one.
More in privacy and compliance
The identifiers, consent signals and rules that bound targeting.