APPS Act of 2016
The source supplies the latest action, but no lifecycle stage.
Latest action (12 Feb 2016): Referred to the Subcommittee on Commerce, Manufacturing, and Trade.
What this bill does
The APPS Act of 2016 would require developers of mobile applications to inform users about how their personal data will be collected, used, stored, and shared. Before collecting this data, developers would need to obtain the user's consent to these terms and conditions. Users would also be given a way to withdraw their consent and request that their data be deleted or that further collection and sharing cease.
This bill affects individuals who use mobile applications and the developers of those applications. It aims to provide users with more control and transparency over their personal data. The bill also requires developers to take steps to protect collected data from unauthorized access. De-identified data, which cannot reasonably be used to identify an individual, would be excluded from these notice and consent requirements.
This bill was introduced in the House of Representatives in February 2016 and referred to the Committee on Energy and Commerce. It is currently in the committee stage. If it were to advance, it would then proceed to the House floor for consideration, and potentially to the Senate. The Federal Trade Commission (FTC) would be responsible for creating regulations to implement and enforce the Act if it became law.
Plain-English summary generated by Bill100 AI from the official record. Always verify against the source below.
Official summary
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.
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.
Timeline
12 Feb 2016
Referred to the Subcommittee on Commerce, Manufacturing, and Trade.
Common questions
- What does H.R. 4517 do?
- The APPS Act of 2016 would require developers of mobile applications to inform users about how their personal data will be collected, used, stored, and shared. Before collecting this data, developers would need to obtain the user's consent to these terms and conditions. Users would also be given a way to withdraw their consent and request that their data be deleted or that further collection and sharing cease. This bill affects individuals who use mobile applications and the developers of those applications. It aims to provide users with more control and transparency over their personal data. The bill also requires developers to take steps to protect collected data from unauthorized access. De-identified data, which cannot reasonably be used to identify an individual, would be excluded from these notice and consent requirements. This bill was introduced in the House of Representatives in February 2016 and referred to the Committee on Energy and Commerce. It is currently in the committee stage. If it were to advance, it would then proceed to the House floor for consideration, and potentially to the Senate. The Federal Trade Commission (FTC) would be responsible for creating regulations to implement and enforce the Act if it became law.
- Has H.R. 4517 become law?
- The source does not supply a confirmed lifecycle stage for H.R. 4517. Check the latest action and official source below.
- Who sponsored H.R. 4517?
- H.R. 4517 was sponsored by Rep. Johnson, Henry C. "Hank," Jr. [D-GA-4] (D-GA), with 5 cosponsors.
- What's the latest action on H.R. 4517?
- Referred to the Subcommittee on Commerce, Manufacturing, and Trade. (12 Feb 2016).
Related bills in Science, Technology, Communications
Accelerating Broadband Permits Act of 2026
Disaster Communications Coordination and Preparedness Act
Mystic Alerts Act
Bots Research Act
More bills from Rep. Johnson, Henry C. "Hank," Jr. [D-GA-4]
Expressing support for the recognition of September 7, 2026, as "Liturgical Dance Day" and the International Dance Commission, and for other purposes.
Expressing support for the designation of September 9 as "National African Immigrant and Refugee HIV/AIDS and Hepatitis Awareness (NAIRHHA) Day".
Supporting the designation of November 9 of each year as "Gold Star Father's Day".
Justice is BLIND Act of 2026
Bill100 mirrors the public U.S. legislative record from Congress.gov and GovTrack and adds plain-English AI summaries. It is an information tool, not legal, compliance or lobbying advice, and it is not affiliated with the U.S. Congress or any government agency. AI summaries can simplify or omit detail — every bill links to the official source; verify there before you rely on it.