The Privacy Act of 1974, codified at 5 U.S.C. § 552a, is the statute that establishes the federal government's baseline legal responsibility for safeguarding personally identifiable information. It binds every executive-branch agency that maintains a system of records and imposes specific duties—publish a system-of-records notice, limit collection to relevant and necessary data, secure the records, and give individuals access and amendment rights—with a civil remedy and criminal penalties attached. Several later statutes layer sector-specific duties on top, but the Privacy Act is the founding obligation.
The condition that surprises people is the gate. The Act applies to records an agency retrieves by an individual identifier; a file that only works as a pile of unindexed paper may fall outside it. And it reaches executive agencies, not the courts or Congress, which follow separate rules.
Judges treat the Privacy Act as a management statute, not a general data-privacy charter. A violation without an actual adverse effect usually produces no recovery, and the civil remedy caps damages at $1,000 per person plus costs and fees. So the honest answer to "what law" is one statute named, plus a short stack of newer laws that add teeth for specific data types.
This article is general educational information, not legal advice. Consult a qualified attorney for how these statutes apply to a particular agency or record system.
Why the Privacy Act's System-of-Records Trigger Leaves Paper Files Uncovered
The trigger is technical and it decides most cases. Section 552(a)(5) defines a "system of records" as a group of records under agency control from which information is retrieved by an individual's name or some identifying number, symbol, or other identifier. An agency can escape the Act's duties by keeping records that are not retrieved by identifier—a real defense, not a technicality.
The Supreme Court has reinforced how narrowly that language cuts, most memorably in DOJ v. Reporters Committee for Freedom of the Press (1989), which treated a compilation of criminal-history data as a record about the compiler's collection rather than an individual's privacy interest. Lower courts have split on how broadly to read the retrieval rule, and agencies have leaned on the split.
Consider the edge case: a contracting officer's spreadsheet of vendor points of contact, sorted by company name with no individual lookup, sits outside the system-of-records definition. Add a filter by last name and the same spreadsheet becomes a system of records overnight—with notice, access, and security duties attached. The law cares about how you retrieve, not what you store.
The Privacy Act's Substantive Safeguards: Purpose, Accuracy, Security, and Access
Once a system of records exists, four duties attach. The agency must collect only information relevant and necessary to a purpose required by statute or executive order; it must publish a Federal Register notice describing the system; it must maintain records with accuracy, relevance, timeliness, and completeness reasonably necessary to assure fairness; and it must establish appropriate administrative, technical, and physical safeguards to ensure security and confidentiality.
The security clause is the safeguarding hook—but it is soft. The Act does not prescribe encryption, access controls, or breach notification; it says "appropriate" safeguards and leaves the standard to agency practice. That is why the Office of Management and Budget's Circular A-130, which governs federal information management, and the Federal Information Security Modernization Act of 2014 do much of the operational work the Privacy Act leaves open.
Two further duties round out the statute: the access right, which lets an individual request a copy of records about themselves, and the amendment right, which lets them seek correction of inaccurate information. Both come with exemptions—law enforcement, national security, and certain civil-service files are among the categories agencies may invoke under 5 U.S.C. § 552a(j) and (k). A requester who does not know an exemption is claimed on a system will waste weeks writing a request that cannot be granted.
Where the Privacy Act Sits on the Federal Statute Map
The Privacy Act is the floor, not the whole building. Congress has passed narrower statutes that impose stricter duties on specific categories of data, and those statutes usually control when they conflict. Knowing the map tells a compliance officer which deadline and which enforcement body apply.
| Statute | Data Covered | Key Obligation | Enforcement or Penalty |
|---|---|---|---|
| Privacy Act (5 U.S.C. § 552a) | Records in agency systems of records | Notice, access, amendment, "appropriate" safeguards | Civil suit; $1,000 statutory damages plus fees; criminal misdemeanor for willful disclosure |
| E-Government Act § 208 (2002) | Agency IT systems handling PII | Privacy impact assessment before collection | OMB oversight; no private right of action |
| Federal Information Security Modernization Act of 2014 | Federal information and systems | Agency security programs, incident reporting to DHS | Inspector General audits; OMB reporting |
| Health Insurance Portability and Accountability Act (1996) | Health data held by covered entities | Privacy and security rules | HHS Office for Civil Rights; civil money penalties |
| Gramm-Leach-Bliley Act (1999) | Consumer financial data | Privacy notices, safeguards rule | FTC and banking regulators |
| 5 U.S.C. § 552a note (2019) | PII breach by agency | Breach notification to affected individuals | Agency practice under OMB guidance |
Read the table as a stack of logos, not a menu. If a VA medical record is involved, HIPAA's privacy rule and the Privacy Act both apply, and the stricter provision governs on the specific point. If a breach exposes Social Security numbers held by an agency, the 2019 notification provision—titled the Federal Cybersecurity Enhancement Act amendments—triggers a notification duty that the original 1974 text never contained.
Computer Matching, the 1988 Amendments, and the Limits They Set
The Computer Matching and Privacy Protection Act of 1988 amended the Privacy Act to govern an activity that had grown common: comparing two automated systems of records to verify eligibility for federal benefits. The amendments require a written matching agreement, a cost-benefit analysis, and notice to individuals, plus an agency Data Integrity Board to review matches every two years.
Matching is where the safeguarding duty collides with the enforcement duty. A matching program that flags a beneficiary for overpayment can be accurate and still wrong—the 1988 amendments were written after reports of erroneous matches produced benefit terminations. The statute's answer is procedural: give the individual a chance to contest before adverse action, and keep the matching records under the same safeguards as the source systems.
An agency that runs a match without a written agreement faces a specific exposure: the Data Integrity Board's report to Congress, an uncomfortable document that becomes public. That reporting duty gives the statute more bite in matching than the general civil remedy does.
Privacy Impact Assessments and the Paper Trail the E-Government Act Requires
Section 208 of the E-Government Act of 2002 requires agencies to conduct a privacy impact assessment before developing or procuring information technology that collects, maintains, or disseminates PII, and before initiating a new collection of identifiable information. The assessment must describe what is collected, why, and how it is secured and shared.
The PIA is not in the Privacy Act, but it is the operational document that agencies use to demonstrate the Act's safeguards exist. An agency that cannot produce a PIA for a system handling PII has a documentation gap a Privacy Act plaintiff can exploit, even though the E-Government Act itself creates no private cause of action.
The time computation matters for planning. A PIA for a moderate system commonly takes weeks of drafting and review, and the assessment must be updated when the system changes materially—a new data feed, a new vendor, a new retention period. Treat PIA maintenance as a recurring cost, not a one-time filing.
Enforcement, Damages, and the Real Failure Cases
The Privacy Act's civil remedy is narrow and its criminal penalty narrow too. An individual who suffers an adverse effect from a willful or intentional violation may sue for actual damages, but the statute guarantees a floor of $1,000 plus reasonable attorney fees and costs. A plaintiff must show an adverse effect—courts have dismissed cases where a disclosure occurred but no tangible harm followed.
Two failure scenarios recur. The first is the routine-use disclosure: an agency shares records for a purpose other than the one stated when it collected them, and the recipient uses them in a way the individual never expected. The second is the records-quality failure, where an inaccurate entry survives in a system of records and drives an eligibility decision.
The criminal penalty applies to a federal employee who willfully discloses records without authority, a misdemeanor under 5 U.S.C. § 552a(i)(1). It has been used sparingly, and that rarity is the point—the statute's real discipline is procedural and reputational, not punitive.
How FOIA Exemptions and the Privacy Act Interact
Freedom of Information Act requests and Privacy Act requests are different instruments with different logic. FOIA gives any person access to agency records subject to nine exemptions, and Exemption 6 protects personal privacy interests in personnel, medical, and similar files; the Privacy Act gives the subject of a record access and amendment rights. The Supreme Court's Reporters Committee decision read Exemption 7(C) broadly, and lower courts have applied Exemption 6 with a balancing test.
The practical confusion is common. A requester seeking their own file should use the Privacy Act, which is faster in many agencies, while a third party seeking someone else's file is routed to FOIA and usually defeated by Exemption 6 unless a public interest outweighs the privacy interest. Filing the wrong request restarts the clock.
The two statutes also differ on correction. FOIA does not provide an amendment right; the Privacy Act does. A veteran seeking to correct a service record should file under the Privacy Act and the applicable military-records correction board, not under FOIA.
State Law Overlays and the Contractor Question
State privacy statutes fill gaps the federal statute leaves. California's Information Practices Act of 1977 binds state agencies, and state breach-notification laws create deadlines the Privacy Act never set. A federal contractor handling agency data is not automatically covered by the Privacy Act unless the contract makes it so through the Federal Acquisition Regulation privacy clauses.
That contractor point is the one most frequently missed. The FAR privacy clauses, including the provisions at FAR 52.224-1 and 52.224-2, impose Privacy Act obligations on contractors operating systems of records for an agency. A contractor outside those clauses may face no direct Privacy Act duty, even while handling the same data—a gap that the agency's own PIA and security authorization are supposed to close.
Annual Reporting, Notification, and Retention Duties
Two recurring obligations round out the framework. Agencies must publish an annual notice of their systems of records in the Federal Register, and the Privacy Act requires agencies to keep an accounting of disclosures made from a system of records, which is available to the individual on request. That accounting is the audit trail that makes safeguarding verifiable.
The 2019 breach-notification provision, added to 5 U.S.C. § 552a as a note, requires an agency to notify affected individuals after a breach of PII—though the exact timeline and content follow OMB guidance rather than the statute's text. This is a place where the law's promise outruns its specificity, and where agencies' own policies determine how fast notice arrives.
Retention ties the safeguards together. A record kept longer than necessary increases exposure; a record destroyed before a pending request defeats an access right. The National Archives and Records Administration's General Records Schedules set the periods, and an agency that follows them has a defensible answer to the "appropriate safeguards" question.
FAQ
Does the Privacy Act cover Social Security numbers held by federal agencies?
Yes—when those numbers sit in a system of records retrieved by identifier. The Act does not create a separate special category for SSNs; it treats the identifier as one way to retrieve a record, so an SSN in a payroll or benefits system is squarely covered. A database of SSNs not retrieved by any individual identifier sits in the gap. Confirm the specific system's notice before assuming coverage.
Is the Privacy Act the same as the GDPR?
No, and the difference matters. The GDPR gives data subjects rights against a broad range of controllers and imposes fines tied to global turnover; the Privacy Act applies to federal executive agencies and caps recovery at $1,000 per person. The GDPR's notice and consent model has no direct counterpart in the federal statute. A company subject to the GDPR cannot assume its federal-agency customer's duties mirror its own.
What happens if an agency discloses my records without authorization?
The agency may face a civil suit, and the individual may recover actual damages with a $1,000 statutory floor. A willful disclosure by a federal employee can also be prosecuted as a misdemeanor. The realistic path for most people is an administrative privacy complaint to the agency and, if unresolved, a suit in federal district court within the statute of limitations.
How long does an agency have to respond to a Privacy Act access request?
The statute itself sets the schedule, and agencies publish it in their system-of-records notices. The Act allows an agency to extend the period for good cause and to charge reasonable fees for copying. An agency that misses the deadline has not automatically violated the Act—the question is whether it exhausted its permitted extensions. Track the date of acknowledgment and the stated extension.
Do contractors handling federal PII have to follow the Privacy Act?
Only if the contract makes them. The FAR privacy clauses at 52.224-1 and 52.224-2 flow the obligations down, and contractors outside those clauses may face no direct duty. That is a real gap, and it is why agency security authorizations and PIAs must cover contractor systems. Ask for the clause language before assuming coverage.
What is the difference between the Privacy Act and the Freedom of Information Act?
The Privacy Act gives the subject of a record access and amendment rights; FOIA gives any person access to agency records subject to exemptions, and Exemption 6 protects personal privacy. Filing under the wrong statute restarts the clock. A third party seeking someone else's records should expect FOIA's exemption to defeat the request in most cases.
Can I amend a record that contains inaccurate information about me?
Yes, through the Privacy Act's amendment procedure, but the agency decides first and exemptions may apply. The process is a written request, an agency review, and if denied, an appeal; a further refusal can be challenged in court. For military records, the correction board process runs in parallel and often produces faster results. Consult a qualified attorney before litigating.
This article provides general educational information about federal information law and is not legal advice or a legal opinion on any specific agency, system, or dispute. Do not rely on it as a substitute for advice from a licensed attorney in your jurisdiction. Laws, agency guidance, and contract clauses change, and their application depends on facts the article cannot assess. If you face a time-sensitive legal issue, consult a qualified professional promptly; for immediate danger, contact local emergency services.