Sub-processors

How to read this page

Under the privacy policy, the firm is the controller of its client data and BRON is a processor acting on the firm's instructions. The providers below are sub-processors: they process data on BRON's behalf so a feature can work.

The right-hand column is the one that matters most. Always on means the provider receives data on any working install. On by default means it is used unless an operator changes a setting. Firm-enabled means nothing reaches that provider until the firm supplies a credential or connects an account, and most firms will never enable most of them.

This list is derived from the code that makes each call. It is maintained as features change, and it does not describe a specific firm's configuration. To find out which of these are active for your firm, ask your firm administrator, who controls the integration settings.

Core infrastructure

Documents are held in a private bucket and served through signed links that expire. The key that can read the database is held on the server only and is never sent to a browser.

[OWNER: name the hosting region for the Supabase project and the host the application server runs on, and state whether backups stay in that region. The repository does not record either, so residency cannot be stated here without you.]

AI model providers

These receive the content a feature needs to do its work. For drafting, analysis, and the assistant, that includes document text and matter facts, which for a law firm means privileged material and client confidential information. Read the AI section of the privacy policy before enabling anything here.

Two things a general counsel should know before signing. First, search and transcription mean OpenAI is not optional in a default install: text you upload is sent there to be indexed, even if every model you talk to is Anthropic. Second, if the primary provider fails or hits a quota, a request can be retried automatically on a different provider from this table. A firm that needs work confined to one vendor should raise that before deployment.

Transcription is the sharpest edge here, and the code says so in its own comments: deposition audio and dictation are privileged speech, and they go to OpenAI today. A self-hosted transcriber is named in the source as the intended replacement and is not built.

Email, messaging, and notifications

Payments, billing, and trust accounting

BRON records and reconciles trust activity. It does not move client money on its own. See the terms for what that division of responsibility means.

Courts, dockets, and legal research

Party and entity screening

Two of these are contacted without any key, so they are active on a default install. They receive the names of the parties and companies in a matter.

Filing and service of process

Practice-management systems

These connect a firm's existing case-management system. Each one exchanges credentials and syncs records in both directions.

Document timestamping

Runs inside the deployment, not sent to a third party

These are worth naming because they are often assumed to be outside services. In BRON they are not, so the data they handle stays in the deployment.

• Electronic signature. Signing is built in house. There is no e-signature vendor. A previous third-party signing service was decommissioned and no code path reaches it.
• Text recognition of scanned documents. Runs in the application process. Scanned pages are not sent to an outside recognition service.
• Text analysis and re-ranking. Runs as a companion service reachable only on the local machine. An operator can point it at a remote host, which requires deliberately setting two separate values.
• Malware scanning. When enabled, it runs inside the deployment rather than at a cloud scanning vendor, so document bytes are not transmitted for scanning. See the security section of the privacy policy for its default state, which is off.

Not used

• No analytics or tracking vendors. There is no analytics package, product-telemetry service, session recording, heatmap, advertising pixel, or tag manager anywhere in the application.
• No third-party error-tracking service.Errors are held briefly in the browser's memory and leave the device only when a signed-in person submits a support report, which shows them what it contains.
• No external fonts or content delivery networksfor the interface. Fonts are served from the application's own address.

Three scripts do load from another company, each only on the screen that needs it: the payment fields on the client retainer screen, the bank-linking dialog used for trust reconciliation, and the Microsoft library required by the Word and Outlook add-ins. Each corresponds to a provider listed above.

Changes to this list

A firm that has a signed services agreement should look to that agreement for any notice commitment about new sub-processors. This public page is updated as the product changes and is not itself a notice mechanism.

[OWNER: if you intend to offer advance notice of new sub-processors, or a data processing agreement, state the commitment and the notice period here. The repository records neither, so nothing is promised above.]

Questions

Signed-in users can ask through Support. Prospective firms can use Request a consultation. A client of a law firm should direct questions about how their own matter is handled to their firm, which decides which of these providers it enables.