Verifying record…
Checking cryptographic signature and verification metadata
Verification successful
Signature valid
Public key fingerprint
Verification failed
Signature invalid
No record to verify
Provide a hash in the URL to verify a record. Example: parentsplit.app/v?h=abc123…
Evidence export detected
Export ID
To verify this export:
- Ask the person who shared this link to also send you the
bundle.jsonfile from the same export. They can download it from the app or forward it from their email. - Run the open-source verifier locally with
parentsplit-verify ./bundle.json(see Verify locally below). - The verifier checks the Ed25519 manifest signature, the SHA-256 hash chain, and any RFC 3161 timestamp token included in the bundle.
Automated bundle-fetch by URL is intentionally not provided here — evidence bundles contain private family and expense data, so the verifier requires the bundle as input rather than fetching it for anyone who has the link.
ParentSplit does not provide legal advice or guarantee court admissibility.
Go to ParentSplitVerifying export…
Checking the cryptographic signature, hash chain, and revocation status.
Verification successful
Export verified
- Signing key fingerprint
- Independent timestamp
ParentSplit does not provide legal advice or guarantee court admissibility. Verification confirms cryptographic integrity of the export, not the underlying claims.
Go to ParentSplitVerification failed
If you believe this link should work, ask the sender to send a fresh share link or the underlying bundle.json file for offline verification.
What does this prove?
This page checks the verification data associated with the record or export you scanned:
- Signature verification — signed data no longer verifies if the signed content changes.
- Hash continuity — financial evidence exports include sequential audit-chain anchors so omissions inside the selected range are cryptographically detectable.
- Independent timestamp status — evidence exports show when an RFC 3161 time-stamping authority has confirmed the export hash.
ParentSplit does not provide legal advice or guarantee court admissibility.
Why don't I have to trust ParentSplit?
For legacy activity records, the private signing key stays on the device that created the record. For evidence exports, ParentSplit signs the canonical export manifest with a server-held evidence key whose public key is published for verification.
Anyone can run the open-source verifier independently against an export bundle.
Verify locally
Install the open-source verifier and run it on your own machine:
npm i -g parentsplit-verify Records and verification, together. Changes or omissions are cryptographically detectable.
Audit the verifier sourceAbout ParentSplit
The co-parenting expense tracker that keeps both parents on the same page — without the spreadsheet. Verifiable records, transparent balances, and AI-powered receipt scanning.