Security & Privacy

JurisFolio is the processor of the practice book. The advocate is the data fiduciary for the client's file. This page describes the product. It is not a DPDP certification.

On the wire and at rest

Flutter talks to the API over HTTPS. The API talks to Postgres with TLS hostname verification to pg18.tailce422e.ts.net.

PII uses an application envelope: AES-256-GCM, one data key per practice, wrapped by a JurisFolio key-encryption key that is not RxFolio's key. Account email, display name, captions, party names, client contact fields, notes, fee amounts, and fee notes are ciphertext. CNR, case number, court codes, and dates stay queryable and access-controlled. Fee amounts and notes are not sent to the model.

Case documents

PDFs are ordinary files in the practice owner's Google Drive or OneDrive. They are readable without the app. JurisFolio does not keep those bytes on the API LXC.

Court passwords

After save, a court password is write-only. The profile holds bar enrolment and court complexes. Fetch case details and today's cause list use that enrolment and those complexes, plus the captcha you type. The password is never shown again, it is not logged, and it is not sent on those calls. Captcha answers are not stored.

Roles

A role is the persona and the security profile. Hidden sections are absent from the payload. A clerk, client, or expert does not get AI Assist. A client sees Today and Matters only, and does not see Fees. A clerk can open Team to record a receipt, and does not see the audit trail. A 48-hour read link has no AI Assist, does not show the fee, and is not a team seat.

What we do not collect

JurisFolio does not train a model on customer files. See Privacy Policy and Professional disclaimer.