For parents, attorneys, and mediators
What a ParentSplit evidence export shows
Every expense, approval, and settlement lives in a tamper-evident history. An evidence export packages that history with a signature and an independent timestamp so anyone can check it — without trusting ParentSplit. Here's a sample, and an honest account of what it does and doesn't establish.
A sample export
Evidence export
Ethan & Amanda — shared expenses
Range
May 1 – May 31, 2026
Expense created · Ethan
May 3, 2026 · 4:12 PM
Pediatric Dental Group — $127.00, tagged Jack, receipt attached
hash a3f9…c41e → links to #141
Expense approved · Amanda
May 4, 2026 · 9:03 AM
Approved the $127.00 dentist expense (split 50/50 → $63.50 each)
hash 7b02…9d8a → links to #142
Settlement recorded · Amanda
May 18, 2026 · 7:46 PM
$63.50 paid via Venmo, reference VEN-83021, covering 1 expense
hash e514…02bb → links to #157
Receipt confirmed · Ethan
May 19, 2026 · 8:15 AM
Confirmed receiving the $63.50 payment
hash 90cd…77f3 → links to #158
Excerpt for illustration. Real exports include every record in the range, the full hashes, the signed manifest, and a verification file.
What this proves
The records existed in exactly this form when the export was created
The export manifest is signed, and an independent RFC 3161 time-stamping authority confirms when the export hash existed. If any record were edited afterward — even by us — verification fails.
Nothing inside the date range was silently removed
Every record carries a sequence number and a hash that includes the previous record. Gaps inside the exported range are cryptographically detectable, so an export can’t quietly omit the inconvenient entries.
Which account recorded each entry, and when
Each record names the signed-in account that performed the action and the server timestamp when it happened — including approvals, edits, deletions, and settlement confirmations.
Both parents saw the same numbers
Balances, splits, and settlements are computed server-side from the same shared ledger. The export reflects the single history both parents worked from — not one parent’s private copy.
What this does not prove
Honest limits matter more in a courtroom than bold claims. Know them before you rely on an export.
That the underlying event actually happened
A recorded expense proves the entry was made and never altered — not that the purchase itself occurred. Receipts and the other parent’s approval strengthen the story; the chain preserves it.
Who was physically holding the phone
Records are tied to a signed-in account. Like email or text messages, they don’t biometrically prove which human typed the entry.
Anything that was never entered
ParentSplit can only attest to what passed through it. Cash handed over in a parking lot and never logged leaves no trace here.
That an uploaded receipt is genuine
Attached images are preserved exactly as uploaded, and duplicate-receipt fingerprinting flags reuse — but the export does not authenticate the original document itself.
That a court will admit it
Admissibility rules vary by jurisdiction and judge. Many courts accept well-kept electronic records, but only your attorney can tell you how this evidence will be treated in your case.
Check it without trusting us
Every export can be verified three ways: scan the QR code on the report at parentsplit.app/verify, share a read-only verification link with an attorney, or run the open-source command-line verifier on your own machine.
npm i -g parentsplit-verify ParentSplit provides recordkeeping tools, not legal advice, and does not guarantee that any export will be admissible in court. Whether and how electronic records can be used depends on your jurisdiction and your case — talk to your attorney about the right way to present them. Names and amounts above are illustrative.