Skip to content
About
The founding record

Built by someone who lived it.Engineered for everyone after.

A father trying to protect his kids discovered that every tool he could buy, install, or subscribe to wanted the full archive uploaded first. So he built the one he wished he’d had.

Founded January 2025Patent-pending Incident FinderFRE 902(14) output
The premise

The record already exists. It is in the messages. Thousands of them, across years, across apps. It just hasn’t been organized in a way anyone could show.

From thousands of messages to what actually happened. Not your interpretation. The record itself, sorted, hashed, and ready to hand to an attorney.

The founding

One father. Nine years of messages. One weekend of code.

Before CustodyComms was a product, it was a problem.

A father navigating a high-conflict custody case had tens of thousands of messages spread across nine years and seven services: WhatsApp, Facebook Messenger, Our Family Wizard, coParenter, Gmail, iPhone, and Android. No realistic way to read them all.

Keyword search missed context. Manual review would have taken weeks he didn’t have and money the family couldn’t spare. Screenshots weren’t going to cut it in front of a judge. And every off-the-shelf tool he looked at wanted him to hand over the full archive to their cloud, their servers, their retention policies, before he could even see a result.

The deepest frustration was quieter than any of that. Not one tool, paid or free or enterprise, could put WhatsApp, Messenger, OFW, coParenter, Gmail, and iPhone on the same timeline. Each app insisted on being its own island. The actual story, the back-and-forth that revealed who said what, when, and in response to whom, was spread across seven silos that had no interest in talking to each other.

“If I don’t want to upload my kids’ lives to a stranger’s server, why should any other parent?”
Founder, week one

So he started writing. A parser that ran on the desktop, not in a browser tab. A deterministic incident finder, not a chatbot, that could be audited and reproduced. An export format that a court would actually recognize, with per-file hashes and a certification template ready for a qualified signer.

The weekend wasn’t an accident. The founder had spent the previous decade building FDA Class II medical device software. In that world, audit trails, deterministic behavior, and defensible documentation aren’t features. They’re table stakes. Applying that same discipline to a pile of custody messages wasn’t a stretch. It was the obvious thing to do.

Artifact · CC-EXPORT-001

The cover page from the first evidence export. Bates-numbered, SHA-256 manifest attached, FRE 902(14) certification template.

That first version worked. It grouped messages he had scrolled past for months. His attorney stopped asking for screenshots and started asking for the PDF. Other parents heard about it. Attorneys heard about it. And what started as one father’s weekend project turned into a patent-pending clustering method and a company.

CustodyComms keeps that original bargain: the person living through this owns the data, does the work on their own machine, and decides what ships to their lawyer. Nothing touches our servers unless you ask it to. And when it does, you stay in control of what and when.

What we build around

Three pillars. See the pattern in every release.

These aren’t marketing values. They’re the roadmap filter. Every feature has to pass all three or it doesn’t ship.

I
Your time, not ours

Efficiency

A parent shouldn't lose another weekend scrolling. An attorney shouldn't bill $15,000 to organize someone's texts. The app does the tedious part: importing, deduping, indexing, categorizing. The people involved focus on the decisions only they can make.

Per source
Minutes, not days
Categories
18, auto-tagged
Output
1 packaged export
II
Checkable by default

Legal Excellence

Most messaging exports are a folder of screenshots with no way to prove nothing changed. CustodyComms ships chain of custody from the first import: SHA-256 per file, an FRE 902(14) certification template, and a chain of custody declaration. The steps most tools skip.

Integrity
SHA-256 per file
Certification
FRE 902(14) template
Custody
Chain of custody declaration
III
On your machine by default.

Privacy First

Analysis runs locally. Source messages never leave your computer unless you turn on Cloud AI for a deeper writeup, and we tell you exactly what gets sent before it leaves. Your archive is yours, on your computer, where we cannot read it. Share a case and it travels encrypted. We hold no key to a case shared from version 2.0 or later; for a case shared from an earlier version, and for a report you send to your phone from this site, we do, and the Privacy Policy says so.

Runtime
Local-first, desktop
Shared cases
Encrypted on your device
Cloud AI
Off until you turn it on
Engineering bar

Enterprise-grade stack. Built for one family at a time.

Deterministic pipelines, cryptographic integrity, least-privilege architecture, applied to the most personal archive a person will ever hand a lawyer.

Runtime
Desktop, not SaaSLocal-first
Integrity
Per file + recordSHA-256
Behavior
Same in, same outDeterministic
Method
Incident groupingPatent-pending
Our four commitments

What you get from us every single release.

Four things we don’t get to quietly drop when a roadmap gets tight. Call us on any of them.

  1. I

    Responsive to feedback

    Product direction is shaped by the cases actually happening, not focus groups.

  2. II

    Continuous improvement

    The keyword lists and export format are refined release after release, from user feedback. We ship changes, not slideware.

  3. III

    Transparent pricing

    One public pricing page. A free tier that's genuinely useful, not a trial. No surprise overage fees and no upsell in the middle of a case. One price covers you; firms that need more seats ask for them.

  4. IV

    Privacy always

    Your archive stays on your machine. If we ever need to change what leaves your computer, it will be opt-in, explained in plain English, and reversible. Not a quiet update to a terms-of-service doc.

If we break one of these, tell us.Write to us
The invitation

Let the record speak.

Install it. Bring your own messages. See what the tool finds in the first five minutes on your own machine. If it earns a place in your case, it’s earned ours.