PlainBillCongress, translated.Legislation. Context. Public interest.Referred to the Subcommittee on Commerce, Manufacturing, and Trade.
Congressional Research Service
Version 00 · Introduced in House · Feb 10, 2016
Application Privacy, Protection, and Security Act of 2016 or the APPS Act of 2016
This bill directs mobile device application developers, before the application collects personal data about the user, to notify the user and obtain the user's consent regarding the terms and conditions governing the collection, use, storage, and sharing of such personal data.
Excluded from such notice and consent requirements is any "de-identified data" that cannot reasonably be used to identify or infer information about, or otherwise be linked to, a particular individual or mobile device, as determined with a reasonable level of justified confidence based on the available methods and technologies, the nature of the data at issue, and the purposes for which the data will be used.
Showing the opening paragraphs of the official summary.
Developers must: (1) provide users with a method to withdraw such consent and to request that the developer delete personal data or refrain from further data collection or sharing, and (2) take measures to prevent unauthorized access to personal and de-identified data.
Violations are to be treated as unfair or deceptive acts or practices under the Federal Trade Commission Act.
The Federal Trade Commission (FTC) must promulgate regulations to implement and enforce this Act.
States may bring civil actions in federal court on behalf of affected state residents.
Nothing in this Act prohibits a developer from disclosing or preserving personal data or de-identified data as required by other federal laws or, except when superceded by this Act, the laws of a state or political subdivision, including court orders.
A developer may satisfy the requirements of this Act by adopting and following a code of conduct for consumer data privacy that is approved pursuant to FTC regulations.
People & committees
Rep. Johnson, Henry C. "Hank," Jr. [D-GA-4] · D–GA
Legislative record
A procedural vote is different from passage. Passage in one chamber does not establish enactment. Explore the glossary.
Referred to the Subcommittee on Commerce, Manufacturing, and Trade.
Referred to the House Committee on Energy and Commerce.
Introduced in House
Introduced in House
Primary sources
Text links open the official source. We currently store references to these documents.
Source last updated: Aug 12, 2025. Consult Congress.gov for the current record.
AI Conversation Starters
Choose a perspective, copy a prompt, and paste it into your preferred AI. Each prompt includes the bill version and available official source links, and asks for counterarguments as well as supporting evidence.
Analyze H.R.4517 as objectively as possible. Explain its main provisions, who would be affected, possible benefits and harms, implementation, exceptions, and uncertainties. Present the strongest arguments for and against it, and identify evidence needed to assess its public impact.
Examine H.R.4517 through a progressive lens, focusing on fairness, access, economic inequality, and effects on vulnerable communities. Explain potential benefits, costs, and unintended consequences. Consider the strongest counterarguments and distinguish stated goals from demonstrated outcomes.
Examine H.R.4517 through a conservative lens, focusing on fiscal responsibility, institutional stability, federalism, and the scope of government. Explain potential benefits, costs, and unintended consequences. Consider the strongest counterarguments and any provisions that challenge this perspective.
Examine H.R.4517 through a civil-liberties and limited-government lens. Consider individual rights, privacy, voluntary choice, accountability, and government power. Explain tradeoffs, possible safeguards, and the strongest counterarguments without assuming the proposal is beneficial or harmful.