[View this page on Briefcase](https://nextbriefcase.com/security) Trust, security, and privacy # Privacy at every step. Lawyers and institutions have always had a confidential system for their legal thinking. Briefcase builds it for everyone else: a private place to work on the most sensitive matters in your life, kept private by how it is built. If a court orders Briefcase to produce my conversation: Nothing exists to produce. Your conversations with Briefcase leave no transcript. Not a copy, not a summary, not a topic. What remains is that a conversation happened, when, with which model, and what it cost. Kept: that it happened · when · which model · what it cost my sealed matter: Ciphertext, which no one at Briefcase can read. Sealed under a key only you hold: not support, not an engineer, not our AI. We cannot hand over what we cannot read. Key: on your device, never with Briefcase my record: The record you approved, and only under valid process. The matter you saved, the messages you chose to send, and the metadata it takes to run the service. A demand is narrowed, only what the law compels is disclosed, and you are notified when the law permits. Produced: only under valid process · narrowed · with notice when the law permits ## What Briefcase never kept, it cannot hand over. What you sealed, no one at Briefcase can read. Briefcase keeps the record you approve and the metadata it takes to run the service. Nothing else exists to produce. Every question a person is right to ask before trusting software with their legal life has an answer here. 1. Could what I say to Briefcase be used against me later? Your conversations with Briefcase leave no transcript. Not a copy, not a summary, not a topic. Briefcase keeps that a conversation happened, when, with which model, and what it cost. Save an answer and it joins your matter, by your hand, and only then. 2. Can a court order Briefcase to hand over my matter? What Briefcase never kept, it cannot hand over. What can be produced is bounded by what Briefcase retains and can read: the record you approve, the messages you choose to send, and the metadata it takes to run the service. A demand must be valid legal process. Briefcase narrows it, discloses only what the law compels, and notifies you when the law permits. 3. Can someone at Briefcase read my documents? No one at Briefcase has standing access. Nobody at all can read a sealed matter. Matter content is reachable only by one dedicated processing identity. Support sees metadata. Any human exception is break-glass, justified, time-boxed, and audited. Seal a matter and it is encrypted under a key only you hold, not support, not an engineer, not our AI. Ask Briefcase to work on it and your key goes only to a verified, sealed workload that keeps nothing when the run ends. You decide what is sealed, and when it opens. 4. Is my legal life training an AI? Your matters train no model, ours or a provider's. Private legal content routes only to models eligible for zero retention by contract, inside one managed model plane under Briefcase's enterprise account. The model provider cannot reach the deployment, its logs, its prompts, or its completions. 5. Who else can see what I put in? The people you grant, and no one else. Sharing is by grant, never by link, and you can grant only what you hold. No advertiser, no data broker, no analytics vendor, and no model provider training a model. 6. What if I want it gone? Export is complete and deletion is real. You can take the record out in usable form and delete it, and the deletion propagates to every derived system, so no copy is stranded. Where a matter is sealed, deleting the key is the deletion. 7. Is what I put in Briefcase privileged? Protection comes from the law and the circumstances, and Briefcase preserves the facts it depends on. Using Briefcase creates no privilege by itself. Materials a self-represented person prepares in anticipation of litigation may qualify for work-product protection, and Briefcase keeps the facts for asserting it: minimal disclosure, disciplined retention, and the context in which the work was created. Federal trial courts have protected exactly that kind of preparation as work product. [See the record](https://nextbriefcase.com/legal-boundaries#record-title) The commitments ## Three commitments, kept in the architecture. 1. ### Your legal matter is yours. Your conversations, documents, evidence, and legal work will never become someone else's product. We do not sell your legal data, use it for advertising, or use your private matters to train any AI model, ours or a provider's. The information you entrust to Briefcase is used to serve you, not to build a business around your data. 2. ### Privacy is something we build, not something we claim. We make Briefcase a private place to work on the most sensitive matters in your life. That means minimizing the information we collect, limiting who and what can access it, encrypting it, isolating sensitive legal work, and choosing AI and infrastructure partners that are contractually and technically restricted from using your information for their own purposes. 3. ### We protect your confidentiality to the fullest extent the law allows. We say exactly what the law protects, and preserve every fact you need to claim it. Briefcase preserves the strongest available facts for asserting a protection: minimal disclosure and retention, private preparation kept apart from shared content, and the context in which the work was created. Any protection comes from the law and the circumstances. How it is built ## Eleven statements. Hold us to every one. Written for a court clerk, a partner, and a diligence team, in the same words the security record uses. 1. ### Zero-trust Every request is authorized from current server-side state. Nothing is trusted for being inside the network or for carrying a claim: a session carries identity only, and membership resolves on every request. 2. ### Least privilege Every principal, human or machine, holds only the permissions its one job needs. Runtime database principals own nothing and cannot turn row security off. Administrative reads run through a separate, audited operator path that is denied tenant content outright. 3. ### Isolation at the database Every tenant's data sits behind row-level security in the database itself, and an isolation suite runs on every change, so a change that would weaken the boundary fails before it ships. Metadata is confidential too: not the document, not the title, not the fact that it exists. 4. ### Encryption at rest, in transit, and during processing Durable content is encrypted under keys Briefcase controls, one per environment and data class. Restricted matter content is envelope-encrypted per object, and one dedicated processing identity is the only principal that can decrypt it. A sealed matter is the exception, under a key only you hold. 5. ### Ephemeral data processing Models read structured matter state and return results. A conversation with Briefcase leaves no transcript and no content-derived record: no copy, summary, topic, tag, embedding, or content hash. The content-free run record is kept. 6. ### Zero retention by contract Private legal content routes only to models eligible for zero retention by contract, inside one managed model plane under Briefcase's enterprise account. The model provider cannot reach the deployment, its logs, its prompts, or its completions. A model that carries any retention is never used for matter content. 7. ### Private processing Seal a matter and it is encrypted on your device under a key only you hold. Ask Briefcase to work on it and your key goes only to a verified, sealed workload that keeps nothing when the run ends. You decide what is sealed, and when it opens. 8. ### AI firewall Every input from outside is decoded against a schema at the edge and rejected on failure. Retrieved material is data, never instructions. Moderation screens both directions, and unsafe output is gated before a chunk reaches the reader. 9. ### Non-human identity Every worker, function, and agent run authenticates as its own identity with short-lived credentials. No long-lived key exists, and every agent run carries a signed identity, so every action it takes is attributable after the fact. 10. ### Guardrails The AI answers from the record you are entitled to use and cites it. When the record does not support an answer, Briefcase says so and points to a next step. A guardrail rejects advice-shaped output; individualized advice exists only inside a professional engagement you chose. 11. ### Continuous control monitoring Every control is policy-as-code, a test that runs before a change integrates and again on deployment. A failing control blocks the change and names the fix. Privileged surfaces are audited, and the evidence is collected as the work happens. Private processing ## How private processing works. Your key opens a sealed matter only inside a workload that has proved what it is running, and that workload keeps nothing when the run ends. No one at Briefcase can see inside it. Your devicePrivate workload 1. 01 Your matter is sealed on your device, under a key only you hold. 2. 02 Before the key is released, the workload proves what it is running. 3. 03 Your key and the sealed matter go only to that verified workload. 4. 04 Inside, the matter opens in memory and the work is done. No one at Briefcase can see in. 5. 05 The result comes back sealed, and opens on your device. 6. 06 The run ends. The key and the plaintext are destroyed. The workload keeps nothing. Legal process ## We can only produce what we can read. Your thinking with Briefcase was never written down. Your conversations with Briefcase leave no transcript, so the thinking you do with it does not exist to produce. What can be produced is bounded by what Briefcase retains and can read: the record you approve, the messages you choose to send, and the metadata it takes to run the service. When someone seeks access to your information 1. 01 We require valid legal process. 2. 02 We narrow an overbroad demand. 3. 03 We disclose only what the law compels. 4. 04 We notify you when the law permits, so you can assert your own rights. The limits ## Protection comes from the law and the circumstances. Privacy is not privilege. These limits are stated here, once, because a false promise about confidentiality is the one failure a person cannot recover from. - 01 Storing something in Briefcase does not make it undiscoverable. No software can, and Briefcase never tells you otherwise. - 02 Using Briefcase creates no attorney-client privilege by itself. Whether a protection applies is fact- and jurisdiction-specific. - 03 Anything posted publicly or shared broadly is neither privileged nor confidential because it lives on Briefcase. In the courts’ words ## A federal court set the bar for AI in a lawsuit. Briefcase clears it for everyone. The terms Briefcase runs on with every model provider are the terms the court wrote for confidential material to enter an AI tool at all, and the court said what those terms cost the people who represent themselves. [Read the full record on the legal boundaries page](https://nextbriefcase.com/legal-boundaries#record-title) > …this provision will (at least for now) bar the parties from using most, if not all, mainstream low-to-no-cost AI to process Confidential Information. This type of restriction disadvantages pro se litigants. Magistrate Judge Maritza Dominguez Braswell, for the court Morgan v. V2X, Inc., D. Colo., No. 1:25-cv-01991, 2026 > …as large firms pour thousands of dollars into enterprise-grade AI and make their use of AI more secure, efficient, effective, and powerful, how will a pro se litigant or a litigant who cannot afford big-ticket legal services and better AI keep up? Magistrate Judge Maritza Dominguez Braswell, for the court Morgan v. V2X, Inc., D. Colo., No. 1:25-cv-01991, 2026 [Read the full record on the legal boundaries page](https://nextbriefcase.com/legal-boundaries#record-title) Standards ## Recognized standards shape the controls. Every claim stays exact. - [Where the legal line sits](https://nextbriefcase.com/legal-boundaries) - [The questions people ask](https://nextbriefcase.com/faq) * ### SOC 2 Briefcase operates against SOC 2 control expectations, pursues independent examination, and publishes attestation status exactly as earned. It claims a completed SOC 2 report only after an auditor issues one. * ### Privacy regulation CCPA- and GDPR-grade access, deletion, data-processing terms, and data-minimization practices are the baseline for every user, in every jurisdiction. * ### Our controls run on every change, not once a year. No exceptions. Security is continuous. The isolation suite and the wider test gate run on every change, privileged surfaces are audited, and the evidence is collected as the work happens. * ### Public Benefit Corporation accountability Briefcase is a Delaware Public Benefit Corporation. Its public benefit is written into the corporate charter, and directors balance it alongside stockholder interests and the interests of those materially affected by the company's conduct. - [Where the legal line sits](https://nextbriefcase.com/legal-boundaries) - [The questions people ask](https://nextbriefcase.com/faq) Pilots start as early as October 1, 2026.