files and attachments

Mask personal data in files before the model reads them.

The attachment is where the whole case file is. A prompt holds a sentence; the file next to it holds the contract, the claims list, the patient letter. OBVELO takes a docx, xlsx, pptx, csv, txt, rtf, eml, HTML or XML file apart, masks it with the same engine and the same tokens as the text around it, and puts it back so it still opens. A PDF with a text layer comes back as its masked text, an Outlook .msg as a masked .eml, and an old .doc, .xls or .ppt as a masked .docx, .xlsx or .pptx on gateways that run the converter — in every plan, at no extra charge — and anywhere else such a file is refused with the remedy, never passed on. What cannot be masked is named — never passed on silently.

A chat page showing the CSV file it received: under the header Name, National ID, Email, Phone and Amount, each row starts with tokens such as [Person …], [ID …] and [Email …], and the add-on confirms that claims.csv was masked and the site now has the masked copy
What the chat site received from the paperclip: tokens where the names, national ID numbers and email addresses were.

what comes back

Word, Excel, PowerPoint, CSV — masked and still open

Authors, comments, chart labels and hidden metadata included. A spreadsheet keeps its sheet and its amounts; only the personal values become tokens.

A Word document before and after: the person, national ID number, address, IBAN, email address and phone number are tokens in the masked copy, and so is the author in the file properties
A Word document, and the masked copy: the author in the file properties included.
A spreadsheet before and after: the names and email addresses are tokens in the masked copy, and the amounts are unchanged
A spreadsheet, before and after.

in the browser add-on

Attach with the paperclip. The site gets the masked copy.

The add-on takes the file before the chat site sees it, has the gateway mask it, and hands the site the masked file under the same name. A panel shows exactly what the site received.

masked

Values out, structure kept

People, identifiers, email addresses and phone numbers become tokens; column headers, amounts and dates the rules do not treat as personal stay where they were, so the model can still work with the table. The same person keeps the same token in the file and in the prompt.

A PDF with a text layer is sent as its masked text, named contract.pdf.txt, and the banner says so — a PDF cannot be edited in place.

read, with OCR

A scan is read and masked — on every paid plan

On every paid plan a scanned PDF, a photographed page or an image is read, masked like typed text and sent as its masked text, and the characters it holds are counted like any other text. On Free, which has no OCR, a scan has no text to mask: by default it is attached unchanged and a banner names the file and the reason, because a person who cannot attach a file switches the add-on off, and then nothing is protected. A company that wants such files refused switches that on in the add-on's settings.

A file dragged onto the chat page or pasted into it is masked the same way as one chosen with the paperclip, and handed to the page’s own file button. If the page has no file button, or no attachment appears in its message box, a banner says that nothing was attached.

The add-on's notice beside a chat page that received scan.pdf: attached as it is, not masked, because it is a scan and OCR, which reads scans on every paid plan, is not offered by this key's plan or gateway

on the gateway page

Drop a document, download it masked

/app

For the person who has no integration yet

Every gateway serves a page at /app: enter your key, drop a docx, xlsx, pptx, csv, txt, rtf, eml, msg, HTML, XML or a PDF with text, and get it back masked — with the table of what was replaced beside it. The document and the table exist in that browser tab and nowhere else; the gateway keeps neither.

The gateway page after masking a Word document: six values replaced — an address, a person, a national ID number (token [ID …]), an IBAN, an email address and a phone number — and a button to download the masked document

in your systems

The same on every path that can give the file back

proxy

Files inside model requests

A file in an OpenAI, Anthropic, Gemini or Mistral request is masked before it is forwarded, and a person the model quotes from the file is restored in the answer. The provider's own response shape is left alone; what happened to the files travels in a header. A PDF with text is forwarded as its masked text. Under the mask policy, a file that cannot be masked — a provider file id, a password-protected PDF, a scan on a plan without OCR or past its monthly page cap — refuses the request with a hint instead of reaching the provider.

API

Any JSON with a file in it

Send the payload as object to /v1/mask: Office, email, HTML, XML, CSV, TXT and RTF files come back masked in their own format, a PDF with text (and a scan, on a plan with OCR) as masked text, and the map carries the file's tokens so you can restore whatever the model writes about it.

never

What no path can mask

A password-protected PDF, a scan on a plan without OCR (Free) or past the plan’s monthly OCR page cap, and a file or picture your model provider fetches by id or by link — that file never passes through the gateway. Each is named in the answer with its reason.

measured on every engine change

Somebody else's documents, sent as real files.

10 000

documents, each sent as a docx, xlsx, pptx, csv or txt file

31 736

personal values the text path masks — 0 left in the file

6 494

copies in file properties and review comments — none left

0

files that no longer open

Nemotron-PII documents no one had read, never used for tuning · each file judged against the same document sent as plain text · rule layer

and the hiding places no public corpus has: 22 hand-built containers — 57/57 personal values masked, 32/32 structural values kept — and 200 malformed files, 0 of them returned damaged

your policy

One choice in the account panel

files in requests

Report, mask or refuse

Report is the default: the file passes on and the answer names it, so a file never goes through unnoticed. Mask masks everything that can be masked and reports the rest. Refuse turns away any request that carries a file. The choice applies to every key on the account.

The account panel's file setting set to mask, with a note that it applies to the model proxy and to the object field of /v1/mask, and the confirmation that every key on the account uses it

Mask the file, not just the sentence.

Questions about your document types? Tell us which files you handle.