VotedBy VotedBy ⌕
Election Day · Tue, Nov 3See how your members of Congress voted →

H.R. 1913 · 113th Congress

APPS Act of 2013

Key: what the circles and colors mean

Each circle is a bill. The ring fills as it moves through Congress:

IntroducedPassed one chamberPassed both chambersBecame law (gold)Resolution agreed to (full, dark)Failed or vetoed (gray)

Under the number: the Yea · Nay count of its final (or latest) recorded vote. On a member's page, the small badge is how that member voted: Y Yea / Aye, N Nay / No, P Present, – Not voting.

Gold and violet are only for Yea and Nay; they never mean a party. A member's party is the letter on their photo.

Never voted on. It didn't reach a floor vote before the 113th Congress ended, so it expired. A bill has to be introduced again to be considered in a new Congress.

8 cosponsors · 5 D, 3 R

4 signed on when it was introduced; the rest joined later. Cosponsors who withdrew aren't shown.

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.

What it does: CRS summary · Introduced in House · May 9, 2013

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.

Written by the nonpartisan Congressional Research Service. All summary versions on Congress.gov

About this bill and sources

Official title: APPS Act of 2013

Also known as: Application Privacy, Protection, and Security Act of 2013

Latest action (May 10, 2013): Referred to the Subcommittee on Commerce, Manufacturing, and Trade.

Policy area: Science, Technology, Communications · Origin: House · Introduced: May 9, 2013

Official page on Congress.gov · Bill text (GovInfo) · Status record (XML)

No recorded floor vote found.