Continuity & Exit.

The case file belongs to the client, and the firm holds it for them. Under ABA Model Rule 1.16(d) and its state equivalents, a lawyer must surrender papers and property to which the client is entitled when the representation ends — and cannot condition that on a fee dispute in most jurisdictions. A vendor that makes the file hard to retrieve puts the firm in breach of a duty the firm cannot delegate to us.

So the commitment is simple, and everything below is just the mechanics of it: your data is yours, you can take a copy at any time, and we will never hold it hostage — including over money you owe us.

• Region: United States only, single region. Database, authentication, and file storage are on Supabase (AWS us-east-1); the application runs on Vercel's US edge and serverless regions.
• No multi-region failover today. A sustained regional outage at our host is an outage for us. This is a deliberate trade-off at our size: a restorable backup and an export you hold yourself retire more real risk per dollar than geographic redundancy, so that is where the next dollar goes.
• Subprocessors: the full list, with what each one touches, is at /legal/subprocessors. We give 30 days' notice before adding one.

This section is deliberately unflattering. A firm doing vendor diligence needs the real numbers, and a disclosed limitation is survivable in a way that a discovered false claim is not.

• Database: one encrypted backup per day, taken by our hosting provider, retained 7 days.
• Point-in-time recovery is not enabled. We have not purchased it. The practical consequence: in a worst-case database loss, the recovery point is the last daily backup, so assume up to 24 hours of lost work — not one hour.
• Recovery time is not yet measured. We will not quote an RTO we have not tested. A documented restore drill is scheduled; we will publish the measured number when it exists.
• Document files do not yet have a second copy. Uploaded PDFs, medical records, scans and signed documents sit in object storage, which is highly durable against hardware failure but is not a backup: it does not protect against an accidental or malicious delete of the object itself. Our recycle bin and soft-delete retention are the current mitigation, and a real second copy of document bytes is the next thing we are building.
• Per-firm backups to your own Google Drive or OneDrive exist in the product (/admin/backups) but are in closed beta, off by default, and have not yet completed a reliable production run. Do not treat that feature as a control you can rely on today. When it is dependable we will say so here, with the date it started working.

Two paths, and we would rather describe them precisely than call it “one-click export”:

• Structured records. A firm administrator can pull a complete JSON export of the firm's records — cases, clients, communications, tasks, medical records, liens, costs, settlement and trust ledger entries, e-sign envelopes, portal activity and the full audit log — across roughly seventy tables. Every table is read with verified row counts, and a read failure aborts the whole export rather than handing you a file that looks complete but is not. Today this runs as an authenticated request (GET /api/admin/firm-export) rather than a button in the interface; a button is in progress, and until it lands, support will run it for you on request.
• Documents. Files download individually, and in bulk as a ZIP by selecting them in the documents browser (up to 200 files or 500 MB per archive). Files mirrored from a connected Google Drive stay in your Drive and download from there. Document bytes are not yet included in the structured export — bundling them into a single archive is in progress, and until it ships, retrieving a large firm's complete file set is a batched process we will help with.
• Narrower exports exist for the surfaces that need to hand data to another system: calendar, exhibit lists, 1099 vendor totals, and accounting exports.

The formats are ordinary JSON and CSV with stable keys. There is no proprietary container, no per-record export fee, and no clause anywhere in our agreement that makes leaving cost money.

• Cancel from the billing page at any time. Monthly plans stop at the end of the period; annual plans are refunded pro-rata per the Terms, §5.
• Export access continues for 30 days after cancellation. Ask and we will extend it; we are not going to argue with a firm that is mid-migration to another system.
• Export is not gated on billing. The export endpoint is deliberately exempt from the lockout that applies to suspended, past-due and canceled accounts, so a firm winding down can still retrieve the client file it is ethically obliged to surrender. We built that carve-out on purpose and we are not going to remove it.
• Deletion: customer data is deleted from primary systems within 90 days of cancellation except where law requires retention; the daily backups that contain it age out within 7 days of that deletion. Ask for earlier deletion and we will do it — after confirming you have your export.
• No exit interview, no retention gauntlet, and no requirement to speak to anyone to cancel.

Lexboard is a small, founder-operated company. That is the relevant risk, and pretending otherwise would be the exact kind of claim this page exists to avoid.

If we wind down deliberately, we commit to:

• At least 90 days' written notice to every firm administrator before the service stops.
• Keeping export and document download working for that entire window, with billing switched off.
• Running the export for any firm that asks, and delivering it in a format their next system can ingest.
• Confirming destruction of remaining copies in writing afterwards.

If something happens to the founder, there is today no third-party continuity trustee and no escrow agent who would step in. We are not going to describe an arrangement that does not exist. The mitigation that is real, and entirely within your control, is holding your own copy: take an export on a schedule, keep it with your other firm records, and you are never dependent on us being reachable.

Source-code and data escrow with a named agent, released on defined trigger events, is something we intend to put in place as enterprise customers require it. It is not in place today. There is no signed escrow agreement, no deposit, and no agent.

When there is one, this section will name the agent, the deposit cadence, and the release conditions, and we will say so in writing to any firm that asked about it. Until then, treat escrow as absent — because it is.

Everything on this list is a control a mature vendor would have and we do not, as of the date at the top of this page:

• No continuous point-in-time recovery — recovery point is up to 24 hours.
• No second copy of document bytes under our control.
• No measured recovery time; the restore drill has not been run yet.
• No multi-region or cross-provider failover.
• No source-code or data escrow, and no continuity trustee.
• No SOC 2 report and no third-party penetration test — see our disclosure policy for where that stands.
• No contractual uptime SLA and no public status page.
• Document bytes are not yet part of the single structured export.

Each of these is on the roadmap in roughly that order. We will move an item off this list on the day it is true and verifiable, not on the day it is planned.

This is the advice we would give a firm evaluating any vendor, including us:

• Take a full export at least quarterly, and store it where you keep your other firm records. It takes minutes.
• Take one before any major change on your side — a merger, a system migration, a staff departure with administrator access.
• Keep the documents you cannot recreate — signed retainers, executed releases, original medical records — mirrored in your own document store as well.
• Ask us for anything in this page in writing on your firm's diligence form. The answers will match what is written here.

Continuity, exit and diligence questions: legal@lexboard.net. Technical or security questions: security@lexboard.net.

Related: the Terms of Service (§5, cancellation and retention), our Security & Trust summary, and the Data Processing Addendum (deletion and return of personal data).