Security at a glance

• Tenant isolation. Every firm's data is separated at the database level by Row-Level Security — one firm can never see another's matters. Enforced in the database, not just the app: on every code change, automated probes confirm that a signed-out visitor gets no rows from the private tables they check, and a suite of negative tests runs as signed-in users against the production database.
• Encryption. Data travels only over HTTPS (TLS, with HSTS on this site), and our database host encrypts stored data at rest.
• Document security. Trusts, death certificates, and financial documents live in private storage, reached only through short-lived signed links issued to someone with access to that matter or firm — never public URLs, never emailed as attachments.
• Access control. Sign-in by a one-time link sent by email, so customer and firm accounts have no password to steal. The browser holds only the public key and the service key stays on the server; staff roles are set per firm; and platform administrators reach a firm's documents and work only under a recorded support-access grant.
• Audit trail. An append-only audit log — the database refuses any edit or deletion of an entry — records who did what, and when. Opening or downloading a stored document is logged before its link is issued; a firm's full matter export is logged as one event.
• AI handling. The self-help documents are assembled from your own answers — no AI model writes, phrases, or reviews them. AI is used only inside a law firm's workspace, as the firm's tool under its own attorney: a finding the AI drafts reaches the firm's client only once approved, and the database accepts that approval only from an attorney of the verified firm or from a platform administrator under a recorded support-access grant. No AI model is connected to EstateDraft today; the platform's operator connects one only for law-firm workspaces.
• Backups & recovery. Our database host backs up the database every day and keeps at least the last 7 days. Stored documents are not in those backups and are not yet copied to a separate backup, and no restore of EstateDraft's data has been tested yet — the first restore drill runs on a separate staging copy once one exists.
• Incident response. A documented runbook with defined severities, containment steps, and a notification decision.

• Independent audits: none has been performed for EstateDraft, and no SOC 2 or ISO 27001 report exists for it — none is claimed. A provider's own audit report covers that provider, not EstateDraft.
• Data Processing Addendum: a summary is published on the Data Processing Addendum page — LegalDraft Technologies LLC acts as your firm's data processor and your firm remains the controller; a counter-signable version is prepared on request.
• Unauthorized practice of law (UPL): the self-help lane is a nonlawyer tool by design — documents assembled from your own answers, general rules cited to the statute, and no review of your situation by a lawyer or a model; in a law firm's workspace, each AI finding and each deliverable reaches the firm's client only once approved, and the database accepts that approval only from an attorney of the verified firm or from a platform administrator under a recorded support-access grant.

Connected today: Supabase (database, sign-in, and file storage, hosted in the United States) and Vercel (hosting and site analytics). Not connected today, and named here before any is switched on: an AI model provider (Anthropic, for law-firm workspaces only), a payment processor, and the senders for email and text-message notices.

Capabilities & limits

For a security questionnaire or our Data Processing Addendum, send a request through the form on our page for firms. For firms

Security researchers: to report a vulnerability, ask us to contact you through that same form, and leave client data and the details of the issue out of it; our disclosure file is published at /.well-known/security.txt.