Court-ready proof that your document was accessed.
Share confidential legal documents, track every open, and generate verifiable access certificates with timestamps, hashes, and cryptographic signatures.
No credit card required. Built for confidential client work.
Private storage
SHA-256 hash
Signed certificate
Verify page
BSC-2026-A19F42E3C0
Settlement_Agreement.pdf
Issued May 1, 2026 - 4 access events
Document hash
d81f...19c4
Event log hash
7c2a...92ee
Signature
Ed25519 valid
Verification
/verify/BSC...
4
Opens
1
Download
UTC
Timeline
My Files
Private documents with retained proof records
7
Active
2
Viewed today
0
Public files
Settlement_Agreement_Confidential.pdf
Viewed todayapp.blinkseal.io/?c=AHKZDD
View-only access - Download blocked
Opened 4 times - Last activity 1 hour ago
Offer_Letter_Director_of_Legal.pdf
Activeapp.blinkseal.io/?c=AHKZDD
Download blocked - Private signed URL
Opened once - Last activity 3 days ago
NDA_Johnson_&_Partners_2026.pdf
Activeapp.blinkseal.io/?c=AHKZDD
No public file - Certificate ready
Opened 11 times - Last activity 22 days ago
Audit-ready exports
Generate signed certificate records with hashes, timestamps, UTC event history, and canonical evidence bundles.
Security-first access
Private storage, server-side validation, scoped access, no public files, and production security headers.
Cryptographic signatures
Ed25519-signed certificate payloads give IT teams a verification path beyond screenshots.
Secure document sharing
Verifiable proof of access, not a hopeful email attachment.
BlinkSeal gives legal teams a controlled link, a live proof timeline, and a signed evidence bundle that captures what happened without making files public.
Secure Links
Revocable links with expiration, view limits, one-time access, and private signed URLs.
Real-Time Tracking
Record opens, downloads, IP, device, browser, referrer, and UTC timestamps.
Exportable Proof
Issue a verified certificate with file hash, event hash, and public verification page.
How it works
Three steps from upload to court-ready proof.
Upload document
Files are stored in a private bucket. The SHA-256 file hash is recorded on upload.
Share secure link
Set access rules, then send a private link that validates server-side before any document access.
Issue certificate
Export a signed access certificate with a public verification page and JSON evidence bundle.
Access proof a lawyer can explain and IT can verify.
Every certificate includes a document hash, event-log hash, Ed25519 signature, public key, canonical JSON payload, and public verification URL.
- File status and SHA-256 fingerprint
- Opens, downloads, IP, browser, and device
- Local and UTC timestamps
- Tamper-evident certificate hash
- JSON evidence bundle for IT review
Certificate BSC-2026-A19F42E3C0
Settlement Agreement.pdf
Document SHA-256
d81f...19c4
Payload SHA-256
7c2a...92ee
Issued UTC
2026-05-01 19:42
Events included
4 opens / 1 download
What this certificate proves
The stored document hash and the event log were signed by BlinkSeal at issuance. Any later change produces a different hash and fails verification.
Security lawyers can trust
Built to withstand careful questions.
BlinkSeal uses private buckets, signed URLs, server-side access checks, revocation, expiration, and certificate signing keys that never enter the browser.
Private file storage
Documents are never served from public object URLs.
Short-lived access
Viewer sessions receive temporary signed URLs only after token validation.
Owner-scoped dashboard
Authenticated owners can only manage their own documents and links.
Server-only signing
Certificate private keys remain server-side and are stored as Vercel secrets.
Built for teams that need proof
From settlement drafts to compliance notices.
Lawyers
Share settlement drafts, demand letters, NDAs, and exhibits. See when opposing counsel opens.
HR Teams
Send offer letters and policy documents with access logs instead of follow-up guesswork.
Consultants
Deliver reports and proposals with proof of receipt and download tracking.
Executives
Distribute board materials with revocation, visibility, and proof.
How verification works
A simple chain of evidence IT can validate.
Each certificate ties the original file to the access log, then signs the canonical payload. The verification page checks that chain independently.
Document hash
SHA-256 fingerprint of the uploaded file.
Event hash
Canonical hash of opens, downloads, IP, and UTC timestamps.
Signature
Server-side Ed25519 signature over the evidence payload.
Public verify
Certificate URL confirms the payload has not changed.
Simple, transparent pricing
Start free. Upgrade when proof becomes workflow.
Every plan keeps documents private by default. Paid plans add longer retention, signed evidence exports, and certificate verification for legal and IT review.
Pro
$29/mo
- Secure links
- Access tracking
- Signed proof certificates
- Private signed URLs
- Unlimited views
- Retention controls
Start sharing with proof.
Join legal, HR, and compliance teams who need private delivery, verified access, and certificate-grade records.