01 · The Question
If You Remove the Names, Is the Research Information Safe for AI?
You have interview transcripts, survey responses, case records, field notes, or a research dataset that you would like an AI tool to summarize or analyze. Before uploading it, you delete the participants' names.
Is that enough?
Sometimes removing names substantially reduces risk. But a name is only one way a person can be identified. Research information can contain other direct identifiers, indirect identifiers, distinctive combinations of characteristics, free-text clues, or links to information available elsewhere. A dataset labeled "anonymous" can therefore remain identifiable in practice.
03 · What You Need to Know
A Name Is Only One Route to Identification
Direct identifiers are the obvious starting point
Names are direct identifiers because they can point directly to a particular person. Depending on the research context, other direct identifiers can include email addresses, telephone numbers, account numbers, identification numbers, biometric identifiers, photographs, and similar information.
Removing those fields is often an important first step. It is not necessarily the last one.
NIST describes de-identification as removing the association between identifying data and the data subject, with the goal of reducing disclosure risk while retaining useful information. Its guidance emphasizes that de-identification is a risk-management process rather than simply a find-and-delete exercise.
Indirect identifiers can identify someone without naming them
Information does not have to say "Maria Santos" to reveal Maria Santos.
A record might instead describe a "61-year-old female neurosurgeon working at the only tertiary hospital in a small provincial city." None of those variables is a name. Together, however, they may substantially narrow the possible identity.
Variables that can contribute to identification when combined with other information are often called indirect identifiers or quasi-identifiers.
| Information |
Why it can matter |
Possible risk-reduction approach |
| Name |
Directly identifies a person |
Remove or replace where appropriate |
| Exact age |
Can become distinctive, particularly at unusual ages |
Consider age bands when analytically acceptable |
| Exact location |
Can sharply narrow identity |
Use a broader geographic category where appropriate |
| Exact dates |
Can link records to public or institutional events |
Generalize or transform dates where methodologically permissible |
| Rare occupation |
May identify a person in a small population |
Use a broader occupational category where appropriate |
| Institution |
May identify participants or research sites |
Generalize or suppress when not analytically necessary |
| Verbatim quotation |
May contain distinctive events or searchable language |
Assess the quotation and surrounding context carefully |
| Photograph, audio, or video |
May contain biometric, visual, voice, or contextual identifiers |
Do not treat removal of a filename as de-identification |
Pseudonymization is not necessarily anonymization
Replacing "Maria Santos" with "Participant 17" changes the identifier. It does not necessarily make the record anonymous.
If a researcher retains a key connecting Participant 17 to Maria Santos, the information is generally better understood as coded or pseudonymized rather than irreversibly anonymous. Depending on the applicable legal and research framework, pseudonymized information may continue to be treated as personal data.
Pseudonymized or coded information
Direct identifiers are replaced or separated, but an authorized party may still be able to reconnect the record to the person using additional information.
Anonymous information
The information cannot reasonably be linked to an identifiable person under the applicable standard and context.
Researchers should therefore avoid calling a dataset "anonymous" merely because participant IDs have replaced names.
Combinations of ordinary variables can become identifying
Identification risk is contextual. A variable that is harmless in one dataset can become revealing in another.
Age 42 may identify nobody in a national survey containing thousands of records. Age 42 combined with a small village, an unusual occupation, a rare diagnosis, and the date of a public incident could point to one person.
HHS guidance on de-identification under the HIPAA Privacy Rule explicitly recognizes that information can identify an individual either alone or in combination with other reasonably available information. Under HIPAA's Expert Determination method, the assessment therefore considers the anticipated recipient and the information that recipient might reasonably have available.
Free text is especially easy to underestimate
Structured datasets make identifiers relatively visible because information sits in labeled columns. Qualitative research is messier.
An interview transcript can contain names of relatives, workplaces, neighborhoods, schools, distinctive events, health histories, political offices, job titles, dates, relationships, quotations from public posts, or descriptions that identify someone without ever stating the participant's full name.
NIST specifically notes that de-identification can apply not only to structured records but also to free-format text, multimedia, and medical imagery. These forms of data can require different de-identification techniques.
Watch Out
Searching a transcript for participant names and replacing them with "[NAME]" is not a complete de-identification procedure when the remaining narrative can still reveal who the participant is.
AI does not make residual identifiers disappear
If you upload a transcript after removing the participant's name, the AI service receives whatever remains. It may receive the participant's workplace, rare medical history, exact dates, quotations, family relationships, location, or other identifying context.
The relevant safety question therefore concerns the information that actually reaches the AI system, not what you removed beforehand.
This connects directly to what happens to research information after it enters an AI system. De-identification and provider data handling are separate safeguards. Neither substitutes for the other.
External information can make re-identification possible
A dataset does not exist in informational isolation. Public records, institutional webpages, social-media posts, news reports, publications, professional profiles, and other datasets can sometimes be linked with supposedly de-identified information.
NIST notes that de-identified data can sometimes be re-identified and recommends evaluating the potential risks created by release rather than assuming that removing a standard set of fields always produces adequate protection.
This means the question is partly about the environment into which the data are released. Information that presents low identification risk to one recipient under controlled conditions may present a different risk when disclosed more broadly.
Formal de-identification standards can be more demanding than removing names
Researchers working with regulated data should follow the applicable standard rather than invent their own definition of anonymity.
For example, the HIPAA Privacy Rule provides two routes for de-identifying protected health information: Expert Determination and Safe Harbor. Safe Harbor requires removal of a specified set of identifiers and requires that the covered entity have no actual knowledge that the remaining information could identify an individual. Expert Determination instead requires a qualified expert to determine and document that the identification risk is very small under the specified conditions.
This does not mean HIPAA governs every research project or jurisdiction. It illustrates how a formal de-identification standard can require considerably more than deleting names.
De-identification reduces risk rather than creating magic immunity
Even properly de-identified information can retain some residual identification risk. HHS explicitly notes that both HIPAA de-identification methods retain a very small, but not zero, possibility of re-identification. NIST likewise treats de-identification as a means of reducing privacy risk rather than guaranteeing that re-identification is impossible.
Researchers should therefore avoid treating "de-identified" as a synonym for "risk-free."
Removing identifiers also does not answer whether AI use is authorized
Suppose you successfully reduce identification risk. You still need to determine whether your ethics approval, participant consent, data-management plan, data-use agreement, institution, funder, or applicable law permits the information to be processed by the AI service.
A study protocol might restrict data processing to approved systems even after direct identifiers have been removed. A data-use agreement may prohibit external services. A participant may have consented to particular forms of processing but not others.
This is why AI research-information safety cannot be reduced to de-identification alone.
04 · A Practical Example
A Transcript Without a Name Can Still Identify the Participant
Hypothetical Example
A researcher removes the participant's name before AI coding
An interview transcript originally identifies the participant as "Dr. Reyes." The researcher replaces the name with "Participant 08" and considers uploading the transcript to an AI tool for thematic coding. The transcript still states that the participant is a 63-year-old hospital administrator, works at the only private hospital in a particular municipality, became administrator in 2019, and publicly led the hospital's response to a distinctive local emergency.
Remove the direct identifier
The participant's name is no longer present.
Inspect indirect identifiers
Age, occupation, institution, location, employment history, and a distinctive public event remain in the transcript.
Consider linkage
Public institutional webpages or news coverage might make the participant straightforward to identify from those details.
Assess the remaining information
The researcher does not label the transcript anonymous merely because the name has disappeared. The applicable de-identification, ethics, consent, and institutional requirements are evaluated.
Decide whether AI processing is authorized
Only after the residual identification risk and governing research requirements are addressed does the researcher consider whether the specific AI environment is appropriate.
The name was one identifier. It was not the only identifier.
07 · A Quick Checklist
Before Treating Research Information as Safe for AI
After removing names, check:
Remove or appropriately transform other direct identifiers required by the applicable de-identification standard.
Look for indirect identifiers such as exact ages, dates, locations, occupations, institutions, relationships, and rare characteristics.
Review free-text responses, transcripts, notes, images, audio, video, and metadata for identifying context.
Consider whether combinations of otherwise ordinary variables could distinguish a participant.
Consider whether public records, websites, publications, social media, or other datasets could be linked with the remaining information.
Distinguish coded or pseudonymized data from genuinely anonymous information.
Apply the de-identification, ethics, privacy, consent, and data-use requirements governing your specific research rather than inventing an informal threshold.
Verify separately that the proposed AI service is authorized for the remaining information.