APPS Act of 2013
Latest action · May 10, 2013 Referred to the Subcommittee on Commerce, Manufacturing, and Trade.
Progress
Where this bill reached, and when. A stage with no date was not reached; one that failed a vote and later carried shows the date it carried.
- IntroducedMay 9, 2013
- Passed HouseNot reached
- Passed SenateNot reached
- To the PresidentNot reached
- Became lawNot reached
Summary
Application Privacy, Protection, and Security Act of 2013 or the APPS Act of 2013 - 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.
Excludes from such notice and consent requirements 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.
Requires developers to: (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.
Requires violations to be treated as unfair or deceptive acts or practices under the Federal Trade Commission Act.
Directs the Federal Trade Commission (FTC) to promulgate regulations to implement and enforce this Act.
Authorizes states to bring civil actions in federal court on behalf of affected state residents.
Declares that 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.
Permits a developer to satisfy the requirements of this Act by adopting and following a code of conduct for consumer data privacy that: (1) was developed in a multistakeholder process convened by the National Telecommunications and Information Administration (NTIA), as described in the document issued by the President on February 23, 2012, entitled Consumer Data Privacy in a Networked World: A Framework for Protecting Privacy and Promoting Innovation in the Global Digital Economy; and (2) is approved pursuant to FTC regulations.
Cosponsors 8
Members who signed on, in the order they did. Signatures ran from May 9, 2013 to Jul 31, 2014, with 4 there on the day it was introduced.
| Seat | Cosponsor | Signed on | |
|---|---|---|---|
| D-NY | Eliot L. Engel | Original | May 9, 2013 |
| D-MI | John Conyers, Jr. | Original | May 9, 2013 |
| D-TX | Sheila Jackson Lee | Original | May 9, 2013 |
| R-OH | Steve Chabot | Original | May 9, 2013 |
| R-TX | Joe Barton | May 22, 2013 | |
| D-TN | Steve Cohen | Jul 17, 2013 | |
| R-WI | Sean P. Duffy | Mar 13, 2014 | |
| D-IL | William L. Enyart | Jul 31, 2014 |
Actions 4
Everything that happened, newest first.
- May 10, 2013Referred to the Subcommittee on Commerce, Manufacturing, and Trade.
- May 9, 2013Introduced in House
- May 9, 2013Referred to the House Committee on Energy and Commerce.
- May 9, 2013Sponsor introductory remarks on measure. (CR H2558)
Subjects
Assigned by the Library of Congress. Policy area: Science, Technology, Communications.
Text 1
Each version as it was printed, newest first.
- May 9, 2013Introduced in House
Everything here is as published by Congress: the summary is the Congressional Research Service's, the action wording is the clerks', and the subjects are the Library of Congress's. How far it got is read from the actions themselves, taking the most recent one of each kind, so a bill that failed a vote and later passed is shown as having passed. Records come from this bill on Congress.gov and govinfo.gov.
