Trust

Data handling summary

A one-page summary you can hand to your bar. It describes only what is built and running today.

Last reviewed: September 5, 2026.

Where your data lives

Intake data is stored in a managed PostgreSQL database on cloud infrastructure. It is encrypted in transit (TLS) and at rest by the hosting provider, which also manages backups.

One firm, one silo

Every table holding firm data carries a firm ID, and row-level security is enabled on every table. A signed-in user can only read or write rows for a firm they belong to, and the database enforces it — not application code.

The public intake form

The form never writes to the database directly. Submissions post to a server endpoint that validates every field and applies a rate limit of five submissions per hour per visitor and per form before writing anything. The rate-limit counter stores only a one-way keyed hash of the visitor's network address and the hour, never the address itself, and counters are deleted after about two days.

Secrets

Privileged credentials exist only in the server environment and are never present in the code running in a visitor's browser. This was verified by building the production bundle and searching it for those values.

No AI

Lead data is not sent to any AI model and is not used to train one. There is no AI feature in the product, and the text-back assistant follows a fixed script.

Payments

Card details are never sent to, stored by, or visible to FirmReply. Checkout and payment management happen on the payment provider's own hosted pages. We keep only your subscription status, renewal date and the provider's customer reference.

Access and deletion

There is no self-service delete button today. A firm can ask us to delete its leads, which also removes their timeline entries and notification records. Firm membership is managed by the firm owner.

What we store per lead

  • Name, phone number, email address
  • Matter type, chosen from the practice areas the firm configured
  • The prospect's brief description of their situation, in their own words
  • How they heard about the firm
  • Source, status, follow-up date and timestamps
  • An append-only activity timeline (created, viewed, status changed, note added) that users cannot edit or delete
  • A log of notification emails attempted, with the true outcome of each

Separately, to count how often each form is opened, we keep one aggregate number per form per day, with no visitor identity attached. Repeat opens are filtered using the same short-lived keyed hash as the rate limit. There is no tracking pixel, no third-party analytics on the intake form, and no advertising integration.

Isolation, verified

Tested on September 5, 2026 with two separate test firms: a user of Firm A reading Firm B's leads and timeline entries — both through the application and through a direct database API call using that user's own session token — returned zero rows in every case. An unauthenticated request returned no lead data at all.

Disclosure on every intake form

Submitting this form does not create an attorney-client relationship. Do not include confidential details.

Firms may edit this text; the above is the default shown above the submit button.

Reporting a concern

Contact your firm's FirmReply administrator, or reach us through the contact page.

Contact us