EO 13768’s privacy section reached agency policies, not Privacy Act rights; mixed systems were the hard part
Section 14 of the January 25, 2017 order told agencies to exclude people who were neither citizens nor permanent residents from Privacy Act protections in their privacy policies. Statutory rights, including Judicial Redress Act remedies published that week, stayed put. Mixed systems were harder.
Looking Back revisits past weeks one at a time, up to the most recent, and asks what it meant for the banks, health systems and public agencies we serve. The series was written in 2026, with the benefit of hindsight, and each article says which week it looks back on.
Two-minute summaryThe dek and the first sentence of each section, quoted from the article
Section 14 of the January 25, 2017 order told agencies to exclude people who were neither citizens nor permanent residents from Privacy Act protections in their privacy policies. Statutory rights, including Judicial Redress Act remedies published that week, stayed put. Mixed systems were harder.
- The week One short section dealt with personal data.
- The Privacy Act itself: a statute that never covered non-citizens other than permanent residents The Privacy Act protects “individuals,” and it defines the term as a citizen or a lawful permanent resident. [3] That definition does the work.
- The Judicial Redress Act: statutory remedies for some, from February 2017 The list is notable for what it omits.
- Agency policies: the only layer section 14 could reach DHS had gone beyond the statute by policy.
- The data itself: mixed systems and a status that changes The 2017 memo was candid about data.
- How the order landed on different agencies and partners For the SEC, the CFTC and the designated Treasury components, the order and the Judicial Redress Act designations arrived together. [1] [2] Their records about EU citizens transferred for criminal enforcement became covered records from February 1, 2017. [2] [4] Section 14 did not change that.
- Objections, in order For the statutory layer, there were no Privacy Act rights to remove from people outside the Act’s definition. [3] For the Judicial Redress Act layer, the order applied only to the extent consistent with law. [1] [4] What it removed was policy-based treatment, and at DHS that included administrative access and amendment under the 2007 policy. [5] That loss was real, but it came from the policy layer.
- What privacy and data leaders could check The checks below follow the four layers.
- With hindsight Section 14 was revoked with the rest of the order.
The week
On January 25, 2017, the President signed Executive Order 13768, Enhancing Public Safety in the Interior of the United States. [1] It was published in the Federal Register on January 30, 2017. [1] Most of the order dealt with immigration enforcement, including enforcement priorities, sanctuary jurisdictions and the reinstatement of the Secure Communities program. [1]
One short section dealt with personal data. Section 14, titled Privacy Act, was addressed to agencies. [1] It directed them, to the extent consistent with applicable law, to ensure that their privacy policies exclude persons who are not citizens or lawful permanent residents. [1] The exclusion was from the protections of the Privacy Act regarding personally identifiable information. [1]
The order’s general provisions limited its reach. It was to be implemented consistent with applicable law and subject to appropriations. [1] It said nothing in it impaired authority granted by law to an agency or its head. [1] Section 15 required the Secretary of Homeland Security and the Attorney General to report on progress within 90 and 180 days. [1]
The statute section 14 referred to had a fixed scope. The Privacy Act of 1974 defines “individual” as a citizen of the United States or an alien lawfully admitted for permanent residence. [3] Its access, amendment and civil remedy provisions run to that individual. [3] So, by statute, people outside those two groups had no Privacy Act rights for section 14 to remove.
A second statute had extended some Privacy Act remedies to some foreign citizens. The Judicial Redress Act of 2015, approved February 24, 2016, let a covered person bring certain civil actions under the Privacy Act regarding covered records. [4] A covered person was a citizen of a country the Attorney General designated. [4] A covered record was one transferred from that country to a designated federal agency or component for criminal law enforcement purposes. [4]
In the same week as the order, those designations were published. On January 23, 2017, the Federal Register published a notice, dated January 17, of the Attorney General’s designations under the Judicial Redress Act. [2] It designated 26 countries and one regional economic integration organization as covered countries. [2] It designated four federal agencies and nine components of other agencies as designated federal agencies or components. [2]
The covered countries were the European Union and 26 of its member states. [2] The four agencies were the Departments of Justice and Homeland Security, the Securities and Exchange Commission and the Commodity Futures Trading Commission, each with all components. [2] The nine components were in the State and Treasury Departments, including FinCEN, the Office of Foreign Assets Control and IRS Criminal Investigation. [2]
The designations were effective on February 1, 2017. [2] That was the date of entry into force of the agreement between the United States and the European Union on protecting personal information exchanged for criminal law enforcement. [2] The notice said the Act was the implementing legislation for Article 19 of that agreement, which required each side to provide judicial redress to the other’s citizens. [2]
So within a few days, two federal documents moved in opposite directions on the same subject. One extended statutory remedies to certain foreign citizens. [2] [4] The other told agencies to withdraw policy-based protections from non-citizens who were not permanent residents. [1] The question for agency privacy offices was how the two fit.
Section 14 is easy to read as stripping privacy protections from immigrants. Its text was narrower. It told agencies to change their privacy policies, and only to the extent consistent with applicable law. [1] What a policy can take away depends on what a policy had given.
Our argument is that section 14 could reach only the protections agencies had chosen to extend. Statutory rights stayed where Congress put them. [3] [4] The practical problem lay elsewhere, in systems that hold records on citizens and non-citizens together and cannot always tell them apart. [5] For a chief privacy officer or chief data officer, that was a data governance question more than a legal one.
We take the protections around a non-citizen’s federal record in four layers:
- The Privacy Act itself, which never covered non-citizens other than permanent residents.
- The Judicial Redress Act, which covered some, by statute, from February 2017.
- Agency policies that extended Privacy Act treatment administratively, the only layer section 14 could reach.
- The data itself: systems that mix populations and record a status that can change.
Each layer has a different source, and together they cover what governed such a record in 2017. After them we look at how the order landed on different agencies and partners, take the objections in order, and end with checks a privacy or data leader could run.
The Privacy Act itself: a statute that never covered non-citizens other than permanent residents
Who the Act protects
The Privacy Act protects “individuals,” and it defines the term as a citizen or a lawful permanent resident. [3] That definition does the work. A visitor, a student on a visa, an asylum seeker or a person without status is not an individual under the Act. [3]
The Act’s main protections follow from that. Its conditions of disclosure bar an agency from disclosing a record in a system of records except with the written consent of the individual or under a listed exception. [3] Its civil remedies let an individual sue when an agency refuses to amend a record or to grant access, among other cases. [3]
The Act also sets duties on the agency that run to individuals. It must keep an accounting of the date, nature and purpose of disclosures, with two exceptions, and the name and address of the recipient. [3] It must keep that accounting for at least five years or the life of the record, whichever is longer. [3]
It must maintain only information about an individual that is relevant and necessary to a purpose required by statute or executive order. [3] It must tell people asked for information the authority, purpose and routine uses, and the effect of not answering. [3] It must keep records used in determinations accurate, relevant, timely and complete enough to assure fairness. [3]
Each of those duties speaks of “an individual.” [3] So each is tied to the Act’s definition. A record about a person outside it does not carry those statutory duties, even when it sits in the same database as a citizen’s record. [3]
What section 14 could not change
An executive order cannot rewrite a statute’s definition. Section 14 did not try. It spoke to agency privacy policies and was limited by applicable law. [1] In our reading, it left the Act’s coverage of citizens and permanent residents exactly where it was. [1] [3]
That point matters for mixed records. A record about a citizen is protected by the Act whatever an agency’s policy says. [3] If an agency cannot tell whether a record is about a citizen, the statute may still apply. A policy that tells staff to treat non-citizens differently does not tell them which records those are.
What the statute already required for everyone
Some federal duties never depended on the Privacy Act’s definition. DHS later noted that FISMA protects all sensitive information, including PII, regardless of a person’s citizenship. [5] The E-Government Act’s privacy impact assessment requirement may apply to people other than citizens and permanent residents, according to DHS. [5]
The Freedom of Information Act was another channel. DHS said people not covered by the Privacy Act or the Judicial Redress Act may still obtain access to records under FOIA, subject to its exemptions. [5] The memo described FOIA as a route to access, not to amendment. [5] That gap is the practical difference between the statutory layers.
System notices describe the whole system
One statutory duty works at the level of the system rather than the person. An agency must publish in the Federal Register a notice describing each system of records, including the categories of individuals covered, the routine uses and its storage, retention and access practices. [3] The notice also describes how individuals can learn whether the system holds records about them and how to contest them. [3]
A notice for a mixed system describes one system with mixed contents. In our reading, a change in policy toward some of the people in it does not change the notice’s description of the system. It changes what the agency will do when one of those people asks for access or correction. [3] [5]
The Judicial Redress Act: statutory remedies for some, from February 2017
What the Act gives
The Judicial Redress Act gives covered persons limited Privacy Act remedies, not the whole Act. [4] They can sue over intentional or willful disclosures that violate the Act’s disclosure rule. [4] They can also sue a designated agency or component over refusals to amend or to grant access, as an individual could. [4]
The Act says those remedies are exclusive. [4] It gives covered persons the same rights and limitations, including exemptions and exceptions, as individuals have when pursuing those remedies. [4]
The list is notable for what it omits. The Act incorporates the Privacy Act’s remedies for refusals to amend and refusals of access, and for willful disclosures. [4] It does not incorporate the Privacy Act’s other civil remedies, such as those for failing to maintain accurate records used in a determination. [3] [4] A covered person can ask a designated agency to correct a record and sue if refused. The person cannot sue under the Act over harm from an inaccurate record in the way a citizen could. [3] [4]
The access and amendment remedies also run only against designated agencies and components. [4] The willful disclosure remedy is framed against an agency more generally, but only for covered records. [4] In our reading, a privacy office in a designated agency has to know which of its records arrived from a covered country for criminal enforcement, because those are the records where the remedies attach. [2] [4]
The agreement behind it
The designations rested on an international agreement. The Attorney General’s notice said that on December 2, 2016, the European Union took the final steps under EU law to approve an executive agreement with the United States. [2] The agreement covered privacy protections for personal information transferred between them for preventing, detecting, investigating or prosecuting criminal offenses. [2]
The notice said the agreement is known in the United States as the Data Protection and Privacy Agreement. [2] Its Article 19 obliged each side to provide judicial redress rights in its domestic law to the other’s citizens. [2] The Judicial Redress Act was the U.S. implementing legislation. [2] [4]
Three member states had special terms. The agreement excluded Denmark, Ireland and the United Kingdom unless each decided it should apply. [2] Ireland had agreed, and was designated. [2] The Justice Department said it intended to designate Denmark and the United Kingdom promptly on notice that they had decided the agreement applied to them. [2]
The conditions for designation
The Act set conditions for each designation. A country needed an agreement with the United States providing appropriate privacy protections for criminal law enforcement information, or an Attorney General determination that it shared such information effectively with appropriate protections. [4] It also had to permit transfers of personal data for commercial purposes to the United States, by agreement or otherwise. [4]
The Attorney General also had to certify that the country’s commercial data transfer policies did not materially impede U.S. national security interests. [4] The Secretaries of State, the Treasury and Homeland Security had to concur. [4] The notice recorded each determination and the concurrences. [2]
The Act made those determinations unreviewable, and the notice said so. [2] That puts the second layer in the hands of the Attorney General and the other Secretaries, not the courts. It also means a covered person’s remedies depend on a designation that can be revoked under the Act’s conditions. [4]
Which records
The Act applies only to covered records. [4] A record qualifies once it is transferred by a public authority or private entity in a covered country to a designated federal agency or component, for preventing, investigating, detecting or prosecuting criminal offenses. [4] A record that an agency collected directly from a traveler at a border crossing is not described by that test, in our reading. A record received from a European police authority could be. [4]
The Attorney General’s notice added a time limit. It said no cause of action would be afforded retroactively for any record transferred before February 1, 2017. [2] It also said designation of the European Union covered records transferred by EU institutional bodies, such as Europol and Eurojust, and did not itself designate member states. [2]
Why section 14 could not reach it
The Judicial Redress Act is a statute. [4] Section 14 applied only to the extent consistent with applicable law. [1] In our reading, a policy change could not remove remedies Congress granted, and the order did not claim to. DHS’s later memo kept those protections, stating that records covered by the Privacy Act or the Judicial Redress Act could be used and shared only with consent or under one of the Act’s exceptions. [5]
The Act also has its own exit. The Attorney General may revoke a country’s designation if, among other things, the country stops meeting the conditions or impedes transfers of information to the United States. [4] So the second layer can change, but through the Attorney General’s designations and not through a privacy policy. [4]
Which agencies it touched
The designated list reached beyond immigration. It included the Securities and Exchange Commission and the Commodity Futures Trading Commission, with all their components. [2] It included Treasury components such as FinCEN, the Office of Foreign Assets Control and the Office of the Inspector General. [2] Where those bodies received records from a covered country for criminal enforcement, the Act’s remedies attached to them from February 1, 2017. [2] [4]
Agency policies: the only layer section 14 could reach
What DHS had extended
DHS had gone beyond the statute by policy. In 2007, it announced that it would treat all persons’ PII the same under the Privacy Act, regardless of citizenship, in what it called its Mixed Systems policy. [5] A mixed system was a system of records holding identifiable information about both U.S. persons and non-U.S. persons. [5]
Under that policy, DHS extended Privacy Act protections to PII in a mixed system, retrieved by a personal identifier, whatever the person’s status. [5] DHS said it had done so because of the difficulty of determining a person’s current immigration status, which can change through naturalization or adjustment. [5]
What DHS did in response
On April 25, 2017, DHS’s Acting Chief Privacy Officer issued Privacy Policy Guidance Memorandum 2017-01. [5] It said section 14 was inconsistent with the 2007 policy, so DHS had to change it. [5] DHS would now treat all persons, regardless of immigration status, consistent with the Fair Information Practice Principles and applicable law. [5]
The memo listed eight principles: transparency, individual participation, purpose specification, data minimization, use limitation, data quality and integrity, security, and accountability and auditing. [5] It required privacy impact assessments to address how DHS would mitigate risks to different populations. [5] It said all information sharing relating to immigrants and non-immigrants had to be described and justified in the relevant assessment. [5]
The memo also described how transparency would work without the Privacy Act. DHS would use privacy impact assessments, system notices, Privacy Act statements, compliance reviews, general notices, public meetings and FOIA. [5] It said that even when not required, DHS tries to include privacy notices on all information collections, and was developing a template for components. [5]
What changed for the person in the record
The main loss was in individual participation. Under the 2007 policy, DHS had extended Privacy Act treatment to all persons in mixed systems. [5] Under the 2017 memo, people not covered by the Privacy Act or the Judicial Redress Act could still seek access under FOIA, unless disclosure was prohibited or harmful to an exempt interest. [5] DHS pointed to other processes, such as its traveler redress program, for correcting some records. [5]
The memo also addressed disclosure to third parties. Staff had to analyze any third-party request for PII under applicable law, balancing the public’s interest against the person’s privacy. [5] It permitted discretionary disclosure of confirmed non-citizen, non-permanent resident PII when no other restriction applied, subject to that balancing review. [5] Components had to develop processes for those disclosures and get the Privacy Office’s approval first. [5]
Use and sharing had their own rules. For records covered by the Privacy Act or the Judicial Redress Act, DHS could use and share only with written consent or under one of the Act’s twelve exceptions, the memo said. [5] Sharing outside DHS had to be compatible with the purpose of collection, and the memo called consent the preferable practice where practical. [5]
The memo separated official sharing from public disclosure. Official sharing covered requests from congressional committee chairs acting for their committees, federal courts, and law enforcement and other agencies with a need for DHS records in their official duties. [5] Third-party disclosures, to members of the public, the media and members of Congress not acting as chairs, went through the balancing analysis instead. [5]
What did not change
Much of the policy framework stayed. DHS said nothing in the order changed its responsibility to use the Fair Information Practice Principles as the foundation of its privacy policy. [5] Purpose specification, data minimization and security applied to everyone. [5] The memo said DHS protects all PII from inappropriate or unlawful access, use or disclosure. [5]
Accountability measures applied regardless of status as well. The memo listed training for all employees and contractors with access to PII, role-based training on systems that manage PII, handbooks and incident guidance. [5] It said DHS takes appropriate action, which can include investigations, when its privacy policies are violated. [5]
It also required component privacy officers to build review mechanisms like the Department’s privacy compliance reviews. [5] Within one year of a request from the Chief Privacy Officer, a component had to review the programs identified and report findings. [5] The memo said these reviews were designed to be public-facing where content allowed. [5]
In our reading, the 2017 memo kept the framework and removed a specific administrative promise: Privacy Act treatment, including amendment, for non-covered persons in mixed systems. [5] That promise was the layer section 14 could reach. [1]
The data itself: mixed systems and a status that changes
The problem DHS named
The 2017 memo was candid about data. It said there is a risk of violating the Privacy Act when sharing records if the subject’s immigration status is uncertain or not in the record. [5] It also said that once a person becomes a citizen or permanent resident, all DHS records about that person are subject to the Act, including records made earlier. [5]
That rule turns a policy distinction into a data quality problem. A record created when its subject was a visitor can become a Privacy Act record later, when the person naturalizes. [5] A bulk sharing agreement made under the earlier status can then cover records that the Act now protects. [5] DHS told staff to account for the fact that a person’s status may change during the life of an agreement. [5]
One record, three treatments
A hypothetical record shows the problem. A person enters the United States on a student visa, and an agency creates a record retrievable by name. Under the 2007 DHS policy, that record got Privacy Act treatment as part of a mixed system. [5] Under the 2017 memo, it did not, while the person remained outside the Act’s definition. [3] [5]
Later the person becomes a lawful permanent resident. From then on, the Privacy Act covers that record, including the parts created earlier, as DHS’s own memo explained. [3] [5] If the agency shared the record in bulk under the earlier status, its sharing agreement now covers a protected record. [5]
Nothing in the record itself may show the change. The status update may sit in another system, or arrive late. The agency’s treatment of the record depends on a fact it may not hold, which is the reason DHS gave in 2007 for treating everyone alike. [5]
No new data to sort people
The memo drew a line on collection. It said section 14 did not require collecting additional data to determine citizenship status when not otherwise required. [5] It warned that collecting more data or building new interfaces to capture status creates its own risks. [5] It said such changes would divert limited resources and could create cybersecurity risks. [5]
That is a data minimization argument applied to a policy that seemed to demand more data. In our reading, it was a consequential paragraph in DHS’s response. It kept the Department from building status flags into systems that had none, which would have made every downstream system depend on a field that changes over time. [5]
What it means for systems design
A system that protects records by citizenship needs three things: a status field, a source for it and a rule for when it changes. The Privacy Act ties protection to status. [3] The memo shows that status can be missing or stale. [5] So a system designer has to choose a default for records whose status is unknown.
DHS’s 2007 answer was to treat everyone as covered. [5] The 2017 memo removed that default as policy but did not require new data to apply a different one. [5] The memo set no default for an unknown record. It told staff, when in doubt, to seek advice from counsel and privacy officials. [5]
Minimization and retention
The memo’s data minimization principle applied to everyone. DHS said it collects only information relevant and necessary to the purposes in its notices, and keeps it only as long as needed for those purposes. [5] It pointed to the Federal Records Act’s retention schedules as a further limit. [5]
The memo named two identifiers for special care: Social Security numbers and Alien Registration Numbers. [5] It said DHS does not collect, use, maintain or disseminate Social Security numbers unless required by statute or regulation or for a specific authorized purpose. [5] Those limits did not depend on the person’s status. [5]
Accuracy cuts both ways
The Privacy Act requires accuracy for records used in determinations about individuals. [3] The 2017 memo kept a data quality principle for everyone, saying DHS should rely on information only when it is reasonably considered accurate, relevant, timely and complete. [5] It qualified that the Department should strive for accurate records to the extent this would not interfere with enforcement investigations or intelligence activities. [5]
The memo also gave an operational reason for accuracy. It said letting people update and amend records can reduce errors, improve outcomes and prevent waste at partner agencies that rely on the same information. [5] In our reading, that sentence makes the case for amendment rights on data quality grounds alone. A record no one can correct stays wrong in every system that copies it.
Security does not depend on status
The memo was explicit that security obligations did not change. It said DHS complies with FISMA, which protects all sensitive information, including PII, regardless of citizenship. [5] It added that further security requirements may come from information sharing agreements, interconnection security agreements and service contracts. [5]
For a CISO, that means section 14 did not create a lower security tier for some records. Encryption, access control and logging apply to the whole system. [5] Any attempt to segregate records by status for privacy purposes would still have to meet the same security baseline, and would add a classification step that could itself go wrong.
For other agencies with mixed systems, the same choice applied. Section 14 directed all agencies, DHS among them. [1] Each had to decide whether its policies extended Privacy Act protections beyond the statute, and if so how its systems would separate records it could not reliably sort. [1] [3]
How the order landed on different agencies and partners
DHS components
DHS was the agency with the clearest policy to change, because its 2007 policy was written down. [5] The 2017 memo required all DHS personnel to follow it. [5] Components had to apply the principles through privacy impact assessments, threshold analyses and compliance reviews. [5] Component privacy officers had to set up review mechanisms and report to the Chief Privacy Officer when asked. [5]
Designated agencies outside immigration
For the SEC, the CFTC and the designated Treasury components, the order and the Judicial Redress Act designations arrived together. [1] [2] Their records about EU citizens transferred for criminal enforcement became covered records from February 1, 2017. [2] [4] Section 14 did not change that. In our reading, their privacy offices needed to tell staff which records the Act reached. [4] For those agencies, the week added a duty rather than removing one. Requests from covered persons about covered records would need to be routed to the Act’s access and amendment process, whatever section 14 said about agency policy. [1] [4]
State and local partners
State and local agencies could be affected when they received federal records under sharing agreements. The 2017 memo told DHS to make sharing decisions with care absent a statutory requirement, and said other authorities can limit sharing depending on the records and the recipient. [5]
Contractors running federal systems
For contractors that operate systems of records for agencies, the order changed instructions, not systems. DHS said section 14 did not require building new interfaces to capture status. [5] A contractor asked to add a citizenship flag would need a lawful basis for collecting it and an agency decision on what the flag would control. [5]
Agencies with no written extension
Section 14 applied to all agencies. [1] An agency that had never extended Privacy Act treatment beyond the statute had, in our reading, little policy to change. Its task was to confirm that, and to check whether any program-level notices or agreements promised more than the statute required. [1] [3]
That check was not trivial. Privacy commitments can sit in impact assessments, data sharing agreements and public notices as well as formal policy. A promise of access or correction made in a program notice is a privacy policy in substance, whatever its title.
Foreign partners
For European authorities sending criminal enforcement data to designated U.S. agencies, the week brought statutory remedies for their citizens from February 1, 2017. [2] The designation rested in part on the country permitting commercial data transfers to the United States. [4] So the second layer tied a law enforcement agreement to the conditions for commercial data flows, in the text of the Act itself. [4]
Objections, in order
1. Section 14 removed privacy rights from immigrants
For the statutory layer, there were no Privacy Act rights to remove from people outside the Act’s definition. [3] For the Judicial Redress Act layer, the order applied only to the extent consistent with law. [1] [4] What it removed was policy-based treatment, and at DHS that included administrative access and amendment under the 2007 policy. [5] That loss was real, but it came from the policy layer.
2. The order changed nothing because the Act never applied
That goes too far the other way. DHS had promised Privacy Act treatment to everyone in mixed systems since 2007, and the 2017 memo withdrew that promise. [5] In our reading, for a person seeking to correct a DHS record, the difference between a Privacy Act request and a FOIA request is the right to seek amendment. [3] [5]
3. Agencies could simply flag non-citizen records and move on
DHS’s own memo explains why not. Status may be missing or out of date, and a person’s status can change, bringing old records under the Act. [5] Adding status data creates new risks and costs. [5] A flag that is wrong once can turn a lawful disclosure into a Privacy Act violation. [3] [5]
4. The Judicial Redress Act made section 14 irrelevant for Europeans
Only in part. The Act covers records transferred from a covered country for criminal law enforcement to a designated agency. [4] It gives limited remedies, not the whole Privacy Act. [4] A European citizen’s record collected directly by a U.S. agency, or held by an agency outside the designated list, falls outside it. [2] [4]
5. Privacy policy should follow the statute and nothing more
That is a coherent position, and section 14 adopted it. [1] The cost is operational. DHS had adopted its 2007 policy because sorting records by status was hard. [5] A policy that follows the statute exactly has to solve that sorting problem, or accept the risk of error in mixed systems.
6. Executive orders on privacy policy are symbolic
Section 14 had concrete effects at DHS. By April 25, 2017, DHS had replaced its 2007 written policy and issued new rules for disclosure and sharing. [5] The memo required all DHS personnel to follow it. [5] The order’s reach was limited to policy, but policy governs how staff answer a request for a record.
7. The Judicial Redress Act covers too few people to matter
The Act’s coverage in 2017 was the European Union and 26 member states, with Denmark and the United Kingdom anticipated. [2] It reached only records transferred for criminal enforcement to designated agencies. [4] That is a narrow group. But it is a group defined by statute, and it covered the citizens of a major data partner. For the agencies designated, the obligations were real from February 1, 2017. [2]
What privacy and data leaders could check
The checks below follow the four layers. They are good practice suggested by the documents, not legal advice.
- Identify which systems of records hold data on both covered individuals and others, and record how each tells them apart. [3] [5]
- Map which records arrive from foreign authorities for criminal enforcement and would be covered records under the Judicial Redress Act. [4]
- Write down any policy that extends Privacy Act treatment beyond the statute, with its source and date, so it can be found when policy changes. [5]
- Set a default rule for records whose subject’s status is unknown, and have counsel approve it. [5]
- Review bulk sharing agreements for how they handle a subject whose status changes during the agreement. [5]
- Search impact assessments, sharing agreements and public notices for promises of access or correction that go beyond the statute. [5]
One further check concerns collection. Before adding a citizenship or status field to a system, confirm there is a requirement to collect it. [5] DHS’s 2017 memo treated new status data as a risk, not a fix. [5]
A last check concerns access requests. A request from a person outside the Privacy Act’s definition may still be processed under FOIA, and DHS processed Privacy Act requests under FOIA too. [5] Staff who handle requests need to know which statute applies to which requester, and what each one allows. [3] [5]
That triage has three outcomes. A citizen or permanent resident has Privacy Act access and amendment rights. [3] A covered person seeking a covered record from a designated agency has the Judicial Redress Act’s remedies. [4] Anyone else has FOIA access, plus whatever the agency’s current policy extends. [5] A request form that captures enough to sort requesters into those groups saves time and errors later.
With hindsight
Section 14 was revoked with the rest of the order. On January 20, 2021, Executive Order 13993 revoked Executive Order 13768. [6] It directed agencies to review actions developed under the revoked order and take action, including issuing revised guidance, as appropriate and consistent with law. [6]
The direction named the officials. The Secretary of State, the Attorney General, the Secretary of Homeland Security and the Directors of OMB and the Office of Personnel Management were among those told to review. [6] The order set out a policy of resetting civil immigration enforcement practices. [6]
DHS acted on that direction in 2022. Directive 262-16, issued May 4, 2022, canceled Privacy Policy Guidance Memorandum 2017-01. [7] It listed Executive Order 13993 among its authorities, along with the Privacy Act and the Judicial Redress Act. [7]
The 2022 directive restored administrative treatment. As a matter of DHS policy, it extended certain Privacy Act privileges to all individuals whose PII is in DHS systems of records, regardless of citizenship or immigration status, when retrievable by a personal identifier. [7] It extended the Act’s access, amendment and accounting for disclosure privileges. [7] It also extended the maintenance and safeguarding procedures and the non-disclosure provisions, to the extent consistent with law. [7]
The directive was careful about what it was. It said the policy did not create or modify any legally binding rights, including a right of judicial review for people who are neither citizens nor permanent residents. [7] It said the policy may be withdrawn or modified at any time, in DHS’s discretion. [7] The third layer was back, and it was still a policy layer.
The cycle then turned again. On January 20, 2025, Executive Order 14159 revoked Executive Order 13993. [8] It directed agencies to take all appropriate action to promptly revoke memoranda, guidance or other policies based on the orders it revoked. [8] Its text does not restate section 14 of the 2017 order. [8] In our reading, revoking the 2021 order did not by its own words reissue the 2017 one.
As checked on November 15, 2026, the copies of both the 2017 memorandum and the 2022 directive on DHS’s website carry a notice saying the document has been archived and may not reflect current policy. [5] [7] We did not find, in the sources we opened, a later DHS document stating its current policy on Privacy Act treatment for non-covered persons. Agencies and partners should confirm DHS’s current position directly.
The statutory layers did not move. As checked, the Privacy Act still defines an individual as a citizen or lawful permanent resident. [3] The Judicial Redress Act remains in the Code as a note to the Privacy Act, with its designation and revocation process. [3] [4] Each policy change in the cycle reached only the administrative layer.
What held up is the structure we describe. Protections granted by statute stayed fixed through three presidential orders. [1] [6] [8] Protections granted by policy were withdrawn, restored and placed in doubt again. [5] [7] [8] Systems that tied treatment to a status field faced the sorting problem DHS described in 2017 each time the policy moved. [5]
Spotted an error? Tell us and we will check it and correct the article where needed.