Encypher Trace

Give every recipient a distinct copy. Find which one comes back.

Trace adds a hidden mark before you send a file. If a copy shows up where it should not, Trace links that mark to the send record.

Get a walkthrough and a sample result See the signed result

hidden mark for each recipient, so no two copies match

visible change for the person reading the file

facts in the result: recipient, send event, and time

What Trace changes

Know which sent copy came back.

Every copy you send carries its own hidden mark, so a copy that surfaces later already has an owner.

Narrow a leak to one recipient

A board pack, a screener, or a draft filing can circulate with dozens of equally plausible suspects. Trace turns that crowd into one name.

Keep the review short

Your team starts with a recipient, a send event, and a time. The first hour goes to what happened next.

Send the file anyway

Deals stall when nobody will release the numbers. A marked copy lets you share the file and still know where it went.

Trace in action

Watch a marked copy lead back to the send.

See Trace mark a file, scan the copy that came back, and open the matching record.

The signed result

A recovered copy points to the matching send record.

Start with the person, send event, and time already in view.

Signed result

Example result

Recipient: Recipient 04
Send event: Board pack 04
Sent on: 11 Mar 2026, 14:07 UTC

Trace links a mark it can read to the sent copy. Your team reviews who moved it and what happened next.

Walk through this result with us

How it works

Protect before you send. Get a lead if the copy returns.

Trace saves the send record while the details are still fresh.

01
Make one copy per recipient
Add a hidden mark and save the person, send event, and time with it.
02
Share it as usual
Send the file through your normal channel. The hidden mark stays out of the reader's way.
03
Check a recovered copy
Upload saved text or a clear scan. If Trace reads the mark, it opens the matching send record.

Proof details

Move from a hunch to a direct lead.

Trace names the sent copy behind a mark it can read, which is where a leak review should begin. Your team can focus on that one send instead of the whole distribution list.

The mark names the sent copy. Your team finds out who moved it.
No result can mean the mark was lost, changed, or not in the file.
A print check needs enough clear, marked text in the scan.

Protect one important file before it leaves your team.

Pick the next board pack or draft filing. Mark one copy per recipient, send them as usual, and keep the record you will want if a copy comes back.

Start with one file

Apply for early access to Trace

Trace adds recipient-specific attribution to your files. Apply to test it with your own content and see a sample leak-resolution report.