For your security review
If you are in IT or a security reviewer, these are the questions you'll probably ask before approving an install. If something you need isn't here, ask.
At a glance
| Question | Answer |
|---|---|
| Network | De‑ID makes no network connections: no account, telemetry, update check, crash reports or cloud model. The detection model is inside the app, so the first launch downloads nothing. |
| How that's tested | Before each release, on Mac, Windows and Linux, the app cleans a set of sample files with the network blocked, including the agents' tool, the Claude Code hook and the OCR workers as their own processes. If anything tries to connect even once, that release doesn't go out. |
| Accounts | None. The computer's own login is De‑ID's login: each account on the computer has its own data folder, readable only by that account, and its own tokens. |
| Updates | Nothing automatic. New versions appear in your downloads on Polar; install one over the old one, and the data folder is kept. |
| Stage | Alpha: an early version, for testing. What it does and how it looks may change from one version to the next. |
| Source code | Not public yet. Release notes and checksums are published on the public repository hantswilliams/de-id-public; the installers come from Polar after purchase. |
What it keeps, and where
Clean copies are saved next to the originals, in a folder named after them with (de-identified) at the end. Everything else De‑ID keeps is in one data folder per account:
| System | Data folder |
|---|---|
| macOS | ~/Library/Application Support/app.deid.desktop/ |
| Windows | %LOCALAPPDATA%\app.deid.desktop\ |
| Linux | ~/.local/share/app.deid.desktop/ |
| In the data folder | Why, and for how long |
|---|---|
| The crosswalk | Maps clean copies back to the real names, so it's as sensitive as your originals. It leaves only if you export it yourself; reports and agents refer to files by generated labels. |
| Run history and settings | Who ran what, when, on which file, with the settings that were on. |
| Copies of a run's originals, and its outputs | Kept so a run can be audited: originals for 7 days, outputs for 30, as the Runs screen says. |
| Which name a token stands for | That <PERSON_26c760> means a particular person. For Copy de-identified and Restore names: kept for 30 days after a conversation's last use. Logs → Copy and restore lists each conversation as counts, never the text, with Forget for each. |
| AI workspace logs | A de-identified timeline and replay of each session, in Logs → AI sessions. It can be turned off in Settings, or for one session when it starts. |
Encrypt the disk. The data folder is protected by the account's file permissions; at rest, it's as safe as the disk it's on. Keep FileVault, BitLocker or LUKS on.
What leaves, and how
Nothing, from De‑ID itself. When a person pastes a de-identified copy into an AI chat, or runs a tool in the AI workspace, that service gets what they give it, under its own terms, as it always would. De‑ID's part is to make that the version without the names. If someone uses Install for me in the AI workspace, the tool's own installer downloads it from its maker.
Agents: one read-only door
Claude Code, Claude Desktop and Copilot in VS Code can connect to De‑ID's own tool (MCP), which reaches only the de-identified copies of runs a person chooses to share. Sharing is off by default for each run, and every call is logged without its content.
| An agent can | An agent can't |
|---|---|
| List the shared files: label, run, pages, whether reviewed | See a run nobody shared |
| Read one, a page range at a time | See an original, an original file name or a folder path |
| Search their text | Send text in to be de-identified, or get a name back |
| Reach the crosswalk, or anything but those three calls |
For Claude Code, Settings → AI tools gives the lines for its own settings: a rule that denies the folders holding originals (De‑ID's data folder is always on the list), and a hook that also stops shell commands naming them and logs reads of the clean copies. De‑ID never edits another app's settings itself. On a Mac it can also watch chosen folders with macOS's own event log and list every program that opened a file in them, so you don't have to take the tool's word for it.
Signing and checksums
The installers are delivered by Polar, the store that sells De‑ID. The release page of the public repository lists the same SHA-256 checksums, so you can check that what you downloaded is what we built.
| System | Signing |
|---|---|
| macOS | Signed and notarized macOS checks it before opening it, with no warning. |
| Windows | Not signed yet Windows can't tell who made it, so SmartScreen shows “Windows protected your PC”. Check the checksum below before choosing Run anyway, and on a managed PC let IT decide. |
| Linux | Installed with the system's own package tool (apt or dnf). Check the checksum below first. |
| File | Size | SHA-256 |
|---|---|---|
| De-ID_0.8.4_aarch64.dmg | 604 MB | f4ac91d794ea0ac1a1d0ad2d0b929ba6fd698f9486443a5e4b907a8fdc24990a |
| De-ID_0.8.4_x64.dmg | 606 MB | 55299cc3b697a851318689af0803c7c80757cd3c6d50834e4b7eb3a000f62e26 |
| De-ID_0.8.4_x64-setup.exe | 487 MB | 61985c53dc7bf07e5fdbcbbe51e340e0ed658cefb08480561d0bbb373d26c1fa |
| De-ID_0.8.4_amd64.deb | 780 MB | 7032186e29822e5aa2478460d94387a8b2dd4071a8ae84f68dd2d2f09ffd5758 |
| De-ID_0.8.4_arm64.deb | 736 MB | 773a390d74c4130e80508976f1c452f7b106f3009d019f6f11ab757128a7008e |
| De-ID-0.8.4-1.x86_64.rpm | 718 MB | f2c18aad943d53630a7b33e7e470926ace2d61e2555ca491ae27cea08c4cedf9 |
| De-ID-0.8.4-1.aarch64.rpm | 689 MB | 2a8fe8013aad220a9ecbf51fa91d473a3575914a532c9c8f4f9e343e7e60485b |
To check a download, run the line for your system in the folder you saved it to, and compare what it prints with the table:
shasum -a 256 De-ID_0.8.4_aarch64.dmg # macOS Get-FileHash .\De-ID_0.8.4_x64-setup.exe -Algorithm SHA256 # Windows PowerShell sha256sum De-ID_0.8.4_amd64.deb # Linux
What it can't promise
- That every identifier is gone. It removes what it finds, re-reads its own output, won't save a file that fails that check, and points a person at the pages to review. Our own spot check of a made-up run scored 57 of 59.
- Handwriting, or badly degraded scans. Handwriting isn't read; review redacted scans before sharing them.
- Every face, or what else in a photo identifies someone. A house, a car or a tattoo can. Every photo is flagged for review.
- Some formats. HEIC pictures, email files and audio aren't read; a file attached inside a PDF is left out rather than cleaned.
- Compliance. FERPA and HIPAA end in a person's judgement. De‑ID says which settings were on and what's still to check, and never calls a dataset “compliant”.
Report a problem
Something it missed, something that looks wrong, or a question this page didn't answer: open an issue, or email. Please don't send real identifiers; de-identify first, or describe the shape of the problem.