Security

What goes in.
What goes out.

AnoVeil talks to our services to check who you are and what you have paid for. It never sends them your documents. This page is the full list of what travels on each path.

The boundary
Never leaves your device
The text of your documents
Every value AnoVeil detects
The codebook of pseudonym → real value
Your custom vocabulary and whitelist
File names and file contents
Your accept and reject decisions at review
Goes to AnoVeil
Who you are — your account identity
Whether your subscription is active
Which devices you have authorized
A bug report, only when you press Send
How the left side is enforced

The engine is local

Document processing runs in a local engine bound to 127.0.0.1. The interface is embedded in the application and loads nothing from a CDN.

The models are bundled

Detection models ship inside the application and offline mode is forced whether or not the cache is present. A missing asset falls back locally instead of fetching one.

A test enforces it

Every non-loopback socket is blocked, then a scan, an anonymise and a restore are driven through. If any reaches out, the build fails. A second test proves the block itself bites.

What the server receives

Four things.

Account identity
Enough to know the account is yours and the session is valid.
Subscription state
Whether the subscription is active, so protected features can be unlocked.
Device authorization
A record that this device is authorized, so it can be listed and revoked.
Standard request logs
Our servers record the IP address and timestamp of each request, as any web service does, to apply rate limits and detect abuse. The application itself sends no telemetry — no analytics, no error reporting, no usage counting.

Authorization

Server-validated

Account, subscription and device access are checked by AnoVeil’s services, not trusted from whatever the local application claims.

Device authorization

A device must be authorized before protected functionality is enabled — per device, not per install.

Revocable

Authorized access can be revoked from your account portal. Once revoked, it is not treated as valid again.

Fails closed

If a check fails, an identity mismatch occurs, or access has been revoked, the application stops treating the device as authorized rather than carrying on.


Data handling

As little as
the service needs.

Collected
Only what the service needs to operate — identity, subscription state, authorized devices.
In transit
Traffic between AnoVeil and its services is protected using modern transport security.
Retained
Only as long as needed to run the service, meet legal obligations, prevent abuse and keep your account working.
Deletable
You can request deletion of your account and its data, subject to legal and operational retention.
Yours to manage
Account, subscription and authorized devices are managed from the AnoVeil account portal.

On your disk

Where the rest
of it lives.

Windows %LOCALAPPDATA%\AnoVeil

Your codebook, your vocabulary, and an unfinished review if you closed mid‑way. On first run you choose whether the codebook is password‑protected or stored as‑is. Uninstalling leaves all of it in place.

AnoVeil is Windows‑only today. macOS and Linux are not supported yet.


Accuracy

What it misses.

Detection is strongest on structured values and weakest on people’s names, the category that matters most. We publish the per‑category figure rather than a blended average, because adding easy categories lifts an average without the hard case moving.

The figures are recall — the share of the person names present that AnoVeil found — measured over a 60‑document corpus, most recent run. Precision on names is higher, at 0.95: when it marks a name, it is almost always right. Across runs recall has ranged from 0.76 to 0.85, and we publish the latest rather than the best.

0.76
Names found · high accuracy
0.49
Names found · fast mode

Review every document before you send it. AnoVeil shows what it found and lets you add what it did not — the review step exists because detection is a safety net, not a guarantee.

Responsible disclosure

If you believe you have found a security vulnerability in AnoVeil, please report it privately. Include enough detail for us to understand and reproduce the issue, and please give us a reasonable opportunity to investigate and address it before disclosing publicly.

Security contact
security@anoveil.com