Articles and practical notes about digital proof, certification and safe document workflows.
Latest article
A timestamp can’t prove a video is genuine. What it can do is prove that one exact file existed no later than a specific moment, and that turns out to be useful in more deepfake disputes than you’d expect.
Read latest articleBlog articles
A timestamp can’t prove a video is genuine. What it can do is prove that one exact file existed no later than a specific moment, and that turns out to be useful in more deepfake disputes than you’d expect.
Read articleThere’s no cheap substitute that gives you what a patent gives you. But you can protect your options while you save, and most of it costs very little: keep the idea confidential, write it up in real detail, create dated evidence of that write-up, and don’t disclose it publicly until you’ve decided what to do.
Read articleYes, the date shown on an email can be faked. The “Date” line in a message is written by the sender’s own software, and nothing in the basic email protocol stops someone from putting any date they like in it.
Read articleA digital file can’t vouch for itself in a federal courtroom. Someone has to show it is what the party says it is, and for years that usually meant putting a witness on the stand.
Read articleRFC 3161 is an internet standard, published by the IETF in 2001, that defines how to ask a trusted third party to vouch for the time at which a piece of data existed. You don’t send the data itself. You send its cryptographic hash.
Read articleA dated record can support trade-secret protection, but it is not trade-secret protection by itself. The useful question is not simply, “Can I put a file on a blockchain?” It is, “Can I show what confidential information I controlled, when a particular version existed, and what reasonable steps I took to keep it secret?”
Read articleGit history is not proof that you wrote or own your code. A commit hash is good at one thing: showing that the history you’re looking at hasn’t been altered.
Read articleArticle 50 is the transparency chapter of the EU AI Act. It requires people to be told when they’re dealing with an AI system, requires generative AI outputs to carry machine-readable marks, and requires visible labels on deepfakes and on some AI-written text.
Read articleChain of custody for digital evidence is the documented history of a piece of electronic data: who collected it, how, where it was stored, who touched it afterwards, and how anyone can tell it hasn’t changed since.
Read articleHashing a document does not take it outside the GDPR by itself. A SHA-256 hash is a one-way fingerprint of a file, and whether that fingerprint counts as personal data depends on three things: who holds it, what else they can get their hands on, and how easy the original would be to guess.
Read articleYou cannot make a PDF impossible to backdate. You can, however, create a dated reference for the exact version you are about to share. The practical method is to preserve the PDF, calculate its SHA-256 fingerprint, and anchor that fingerprint to an independent timestamp before sending the file.
Read articleTrusted timestamping is a way of proving that a piece of digital data existed at or before a specific moment, using a time record that someone other than you vouches for.
Read articleA blockchain record can be put in front of a court. In most legal systems it won’t be thrown out just because it lives on a blockchain, and a few systems have said so in writing. But no major jurisdiction treats it as automatically conclusive.
Read articleIf you trained a model on synthetic data, an auditor will want to know where that data came from, how it was generated, what was done to it afterwards, and how you know it’s fit for purpose.
Read articleBefore you pay an invoice, confirm four things. The sender is who they claim to be. The invoice matches something you actually ordered.
Read articleNot by default. Most photographers deliver edited final images and hand over RAW files only when the contract says so, the client has a real reason to need them, and the price and licence reflect that.
Read articleA real estate due diligence document checklist is the list of records a buyer, investor or lender collects and reviews to verify a property before closing. It usually covers four groups: legal and title documents, financial and lease documents, physical and environmental reports, and regulatory and insurance records.
Read articleYou can verify that an insurance claim document has not changed since a particular moment by comparing its SHA-256 hash with a hash recorded earlier. A blockchain timestamp makes that earlier record independently checkable.
Read articleAn LLM audit trail should record enough to reconstruct, later, which model and configuration produced an output, from which inputs and context, through which tool calls and human decisions, and what the system did next.
Read articleAn SBOM already contains a timestamp, but the SBOM’s own author writes that value. An independent timestamp is different: you compute a SHA-256 hash of the exact SBOM file, anchor that hash somewhere nobody on your team controls, and later show that the same file produced the same hash at or before the recorded time.
Read articleA backup is not verified merely because the backup job reported “successful.” After a ransomware attack, you need to establish three separate things: the copy is from before the compromise, the data is intact and complete, and the organisation can restore and use it without reintroducing the attacker.
Read articleA file has changed if even one byte inside it is different. The reliable way to detect that is to compute a cryptographic hash, such as SHA-256, of the file at one moment and compare it with the hash of the same file later.
Read articleA policy's effective date is the day the document starts to apply. It should be written on the document itself, kept separate from the approval date, and recorded in a version history so you can show later which wording was in force on any given day.
Read articleA notary vouches for people and acts: who signed, that they did it willingly, that the ceremony followed the rules.
Read articleA tamper-evident log is one where any later change, deletion or reordering of entries can be detected, even though it can't be physically prevented.
Read articleA Merkle tree is a way of combining many hashes into a single hash, called the Merkle root, so that anyone can later prove a specific record was part of the set without seeing the other records. Change one byte in any record and the root changes.
Read articleA human review record is a stored note of what a person looked at, what they decided, and when, in relation to a specific AI output
Read articleA qualified electronic timestamp is a specific legal category in EU law. It is issued by a supervised trust service provider and carries a statutory presumption that the date, time and data integrity are correct.
Read articleA digital timestamping service gives you a verifiable record that a particular file existed in a particular form at or before a particular moment. Services differ in how they create that record, who has to be trusted, what happens to your file, and how much the result is worth if someone challenges it.
Read articleGovernments timestamp documents all the time, but they rarely call it that. A stamp on a filed form, a receipt number on a tax return, a registry entry with a date: all of these exist to answer one question
Read articleProving a document's history means being able to show, later and to someone who doesn't trust you, what the document looked like at specific points in time and that those versions weren't rewritten afterwards.
Read articleBefore you send a confidential file to someone, you can create a timestamped record showing that a file with that exact content existed at or before a certain moment, without handing the file to anyone.
Read articleShort answer: often yes, but in proportion to the risk. If your project could face questions about what data you trained on, what your model looked like at a given point, or who had what first, then a small, cheap habit of recording tamper-evident, dated fingerprints of key artifacts is worth it. If you're running throwaway experiments on public benchmarks, it's probably overkill.
Read articleHR departments can preserve employee documents by combining a sound retention process (where files are stored, who can access them, how long they are kept) with a way to show later that a file hasn't changed.
Read articleYou can't fully "protect" an invention before you file a patent, because patent rights come from filing, not from having the idea. What you can do is avoid wrecking your chances, control who learns about it, and keep good evidence of what you had and when
Read articleTo verify a file with a hash, you compute its cryptographic hash (for example with SHA-256) and compare the result to a trusted reference value. If the two strings match exactly, the file is bit-for-bit identical to the one the reference was made from. If they differ by even one character, the file has changed.
Read articleAn auditor's basic problem with a document is simple to state. The file in front of them says one thing, and they need some reason to believe it said the same thing on the date the auditee claims.
Read articleTransparency at a research institution means that the people responsible for research can show what was done, when, by whom, and on what evidence, and that outsiders can check it
Read articleYou can record a document's SHA-256 hash instead of storing the document itself, and for many purposes that is enough. A hash is a short fixed-length fingerprint calculated from the file's exact bytes
Read articlePreserving board documents means two things: keeping the records for as long as you're required or advised to, and being able to show later that they haven't changed.
Read articleLearn how researchers can create a verifiable, private timestamp for draft manuscripts, what to hash, when to do it, and what a timestamp can't prove.
Read articleA startup should archive product development by hashing each milestone artifact (specs, design files, source snapshots, release builds, test results) with SHA-256 and anchoring those hashes to a public blockchain at the time each artifact is finished.
Read articleTo document research paper drafts, keep every significant version of the manuscript in a dated, organized archive.
Read articleFounders keep documentation trustworthy by making each important record verifiable on two points: when it existed and that it has not changed since
Read articleTo independently verify a product specification, have someone with no stake in the sale test the product against the written claim, then preserve three things.
Read articleAI documentation stays independently verifiable when the proof of its content and creation date does not depend on trusting the organization that produced it
Read articleProvenance matters in AI development because it establishes a verifiable record of where data, models, and content actually came from and without that record,
Read articleStartups should timestamp pitch decks because a deck is often the first written record of a company's core idea, market positioning, and technical approach.
Read articleDocument AI workflow milestones with preserved files, version history and timestamped fingerprints. Keep the records that explain who prepared, reviewed and approved each artifact; a timestamp alone does not prove that a process took place.
Read articleMachine learning projects can preserve dated evidence of model checkpoints, datasets and governance documents. Timestamped fingerprints complement project history; they do not establish who built a model or whether a training process complied with a licence or law.
Read articlePreserve experiment checkpoints, dataset snapshots and results logs with timestamped fingerprints. The record supports existence of a matching saved version by the recorded time, without proving how the experiment was conducted.
Read articleBefore training, preserve the dataset or a manifest identifying its files, hashes and sources. Timestamping the saved document adds a dated reference; separate logs are needed to establish what data was actually used.
Read articlePair prompt version history with timestamped fingerprints at meaningful checkpoints. Preserve each exact prompt file and proof reference, plus the process records that explain how it was used.
Read articleAn AI-generated image can be hashed locally and its fingerprint registered with blockchain evidence. This supports prior existence of a matching file without establishing who created it or who owns its rights.
Read articleA logo goes through fourteen revisions before a client signs off. A screenplay passes through six drafts, three of them written in a single weekend. A photographer culls two thousand raw shots down to forty finals, discarding everything in between.
Read articleMost creative work doesn't arrive in one finished burst. A song goes through a dozen rough mixes before it's mastered. A logo starts as a scribble and ends up, three weeks later, as something unrecognizable from where it began. A codebase gets refactored so many times that the version from six months ago barely resembles the one in production today.
Read articleHow can companies record AI governance documents? Companies can record AI governance documents by generating a cryptographic hash of each file model cards, risk assessments, bias audit reports, human oversight logs and anchoring that hash to a public blockchain at the moment it's finalized.
Read articleTimestamping important AI prompt versions provides dated references for saved files. Keep process and identity records separately: a timestamp does not prove who wrote a prompt, whether it was used or how an output was generated.
Read articleMost people wait until something is "done" before they think about protecting it. A song isn't really a song until the mix is final. A novel isn't a novel until the last chapter is written. A design isn't a design until it's approved and shipped.
Read articleA designer spends three weeks on a brand identity. Logo variations, a color system, type pairings, mockups on packaging and signage. The files go out to the client for the first round of feedback, and from that point on, the designer has no real control over where they travel next.
Read articleFreelancing runs on trust that isn't always earned back. A client disappears mid-project and later claims the deliverable was never finished. A logo gets "borrowed" by someone who saw it on a portfolio site months before the contract was signed.
Read articleConsider a novelist who shares a draft with a writing group and later needs to reconstruct its history. Preserving early manuscripts, correspondence and proof references can help a reviewer compare the records.
Read articleThe moment a file leaves your hands, you lose a little bit of control over it. A designer emails over a set of mockups. A developer shares a working demo. A photographer sends a gallery of proofs. A copywriter attaches a first draft. In each case, the creator has just handed a client something valuable and, if things go sideways later, something that's suddenly hard to prove was theirs to begin with.
Read articleConsider a songwriter who saves a rough voice memo and later needs to explain how a song developed. Preserve the audio file, drafts, communications and proof references to support a review of the timeline.
Read articleConsider an artist who shares a work and later needs to compare it with a similar release. Preserved originals, timestamps and project records can help reconstruct a timeline without proving authorship on their own.
Read articleConsider a photographer who finds an image reused without permission. Preserved originals, delivery records and timestamped fingerprints can help reconstruct the file history, without establishing ownership on their own.
Read articleZero-account, browser-based service anchors document fingerprints to a public blockchain, creating independently verifiable evidence for legal, audit, IP, and digital workflows without uploading original documents
Read articleYes. A timestamped fingerprint can support prior existence of a matching file without uploading it. It does not prove who created it. You may want a dated reference for a document, source code, design file or master track while keeping it private. Certelo generates a SHA-256 fingerprint in the browser and registers that fingerprint with blockchain evidence. The original stays on your device. Keep the exact original and its proof references. They are needed to check that the file matches the registered fingerprint.
Read articleAfter timestamping a document, keep the exact file and its proof references. A reviewer can calculate its SHA-256 fingerprint, compare it with the registered value and inspect the blockchain record. A match supports existence of that version by the recorded time; it does not establish who created it. This is where a lot of people get stuck. They understand the idea of blockchain timestamping in theory, but the verification step feels like a black box. It isn't. It's actually one of the simplest parts of the whole process, and understanding it is what turns a proof of existence from an abstract concept into evidence you can rely on.
Read articleA blockchain timestamp records a file fingerprint with an independently checkable time reference. It supports prior existence of a matching file, without uploading the original or replacing notarisation, copyright registration or legal advice.
Read articleCertelo calculates a SHA-256 fingerprint in your browser without uploading the file, then registers the fingerprint with blockchain evidence. Comparing a preserved original with that record supports existence of a matching version by the recorded time. It does not establish authorship, ownership, truth or a guaranteed legal outcome.
Read articleA timestamp is a recorded date and time. Its usefulness depends on the system that produced it and the evidence connecting it to a file. Blockchain-based proof of existence combines a file fingerprint with a public time reference, allowing a later comparison with the preserved original.
Read articleAn independently checkable file reference lets a reviewer calculate a fingerprint and compare it with an external record. This helps assess a saved version without relying solely on the person presenting it. It does not replace an assessment of identity, custody, context or legal effect. For a blockchain proof, preserve the exact original, its certificate and usable blockchain references. The comparison supports prior existence of a matching version, not proof of who created it.
Read articleThe core reason proof of existence matters: it turns "trust me" into something verifiable.
Read articleBefore sharing an important file, preserve the exact version and the records that explain it. Files can be copied, edited or redistributed after sharing. A timestamped fingerprint gives you an external reference for the saved version, while delivery records, agreements and project history provide additional context. Timestamping supports prior existence of a matching file by the recorded time. It does not establish authorship, ownership or delivery, and it does not eliminate disagreements.
Read articleProof of existence is a way of establishing that a specific piece of content a document, an image, a piece of code, a contract, a song which existed in a particular form at a particular point in time.
Read articleTimestamping an important file adds an external reference for a saved version. A reviewer can compare its SHA-256 fingerprint with the blockchain record to check prior existence by the recorded time. Keep the exact original and proof references; timestamping does not prove authorship, ownership or a legal outcome.
Read articleA practical guide to two tools that answer different proof questions.
Read article