Before you hand over a build or repo zip, timestamp the exact delivery. TimeBinder® makes a fingerprint in your browser. The files stay on your device. You get a checkable Proof of Time Certificate that shows that exact delivery existed no later than a recorded time. It does not show who wrote the code, who owns it, or that the client must pay. Free to start. See timestamping for freelancers and source code timestamping.
Table of Contents
The routine: timestamp before you deliver
- Export the delivery (zip of the agreed branch, build artefacts if included, and a short README of what is included).
- Optional. Check the hash with the free SHA-256 hash checker.
- Timestamp the zip (add the invoice PDF if you want both in one TimeBind). Your first Pooled TimeBind is free, with no credit card required.
- Save the Proof of Time Certificate with your copy.
- Then deliver the link or zip to the client.
- Fixes after feedback are new deliveries. Timestamp each paid milestone.
How to timestamp a file has the steps. Prove source code existed before a date explains limits of git dates.
Payment holds and scope fights
Disputes often turn on “what did you send, and when?” Email attachments get re-saved. A dated zip matches later only if you kept those bytes. Keep the statement of work and messages about scope. A timestamp does not create an invoice obligation; it dates the files.
What a TimeBind shows, and what it doesn’t
A TimeBind shows that this exact file existed no later than the recorded time. It does not show authorship, ownership or copyright, and it does not force payment. Keep contracts and invoices. This is general information, not legal advice. For design freelancers in a similar spot, see client used your design without paying.
If an assistant helped write the delivery set, the free vibe-coding review checklist asks whether you can explain and review the change before you hand it over. It does not scan the files.
Frequently Asked Questions
-
Should I wait until they pay to send the code?
That is a contract choice. Either way, timestamp what you send when you send it.
-
Repo invite instead of a zip?
Timestamp a zip of the commit you invited them to, so you have bytes under your control.
-
Source and invoice in one TimeBind?
Yes, up to 10 files.
-
What if they ask for the private key or credentials?
Do not put secrets in the timestamped zip. Deliver credentials by a separate agreed channel.
-
What does it cost?
Your first Pooled TimeBind is free, with no credit card required. After that, from US$5; ASAP is US$15. See plans and pricing
Timestamp your next delivery free
Show that this exact file existed no later than a recorded time. Files stay on your device. Get a checkable Proof of Time Certificate. Free to start. Open TimeBinder







