Media
1 item
Description
Save web pages as evidence with an eIDAS qualified timestamp: server capture for public pages, browser capture for logged-in pages. Capture web pages as tamper-evident evidence, sealed with an eIDAS qualified electronic timestamp. GetProofAnchor Capture turns the page you are looking at into a forensic evidence record: what was shown, when, and at which address, in a package anyone can verify independently. It is built for disputes, investigations, compliance and any situation where a screenshot alone is not enough. 🔍 What a capture contains - Full-page screenshot, or exactly the visible part of the screen (viewport mode) - Page HTML as rendered and the visible text - MHTML snapshot: a self-contained offline archive of the page (RFC 2557) - Network log (HAR) of the capture, with cookies, authorization headers and tokens in URLs masked - Server IP address and TLS certificate details of the captured site - Capture metadata: time, URL chain, viewport, user agent, capture mode and every interaction with the page - Optional video of the capture (off by default) Public pages can be captured by the GetProofAnchor server, which also records DNS from three independent public resolvers and RDAP/WHOIS data. Pages behind a login (member areas, dashboards, chat platforms, social media) are captured in your own browser. 🛡️ EU legal framework: Regulation (EU) 910/2014 (eIDAS) On every paid GetProofAnchor plan (from the 9 € starter pack), each capture is sealed with a qualified electronic timestamp issued by a qualified trust service provider listed on the EU Trusted List. The timestamp covers the hashes of all captured files. Under Article 41(1) of eIDAS, a qualified electronic timestamp cannot be denied legal effect or admissibility as evidence in legal proceedings solely because it is in electronic form. Under Article 41(2), it enjoys a presumption of the accuracy of the date and time it indicates and of the integrity of the data to which that date and time are bound. A qualified timestamp issued in one EU Member State is recognised as qualified in all Member States (Article 41(3)). 📋 Standards - RFC 3161 time-stamp tokens, issued by a qualified TSA operating under ETSI EN 319 421 and EN 319 422 - EU Trusted List (ETSI TS 119 612): a trusted-list snapshot is included in every evidence package for offline checking of the provider's qualified status - Methodology aligned with ISO/IEC 27037:2012 (identification, collection, acquisition and preservation of digital evidence) - OpenTimestamps: periodic anchoring of the GetProofAnchor proof chain in the Bitcoin blockchain as an additional, independent proof of existence 📦 Evidence ZIP: independently verifiable Every proof can be downloaded as an evidence ZIP containing: - all captured files - a manifest with the SHA-256 hash of every file - the qualified timestamp token (.tsr) and the exact data it seals - the TSA certificates, a verification report and an EU Trusted List snapshot - the OpenTimestamps receipt, once the Bitcoin anchor is available - the full capture metadata Verify it on getproofanchor.com/verify (it shows exactly which files the qualified timestamp seals) or offline with the open-source gpa-verify tool, without relying on the GetProofAnchor service. 🔐 Privacy and control - Runs only when you click "Create proof". Nothing happens in the background and no content scripts run automatically. - No tracking, no advertising, no analytics. - Your API key is stored locally (chrome.storage.local) and is never synced to your Google account. - Cookies, authorization headers and tokens in URLs are masked in your browser before upload. Page content itself is recorded as displayed. - Captures of logged-in or private pages are private by default. A public link is created only if you switch on "Publish public link". - Data goes only to your GetProofAnchor account (getproofanchor.com). A custom server can be set in the options, but only over HTTPS and only after confirmation. - You can delete your account at any time (GDPR Art. 17). Personal data is anonymised, and the cryptographic records stay verifiable. 🧠 Typical uses - Consumer disputes: prices, promised terms, return policies - Logged-in content: member areas, dashboards, chats, social media - Preserving evidence before litigation - Regulatory compliance and audit trails - Trademark and IP infringement documentation - Before/after records of changing pages - Source preservation for journalism ⚠️ Important GetProofAnchor records and seals the state of a web page at a specific moment. It does not judge whether the content is true and does not provide legal advice. Whether and how evidence is used is decided by the court or authority in each case. For case-specific guidance, consult a lawyer. 🌐 Requires a GetProofAnchor account: https://getproofanchor.com Privacy Policy: https://getproofanchor.com/privacy Terms of Service: https://getproofanchor.com/terms