Trust Center
What DraftAria does with your documents, and how we keep Aria honest.
Law firms need specifics. This page lists the services that handle your data, how citations and court rules are checked, and what we have and haven't done yet.
At a glance
Security & data handling
Citations are never invented
Court rules, watched weekly
Rule checks without AI
Subprocessors
Services that handle customer data
| Service | Purpose | Data involved | When |
|---|---|---|---|
| Supabase | Database, sign-in and file storage | Account details, firm workspace data (documents, versions, analyses, deadlines), uploaded files, audit log | Always |
| Vercel | Hosts the website and app files | Standard web request data (IP address, browser, pages requested). Documents are not stored on Vercel. | Always |
| Anthropic | AI model provider for Aria (Claude) | Text you submit to an Aria feature, and files you attach in the AI workspace | When you use an Aria feature |
| Free Law Project (CourtListener) | Looks up case citations to confirm they exist | The citations found in a document (not the document itself) | Only when citation lookup is turned on |
Last updated October 2026. We'll update this list before adding a service that handles customer data.
Methodology
How Aria handles citations
No invented authority. Every Aria prompt that can touch legal authority tells the model not to fabricate citations. Templates use a [CITE AUTHORITY] placeholder instead of guessing.
Flagged, not trusted. When Aria reviews arguments or drafts, citations it can't confirm are flagged so a person checks them. Aria's output is labelled "Drafted by Aria · review before relying on it."
You decide. DraftAria is a drafting and checking tool. An attorney reviews every filing before it goes to court.
Methodology
How court rules are sourced and kept current
Official sources only. We keep a register of the official websites of the U.S. Supreme Court, every federal court of appeals, district court and bankruptcy court, and the national rules pages.
Checked every week. An automated job visits each site every Monday, finds its local rules and standing orders, and records a fingerprint of each page and rule document. It reads the rule text for requirements such as file type and size, font and font size, line spacing, margins, page and word limits, and Word styles, and reports any change for review. It never changes DraftAria's rules by itself.
Labelled until verified. Court requirements are shown as "Not yet verified" until a reviewer has checked them against the court's own rules. Always confirm with the court's current local rules and standing orders before filing.
See the court pages for each court's requirements.
Being open about it
What we haven't done yet
- No SOC 2 or ISO 27001 audit has been completed.
- Single sign-on (SAML / Azure AD / Okta) and multi-factor authentication are not available yet.
- Court requirements in our database have not yet been verified by a reviewer; they are labelled accordingly.
Reporting a security issue
If you believe you've found a security problem, email support@draftaria.com with "Security report" in the subject. Please don't access other people's data or disrupt the service while testing.
Going through vendor review?
We'll complete your security questionnaire and walk your IT and risk teams through how data is handled.