AI FORENSICS FOR TRUTH — CLIENT-SIDE — NOTHING LEAVES YOUR DEVICE
Document Sealing Service
Apply a forensic-grade cryptographic seal with A4 watermark, clean QR code, SHA-512 fingerprint, identity verification, GPS/device tracking, optional password protection, and Bitcoin blockchain anchoring via OpenTimestamps.
✓ FREE FOR LAW ENFORCEMENT & PRIVATE CITIZENS
Secure document sealing with forensic verification — powered by Verum Omnis cryptographic platform. Commercial sealing requires licensing.
📄
Upload PDF Document(s) — sealed as one
Drag and drop up to 10 PDFs here, or click to browse (hold Ctrl/Cmd to pick several). Multiple documents are merged and sealed as ONE — you get back a single sealed document and a single seal certificate.
Voice notes: pick the recordings (.opus) with any screen grabs of them — or upload a WhatsApp chat export (.zip): on your phone open the chat → ⋮ → More → Export chat → Include media. The archive is unpacked on this device, never uploaded; every voice note, image and the chat text seal together and the report ties each note to its sender and time.
📎
🔒 This PDF is password-protected. It can still be sealed — the seal (SHA-512 fingerprint + blockchain timestamp) will cover these exact bytes, and remains fully verifiable. But the watermark, QR code and footer cannot be stamped inside a locked file, so they will appear on your Seal Certificate instead of on the document pages. If you want a stamped copy, remove the password first (e.g. print the PDF to a new PDF), then seal that.
Identity details appear only in your private Seal Certificate — never in the public QR code.
The recipient must contact you to request the password before they can open the document. You will know they received it and opened it. This is your delivery receipt.
📊The engine improves as it is used: after each forensic report, anonymous pattern data — detector ids, contradiction types, severities and page counts, never document content, names or quotes — is shared with the rules service, and signed rule packages come back to every client.
Rule package: checking the rules service…
🤖 What "Seal document with forensic report" does. Your document is analysed entirely on this device, in your browser, by the deterministic engine; its findings are stated as fact and anchored to quoted text on cited pages. Then the AI review runs on Cloudflare Workers AI: a short excerpt is classified for context, the findings are assessed before the report is built, Brain 9 reads the sealed page text (up to 16 windows of about 11,000 characters, pages without findings first) for anything the engine missed — every suggestion must quote the text verbatim or it is discarded — and the court-ready narrative is written section by section beside the technical report. Brain 9 recommendations are shown here and held outside the sealed reports; the verdict on any person is for the court.
What leaves this device for those steps: finding metadata — the type, severity and a short quote for each finding — plus text excerpts (up to 4,000 characters from the first pages for classification, up to 12,000 characters around the finding pages for the report narrative, the sealed page text in windows of about 11,000 characters for the Brain 9 sweep, and the pages the narrative sections cite); voice-note audio for transcription. Nothing is stored server-side; GPS, device and sealer identity are never sent. For privileged or sensitive matters choose Seal document instead: nothing leaves the device.
📄 Case details (optional). Anything you enter here is printed on the forensic report cover — like a case file. Leave blank and the report simply uses the document name.
📱 This report comes from the website's deterministic engine — free for everyone, no download needed. For the full experience — the hybrid on-device AI with richer narrative reports, an evidence vault, and the legal chat — get the app that suits you when they release: Android, Windows Lite, or the Fraud Firewall for institutions.
🔒 This document is password-protected, so it was sealed exactly as-is: the SHA-512 fingerprint and blockchain timestamp cover these exact bytes and verify normally. The watermark, QR and footer could not be stamped inside the locked file — your Seal Certificate carries the seal record instead.
What Your Sealed Document Looks Like
Every page has the A4 watermark as a background layer at 20% opacity. Your original document text is preserved exactly — no content is moved, scaled, or altered. The QR code sits in the top-right margin and the seal footer with your SHA-512 fingerprint appears at the bottom of every page.
Clean QR — no border, no interfering box. Scans instantly.
Pending: the Bitcoin anchor typically confirms within 1–2 hours. Verify this document later on verumglobal.foundation/verify.html to upgrade this receipt to a confirmed proof.
How Document Sealing Works
Every document sealed by Verum Omnis receives a forensic-grade cryptographic seal that makes it tamper-evident and court-admissible.
📜 A4 Watermark Background
The full-page Verum Omnis watermark is applied at 20% opacity behind your content. Your original document text is preserved exactly — the QR code sits in the natural page margin.
📱 Clean QR Code
QR sits in the top-right margin with white background panel — never covers document text. Original document layout is fully preserved. Scans instantly with any phone.
🔒 Dual Hash
SHA-256 for OpenTimestamps blockchain anchoring. SHA-512 as the Verum forensic fingerprint. Two independent hashes, zero trust required.
⛓ Bitcoin Blockchain
OpenTimestamps anchors the SHA-256 hash into Bitcoin. Once confirmed (~1-2 hours), the timestamp is permanently and independently verifiable.
👤 Identity Pipeline
Optional sender identity (name, ID, address, email) is written into your private Seal Certificate for affidavit pre-fill and chain of custody — never into the public QR code unless you explicitly opt in.
📍 GPS + Device
Automatic geolocation and device fingerprint capture. Proves where and from what device the seal was applied.
🔐 Password Protection
Optional AES-256 password protection with delivery receipt cover page. Recipient must email sender for password — that email IS the read receipt.
🛡 Tamper Detection
Recipient uploads document to verify page. If SHA-512 doesn't match --> "TAMPERED — DO NOT ACCEPT". Cryptographically impossible to forge.
