Identity and access
Users authenticate through Clerk and work within an active organization. Protected pages and APIs check the session and organization rather than relying on navigation or a perimeter redirect alone.
Organization roles and product entitlements limit administrative, billing, export, and paid-product actions. Workspace administrators are responsible for membership and should remove access promptly when a user changes roles or leaves.
Data separation
Customer and billing records are separated from the shared legal-source corpus. Production is designed to use independent PostgreSQL credentials and database boundaries so the customer application cannot rely on cross-database joins or shared mutable tables.
Customer records are scoped to the active organization. Server-owned identity fields are derived from the authenticated request, not accepted from browser payloads.
Application controls
- Signed Clerk and Stripe webhooks are verified before identity or entitlement state changes.
- Billing access is granted from the local projection of verified subscription events, not from a browser redirect.
- Customer inputs are constrained by field, type, and length before persistence.
- Secrets and provider credentials are supplied through the deployment environment rather than client-side code.
- Draft records support organization scoping, history, review state, and soft deletion where the workflow requires it.
Legal-workflow controls
Practice updates preserve source links and identify the underlying authority. Generated drafts are not treated as approved client communications. Review and approval remain separate actions performed by an authorized user.
AI drafting uses the provider configured for the deployment. Customers with provider, retention, confidentiality, or procurement requirements should document them in the applicable order and deployment configuration.
Critical providers
Clerk provides identity and organization membership. Stripe provides payment and subscription services. Infrastructure, database, communications, and AI providers depend on the deployment. We can address the current provider set and contractual controls during security review.
Customer responsibilities
- Keep organization membership, roles, and billing administrators current.
- Use available strong-authentication controls and protect account credentials.
- Review professional, client, privilege, and data-residency requirements before submitting content.
- Verify authorities, citations, dates, and generated conclusions before use.
- Report suspected account compromise or data exposure promptly.
Security review and reporting
To report a suspected vulnerability or request current security documentation, email hello@ofcounsel.ai. Include a concise description and a safe way to reproduce the issue. Do not access another customer’s data or degrade the service while testing.
Certifications, deployment-specific controls, subprocessors, recovery objectives, and contractual commitments are provided only when current and applicable; this page does not claim a certification or service level.