Transfer
Chain

Every Clex transfer is logged to a public, hash-chained ledger. No filenames. No file contents. Just anonymous session metadata — verifiable by anyone.

Append-Only SHA-256 Chained No PII Cloudflare D1
No filenames stored
No file contents stored
No IP addresses logged
Chain ID generated locally
Publicly verifiable hashes
01

Local ID

Your browser generates a random 32-hex chain ID and stores it locally. No server involvement. No fingerprinting.

02

Session Log

Each transfer creates a ledger entry with route, file types, sizes, and SHA-256 hashes. Never filenames or contents.

03

Hash Chain

Each record includes the hash of the previous record, creating a tamper-evident, append-only chain backed by a Durable Object.

04

Public View

Anyone can browse the full ledger here — transfer routes, durations, file categories, and status timelines.

Vault Stays Private
Chain Stays Public

The public Transfer Chain is for workspace transfer metadata only. Vault notes, secret links, and timed Drive-share files are not written to the public ledger.

Not on Chain

Encrypted notes, folder structure, secret-link content, selected secret protections, and timed Drive-share file contents stay outside the public ledger entirely.

What Chain Records

Chain records anonymous transfer-session metadata for public workspace delivery flows: route choice, timing, file-class information, and hash-linked status records.

Why the Split Exists

Vault is built for private drafts, secrets, and temporary handoffs. Chain is built for public verifiability of transfer routes. They serve different privacy models on purpose.

Live Ledger

Auto-refreshes every 30s

Your Transfer.
On the Chain.

Open the workspace, drop files, and send — your session will appear here automatically.