Product
Trace a leaked deck back to the share that made it.
Every share carries a visible watermark with the recipient's name and an invisible fingerprint across three channels in the HTML. Drop a leaked file into the forensics tool and Codexroom returns the share that produced it.
The problem
"Confidential" written on a slide stops nobody.
Watermarking decks today is an honour system. The deck has the word "Confidential" stamped in 11pt grey at the bottom. The recipient screenshots it, pastes the screenshot into a chat, and the trail ends. The compliance team writes a memo and the partner shrugs.
A leaked deck deserves a forensics answer.
The visible layer
A watermark every recipient sees.
Five styles ship by default. Confidential with the recipient name. Draft. Under NDA with the recipient name. Custom (a free-text template with {recipient_name} and {date} placeholders). None (off, with a confirmation step that puts the choice into the audit log).
Placement on the bottom-right of every slide. 11pt. 55 per cent opacity. Sentence case with light letter-spacing. Colour follows the slide text so it reads on light and dark slides.
The invisible layer
Three channels combined. Six to twelve bits per slide.
Codexroom embeds an invisible fingerprint inside the rendered HTML of every share. Three independent channels work in parallel.
Whitespace. The number of spaces between specific elements varies in a pseudorandom pattern derived from the share token. Invisible to a reader. Stable across copy-paste of the HTML.
CSS rule order. Equivalent CSS rules in the inline stylesheet reorder according to the share's seed. No visual change. Stable across most HTML edits.
Zero-width characters. Strategically placed zero-width spaces, joiners, and non-joiners inside text nodes. Survive copy-paste of rendered text into another document.
A 12-slide deck carries about 72 bits of invisible payload. That is enough to identify one share inside a portfolio of a billion.
The forensics tool
Drop a leaked file in. Get the share back.
Codexroom ships a CLI: pnpm forensics:identify --html <path-to-leaked-file>. The tool decodes the bits from the three channels, looks them up against the share database, and returns the matching share with recipient name, recipient email, deck, and the user who created the share.
The same decoder works on plain-text copy if the zero-width channel survived the paste.
What it replaces
The honour system. The memo. The shrug.
The reader knows the watermark is there. The compliance team knows the forensics tool will find them. The deck stops leaking, or the leaker stops being a problem.
PDF and PPTX
Different format, same trail.
PDF carries the visible watermark in the render and the share's fingerprint in the PDF metadata. PPTX writes the fingerprint into the document properties XML. Survival depends on what the recipient does to the file. Codexroom flags the survival profile of each channel on the audit page so your team knows what to expect.
See it work