Last updated: 13 November 2026

Free tool: runs in your browser

Copy dispute timeline builderwhen you think someone copied your work

TimeBinder adds a layer of protection against AI and human fraud and disputes. Add your dated steps and the date the other work first appeared. You get a timeline in date order, the days between, and a list of gaps.

Everything you type stays on this page. The dates are what you type. This page cannot check them, and it does not show that anything was copied, who made what first, or who owns anything. It is not legal advice.

Put your events in date order

Add each step with its date, whose event it is, and what dated record backs it up. Use the made-up example to see how it works. Nothing you type is sent to TimeBinder.

Everything you type stays on this page. Nothing is sent anywhere or tied to your name.

Put your dated events in order and see which ones have no dated record

Add the dated steps of your work, and the date the other work first appeared. You get a timeline in date order, the number of days between the two, and a list of gaps. Dates are what you type, and the page cannot check them.

How do I show what happened in order when I think my work was copied? The short answer

Write a dated list of your own steps (first draft or commit, public page, trailer or preview, release) and of the date the other work first appeared, and for each date note what backs it up: a platform page, an email, or a TimeBind of the exact file. A neat timeline is easier for a platform, a lawyer or a client to read than a long message. The order of dates alone does not show copying, so keep the list factual.

A TimeBind of a file you already hold can show that exact file existed no later than a recorded time and still matches. It cannot date a file earlier than the moment you make it, so the timeline will show gaps where nothing was recorded.

Why this came up in November 2026

Developers and artists are asking what to do when AI makes a similar copy of their work. Counts below were read on 13 November 2026 (Australia/Brisbane) unless the text says another date. Game Maker’s Toolkit’s “My game was cloned with AI... what do I do?”, uploaded on 5 November 2026, showed 902,974 views, 25,819 likes and 6,500 comments. JoGameDev’s “My indie game got cloned before I released it”, uploaded on 18 October 2026, showed 334,600 views, 9,643 likes and 1,100 comments. BBC News’s “How AI ‘reskins’ are stealing human content”, uploaded on 16 October 2026, showed 215,505 views. A smaller video, “AI Clones Are Destroying Steam Next Fest”, showed 7,179 views. These are demand signals. This page does not check the claims made in any of them.

What these videos have in common is a question of order: what existed, when, and how do you show it. The tool lays out that order and highlights where your own records are thin.

Sources: Game Maker’s Toolkit, JoGameDev, BBC News and Forrest Spellman, all on YouTube. For a record checklist for the same situation, see the game clone record checklist.

What this tool does and does not do

The honest job of this page is to put your dates in order and show where your records are thin. See also the glossary entries for existed no later than and SHA-256.

Limits of the Copy dispute timeline builder
Part	What it does	What it does not do
Your timeline	Sorts the events you enter by date and puts undated events last.	Check that any date is correct.
The days between	Counts the days between your earliest dated event and the other party’s earliest.	Show that anything was copied, or who came first in fact.
Gaps	Flags events with no dated record, no valid date, or no named file.	Create a record for a past date.
A TimeBind of a file you already hold	Records that an exact file existed no later than a recorded time and still matches, using a SHA-256 fingerprint made in your browser. The file stays on your device.	Show who made a file, who owns it, or that another work was copied from yours.

If the files behind the timeline are something you may need to show later

For each “mine” event on the timeline:

Find the exact file behind it: the earliest build, the design document, the trailer master, the store page assets.
Make a TimeBind of each exact file you already hold. The fingerprint is made in your browser and the file stays on your device. You can later download a Proof of Time Certificate.
Store the files, the timeline and the certificates together, with the date of each event.

A TimeBind shows the exact file existed no later than the recorded time and still matches. It cannot show that another work was copied from yours.

Make a TimeBind: first one free →

First Pooled TimeBind free, no card, then from US$5. An ASAP TimeBind is US$15.

What a TimeBind shows, and what it does not. It shows that an exact file existed no later than a recorded time and that a copy shown later still matches its fingerprint. It does not show who made the file, who owns it, that its contents are true, or whether AI was used to make or edit it. This is general information, not legal advice.

Copy dispute timeline builder: FAQ

Does the order of dates show that someone copied my work?

No. An earlier date is not a finding of copying. The timeline only lays out the dates you give it. Whether something was copied is a question for the people deciding the dispute.

Can the tool check my dates?

No. It uses the dates you type. A platform page, a sent email or a TimeBind gives a date set by someone else, which is why the tool asks how each date is backed up.

What if the other work appears earlier than mine?

The tool says so and suggests looking for earlier records of your own, such as older files or emails. It does not draw a conclusion.

Can a TimeBind go back and date my old files?

No. A TimeBind records the time you make it. For an old file it shows that the exact file existed no later than that time, not before it.

Is this legal advice?

No. It runs in your browser and helps you organise your own records. If a claim or a dispute is involved, ask a qualified adviser.

Is anything I type or tick sent to TimeBinder?

No. This page runs in your browser. What you type stays on the page.

Related guides and tools

Your file’s fingerprint, anchored to a global network secured by real electricity and cryptography.

Editing a file—including with AI—changes its fingerprint, not its existing network record.

How this works

Your file’s SHA-256 fingerprint, a short code worked out from its exact contents, is made in your browser, and the file itself stays on your device. A cryptographic commitment to that fingerprint, which may be combined with others, is then anchored in a block on the Bitcoin blockchain. Bitcoin is secured by proof of work: computers around the world spend real electricity to add each block, and changing an earlier block would mean redoing that work faster than the rest of the network. Until that block is confirmed, your proof is pending. Once the Bitcoin anchoring is confirmed, you can verify the proof against that recorded commitment. The confirmed record can then be checked; Pooled TimeBinds are checked through TimeBinder, while ASAP TimeBinds can also be checked independently. If you check the file later and its fingerprint still matches, that shows the file existed no later than the recorded time. The record doesn’t show who made the file, whether AI was used, or that its contents are true.

Your filestays on your device
FingerprintSHA-256
Network timestampon Bitcoin

Date the exact files you already hold

Add a layer of protection against AI and human fraud and disputes: a dated, checkable record of the files behind each step on your timeline.

Open the app and sign in with email or Google.
Add your files. They stay on your computer.
Seal them and download your Proof of Time certificates.

Open TimeBinder →

First Pooled TimeBind free, no card, then from US$5. See pricing.

Related glossary entries: Content ID (YouTube), DMCA counter-notice and safe harbour.