Anonymize a Word document for Gemini — in your browser
Meeting notes, interview transcripts, and case write-ups live in Word. Data Alias extracts the body text of a .docx entirely in your browser, turns each line into a reviewable row, and suggests in-place aliases for the emails, phone numbers, and other contact details scattered through the prose — so the document's meaning survives while the identities don't travel.
How it works, step by step
Upload your DOCX
Drop the .docx into the workspace (a Pro format, free during the beta). The body text is extracted locally in your browser — the document is never sent to a server.
Review what was detected
Detected emails, phones, and IPs are suggested for in-place aliasing with the surrounding sentences preserved; credential patterns default to removal. Optional on-device name detection (English and Korean) can suggest person names as aliases. Everything is reviewable before it applies.
Download the .safe.txt extract for Gemini
You get an AI-ready .safe.txt extract of the document — not a rebuilt .docx. Hand that to Gemini for summarizing or analysis, and keep the mapping locally to de-alias the response.
Example: session-notes.docx → session-notes.safe.txt
Why anonymize before Gemini?
Human reviewers can read consumer conversations
Google documents that conversations in the consumer Gemini apps may be read by human reviewers to improve the service. That is a documented process, not a leak — and it is exactly why pasting a customer list into a consumer chat deserves an anonymized copy instead of the original.
Source: Google Gemini Apps privacy notice ↗A reviewed conversation should contain aliases, not identities
If a conversation can be sampled for review, the safest version of your file is one where the reviewer would see PERSON_001 and EMAIL_002 rather than real people. The analysis quality is the same; the exposure is not.
Source: Google Gemini Apps privacy notice ↗These are Google's own documented behaviors as of our research (July 2026). Policies and defaults change — an anonymized copy is the control that doesn't depend on them.
What to know about word (docx) files
Body text extraction, stated plainly
The extract is the document's body text. Formatting, comments, and embedded objects are not part of the output — the preview shows exactly what was extracted, so you can check nothing important was left behind before you rely on it.
Consistent aliases across a set of documents
With the Pro alias vault, the same participant keeps the same alias (PERSON_003) across every transcript in a project — the mapping is encrypted with your passphrase and stored only in your browser. Useful when a project spans many interview files.
Common questions
- What parts of the document are extracted?
- The body text. Headers, comments, and formatting are not included in the extract. The review table shows the extracted lines before anything is transformed, so you can verify what will be in the safe copy.
- Why is the output a .txt file?
- Data Alias produces an AI-ready text extract rather than rebuilding a Word file. Reconstructing a .docx would risk silent content changes; a plain extract is honest about what it is and pastes cleanly into any AI tool.
- I anonymize interview transcripts — anything for researchers?
- Yes. Consistent PERSON_00x aliases across interview files (via the encrypted alias vault), an on-device anonymization report, and a locally kept reversible mapping are built for qualitative research workflows. See the research page for the full mapping to IRB-style de-identification needs.
An honest note on detection
Data Alias reduces exposure risk but cannot catch every sensitive value, and no automated detector can. That is why nothing is applied without your review: check the safe copy before you share it with Gemini or anyone else.
No account needed. Files stay in your browser — verify it yourself.