Private storage, no public URLs
Files are only reachable through access-checked application routes — there is no bucket URL to leak.
Feature · Secure file handover
A handover link you control, down to the last byte
Deliverables live in private storage and reach your client through one revocable link. Every file carries a SHA-256 hash, every download is logged, and you can cut access the moment something feels wrong.
A shared Drive folder is not a handover
Public share links get forwarded. Permissions get fat-fingered. Files get replaced silently and nobody can prove what was delivered when. A professional handover needs the opposite properties: private by default, access you can revoke, an integrity fingerprint for each file, and a record of who downloaded what.
Who this is for
- Freelancers delivering source files, exports, and credentials
- Agencies with contractual delivery obligations
- Anyone who has had a share link forwarded to the wrong person
- Teams that need delivery evidence after the project closes
How it works
- 1
Upload deliverables to the project
Files go into private storage — malware-scanned on upload and hashed with SHA-256 at rest.
- 2
Share one handover link
The client portal shows previews, finals, approval and payment state in one place. The link token is unguessable and unique to the project.
- 3
Client downloads through checked routes
Every download re-validates access, re-verifies the file hash, and is written to the proof timeline.
- 4
Revoke when you need to
One click revokes the link. Open portals redirect away and further downloads are refused — instantly.
SHA-256 integrity
Hashes are computed at upload and re-checked at download, so corruption or tampering cannot pass silently.
Download logging
Who fetched which file, when, and through which channel — recorded on the project's proof timeline.
Instant revocation
Access revocation is immediate and generation-based: an old link cannot be resurrected.
Frequently asked questions
How is this different from a password-protected ZIP?
A ZIP password protects one archive once. A handover link is living access control: you can revoke it, gate parts of it on payment, watch downloads happen, and keep hashes proving what was inside.
Are uploads scanned?
Yes, uploads pass through malware scanning before they are accepted into project storage.
Can I verify a delivered file hasn't been altered?
Every file's SHA-256 hash is stored and shown on the certificate and verification page. Hash the file you have and compare — if they match, it is byte-for-byte what was delivered.
What happens to files if I delete the project?
Deleting a project removes its files and access links from the application. Keep your proof packet export if you want the evidence record.
Send your first handover link in minutes
Free plan includes one full handover — approval link, payment-gated files, and a proof certificate.
Create your free account