Transparency
Claims & Sources
Every claim on CertNode.io is documented here with sources, limitations, and verification methods.
Our Approach to Claims
CertNode follows a forensic calm approach to marketing:
- No unsubstantiated statistics (removed all unsourced percentages)
- No absolute guarantees (replaced with verifiable mechanisms)
- All accuracy claims cite sources and acknowledge limitations
- Legal claims defer to courts for actual admissibility determinations
If you find a claim on our site that isn't listed here, please contact us.
All Claims
Technology
Independently VerifiableRFC 3161 compliant timestamps
Limitations: Timestamps are obtained from third-party TSAs. CertNode does not operate its own TSA.
Technology
Independently VerifiableBitcoin blockchain anchoring via OpenTimestamps
Source:OpenTimestamps project
Limitations: Anchoring is asynchronous (1-2 hours). Initial receipts are protected by L1 and L3.
Technology
Independently VerifiableSHA-256 cryptographic hashing
Source:NIST FIPS 180-4
Limitations: Hash collisions are theoretically possible but computationally infeasible.
Technology
Independently Verifiable3-layer verification system
Limitations: Each layer uses different trust anchors. All three must be verified for full assurance.
Legal
RFC 3161 timestamps meet FRE 902(13-14) technical requirements
Source:Federal Rules of Evidence
Limitations: Actual admissibility is determined by courts on a case-by-case basis. CertNode does not provide legal advice.
Technology
Independently VerifiableTamper-evident receipts
Limitations: Receipts detect tampering after creation. They cannot prevent manipulation before data enters CertNode.
Performance
Independently VerifiableReal-time receipt generation
Source:CertNode system monitoring
Limitations: Typical latency <100ms for L1 signature. L2 (Bitcoin) takes 1-2 hours. L3 (RFC 3161) takes 1-5 seconds.
Claims We Removed
As part of our forensic calm audit, we removed the following claims that couldn't be independently verified:
| Removed Claim | Reason |
|---|---|
| "70%+ dispute reduction" | No published study to support claim |
| "95%+ win rate" | Insufficient data to substantiate |
| "Court-admissible" (as guarantee) | Courts determine admissibility, not vendors |
| "Your proof works forever" | "Forever" is unprovable; now uses "independently verifiable" |
| "Industry-leading" | Subjective claim without metrics |
| "Reduce claims by 40%" | Unverified statistic |
How to Verify Our Claims
Technology Claims
Use the public /verify page to independently verify any receipt.
- • SHA-256 hash can be recalculated locally
- • RFC 3161 token can be validated against TSA certificate
- • OTS proof can be verified using OpenTimestamps client
Legal Claims
We cite standards, not outcomes. Consult legal counsel for your jurisdiction.
- • RFC 3161 is an IETF standard (verifiable)
- • FRE 902 text is publicly available
- • Actual admissibility = court discretion