Skip to content
Legal Beagle

Security

How we handle client-confidential documents

Draft policy — pending legal review. This page describes how the system is actually built today. It is not a substitute for review by qualified counsel before being relied on as a binding representation.

Why this matters more here than in most apps

The documents that move through Legal Beagle — bank statements, medical records, immigration petitions, tax filings, custody and financial declarations — are client-confidential, and frequently covered by attorney-client privilege. That's a materially higher bar than a typical document-upload tool, and we hold to it explicitly rather than by accident.

Document processing runs on our own infrastructure — never a public AI vendor

No document you or your clients upload is sent to a public or hosted AI API (OpenAI, Anthropic, Google, AWS Textract, or similar) for extraction or analysis. Document extraction runs on dedicated, self-hosted infrastructure that we control — a queue-fed worker fleet, not a call out to a third-party model. As volume grows, we add more workers to that same infrastructure rather than routing overflow to a public API. No client document or client answer leaves that infrastructure to reach a model that logs or trains on it.

If we ever consider a hosted AI vendor for any part of this pipeline in the future, that would require a signed enterprise no-training, no-retention agreement confirmed in writing beforehand — not an assumption based on a vendor's general privacy policy — and we'd update this page before it shipped.

Access control

Every document download is authenticated and scoped to the firm and matter it belongs to — a request for another firm's document fails, not just gets denied at the UI layer. Client-facing links (portal access, per-matter collection links) are single-purpose tokens scoped to one client or one matter, not a shared or guessable credential.

If something goes wrong

We maintain an internal incident response process covering how a security incident gets detected, contained, assessed, and remediated. If an incident is confirmed to have affected your documents or account information, we will notify your firm (for a firm's client, notification runs through your firm — see Privacy) and take the legally required steps for the jurisdictions involved. We're deliberately not publishing a specific notification deadline or SLA on this page — those obligations vary by jurisdiction and by what happened, and we'd rather commit to something real once that's been reviewed by counsel than promise a number now that we can't guarantee.

What this product does not do

Legal Beagle drafts and organizes. It does not file, submit, or e-sign anything on an attorney's or client's behalf, under any circumstance. Every draft carries a persistent, non-dismissable label to that effect. Filing happens outside this system, by the attorney, through the tools they already file through.

Questions

If you or your firm have a specific security question — including one from your own IT or compliance review — contact us directly.