The 2017 voter-roll request tested whether privacy duties follow the data or the collector’s legal status

In early July 2017, a White House advisory commission asked every state for voter-roll data, routed through a Defense Department file service. In our reading, the legal fight turned on the collector’s legal status and on who was suing, not on the records themselves.

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

In early July 2017, a White House advisory commission asked every state for voter-roll data, routed through a Defense Department file service. In our reading, the legal fight turned on the collector’s legal status and on who was suing, not on the records themselves.

  1. The week In the first week of July 2017, a new White House advisory body was collecting state voter rolls, and a privacy group was in federal court trying to stop it.
  2. The request: a voluntary ask for records each state defined The commission did not order anyone to do anything.
  3. The pipeline: each transfer choice changed who held the data The second part concerns plumbing.
  4. The assessment: section 208 binds an agency, and only an agency The third part is the federal paperwork.
  5. The enforcement: a duty only the affected individuals could press The fourth part asks who could make the collector comply.
  6. How the episode reached different organizations The commission’s request was a federal matter, but its lessons were not limited to the White House.
  7. Objections, in order The argument that privacy duties followed the collector’s status has serious counterarguments.
  8. What a chief privacy officer could check The episode is a good test of internal privacy controls in any public body or regulated organization.
  9. With hindsight The district court ruled on July 24, 2017.

The week

In the first week of July 2017, a new White House advisory body was collecting state voter rolls, and a privacy group was in federal court trying to stop it. The body was the Presidential Advisory Commission on Election Integrity. The district court’s opinion of July 24 later set out how the collection was meant to work and what each side argued that week. [5]

The commission had been created by Executive Order 13799, signed on May 11, 2017. The order charged it to study the registration and voting processes used in federal elections, consistent with applicable law, and made it solely advisory. The Vice President chaired it, and the order let him select a vice chair from among the members. [3] He named a state secretary of state, as the court later described. [5]

The vice chair had directed that identical letters go to the chief election officials of every state and the District of Columbia. As the court later described them, the letters were dated June 28, 2017. They asked for publicly available voter roll data, including, if public under the state’s laws, full names, addresses, dates of birth, party affiliation where recorded, the last four digits of Social Security numbers if available, and voting history from 2006 onward. [5] The list also named active, inactive or canceled status, felony conviction information, registration in another state, military status and overseas citizen information. [5]

The letters offered two channels. Narrative answers to the commission’s policy questions could go to a White House email address in the Office of the Vice President. Data files could be uploaded through the Safe Access File Exchange, known as SAFE, which the letters described as a secure file-transfer site the federal government uses for large data files. [5]

As the court later described it, SAFE was run by an Army research and engineering center, a component of the Department of Defense. It let a user send up to 25 files to recipients with .mil or .gov addresses. Once states had uploaded their files, the commission intended to download the data and store it on a White House computer system. [5]

The Electronic Privacy Information Center, a nonprofit privacy group, had sued and asked for a temporary restraining order. As the court later summarized the briefing, the parties disagreed above all on whether any agency was involved. That mattered because the E-Government Act gives no cause of action of its own, and the Administrative Procedure Act reaches only agency action. [5] The government also challenged the group’s standing to sue. [5]

The agency question mattered for a second reason: section 208 of the E-Government Act. Section 208 requires an agency to conduct a privacy impact assessment before it starts a new collection of identifiable information using information technology. The trigger applies where identical questions go to ten or more persons outside the federal government. [4] The agency must have the assessment reviewed by its chief information officer or equivalent and, if practicable, make it public. [4] No assessment had been published, and the government’s position, as the court later described the dispute, was that no agency was collecting the data. [5]

On Friday, July 7, the court held what it later called a lengthy hearing. The government told it that only one state, Arkansas, had uploaded voter roll data through SAFE, and that the commission had not yet downloaded it. [5] The government also conceded that files on SAFE stayed on a Defense Department system until downloaded, for up to two weeks. How the data would then reach White House systems, and who would handle it, was unresolved at the hearing. [5] Shortly afterward, the group amended its complaint to add the Department of Defense as a defendant. [5]

The same week, the commission’s ordinary paperwork moved forward. On July 5, the Federal Register carried a General Services Administration notice that the commission, a federal advisory committee under the Federal Advisory Committee Act, would hold its first meeting on Wednesday, July 19, 2017. [1] The meeting would be livestreamed. The notice warned that written comments might be posted publicly, including names and contact information, in line with that Act. [1]

On July 7, a supplemental notice explained that the meeting was being announced with less than 15 calendar days’ notice because the July 4 federal holiday had delayed processing. [2] Both notices repeated that the commission would be solely advisory and would report to the President on laws and practices affecting confidence in federal elections and on vulnerabilities in voting systems. [1] [2]

By the end of the week, then, the shape of the dispute was set. A federal body was asking states for a national set of voter records. The records would pass through a Defense Department transfer service and land on White House systems. The government’s defense, as the court later described it, rested on the claim that no agency was doing the collecting. [5]

One way to think about a privacy duty is to start with the data. Social Security digits, dates of birth and voting history sound like the kind of records that federal privacy law protects. The July 2017 voter-roll request showed a different starting point. The government’s defense did not dispute what the data was. It disputed what the collector was. [5]

Our argument is that the federal privacy duties in play followed the legal status of the collector, not the sensitivity of the records. The commission’s design, the government’s defense and the two court rulings that followed all turned on that point. [5] [6] We take the episode in four parts:

  1. The request: what was asked for, on what footing, and what state law decided.
  2. The pipeline: how the data would move and where it would rest, and why each choice changed who held it.
  3. The assessment: what section 208 of the E-Government Act requires, and of whom.
  4. The enforcement: who could ask a court to compel compliance, and what the courts said.

The first part covers the data before it left the states. The second covers its path. The third covers the federal paperwork that a collection triggers. The fourth covers who can hold the collector to that paperwork. Together they run from the request to the remedy. After the four parts, we look at how the episode reached different organizations, answer the strongest objections, and list what a privacy officer could check.

A note on sources and our reading. We describe the July 2017 positions from the government’s court filing of July 5 and the Federal Register notices of that week. We describe later events from the court opinions and the orders that ended the commission. Statements about what a statute required of a given body are our reading. Organizations should confirm their own obligations with counsel.

The request: a voluntary ask for records each state defined

The commission did not order anyone to do anything. The government stressed this in court. Its sworn declarations, as the court described them, said the information was already public under state law and had only been requested, not demanded. [5] The request was a letter, not a subpoena or a regulation.

Public under whose law

The letters asked for each field only if it was publicly available under the laws of the state receiving the letter. [5] That phrase moved the key decision to fifty-one separate legal regimes. Each state decided which fields were public, to whom, and on what terms. A field public in one state could be closed in another.

The result was a request whose content was undefined until each state answered. A state that treated birth dates as public would send them. A state that did not would send less. The commission could not know in advance what dataset it would hold. Neither could anyone assessing the privacy risk of holding it.

In our reading, that is a design problem as well as a legal one. A privacy assessment starts by listing the fields collected. Here the field list depended on the answers. A careful assessment would have had to plan for the widest set the letter named, since some states might send all of it.

Public is not the same as assembled

The government’s answer to the harm claim started from that public status. [5] The privacy group’s position, as the district court later described it, was that consolidation itself created risk, and that states placed conditions on access to voter files. [5]

The district court did not accept that harm theory on the record before it. In rejecting the claims brought for the group’s advisory board members, it found that, at most, the plaintiff had shown an increased risk of harm from consolidation, and that an increased risk was not enough for standing under Supreme Court precedent. [5] That finding concerned standing. It did not hold that consolidation was harmless.

For a data governance team, the distinction matters. Fifty-one public files held in fifty-one places present one risk profile. One file holding all of them presents another. The second is easier to search, to match against other data and to lose in a single incident. The law of standing did not weigh that difference. A risk register can.

A request before the first meeting

The timing of the request is worth setting out. The letters were dated June 28, 2017, according to the court’s description of the copy before it. [5] The commission’s first meeting was scheduled for July 19. [1] The data was requested before the members had met in public to discuss their charge or their methods.

That order of events has a governance consequence. A privacy review starts from the purpose of a collection, because the purpose decides what is needed. Here the request went out before the body had held a public meeting on what it would study and how. [1] [5] In our reading, a purpose statement written after the data arrives cannot do the work a privacy review needs it to do.

The Federal Register notices add a small but telling detail. Both described the commission as established under Executive Order 13799 of March 11, 2017. [1] [2] The order itself is dated May 11, 2017, as the district court also stated. [3] [5] An error in a meeting notice is minor. It is also the kind of slip a document review step exists to catch.

Fields that change the risk

Some requested fields carried more weight than others. The last four digits of a Social Security number, where public, could help link a voter record to other records. Voting history from 2006 onward recorded behavior over a long period. Military and overseas status identified people abroad. [5]

None of these fields is secret in every state. Combined in one national file, they would form a dataset that no single state held. In our reading, the request treated each field’s public status in its home state as settling the privacy question for the combined file. That is the step a data steward would question first.

What the commission said it would publish

The letters said documents submitted to the full commission would be made available to the public. The government later told the court this applied to narrative responses, and that voter roll data would be de-identified before any public release. [5] The district court noted that the exact de-identification process had not been determined. [5]

A promise to de-identify, with no method chosen, is a placeholder. Voter files contain names and addresses by design. De-identifying a national file well enough to publish it is a hard technical task. The record never showed how it would be done, because the data was never used. [5]

The pipeline: each transfer choice changed who held the data

The second part concerns plumbing. Where data travels and where it rests decides which organization holds it at each moment. Under the statute at issue, that decides which legal duties attach. The commission’s plan changed within days. [5]

Email and a military file service

The original plan used two channels. Narrative responses would go to a White House email address in the Office of the Vice President, which the government said was protected like all White House communications. [5] Data files would go through SAFE, which the letters described as a secure site the federal government uses to transfer large data files. [5]

The district court later set out what SAFE was. It was operated by an Army research and engineering center, a component of the Department of Defense. Files uploaded to it stayed on the Defense system until downloaded, for a default of seven days and a maximum of two weeks. [5] The government described SAFE as a conduit. The court accepted that description in part, while noting that the files sat on a Defense Department system in the meantime. [5]

That detail mattered legally. The Department of Defense is an agency. If an agency’s system holds the data, even briefly, the argument that no agency is involved becomes harder to make. The privacy group amended its complaint after the July 7 hearing to add the Department of Defense as a defendant. [5]

One upload, then a pause

At the July 7 hearing, the government said only one state, Arkansas, had uploaded voter roll information through SAFE. The commission had not yet downloaded it. [5] On July 10, the government told the court the commission no longer intended to use SAFE and had asked states to hold off on submitting any data until the court ruled. [5]

In place of SAFE, the Director of White House Information Technology would repurpose an existing system that already accepted personally identifiable information through a secure, encrypted application. [5] The government later said the Arkansas data had been deleted without ever being accessed by the commission. [5]

Retention set by the sender

SAFE had one feature that a records manager would notice. The person uploading a file set its deletion date. The default was seven days after upload, and the maximum was two weeks. [5] Files were not archived after their deletion date, according to the court’s description. [5]

That design put a retention decision in the hands of each state official who uploaded a file. It also meant the federal side had a fixed window to download the data before it disappeared from the transfer service. Neither point is a flaw in a file-transfer tool built for that purpose. [5]

The difficulty was what happened next. The government said downloaded data would be stored on White House systems, with the details of how and by whom unresolved at the July 7 hearing. [5] Retention on the transfer service was defined to the day. Retention at the destination was not yet defined at all, on the record before the court. [5]

A repurposed system inside the White House

The replacement design, as the government described it, required state officials to request an access link and then upload to a server within a White House domain. Authorized commission members would use dedicated laptops to reach the data through a secure White House network. [5] Only a limited number of technical staff from the White House Office of Administration would help. [5]

Each element of this design kept the data inside offices that, in the government’s view, were not agencies. The design came from a declaration the government filed with the court. [5] In our reading, the switch from SAFE to an in-house system served the legal argument as well as the security one.

What the switch did to the risk

Security and legal status pulled in different directions here. A mature transfer service run by a large department has its own controls, logs and support staff. A repurposed internal system has whatever its owners configure. The record does not tell us which was more secure, and we do not guess. [5]

What the record does show is that the choice of system was made, in part, with legal exposure in view. The government told the court it made the change so as not to affect other customers of SAFE. [5] Whatever the reason, the effect was to take an agency’s system out of the data path.

For a technology leader, the episode is a reminder that hosting decisions carry legal weight. The question “whose system holds this, and for how long?” has a legal answer as well as an operational one. An architecture review that skips it can create obligations nobody planned for, or remove ones people relied on.

The assessment: section 208 binds an agency, and only an agency

The third part is the federal paperwork. Section 208 of the E-Government Act of 2002 is the source of the privacy impact assessment that federal agencies prepare for new systems and collections. [4] Its purpose clause speaks of protecting personal information as agencies implement citizen-centered electronic government. [4]

What the statute requires

The statute requires an agency to act before either of two things. One is developing or procuring information technology that collects, maintains or disseminates information in identifiable form. The other is initiating a new collection of such information using information technology, where identical questions go to ten or more persons outside the federal government. [4]

Before either, the agency must conduct a privacy impact assessment and have it reviewed by its chief information officer or equivalent. If practicable, it must then publish the assessment on its website, in the Federal Register or by other means. [4] Publication may be modified or waived for security reasons or to protect sensitive information in the assessment. [4]

The statute also tells the Office of Management and Budget to issue guidance on contents. That guidance must scale the assessment to the size of the system, the sensitivity of the information and the risk of harm from unauthorized release. [4] It must address what is collected, why, the intended use, and with whom it will be shared, among other points. [4]

The voter-roll request on the statute’s terms

On its facts, the commission’s request looked like the second trigger. Identical letters went to fifty-one officials. The data named individuals and would be collected and kept using information technology. [4] [5] The open question was the first word of the requirement: agency.

One wrinkle deserves mention. The statute counts persons “other than agencies, instrumentalities, or employees of the Federal Government.” [4] The letters went to state officials, not to voters. Whether a request to states for records about voters is a collection from ten or more persons is a question the courts did not need to reach. We flag it as unresolved, not as settled either way. [5] [6]

What an assessment would have had to answer

We can walk through what an assessment of this collection would have covered, using the elements the statute names. The exercise is ours; no assessment was published, and the government’s position, as the court described it, was that no agency was involved. [4] [5]

What information is to be collected. The answer would have been the full list in the letters, qualified by each state’s law. As we noted, that list was not fixed until states replied. [5]

Why it is being collected. The commission’s charge was to study registration and voting processes and report on laws, practices and vulnerabilities. [1] An assessment would have had to explain why a national file of named voters, rather than aggregate statistics or samples, was needed for that report.

The intended use. The government told the court that voter roll data would be de-identified before any public release, without a settled method. [5] An assessment would have needed to say what analysis the identified data would support before de-identification, and who would run it.

With whom it would be shared. The record named the White House technology office, technical staff from the Office of Administration, and authorized commission members using dedicated laptops. [5] An assessment would also have had to address the Defense Department’s transfer service while it was in use. [5]

How it would be secured and what choice individuals had. The statute’s guidance provision names notice, consent and security among the further topics. [4] Voters had no notice from the commission that their state file might be sent, and no way to object to it apart from whatever their state allowed.

Whether a system of records was being created. The statute asks this with reference to the Privacy Act. [4] A national file retrieved by voter name would raise that question directly. We do not analyze the Privacy Act here; it has its own definitions and its own case law, and the courts in this matter did not reach it. [5] [6]

Set out this way, the assessment would not have been a formality. Several answers were open. In our reading, that is the strongest practical case for doing one: it forces a sponsor to settle questions before data moves, not after.

Why agency status decided everything

The district court weighed, among other factors, whether the commission exercised substantial independent authority and whether its sole function was to advise and assist the President. [5] It found the record did not show the commission was an agency, applying circuit precedent that entities close to the President without substantial independent authority are not agencies for the Administrative Procedure Act. [5]

The court applied the same reasoning to the Director of White House Information Technology, who was by then charged with collecting the data. It found that office was part of the White House Office and likewise not an agency. [5] It relied on the government’s sworn statement that other named bodies, including the U.S. Digital Service, would have no role in collection. [5]

The court left a door open. It said that if the commission’s powers grew beyond those of a purely advisory body, the agency question might need to be revisited. [5] It also said its finding depended on the facts as they stood, which had changed substantially since the case was filed. [5]

The gap this exposed

In our reading, the episode showed a structural gap. A body close to the President could gather identifiable data on a national scale with no statutory duty to assess or publish the privacy risk. The duty would attach the moment an agency’s system became the collector or the holder. [4] [5]

This is a gap of design, not of bad faith. Section 208 was written for agencies building electronic services. Its text does not address an advisory commission assembling a national voter file. The courts applied the text as written, and the text keyed on the collector. [4] [5] [6]

The enforcement: a duty only the affected individuals could press

The fourth part asks who could make the collector comply. A duty without a party able to enforce it depends on voluntary compliance. The two courts reached different answers on standing and the same result on relief. [5] [6]

The district court: standing yes, agency no

The district court found that the privacy group had informational standing. Its reasoning was that the group alleged a statutory right to a published assessment and suffered the kind of harm the disclosure provision aimed to prevent. [5] It rejected the group’s claim to represent its advisory board members. [5]

It then denied relief. The E-Government Act gives no cause of action of its own, so the group had to sue under the Administrative Procedure Act. That Act reaches only agency action, and the court found no agency in the collection as it then stood. [5] The court called the standing victory a pyrrhic one. [5]

The appeals court: no likely standing

The D.C. Circuit affirmed the denial on December 26, 2017, on a different ground. [6] It did not decide whether any defendant was an agency. It held that the group had not shown a substantial likelihood of standing. [6]

The court read section 208 as intended to protect individuals, in this context voters, by requiring an agency to consider their privacy before collecting their information. The group was not a voter, so it was not the type of plaintiff Congress had in mind. [6] Its interest in public oversight of record systems was not the interest the provision protected. [6]

Why the standing question matters to oversight groups

Published assessments are one of the few public windows into what an agency collects and why. [4] The appeals court’s reading limits the ability of outside groups to sue for an assessment that was never prepared. [6]

The court did not say such groups cannot use other tools. It noted that the group’s Freedom of Information Act requests sought information an assessment would not have contained, and that the group would likely have made them anyway. [6] The ruling closes one route, not every route.

For an agency, the practical effect is that a missing assessment is unlikely to be cured by litigation from outside groups alone. In our reading, that puts more weight on the inspector general, the agency’s privacy staff and the Office of Management and Budget, whose Director the statute says receives a copy of the assessment for each system for which funding is requested. [4] [6]

What the two rulings mean together

Read together, the rulings narrowed enforcement to a small set of cases. The duty binds agencies. Private enforcement, on the appeals court’s reading, belongs to individuals whose information is being collected. [6] An organization that wants an assessment published for oversight purposes faces the standing barrier the appeals court described. [6]

In our reading, this places the weight of compliance on internal controls: chief information officers, privacy officers, inspectors general and the Office of Management and Budget. Courts remain available to affected individuals. But the immediate check on a new collection is the agency’s own process. [4] [6]

That allocation is a fact of the statute, not a criticism of the courts. It matters to anyone who assumes outside litigation will catch a collection that skipped its assessment. On this record, it did not.

How the episode reached different organizations

The commission’s request was a federal matter, but its lessons were not limited to the White House. Each kind of organization that holds or exchanges government data faced a version of the same question.

State election offices

State officials were the recipients. Each had to decide which fields its law made public and whether to send them. The decision rested on state law, not federal privacy law. [5] The record shows that only one state had uploaded data by the July 7 hearing, and that the commission later asked states to hold. [5]

For a state chief information security officer, the request also raised a transfer question. A state sending a full voter file to a federal service needs to know where the file will rest, who can read it, and for how long. The SAFE retention window, up to two weeks, is the kind of fact such an officer would want in writing before uploading. [5]

Counties and local registrars

The letters went to state officials, so local registrars had no direct role in this request. [5] In our reading, the point for them concerns downstream use. A record a county collects for one purpose can end up in a dataset assembled for another, through a request the county never sees.

A local office can still act on that lesson. It can record, for each data field it collects, which state law makes it public and on what terms. When the state later answers a request like this one, the local record shows what the voter was told at registration and what the state is now sending. That record is the evidence a later privacy complaint could turn on.

Federal agencies providing services

The Department of Defense, through SAFE, and the General Services Administration, through its support role, were both part of the commission’s operations. [1] [5] The Defense system briefly held real data. That made the department a defendant in the amended complaint. [5]

For a federal agency, the point is that providing a shared service to a non-agency customer can bring the agency into that customer’s privacy dispute. An agency running a transfer or hosting service could ask, before onboarding a customer, whether the customer’s collection has had its own assessment.

Contractors and cloud providers

Contractors hosting agency data operate under their contracts and the agency’s assessments. The commission episode does not change their obligations directly. It does show that the identity of the customer, agency or not, decides which federal privacy duties travel with the data into the contractor’s environment. [4] [5]

Inspectors general and auditors

Oversight offices test whether agencies follow their own privacy process. The commission episode shows the limit of that test. An inspector general can review an agency’s assessments. It has no obvious role where the collector is not an agency. [4] [5] Auditors reviewing an agency that supports such a body, as the Defense Department and GSA did, can still ask what data passed through the agency’s systems and under what terms. [1] [5]

Banks and health systems

Financial institutions and health systems face their own privacy statutes, and those statutes define their own triggers. The parallel lies in the method. Under several regimes, a duty attaches to a type of entity or a defined activity. An organization that changes its structure, its vendors or its data flows can move in or out of a regime without changing the data at all.

A health system that routes data through an affiliate, or a bank that uses a vendor to hold customer files, should know which legal entity holds the data at each step. The commission’s plan shows how much can turn on that answer. [5]

Objections, in order

The argument that privacy duties followed the collector’s status has serious counterarguments. We take the strongest in turn.

1. The data was public, so privacy law should not apply

The government made this point in court. [5] It has force for each field in each state. It has less force for the combined file. The text of section 208 contains no exemption for public information; it covers information in identifiable form. [4] In our reading, public status in a source system does not end the analysis for a new system that assembles it.

2. An advisory commission should not carry agency paperwork

This objection is the courts’ holding in another form. Circuit precedent treats bodies close to the President that lack substantial independent authority as outside the Administrative Procedure Act, and the Supreme Court has held the President himself outside it. [5] Our point is narrower. Once such a body collects identifiable data at scale, the absence of an assessment is a choice with consequences, even if the statute does not require one.

3. The courts never reached the privacy merits

That is true. The district court decided agency status and the appeals court decided standing. [5] [6] But that is the argument. The outcome depended on who the collector was and who was suing, not on how sensitive the records were.

4. Nothing was actually collected, so the case proves little

Only one state uploaded data, and the government said it was deleted unread. [5] The replacement design, though, was complete and set out in a declaration filed in court. A plan that would have assembled a national voter file without an assessment shows the gap whether or not it ran. [5]

5. Agencies already do assessments, so the gap is academic

Agencies do conduct assessments under section 208. [4] The gap is for bodies outside that definition. The commission episode showed such a body could build the collection in days, using a repurposed system. The gap was narrow and real.

We agree as a principle. The record does not show that the move away from SAFE was made for legal reasons alone. The government gave an operational reason: avoiding impact on other users of the service. [5] Our point is that the move had a legal effect either way, and an organization should see that effect before it chooses, not after.

What a chief privacy officer could check

The episode is a good test of internal privacy controls in any public body or regulated organization. These questions apply whether or not a statute requires an assessment for a given collection.

  1. For each new collection, record which legal entity is the collector, and which statutes attach to that entity.
  2. When data passes through a shared service, record whose system holds it, for how long and under whose rules.
  3. Treat a combined dataset as a new collection, even when each source field is public somewhere.
  4. Choose and document a de-identification method before promising de-identified release.
  5. When a hosting or transfer design changes, re-run the privacy review rather than carrying the old one forward.
  6. Know who could enforce the obligation from outside, and assume the internal process is the main control.

The first two questions are the core of the argument. A data inventory that lists systems but not the legal entity behind each one cannot answer them. The third question addresses the consolidation risk the courts did not weigh. The fourth and fifth address promises and changes made under time pressure, as the commission’s were. [5]

The sixth question is the hardest. If outside enforcement is narrow, the organization’s own review is the control that matters. A privacy officer should be able to show that review happens before a collection starts, and that a sponsor cannot route around it by changing the system.

These steps need no court ruling. They follow from the record of what the commission planned and how the law responded. Organizations should confirm their own statutory triggers with counsel.

With hindsight

The district court ruled on July 24, 2017. It found the privacy group had informational standing. It still denied a temporary restraining order and preliminary injunction without prejudice, because neither the commission nor the White House technology office was an agency under the Administrative Procedure Act. [5] It said the question might need revisiting if the commission’s powers grew. [5]

The D.C. Circuit affirmed on December 26, 2017, on standing alone. It read section 208 as protecting individuals whose data an agency collects, and held that a privacy organization that is not itself a voter was not the type of plaintiff Congress had in mind. [6] It did not decide whether any defendant was an agency, assuming one might be only for the sake of argument. [6]

The commission did not last much longer. On January 3, 2018, Executive Order 13820 revoked the order that created it and terminated the commission. [7] A White House statement the same day said that many states had refused to provide the commission with basic information. It said the President had asked the Department of Homeland Security to review the commission’s initial findings and determine next courses of action. [8]

What held up from the July 2017 positions? The government’s core legal claim held. No court found that section 208 bound the commission. The district court accepted the agency argument on the facts then before it, and the appeals court did not need to reach it. [5] [6]

The government’s factual assurances also held, as far as the record shows. The only data uploaded through SAFE was, by the government’s account in a court declaration, deleted without being accessed. [5] The court had said it expected the government to strictly abide by its sworn representations that the data was public, requested rather than demanded, and would be de-identified before any release. [5]

What did not hold was the collection itself. The request went out at the end of June; the commission paused it within days and was terminated within months. [5] [7] The White House statement attributed the termination to state refusals and the cost of litigation. [8] The national voter file the letters described was never assembled, on the record we have.

The legal gap the episode exposed did not close through these events. Nothing in them changed section 208, which keys on agency status, and the appeals court’s reading of who may enforce it was the last word in this case. [4] [6] The district court’s reasoning on advisory bodies close to the President was not disturbed on appeal, although it was not adopted either. [5] [6]

The referral to Homeland Security is worth precision. The January 2018 statement said only that the department was asked to review initial findings and decide next steps. [8] The statement did not say what data, if any, would move. We have not found a primary source describing such a transfer, so we make no claim about one.

For leaders in 2026, the episode remains a clear case of privacy duties defined by the collector’s identity. The same pattern appears wherever statutes attach to entity types: agencies, covered entities, financial institutions, service providers. A change in which entity holds data can move it in or out of a regime overnight.

Our reading is that the more durable lesson concerns internal process. The courts made clear that outside enforcement of section 208 is limited to the individuals whose data is collected. [6] The control that actually operates at the start of a collection is the one inside the organization doing it. The commission’s plan was built in days. An internal review step would have had to be faster still to matter.

Two questions from July 2017 stay open in our reading. One is whether a request to states for records about voters counts as a collection from ten or more persons under section 208. The other is when a body assisting the President acquires enough independent authority to become an agency. [4] [5] Neither was decided. A future collection could raise both again.

Spotted an error? Tell us and we will check it and correct the article where needed.

  • privacy impact assessment
  • E-Government Act
  • voter data
  • data governance
  • federal advisory committees