Trust center

What Proofmark records

• Client sign-off: who approved, when (UTC timestamp), from which IP address, and against which project version.
• Deliverable integrity: a SHA-256 hash of every uploaded file, computed at upload and re-checked at download.
• Payment state: whether payment was pending, marked paid by the client, or confirmed by you — and when final files were unlocked as a result.
• Access events: when deliverables are downloaded (and through which channel), and when handover access is revoked.
• Agreement status: the scope your client signed off on, and when it was signed.

What your clients see

Clients interact with a single handover link. On it they see the project summary, the agreement scope, preview deliverables, a clear approve action, the payment state, and final files with an explicit locked/unlocked status. They do not see your other projects, your client list, or your workspace. Anonymous visitors can see nothing: every piece of project data requires a valid link token, and the database enforces row-level access rules on top.

How files are protected

Files live in private storage and are served only through access-checked download routes. Payment-gated files stay locked on the server until you confirm payment — a client cannot bypass the lock by guessing a URL. You can revoke a handover link at any moment, which immediately cuts off portal access and downloads. Details are on the security page.

What a proof certificate means

A proof certificate is a snapshot of the records above for one completed handover: the certificate ID, project, client sign-off timestamp, deliverable names with their SHA-256 hashes, payment status, and the proof timeline. Anyone can check that a certificate is genuine at its public verification URL (/verify/<certificate-id>), which shows a safe subset of the record — never emails, IP addresses, signatures, or the files themselves.