This is the package built for formal review. Messages rendered as the bubbles people actually sent. Emails preserved with the headers a forensic examiner reads. Attachments imaged page-by-page so a court order looks like a court order, not a thumbnail. A SHA-256 manifest, a chain-of-custody log, and an FRE 902(14) certification template, structured so a qualified person can sign and the package supports self-authentication when signed.
Quick for first-meeting discussions. Family Law Standard for the working file. Forensic for contested matters.
Every option above is toggle-able in Advanced mode inside the desktop app.
iMessage, SMS, Android, WhatsApp, and Messenger render as the bubbles people sent. Color-coded per participant, group threads with a five-color palette, timestamps preserved per message, and a B&W-print-safe variant for the printed binder. No screenshotting, no cropping.
Gmail mbox exports render with the From, To, Subject, and Date block intact and the RFC 5322 raw headers preserved at the page footer. Threaded replies indent under their parent so a fourteen-message exchange reads like an exchange, not a wall of text.
AppClose, coParenter, and OurFamilyWizard PDFs are parsed and re-rendered as text rows in the host document, preserving the original "viewed by" timestamps. The source PDF, including any AppClose watermark baked into it, is preserved unchanged in the rasterized appendix. Every row carries its source filename above.
Bubbles, AppClose rows, and email blocks interleave in chronological order on a single page. A SOURCE: divider stamps the originating file above every segment, making the chain of custody visible in the rendering itself. One exhibit binds iMessage, AppClose, and Gmail into a single readable record.
iMessage, SMS, Android, WhatsApp, and Messenger render as the bubbles people sent. Color-coded per participant, group threads with a five-color palette, timestamps preserved per message, and a B&W-print-safe variant for the printed binder. No screenshotting, no cropping.
Gmail mbox exports render with the From, To, Subject, and Date block intact and the RFC 5322 raw headers preserved at the page footer. Threaded replies indent under their parent so a fourteen-message exchange reads like an exchange, not a wall of text.
Sharing the updated itinerary for the week of April 14. Flights are confirmed both ways and the rental car is booked under my name.
Let me know if you want me to forward the airline confirmation. I can call them to add you on the reservation if helpful.
Thanks. Forwarding the airline confirmation works. I will save it with the school calendar attachments.
AppClose, coParenter, and OurFamilyWizard PDFs are parsed and re-rendered as text rows in the host document, preserving the original "viewed by" timestamps. The source PDF, including any AppClose watermark baked into it, is preserved unchanged in the rasterized appendix. Every row carries its source filename above.
Bubbles, AppClose rows, and email blocks interleave in chronological order on a single page. A SOURCE: divider stamps the originating file above every segment, making the chain of custody visible in the rendering itself. One exhibit binds iMessage, AppClose, and Gmail into a single readable record.
Owen has his annual checkup Thursday at 3:30pm with Dr. Martinez. Can you take him? I have parent-teacher conferences that afternoon.
Group several Initial Exports into a single packet with sequential exhibit labels and a unified Bates range. The combined cover keeps each source's chain of custody intact.
Every source is verified against its original SHA-256 the moment you click export. If any byte changed since import, the export halts and tells you which file diverged.
The export ships a per-source registry: SHA-256 of the source file, plugin that parsed it, exported count out of total, and the chronological range with gap count. A forensic examiner can reproduce the audit without opening the source files.
| Source | SHA-256 | Range | Exported |
|---|---|---|---|
demo_messages.csv plugin: demo | 22b641fd9e00… | #88 to #4400 49 gaps | 50 / 112,288 |
appclose_demo_paige_evan.pdf plugin: appclose | bb250eaeae23… | #65 to #3250 49 gaps | 50 / 3,965 |
custodycomms_demo_harper_emails.mbox plugin: mbox | 747eb8b935b9… | #88 to #4400 49 gaps | 50 / 7,392 |
A custom prefix and a starting number, applied to every page of every section. Cite by Bates number, not by platform.
Boilerplate certification block ready for a qualified person to complete. Supports self-authentication when signed by a qualified person.
I, the undersigned qualified person, certify that the data copied from an electronic device, storage medium, or file referenced in the accompanying manifest was authenticated by a process of digital identification…
The export is generated on your machine. The bundle never leaves your device unless you send it. You decide who sees it.
CustodyComms provides formatting and documentation tools. Authentication and presentation decisions remain with the attorney of record. Admissibility determinations are made by the presiding court under applicable rules of evidence. Evidentiary rules vary by jurisdiction. Consult your local court rules.
CustodyComms is a software tool for organizing digital communications. It is not a law firm, does not provide legal advice, and does not guarantee evidentiary admissibility. Consult a qualified attorney for legal guidance specific to your matter.
