Agreement Calls for Mobile App Privacy Disclosures But Does It Have Teeth?
Sample screens disclose what is collected and how it is shared (Source: NTIA) — A new voluntary code has been tentatively established to assure greater transparency in the types of information apps collect …
Context & Ripple Effects
Mobile privacy policy coverage in 2012 documented an uneven disclosure baseline, while the FTC's February guidance for app developers put mobile-specific privacy controls, including Do Not Track, on the policy agenda. The proposed code turns that debate toward a common presentation for what apps collect and share.
Because the arrangement is voluntary and tentative, its significance lies less in creating a new legal obligation than in giving developers and users a shared disclosure format against which app privacy practices can be compared.
First-order effects
- App developers participating in the proposed code would need to present what information their apps collect and how they share it in the agreed disclosure screens.
- Users gain a more consistent basis for comparing an app's data practices before deciding whether to use it.
Second-order effects
- Developers that already publish privacy policies, an issue highlighted in earlier coverage of mobile app privacy policies, face pressure to make those policies more specific and easier to compare.
- The FTC's mobile privacy guidance gains a practical companion: disclosure design can translate broad expectations into an app-level user choice.
Third-order effects
- If adoption broadens, standardized disclosures can make privacy practices a product-selection criterion rather than a detail buried in separate policies.
- A voluntary format also makes adherence the central test: the framework can normalize transparency without itself establishing an enforcement mechanism.
The trend: Mobile privacy is moving from generic policy statements toward standardized, user-facing disclosures about collection and sharing.