A local ID
Your browser makes a random 32 character ID and keeps it. No fingerprinting, nothing tied to you.
Transfer chain
Receipts, not copies
Every transfer adds an anonymous record to a public, hash linked ledger. No filenames, no contents, just enough for anyone to check that a delivery happened
- Transfers
- —
- Completed
- —
- Browsers
- —
How it works
Four links, one chain
A session record
Each transfer logs its route, file types, sizes and SHA-256 hashes. Never names, never contents.
A hash link
Every record carries the hash of the one before it, so the chain is append only and tamper evident.
A public view
Anyone can browse the ledger below: routes, timings, file categories and status timelines.
The boundary
Chain is public, Vault is not
The chain exists to make deliveries checkable. Vault exists to keep things private. They never mix
What the chain records
- Route taken, direct or local
- File category, type and size
- A SHA-256 hash of each file
- Status changes and their times
- The hash of the previous record
What it never records
- File names or file contents
- IP addresses
- Vault notes, folders or secret links
- Anything that names a person
Live ledger
Refreshes every 30 s