Trust & security: how ExhibitPrep handles your files, payments and output

Our on-device privacy statements describe ExhibitPrep’s own document-processing service, provided on a best-effort basis. They are not a guarantee of the privacy or security of your entire device. Browsers, extensions, operating systems, cloud-sync or backup services, malware, and other software may independently access, store, or transmit information. ExhibitPrep does not control their behavior.

Medical records and HIPAA-sensitive exhibits are processed locally; firms remain responsible for HIPAA safeguards, vendor classification, and any required agreements.

Closing the tab clears working memory. Completed recovery copies are generally removed from this browser 30 days after creation; unfinished deliveries and active revision windows can remain longer so paid access is not lost. You can delete them from Recent Jobs.

A purchase is delivered as a license key, emailed with the receipt and kept in this browser. Google sign-in is optional: it fills in forms and helps recover a purchase, and it is not required to buy or download.

Closing the tab clears working memory. Completed recovery copies are generally removed from this browser 30 days after creation; unfinished deliveries and active revision windows can remain longer so paid access is not lost. You can delete them from Recent Jobs.

1. At checkout, read the address bar: the payment page is served by Stripe, and the receipt comes from Stripe.
2. Your license key is in the receipt email and on the billing page; recovery re-sends it to the purchase address without any document data.
3. In the network inspector, the licensing requests carry a key and counts — open one and read its payload.

Operational error reports use controlled error categories, application versions, counts, and static code locations. Document names, labels, contents, and credential links are excluded.

There is no document account: a purchase does not upload, store, or index your exhibits anywhere. Account, payment, and service records are separate from your documents and may be retained; see the Privacy Policy for the formal terms.

Contact us to discuss licensing, invoicing, and implementation requirements. Team administration, single sign-on, customer audit logs, and custom integrations are not included in self-service plans; any additional service requires a written scope before purchase.

Verification record. Every delivered file is hashed with SHA-256 in the browser, read incrementally so even a large ZIP is never copied twice. The verification record (a small .jsonfile you can save with the download) lists the file name, its size in bytes, that hash, the number of documents and the download type, with a notice that it identifies the downloaded bytes and nothing more.

Preparation record. The record of a prepared set lists which settings were applied, which documents were included, and what the reviewer confirmed. The confirmations are self-reported; the record asks the reviewer about each of these:

• The correct source documents and complete pages are included.
• Exhibit labels, descriptions, order, and references in my other documents agree.
• I inspected the pages for readable stamps and obscured content.
• I checked applicable filing instructions, confidentiality, and any case-specific order.

Metadata removal. Before a stamped PDF is saved, the authoring metadata of the source — author, company, matter number, "last modified by" — and the XMP metadata packet are removed, so an input file's drafting history does not ship in the output to opposing counsel.

1. Save the verification record next to the download. Compute the file's SHA-256 yourself — shasum -a 256 file.pdf on macOS, certutil -hashfile file.pdf SHA256 on Windows — and compare it with the hash in the record.
2. Open the stamped PDF's document properties in any viewer: the author and creator fields name ExhibitPrep, not the drafting attorney or firm.
3. Keep the record with the matter file; a later re-check only means something if the record was kept.

Or let the browser do the arithmetic: check a prepared file against its record — the file is read in the page, not uploaded, exactly as the stamping is.

ExhibitPrep records how a file was prepared and lets you confirm later that a file is byte-for-byte the one it produced. It does not authenticate the underlying document, prove who created it, or establish that it is what it purports to be — that remains the proponent’s burden under the applicable evidence rules. It is not an electronic signature, not a timestamp from any authority (times come from the preparing device’s own clock), and not a certification by ExhibitPrep. A matching hash shows the file has not changed since the record was made; it cannot show that the record itself was kept safely, so keep the record with the matter file.