Where client information lives
- On your computer, encrypted. Drafts, intake answers and review notes are kept in this browser's database, each encrypted (AES-GCM) with a key the browser will not hand to any web page. Your computer's login, screen lock and disk encryption (FileVault on a Mac, BitLocker on Windows) still guard them while the computer is in use. Close desk erases them and destroys the key.
- In transit, and only to draft. When you press Draft it, the facts the document needs travel over HTTPS to Lawsmith's server and on to the AI model. The server does not save them.
- At the model, not retained. Every model request goes through OpenRouter on a route that must be marked for zero data retention, with data collection denied, and with no fallback to another model. These are requirements in our code; they are not an independent audit of each provider.
What our server keeps
- Your account, not client matters: sign-in email, profile, firm membership and shared blank templates, Stripe customer references, billing dates and usage totals.
- Stored on Amazon DynamoDB, encrypted at rest, with point-in-time backups kept for 35 days so an account can be recovered.
- Logs of events and counts only: the kind of document, the state, timings and cost. Never the client's name, the answers or the draft. Logs are deleted after 90 days.
- Deleted on request. An attorney can delete the account from the Account page. It removes the account record and signs out every device at once; the privacy page lists the two things that remain.
Signing in
- No passwords to steal. You sign in with a six-digit code sent to your email. A code works once, for ten minutes, with five tries, and an address is locked for the day after repeated wrong codes.
- Sessions your browser's scripts cannot read. The session is a signed cookie marked HttpOnly, Secure and SameSite=Strict. Signing out revokes it on the server.
- Firm roles. Only the firm's owner can add or remove an administrator; members see the firm's blank templates and nothing of each other's matters.
Infrastructure
- Amazon Web Services. The server runs on AWS Lambda in the United States and can be reached only through Amazon CloudFront; direct requests are refused.
- Encrypted connections. TLS 1.2 or later, with plain HTTP redirected to HTTPS and HTTP Strict Transport Security.
- A locked-down page. A strict content security policy lets only Lawsmith's own code run. There are no third-party scripts, trackers or ad tags, and fonts are served by Lawsmith itself.
- Checked files. A Word file you email through Lawsmith is checked for size and structure first, and one with active fields or embedded external content is refused. A template you upload is read as plain text in your browser.
- Payments by Stripe. Card details are entered on Stripe's page and never reach Lawsmith.
Service providers
| Provider | What it does for Lawsmith |
|---|---|
| Amazon Web Services | Hosting, the account database, and sign-in and support email |
| OpenRouter | Routes each drafting request to the AI model on a zero-retention route |
| The model providers | The AI models that write and check drafts (named on the privacy page when the server can be reached) |
| Stripe | Subscriptions and payment |
Your professional duties
ABA Formal Opinion 512 (July 2024) asks lawyers who use generative AI to understand how the tool handles client information (Model Rule 1.6), to keep the competence to use it and review its output (Rules 1.1, 5.1 and 5.3), to tell clients where it matters (Rule 1.4), and to bill fairly for it (Rule 1.5). This page and the privacy page answer the first question. Every Lawsmith draft cites the official sources it was written from, lists what to verify, and needs your review before it is filed, signed or sent. Your state bar's own guidance governs; this is not legal advice.
Report a security problem
Email support@lawsmith.ai with "Security" in the subject. Please do not include client information. The full detail of what goes where is on the privacy page.