The primary Air Force instruction covering privacy and the civil liberties programs is Department of the Air Force Instruction (DAFI) 33-113, Privacy and Civil Liberties Programs. It assigns program responsibilities across the Department of the Air Force (DAF), while DoD Directive 5400.11 and DoD Instruction 5400.16 supply the department-level policy and investigative framework those programs execute. The Air Force's earlier standalone civil liberties instruction, AFI 35-107, was superseded as the two programs consolidated under the privacy office.

That single-sentence answer matters more than it looks, because the civil liberties program and the privacy program are not the same thing. They share an office, a governance rhythm, and a compliance vocabulary. They do not share statutes, complaint channels, or remedies.

What the instruction actually governs: the DAFI 33-113 mechanism

DAFI 33-113 is an implementing instruction, not a statute. It converts higher-level law and DoD policy into tasks a wing, base, or staff agency can actually perform. The Privacy Act of 1974 (5 U.S.C. § 552a) supplies the privacy foundation. DoD Directive 5400.11 establishes the DoD Privacy Program and names the components that must run one. DoD Instruction 5400.16 defines how records are collected, maintained, and accessioned into the Defense Privacy, Civil Liberties, and Transparency Division framework.

The instruction then does four mechanical jobs.

First, it designates roles. A DAF privacy and civil liberties office sits at the secretariat level. Each Major Command and installation names a Privacy Act officer and a civil liberties point of contact who carry the program locally.

Second, it sets a review cycle. System of Records Notices (SORNs) — the public notice that says what data a system holds, why, and to whom it may be disclosed — must be reviewed and validated on a recurring schedule rather than standing unchanged for years.

Third, it requires Privacy Impact Assessments (PIAs) before a system handling personally identifiable information goes operational. A PIA is not a security authorization. It is an analysis of what privacy risk the collection creates and how that risk is mitigated.

Fourth, it establishes the civil liberties review function: assessing whether a proposed action, technology, or information collection burdens rights such as speech, assembly, association, or due process, and documenting that assessment.

The mechanism is deliberately bureaucratic. Privacy compliance is mostly a records-management discipline. If a SORN is stale or a PIA is missing, the collection is unauthorized regardless of whether anyone was harmed. That is the professional caveat most thin explainers miss: in this system, documentation is not paperwork about compliance — the documentation is the compliance.

Scale and quantified context

The Defense Privacy, Civil Liberties, and Transparency Division maintains the authoritative public register of DoD SORNs and PIAs. The Air Force's portion of that register is large because the service runs thousands of personnel, medical, personnel-security, and mission-support information systems across active, guard, reserve, and civilian components.

Three numbers frame the load.

One: a single SORN can cover dozens of subordinate systems, so counting notices undercounts actual collections substantially.

Two: PIAs are required per system or per material change, not per base, so one enterprise platform can generate dozens of assessments across the department.

Three: the review cadence is measured in years, not months — a two-year or longer validation interval is typical for a SORN, which means a stale notice can persist through multiple personnel rotations.

The practical consequence: most privacy failures at the installation level are not malicious. They are the residue of a review that fell behind when the responsible officer changed duty stations. A 1-to-3 person privacy office at a large installation can be responsible for oversight of scores of systems.

Edge cases where the instruction bends

The clean answer — DAFI 33-113 — starts to fragment at the boundaries. Four edge cases recur.

Records held by a contractor on behalf of the Air Force remain subject to the Privacy Act if the government controls them. The instruction's coverage question turns on control, not on who physically holds the data. A contractor-operated system without a valid PIA is a compliance gap even if no uniformed member touches it.

Law enforcement records occupy a partial exemption zone. The Privacy Act permits certain exemptions for investigatory material compiled for law enforcement purposes, and DoD implementing policy channels those through specific exemption rules. That does not remove civil liberties review; it changes what the public can see and what the subject can request.

Civil liberties review and privacy review can point in opposite directions. A security measure that narrows data collection may reduce privacy exposure while still raising an association or expression concern. The instruction expects both analyses, not one substituted for the other.

Guard and reserve components add a jurisdictional wrinkle. State-level obligations can apply alongside federal ones for certain records, and the DAFI does not displace them.

One counterintuitive detail deserves emphasis: a system can be fully compliant with the Privacy Act and still fail civil liberties review. Privacy law governs information handling. Civil liberties review governs the effect of a government action on protected rights. Passing one is not passing the other.

Misconceptions that send people to the wrong instruction

The most common error is citing AFI 35-107 for civil liberties. That instruction was the Air Force's civil liberties document, and its functions were folded into the consolidated privacy and civil liberties program under the 33-series. Personnel working from old continuity binders routinely cite it.

A second error confuses security with privacy. The Risk Management Framework under DoD Instruction 8510.01 authorizes a system to operate. It does not satisfy Privacy Act notice or PIA requirements, and an authority to operate is not a privacy clearance.

A third error treats the Privacy Act as a general confidentiality statute. It governs federal records retrievable by a personal identifier. It does not cover every piece of information about a person, and it does not create a blanket bar on disclosure.

A fourth error assumes the Privacy Act officer is the same person as the Freedom of Information Act (FOIA) requester. FOIA and Privacy Act requests run on different statutory tracks with different exemptions and deadlines, even when one office processes both.

Comparison of the governing instruments

Instrument Level What it governs Who executes Typical trigger
DAFI 33-113 DAF instruction Privacy and civil liberties program roles, PIA and SORN review, civil liberties assessment DAF privacy office; MAJCOM and installation points of contact New system, material change, program review
DoD Directive 5400.11 DoD directive DoD Privacy Program structure and component responsibilities Component heads; Defense Privacy office Department-level policy change
DoD Instruction 5400.16 DoD instruction Privacy program procedures and records accessioning Component privacy offices System onboarding, records disposition
Privacy Act (5 U.S.C. § 552a) Federal statute Records retrievable by personal identifier; access, amendment, disclosure limits Every federal agency Any covered record system
DoD Instruction 8510.01 DoD instruction Security authorization (RMF) Authorizing officials System authorization to operate
AFI 35-107 (superseded) Legacy AF instruction Former civil liberties program Historical reference only Do not cite as current authority

Timeline of a system through the privacy pipeline

Stage What happens Typical duration or threshold
Concept and requirement Determine whether personally identifiable information is collected At requirement definition, before acquisition
PIA drafting Analyze collection purpose, retention, sharing, and risk Before operational testing
SORN check Confirm an existing notice covers the collection or draft a new one Before first collection; 60-day public comment for new SORNs
Civil liberties review Assess effect on protected rights; document mitigation Before deployment decision
Authorization Security authorization to operate under RMF Independent of privacy clearance
Recurring validation Review SORN and PIA for accuracy Multi-year cycle, often 2 years or longer
Decommission Retire records per disposition schedule; close the notice At system retirement

New SORNs published in the Federal Register generally carry a 60-day comment period before they take effect, though routine notices can move faster. The timeline is not a guarantee of duration; it is a sequence that a program must not skip.

Practical actions: what to do with the instruction

Before buying or building anything that touches personnel data, request the current DAFI 33-113 through official publishing channels and confirm the version in force — do not rely on a saved PDF from a prior assignment. Check whether a SORN already covers the collection. A new notice takes a public comment cycle, so starting late is a schedule risk, not just a compliance risk. Complete the PIA before operational testing, not before fielding. The earlier the analysis, the cheaper the redesign. Route the civil liberties assessment separately from the privacy review. Different question, different reviewer, different documentation. Flag these red conditions to your privacy office immediately: A system holding personal identifiers with no PIA on file A SORN whose stated routine uses no longer match actual sharing Contractor-held records under government control with no coverage analysis A security authorization being treated as a privacy approval Escalate through the installation privacy officer first, then the MAJCOM point of contact; keep a written record of each query and response.

Limitations and what the instruction cannot do

DAFI 33-113 is a program instruction. It tells the Department of the Air Force how to run privacy and civil liberties compliance. It does not create a private right of action, does not override statutory exemptions, and does not settle every interagency question about records shared with other components.

The instruction is also versioned. Numbering, titles, and office alignments shift across publishing cycles, and the consolidated 33-series arrangement is itself the product of reorganization. Anyone citing it as authority should verify the current edition rather than trust a secondary summary — including this one.

Finally, a program instruction cannot substitute for individualized advice. Whether a specific collection is lawful, whether a particular record is exempt, and how a specific request should be answered depend on facts the instruction does not contain.

This article is general educational information, not a legal opinion or a compliance determination. It does not promise any outcome, and it is not a substitute for review by a qualified attorney or your organization's privacy office. For a specific records, FOIA, or civil liberties question, consult a licensed legal professional or the appropriate Air Force privacy and civil liberties point of contact.