No legal AI product should ask for confidential information before its controls are ready.
Every account is authenticated, and every record belongs to the account that created it — enforced in the database, not in the interface. That is a real foundation. It is not yet the full set of controls privileged client material needs, so this page names both.
Available now
In the running product, and checkable by anyone with an account.
Authenticated accounts
Sign-in with email, Google or Apple, with session refresh and logout. There is no anonymous path into the workspace.
User-scoped data
Matters, documents, conversations and drafts belong to the account that created them.
Row-level security
Access rules run in the database, so a request for another account's record returns nothing, whatever the browser sends.
Private storage
Uploads are stored privately and reached through short-lived signed links, with integrity checks on the content.
Server-side authorization
Ownership and model access are decided on the server from the signed-in session, never from a value the browser supplies.
Before enterprise launch
What a firm should expect to see before confidential matters move in.
Retention controls
Defined retention windows, export and verified deletion.
Audit logs
A record of access and changes that the firm itself can review.
SSO
Single sign-on through the firm's identity provider, with user provisioning.
Independent security review
A third-party assessment of the product before confidential production use.
Astra for Law
Legal model integration coming soon
◆
PRIVATE BETA
Keep the research visible. Keep the document yours.