Last updated:

Guides

Guides for protecting files, evidence and recordsAgainst AI fakes, forgery and backdating

TimeBinder adds a layer of protection against AI and human fraud and disputes.

TimeBinder adds a layer of protection against AI and human fraud and disputes. A TimeBind records that an exact file existed no later than a recorded time and still matches. The fingerprint is made in your browser and the file stays on your device. It does not detect AI, and it does not show who made a file, who owns it, or that its contents are true.

How to use this hub

These guides are for people who need a clear record of a file: lawyers, architects, inventors, developers, writers, musicians and anyone trying to protect their own records against AI forgery or a backdating dispute. They are practical, kept current, and written to be honest about limits.

Start with one of the two complete AI-forgery guides, or jump to a topic: proving a file existed first, AI forgery and deepfakes, the AI fakes and file-integrity glossary, what AI detectors can and cannot do, timestamping compared with other methods, file integrity checks, or routines by profession. You can also browse Answers, Compare, Free tools and the industry hubs.

Start here: the two complete guides

Prove your file or drafts existed first

A dated fingerprint can show that an exact file existed no later than a recorded time, and that a copy shown later still matches. It is not proof of authorship or ownership. Start with the pillar article below, or Answers for short, direct questions.

AI forgery and deepfake defence

How to respond when a document, recording, image or piece of evidence may have been faked or backdated, and what a dated original can (and cannot) show.

Timestamping compared with other methods

Registration, notarisation, email-to-self, git history, cloud versioning, C2PA Content Credentials and trusted time-stamp protocols each show something different. The compare hub sets them side by side.