← Back to the category

Websites, pages, posts and online content

A page, ad, offer or post that may be changed or deleted

Goal: document a copy of online content with its context.

Create an account and start

The problem

An offer, ad, post, comment, policy, profile or page may change or be taken down, with significant financial, civil, criminal or reputational consequences.

Note the URL and the context of the capture. A copy may miss dynamic content, logged-in views, comments and later changes. For campaign rules, see promotions; for exam notices, see answer keys and exam pages.

Online content can be edited by design. A shop can change an offer's price after you've bought. A profile can delete an offensive comment. A company can rewrite its returns policy. By the time a dispute starts, the page shows something else, and it's your word against the current version.

That's why anyone who relies on that content needs to keep their own copy while it's live, in a way that shows the context.

What to preserve

A full capture, the URL, a PDF, the HTML when available, associated files and, when useful, a screen recording that shows the context.

Goal: document a copy of online content with its context.

Main file: a full capture, PDF or available HTML, together with the URL.

When to capture: when you see the relevant content.

Supporting sources: the URL, associated files and the platform's records.

Limit of this scenario: on its own, the Record does not establish that the content was published at that URL, who published it or that it wasn't altered beforehand.

Collect only what you need, through access you are lawfully entitled to. Use neutral file names and descriptions, store files securely and share them only with people who need them. Where it is lawful to make a redacted copy, keep it as a separate file from the preserved original and note which version's hash you registered. See the Privacy Policy.

A full-page capture with the address visible says more than a three-line crop. Saving the page as a PDF from the browser, or keeping the HTML, helps show its structure. A screen recording that starts from the search, opens the page and scrolls to the key passage shows the path. Note the URL in a text file alongside the captures.

How Provenia documents this scenario

Your browser calculates the SHA-256 hash of the file you select. The file itself stays on your device: Provenia receives only the hash and metadata, meaning the file name, its size and the context fields you fill in. Provenia stores the hash and the Record data. Keep the exact file you used and the exported Dossier, because they are what make a byte-for-byte check possible later.

Three different times are involved. The time the Record was created on Provenia comes from Provenia's server and is not certified. The date of the event or capture is something you declare in the context, in the description or in the file itself, and it depends on other sources. The externally certified UTC date and time ties the hash you submitted to the timestamp authority's response; it does not certify when the event happened.

Provenia sends the hash, never the file, to FreeTSA, an external timestamp authority, which issues an RFC 3161 timestamp. Provenia validates that timestamp before the Record is completed. If FreeTSA is unavailable, or the timestamp cannot be obtained or does not validate, the Record is not created and no credit is used. Older Records created before this feature was active may have no external timestamp. A timestamp obtained today covers the hash submitted today; it is never issued later or backdated.

Each Record's timestamp is separate from the signatures on the exported Dossier: Provenia's digital signature on the PDF and the Ed25519 signature on Dossier.json. Those signatures cover the exported documents and do not certify the date of the event. See Trust and Verifiability.

In this scenario, use a full capture, PDF or available HTML, together with the URL as your reference material and check it against the URL, associated files and the platform's records. The timestamp on a hash does not confirm that the content was published at that URL, who published it or that it wasn't altered beforehand.

Step by step

  1. Define your goal and check that your access is legitimate, which permissions apply and whether any deadlines are running before you collect anything.
  2. Note the URL and the context of the capture. A copy may miss dynamic content, logged-in views, comments and later changes. For campaign rules, see promotions; for exam notices, see answer keys and exam pages.
  3. Preserve a full capture, PDF or available HTML, together with the URL exactly as it is; don't edit the file you register.
  4. Link the material to the URL, associated files and the platform's records; describe its origin and when it was captured as declared information.
  5. Group the milestones in a Project and register each relevant file separately. Keep the files untouched and the exported Dossier, with a secure backup.

What the Record shows and what it does not

A Record is a private electronic document that can form part of a wider body of evidence, assessed according to its context and origin. On its own, it does not establish that the content was published at that URL, who published it or that it wasn't altered beforehand. Keep the supporting sources and read the Terms of Use.

Frequently asked questions

Does Provenia capture the page automatically?

No. You make the capture with the tools you already use and register the resulting file.

How should I organize the files for this case?

Register the main capture (PDF, HTML or full-page image) and a text file with the URL as separate Records, plus a screen recording if the context matters. If the page changes later, capture the new version and add it to the same Project, so the two states can be compared.

Which date is certified?

Only the UTC date and time in a valid external RFC 3161 response tied to that Record's hash. The time on Provenia's server and the event or capture date you declare are separate pieces of information. The timestamp does not certify when the event happened.

Official references

Technical reference for context only. It is not legal advice or a conclusion about any case. Provenia is not affiliated with, integrated with or endorsed by the organization listed.

Start with three free credits

Each Record covers one file. Each completed Record uses one credit, including the first one, which creates the Project. A new account includes three free Document Credits and one Project, with no payment and no card, so the starter credits cover three single-file Records. For prices and conditions, see Pricing.

Already have an account? Log in.

Create an account and start

Continue reading