Terms of Service

1. BRON is software, not a law firm

BRON is a litigation-management platform. It is not a law firm, it does not practice law, and it does not provide legal advice. Using this website, a product walkthrough, an intake form, or the hosted application does not create an attorney-client relationship with BRON, and no communication with BRON is privileged by reason of these terms.

Nothing the software produces is legal advice to anyone. Output is material prepared for a lawyer to review, and it becomes work product of the firm when that lawyer adopts it.

2. The firm is responsible for the legal work

This division of responsibility is the foundation of the entire agreement, and a firm should be satisfied it can live with it before signing.

The firm, through its licensed lawyers, is solely responsible for legal judgment. That includes deciding what to file and when, calculating and meeting every deadline, verifying every authority cited, deciding what to send and to whom, supervising everyone who works on a matter, deciding what a client is told, deciding whether and when a proceeding may lawfully be captured, and handling client funds in accordance with the rules that govern them.

BRON supplies tools that assist those judgments and records what was done. It does not make them, and it is not a substitute for a competent lawyer. In particular, a date that the software calculates, a citation it reports as verified, a conflict it does not flag, and a document it prepares are all inputs to a lawyer's decision, never the decision.

3. Who may use the service

Accounts are for people authorized by a firm, and for clients a firm invites to its portal. You must be old enough to enter a contract, must give correct registration information, and must keep credentials and recovery methods secure. Use only an account and a matter you are authorized to access. You are responsible for what happens under your credentials, including any API key you mint and any device you pair.

A firm administrator controls who at the firm may use the service, what role each person holds, which integrations are connected, which of the firm's own systems hold a credential to read the record, and what is shared with a client. Those choices are the firm's to make and its responsibility to police.

4. Prohibited conduct

The controls listed here exist because this software holds privileged material and records of regulated conduct. Interfering with them is a material breach, whatever the motive.

• Do not attempt to bypass, disable, forge, or work around access controls, role restrictions, ethical walls, client-visibility screens, confirmation gates, the citation gate, litigation holds, the on-the-record gate on deposition capture, or any audit or record-keeping mechanism.
• Do not attempt to reach another firm's data, another client's matter, or material screened from you within your own firm.
• Do not probe, scan, or test the security of the service except under a written authorization from BRON, and do not use it to store or distribute malicious code.
• Do not upload material you have no right to process, and do not use the service to break the law or a court order.
• Do not use the service to give legal advice to the public, to hold yourself out as a lawyer if you are not one, or otherwise in a way that would constitute the unauthorized practice of law.
• Do not attempt to induce the assistant, through instructions hidden in an uploaded document or otherwise, to take an action the person operating it has not approved.
• Do not scrape the service, resell access, or use it to build a competing product.

5. Generated material and the attorney-in-the-loop controls

Summaries, drafts, research, analysis, valuations, and suggested dates can be wrong, out of date, or missing something. A licensed lawyer must review anything consequential before it is used, sent, filed, signed, or relied on. The controls below support that review. They do not perform it, and none of them is a warranty about the result.

• Confirmation gate. Actions that send, sign, file, bill, move a matter forward, or delete something refuse to run until a person approves them. Approval uses a single-use token minted by the server and bound to the exact action, matter, user, and arguments. The token is routed to the screen and never back into the model, so the assistant can neither read nor forge it, and an instruction planted inside an uploaded document cannot satisfy the gate on a human's behalf.
• Citation gate. A document with unverified case authority cannot be prepared for signature unless a person deliberately overrides, and the override is recorded. The gate is built to fail toward blocking when a check cannot run. The same gate runs inside the Word, Outlook, Google Docs and Gmail panels against the same server code, so those surfaces cannot return a softer answer about the same draft.
• Deadlines are suggestions until a lawyer confirms them. The software proposes a date from a cited rule and a trigger event, and raises it as a task. It does not write a deadline into the calendar on its own, because a date invented without a real trigger is a malpractice risk rather than a convenience. Confirming a deadline is the lawyer's act, and so is meeting it.
• Litigation holds. Material under an active hold is refused for deletion and for edits that would alter it, on every path that could change it.
• Valuation is a range, not a measurement. Where the software estimates the value of a matter, it is a modelled range with an explicit interval around it, and it is an estimate. It is not a prediction of what a court will do and must not be presented to a client as one.
• Bar-license gate, stated plainly. Before a member is given the attorney role, the firm records that the person's bar credentials are verified. That is the firm attesting, not BRON verifying. BRON does not check a bar registry, and a firm owner account is treated as licensed without that attestation. Confirming that a person is admitted and in good standing remains the firm's duty.

6. Deposition capture on glasses

A firm can run a deposition with a heads-up display on glasses its attorneys wear. Because this captures other people speaking, the allocation of responsibility is stricter than anywhere else in these terms.

• The hardware is the firm's own. Glasses are not supplied with the service, and nothing is captured without a device the firm paired into the session.
• Whether a room may lawfully be captured is the firm's decision, not BRON's. Recording and consent rules differ by jurisdiction and by forum, and a court or a reporter may impose its own. Nothing in the software can know the law of the room, so it does not try to. The attorney decides, and the decision is recorded against them.
• Capture is gated on the record, by the server. With the session off the record the audio path refuses and transcribes nothing; on the record the voice-command path refuses instead. Going on and off the record is written to the audit trail with the person who did it.
• A transcript from a room microphone is not a certified transcript. It carries no page and line, because only a licensed stenographic feed does, and the software will not attach one it could not derive. The certified record remains the reporter's.
• Transcription uses an outside vendor today. Audio is sent to a hosted transcription vendor named on the sub-processors page, and the privacy policy sets out that path in full. A firm unwilling to send privileged testimony to a hosted vendor should attach a stenographic feed instead of using the microphone.
• One of the two runtimes is beta. The Even G2 path is the shipped one. The MentraOS path is in beta and is not cleared for use in a client deposition. Beta means what it says here: it is offered for evaluation, without the availability or fitness expectations that attach to the rest of the service.
• Silence is not a clean bill. The display shows nothing unless a detector has earned its place on this firm's own reviewed results, so an early session runs with most of them held back. Nothing appearing on the lens means the system had nothing it was confident enough to say, never that the record holds nothing.

7. The firm's own systems and agents

A firm may connect its own software, including its own AI assistant, to the record through an API key or the agent interface. The terms of that access are part of this agreement.

• A key is a firm credential and its class is set when it is minted. An attorney-class key acts as its owner and reaches the attorney-grade record; minting one requires a firm administrator. A client-safe key is forced onto the privilege-gated client view. An administrator can enumerate and revoke every key held by anyone at the firm.
• A key reaches only what its owner reaches. Scopes, an optional per-matter allow-list, and the owner's own matter set, less ethical-wall screens, all apply. Supplying a matter identifier a key does not reach is refused, not served.
• An outside agent may propose; it may not act. A proposal lands in the same approval inbox a person already uses and executes nothing. It is capped at the lowest rung of the trust ladder regardless of any setting, and an attempt to include a confirmation token, a matter identifier, or an override flag is stripped and disclosed rather than honoured. Execution happens only when a person approves, and the whole gate stack runs again at that point.
• You are responsible for what your credential does. Keep it secret, revoke it when a system or a person no longer needs it, and do not embed it in anything you distribute. Usage is metered per key and visible to a firm administrator.
• Do not use the interface to replicate the record elsewhere. Reading a firm's own matters through its own credential is the intended use. Bulk extraction to build a competing product is prohibited under section 4 whether it happens through a browser or a key.

8. Electronic signatures

Signing is performed by BRON rather than by an outside signature vendor. Before signing, a signer must affirmatively consent to do business electronically. The server requires that consent rather than merely displaying it, the disclosure covers the legal effect, the hardware and software needed, the right to a free paper copy, and how to withdraw, and the exact disclosure the signer accepted is stored word for word on their own record. A signer may obtain their executed copy, ask for a paper copy, and withdraw consent, which permanently disables their signing link.

These features are designed to support enforceability under the federal ESIGN Act and state enactments of UETA. Whether a particular signature is legally effective for a particular document in a particular jurisdiction is a legal question for the firm, not a promise by BRON. Some instruments are excluded from those statutes or carry their own execution formalities, and some courts require more.

What a sealed record is. When signing finishes, the executed document is stored as a new version, and a SHA-256 fingerprint of its exact bytes is recorded and submitted to a public timestamping service that anchors it in the Bitcoin blockchain. That provides tamper-evidence, because re-hashing an altered file will not match, and independent evidence that the file existed at a date. Anyone can verify a document against its fingerprint without an account.

What a sealed record is not. It is not proof of who signed. The signing link is a secret address sent to the signer's email, and BRON does not separately verify identity with a one-time code, a knowledge test, or an identity document; a person holding the link can sign. It is not a smart contract, nothing self-executes, and no money or cryptocurrency moves. It is not a notarization and does not satisfy a requirement for a notary, a witness, or a wet signature. A firm needing identity assurance or a notarial act should use a process that provides it.

9. Trust accounting and client funds

BRON does not take custody of client funds and does not move money out of a trust account. The firm holds client money at its own bank under the rules that govern client property, including ABA Model Rule 1.15 and its state equivalents.

What the software does is keep the record. It maintains a per-matter trust ledger separate from operating funds, supports three-way reconciliation against the bank statement, refuses a disbursement entry that would overdraw a client's balance, and treats posted entries as immutable, which the database itself enforces, so a correction is an adjusting entry rather than an edit. When a firm records a disbursement it records a reference for a payment the firm itself made. The instruction to the bank is the firm's act.

One exception is worth naming plainly: if a firm connects a payment processor, the service can initiate inbound card payments from a client, and can read connected bank transactions for reconciliation. That is money coming in through a processor named on the sub-processors page, not BRON moving money out.

Reconciling, safeguarding, and reporting on client funds remain the firm's responsibility. The software does not discharge a lawyer's duty under Rule 1.15.

10. Devices, extensions, and document add-ins

The service includes a native iOS application with a share extension and home-screen widgets, and panels for Word, Outlook, Google Docs, and Gmail. Using them is using the service, and these terms apply.

Two responsibilities sit with the person holding the device. Keep a device that holds privileged material under a device passcode, and use the application lock, which is on by default for firm staff. Tell your firm promptly if a device is lost, so the firm can revoke the session, and understand that signing out is what clears what the widgets can show. The add-ins send the text of the document or message you have open to BRON in order to run the checks you asked for; do not open a panel on a document you are not entitled to send to the service. What each surface holds and transmits is described in the privacy policy.

These surfaces are distributed through stores and marketplaces operated by others, and their own terms apply to the distribution. BRON is not responsible for a platform's policies, and a platform may withdraw or change what it allows.

11. Product walkthrough material

A product walkthrough arranged with BRON uses fictional, isolated material. It cannot access a firm or client record, and simulated actions do not file, send, sign, notify, upload, download, export, or move funds. A walkthrough is not legal advice, not a record of a real matter, and not a promise that any particular feature will be available in a given configuration. Do not put confidential, privileged, or personal information into it.

12. Intake creates no engagement

Sending an intake request does not mean a law firm has accepted a matter, and it creates no attorney-client relationship with BRON. Creating an account, receiving an invitation, or gaining access to a portal does not expand the scope of a firm's engagement. The firm decides whether to accept a matter and on what terms.

Do not send time-sensitive information through an intake form and assume it has been received and acted on. Until a firm confirms an engagement, no one is acting on your behalf and no deadline is being watched for you.

13. The firm owns its record

As between the firm and BRON, the firm owns its own records: its matters, documents, communications, ledgers, transcripts, and work product. BRON claims no ownership of them. BRON receives only the limited permission needed to host, process, back up, secure, and display that material in order to provide the service, and to act on the firm's instructions.

BRON does not use a firm's client data to train models. Regarding model vendors, see the AI section of the privacy policy, which states exactly which half of that posture the software enforces and which half rests on a contract.

BRON owns the software, the interface, the design system, and its documentation, and nothing here transfers those rights. The offline verification tool BRON publishes is separately licensed for anyone to use, including a party adverse to the firm, which is the point of it. If you send feedback or suggestions, BRON may use them to improve the product without owing you compensation or an obligation to adopt them. Feedback should not contain client confidential information.

14. Confidentiality

BRON treats firm and client material as confidential, discloses it only to the sub-processors needed to operate the features the firm enabled, and requires those providers to be bound to their stated purpose. BRON does not sell it. If BRON is compelled by law to disclose firm material, it will give the firm notice unless legally prohibited, so the firm can seek protection, since the privilege at stake belongs to the firm and its client rather than to BRON.

15. Third-party services

Many features depend on services chosen or connected by the firm, including model vendors, transcription vendors, courts and e-filing gateways, docket and research sources, identity providers, mail systems, payment processors, and practice-management systems. Those services are operated by others, can be unavailable, can change, and can return partial or wrong information. BRON is not responsible for them, and a firm's use of each is governed by that provider's own terms. The current list is on the sub-processors page.

16. Availability and disclaimer of warranties

BRON works to keep the service available and to surface a degraded or unavailable lane rather than silently returning a worse answer. No uptime level is promised on this page. Any availability commitment lives in a signed services agreement. A feature marked beta carries no availability expectation at all.

To the fullest extent the law allows, the service is provided as is and as available, and BRON disclaims all warranties, whether express, implied, or statutory, including merchantability, fitness for a particular purpose, title, non-infringement, correctness, and any warranty arising from a course of dealing. BRON does not warrant that the service will be uninterrupted or error free, that a result will be right or exhaustive, that an authority reported as verified is still valid or controlling, that a calculated date is correct, that a transcript from a microphone matches what was said, or that a conflict or a deadline will be detected.

17. Limitation of liability

Stated plainly, because a clause this important should be readable.

BRON is not liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or for lost profits, lost business, lost data, or reputational harm, even if it was told such harm was possible. BRON's total liability arising out of or relating to the service is capped at the amount the firm paid BRON for the service in the twelve months before the event giving rise to the claim.

In particular, and given what this software is used for: BRON is not liable for a missed deadline, a barred claim, a sanction, an adverse ruling, a filing that was rejected or never made, a document sent to the wrong person, a citation that turned out to be bad, a recording made where the law of the room did not permit it, a disclosure of privileged material caused by how a firm configured access or a credential it issued, or a malpractice claim. Those risks sit with the firm, which is why sections 2, 5, 6 and 7 are written the way they are.

Some jurisdictions do not allow some of these exclusions, so parts may not apply to you. Nothing here limits liability for fraud, willful misconduct, or anything else that cannot be limited by law. A signed services agreement may set different terms, and if it does, it controls.

18. Indemnity

The firm will defend and indemnify BRON against third-party claims arising from the firm's use of the service, including claims about the firm's legal services, its handling of client funds and client material, its configuration of access and client visibility, its decision to capture a proceeding, content it uploaded or sent, credentials it issued, and its breach of these terms or of law. BRON will notify the firm of a claim promptly and cooperate in its defense, and the firm will not settle in a way that imposes an obligation or an admission on BRON without consent.

19. Suspension, termination, and getting your data out

A firm may stop using the service at any time. BRON may suspend an account for non-payment, for a breach of section 4, or where continued operation poses a security or legal risk, and will limit a suspension to what the circumstances require. Because this software holds records a lawyer needs in order to meet duties to clients and to courts, BRON will not use suspension to withhold a firm's ability to retrieve its own records, absent a legal requirement to do so.

Export is self-service and available at any time, without asking BRON. A firm can export a single matter or its entire record. The archive contains the document files, the matter data in a documented interchange format, the audit trail, and a manifest of fingerprints with an independent timestamp proof.

The export can be checked without BRON, and that is deliberate. The verification tool is published separately, is openly licensed, has no runtime dependencies, and runs offline on a reader's own machine with no account and nothing from the firm that produced the file. It re-derives each verdict rather than trusting a stored one, and the single optional network call sends a 64-character digest and only when the reader presses the button. A successor system, a court, an auditor, or an adverse party can therefore check that nothing changed in transit without BRON's participation and without BRON's permission.

A firm should export before terminating. After termination, BRON will make the firm's data available for a reasonable retrieval period and then delete or de-identify it, except where records must be retained by law, and except for the append-only trust and audit records and any fingerprint already anchored publicly, which are described in the privacy policy and exist precisely so they cannot be quietly removed.

The exact retrieval and deletion timelines for a firm are set in its signed services agreement. If the agreement is silent, contact contact@bronlaw.com before termination so the retrieval plan can be confirmed in writing.

20. Governing law and disputes

The governing law, venue, and dispute process for a firm are set by its signed services agreement. If no signed agreement applies, mandatory law governs and neither party is given a contractual arbitration or class-action waiver by this page.

Until that is settled, nothing on this page waives any right either party has, and any dispute is governed by the law that would otherwise apply and by any signed services agreement between the parties.

21. Changes to these terms

These terms are updated as the product and the law change, and the date at the top reflects the most recent revision. For a material change that reduces a firm's rights, BRON will give notice through the service or to the firm's administrator before it takes effect, and continued use after that date is acceptance. A firm that does not accept a material change may terminate and export under section 19.

Questions about a proposed change can be sent to contact@bronlaw.com. A signed services agreement controls if it sets a different notice period or channel.

22. Which document controls

Where a signed services agreement between a firm and BRON differs from this page, the signed agreement controls. This page is the baseline for anyone using the website, a product walkthrough, an intake form, or a portal without such an agreement. If a provision here is unenforceable, the rest stands. A failure to enforce a provision is not a waiver of it.

23. Contact

Signed-in users can reach the team through Support. Prospective firms can register interest for a product walkthrough or use Request a consultation.

For questions about these terms or formal notice routing, email contact@bronlaw.com. The contracting legal entity and formal notice address are stated in the firm's signed services agreement.

These terms should be reviewed by qualified counsel for the jurisdictions in which a firm operates.