ProofLedger gives you a simple, independent way to say “we had this exact file at this time.” You upload once, we turn it into a cryptographic fingerprint and lock that fingerprint onto Polygon and, when requested, Bitcoin — without ever keeping your file.
- Choose a file — anything from a contract or policy to a photo, song, or video.
- ProofLedger computes a SHA-256 hash locally and discards the file.
- We store only the hash and minimal metadata in an internal audit log.
- We anchor that hash to Polygon (and optionally Bitcoin) so anyone can verify it later.
- You immediately get a certificate that explains the process step-by-step; the online verification page remains the authoritative record.
- A single page you can share with reviewers or stakeholders.
- The SHA-256 hash, key timestamps, and who submitted the proof.
- Polygon and Bitcoin transaction details so anyone can check the chain directly.
- Duplicate-check notes when the same hash has appeared before.
- Plain-language guidance on how to verify everything independently.
ProofLedger is built for anyone who needs to prove “this digital thing existed, just like this, at this time.” The same proof engine protects creative work, business records, technical logs, and legal evidence without forcing you into a one-size-fits-all legal product.
- Show who had a given file first and when it was recorded.
- Support procedural clarity by enabling independent verification of timing and hash consistency.
- Provide a neutral, independently verifiable record that others can review independently.
- Timestamp policies, reports, contracts, and approvals before and after changes.
- Show that a specific document version existed before an incident, launch, or decision.
- Help audit, risk, and compliance teams check records without digging through inboxes.
- Plan for future API access so your app can create proofs automatically.
- Trigger proofs on uploads, releases, or approvals while your users stay in your UI.
- Let users open a standalone ProofLedger certificate without exposing internal tooling.
- Plant a clear “we were here first” marker for drafts, finals, and releases.
- Lock in the state of your work before you send it to clients, partners, or platforms.
- Anchor key milestones for songs, art, scripts, products, and campaigns.
The fine print should still be readable. These pages explain how ProofLedger works as a business, what you can expect from us, and how we protect your data and proofs over time.
If there is any conflict between this Support page and a formal legal document, the formal document (Terms, Privacy, Refund Policy, or Security & Hashing Practices) controls. This page is here to explain those commitments in plain language.
A ProofLedger certificate is meant to sit beside your original file, not replace it. Think of it as the technical spine behind your story: it shows when a file was recorded and how it was anchored so your team, clients, or counsel can check it for themselves.
- Keep the original file (or a clearly agreed copy) stored safely in your own systems.
- When it matters, recompute the SHA-256 hash and confirm it matches the certificate.
- Use public blockchain explorers to confirm Polygon and Bitcoin transaction details.
- Present the certificate, the file, and a short note of how you verified everything.
- Work with counsel on how to position digital evidence in your specific jurisdiction.
ProofLedger does not provide legal advice or representation. Our job is to run a repeatable, transparent technical process and give you artifacts that others can verify independently.
What does ProofLedger prove?
ProofLedger proves that a specific SHA-256 fingerprint (hash) was recorded at a specific time, and (when present) that the fingerprint was anchored to public blockchains. It proves timing and integrity of a recorded fingerprint — not authorship, ownership, rights, or intent.
What does ProofLedger NOT prove?
ProofLedger does not prove who created a file, who owns it, whether it is truthful, whether it is original, or whether a party had permission to use it. It records evidence; it does not adjudicate disputes.
Do you store my files?
No. ProofLedger does not store your original files. ProofLedger stores only a one-way SHA-256 hash and minimal metadata needed for operational integrity and verification. You keep the original file.
How do I verify a proof independently?
(1) Recompute the SHA-256 hash of the original file using any standard hashing tool. (2) Confirm the hash matches the value shown on the ProofLedger verification page. (3) If on-chain references exist, confirm them using public blockchain explorers.
Which page is authoritative: the certificate or the verification page?
The online verification page is the authoritative record. Certificates are derived, human-readable artifacts and do not override the verification page.
Polygon vs Bitcoin anchoring — what is the difference?
Polygon is the default for fast, low-cost anchoring. Bitcoin anchoring is an optional higher-decentralization anchor used when additional external durability is required. When Bitcoin anchoring is present, the verification page will display the relevant Bitcoin references.
What happens if ProofLedger disappears?
Your original file remains yours. Your SHA-256 hash remains independently verifiable. If on-chain anchors exist, they remain publicly verifiable via the underlying blockchains. ProofLedger cannot “delete” what was publicly anchored.
What if two users upload the same file?
Identical files produce the same SHA-256 hash. ProofLedger may mark the later submission as a duplicate/previously-seen hash and preserve timing. This can show ordering of recordings, but it does not establish ownership, rights, or authorship.
Can ProofLedger be used in legal, insurance, or compliance matters?
ProofLedger does not promise admissibility or outcomes. Those depend on jurisdiction, foundation, chain-of-custody, witnesses, and case facts. ProofLedger provides a repeatable technical process, an immutable recorded fingerprint, and (when present) public anchoring references that can be independently verified.
What should I do after recording evidence?
Keep the original file stored safely under your own control. Keep the certificate alongside it for readability. When it matters, recompute the SHA-256 hash and verify it against the verification page, then document the verification steps you performed.
- Questions about a specific certificate or verification result.
- Billing, subscription, or account access issues.
- Security concerns or questions about how proofs are generated.
- Ideas for new features, industry workflows, or integrations.
Please avoid sending sensitive personal data or confidential case details by email. Use certificate IDs, file hashes, and high-level descriptions where possible. If you need a more formal engagement or review, reach out and we’ll discuss options.