Security
Last updated: October 8, 2026 · Version 2026-10-08.1
LegalYoda is an early-stage product. This page states what we do today and what we do not yet have, so that you can assess whether the Service fits your confidentiality obligations.
1. What we do today
- Encryption in transit: the Service is served only over HTTPS.
- Encryption at rest: provided by our database host, Neon.
- Authentication: handled by Clerk. We never store your password.
- Access scoping: application queries are designed to return only data belonging to your account or organization.
- Compliance records: acceptances, attestations and download acknowledgments are written to an append-only log with a SHA-256 integrity hash. The application has no function that edits or deletes these records.
2. Infrastructure providers
- Hosting: Vercel
- Database: Neon (PostgreSQL)
- Authentication: Clerk
- Payments (not live yet; planned): Stripe. Card details will go directly to Stripe and never reach our servers.
- AI model provider: Anthropic
- Citation lookups: CourtListener (citation text only)
Each provider publishes its own security documentation and certifications. Their certifications are theirs and do not apply to LegalYoda itself.
3. What we do not have yet
- No SOC 2 or other independent security audit of LegalYoda.
- No uptime or service-level agreement.
- No self-service data export; contact us for an export.
4. Retention and deletion
Retention periods and deletion requests are described in the Privacy Policy.
5. Report a security issue
To report a vulnerability or a suspected incident, email us with details. Please do not access data that is not yours.