Security

Last updated: November 2, 2026

This page describes, in plain language, how Proserus, Inc. protects the data that law firms place in Proserus Legal. Every control listed here exists in the platform today unless it is marked as a commitment or a roadmap item. Report security concerns to security@proserus.com.

1. Shared Responsibility

The platform spans two environments, and responsibility is split accordingly.

• Your Microsoft 365 tenant (you manage). Documents, email, and Teams live in your tenant. You control identity (Entra ID users, multi-factor authentication, conditional access), SharePoint permissions and retention, and which administrator grants Proserus consent. Removing a user from Entra ID or revoking consent immediately cuts that access.
• Proserus infrastructure (we manage). The application, the PostgreSQL database holding structured practice data, document text passages and embeddings, AI records, the OCR service, background job runners, Azure storage for litigation archives, and the SMS sending service. We are responsible for hardening, patching, isolation, backups, and monitoring of these systems.
• Shared. You decide which users get which roles inside Proserus, how autonomous the AI may be, how long AI content is retained, and whether to bring your own AI provider keys. We enforce those decisions server-side.

2. Identity and Access

• Single sign-on only. Users sign in with Microsoft Entra ID. Proserus has no password database; your tenant's MFA and conditional-access policies apply automatically.
• Server-side authorization on every request. Each API route verifies the caller's token, resolves the firm it belongs to, and checks the required permission before reading or writing anything. The browser never decides what a user may do.
• Role-based permissions. Firm administrators assign roles; permissions are checked on the server, and access to individual matters can be restricted per user.
• Suspended firms are refused. A firm whose account is suspended, cancelled, or deleted is rejected at the authentication layer for every request.

3. Microsoft Graph Permissions

Setup needs one consent from a Microsoft 365 administrator in your firm. The permissions below are delegated: Proserus acts as the signed-in user and can reach only what that user can already reach in your tenant. The Copilot permissions are not part of the first-run consent; they are requested only when a user with a Microsoft 365 Copilot license turns on Copilot time suggestions.

A few features run in the background without a signed-in user: sending email from your firm's mailbox, keeping deadlines in sync on Outlook calendars, creating matter sites and Teams, and the found-time review of calendars and meetings. These use application permissions that your administrator approves for the Proserus app in Microsoft Entra ID. You can review or revoke every permission at any time under Enterprise applications in the Entra admin center. For a walkthrough of the admin consent, write to sales@proserus.com.

4. Tenant Isolation

• Database row-level security. Every tenant-scoped table carries a firm identifier and is protected by PostgreSQL row-level security policies that fail closed. The application connects as a restricted database role that cannot bypass those policies, and the process refuses to start in production if it detects a role that could.
• Scoped data access in code. Application code reads and writes through a tenant-scoped client that injects the firm identifier automatically, so a missing filter cannot leak another firm's rows.
• Separate Microsoft tenants. Each firm's documents are in its own Microsoft 365 tenant, and Graph calls are made with tokens issued for that tenant.

5. Encryption

• All traffic between browsers, the application, and third-party services uses TLS.
• The database and storage volumes are encrypted at rest by the hosting providers (Railway and Microsoft Azure).
• Firm-supplied AI provider keys are stored with AES-256-GCM envelope encryption (a per-secret data key wrapped by a master key held outside the database) and are decrypted only on the server at the moment of a request. No API returns more than a key fingerprint.
• Public links (payment pages, questionnaires, approval links) use long random tokens and are rate-limited.

6. Audit Logging and Monitoring

• Firm audit log. Administrative and data-changing actions are written to an audit log that firm administrators can review.
• AI audit trail. Every AI request records who initiated it, the task, the provider and model, token counts, and cost. This metadata is kept permanently; the content is retained per your policy.
• Trust ledger. Trust journal entries are append-only and cannot be edited or deleted; corrections are recorded as new entries.
• Error monitoring. Application errors may be reported to Sentry with request bodies and cookies stripped; document content and email addresses are never included.
• Health checks. Liveness and readiness endpoints let our hosting platform and our monitoring detect and restart unhealthy instances.

7. Operator (Proserus Staff) Access

• Access to the operator console is limited to an explicit allowlist of Proserus staff whose sign-in token was issued by Proserus's own Microsoft tenant; an allowlisted address signing in from any other tenant is refused.
• Every operator API call is written to a separate, cross-tenant operator audit log.
• Viewing a firm's workspace for support (“view as”) is read-only, uses short-lived signed tokens, and is audited. It is disabled entirely unless the feature is explicitly configured.
• Proserus staff do not access firm documents in Microsoft 365 except through these audited paths.

8. Application and Platform Hardening

• Rate limiting. A replica-safe token bucket backed by the database protects authentication, AI, and public endpoints and degrades safely if the database is unavailable.
• Webhook verification. Inbound webhooks from Stripe, Microsoft Graph, and Azure Communication Services are verified by signature or shared secret and fail closed when a secret is missing.
• Internal services. Background jobs and the OCR service run on private networking and authenticate to the application with dedicated secrets.
• Upload limits and validation. File uploads are size-limited and validated before being written to your SharePoint.
• Dependency and image updates. The application is rebuilt from source on each deploy; dependencies are updated on a regular cadence.

9. AI Provider Safeguards

• All AI calls go through a single internal gateway that enforces entitlements, selects the provider, meters usage, and writes the audit record. No other code path talks to a model provider.
• Our provider agreements prohibit training on your content, and we use zero-data-retention options where the provider offers them, as configured in our provider agreements.
• Autonomy ceilings are hard-coded: outbound communications, court-facing documents, billing finalization, and calendar or task writes always require human approval.

10. Backups and Resilience

The database is backed up by the hosting platform on a rolling schedule, and the application runs stateless instances that can be replaced without data loss. Documents in your Microsoft 365 tenant are covered by Microsoft's own resilience and by your retention policies. Recovery objectives for paid plans are stated in the Service Level Agreement.

11. Incident Response

Commitment. If we confirm a security incident that affects your firm's data, we will notify your firm's administrator without undue delay and no later than 72 hours after confirmation, with what we know about the scope, the data affected, the steps we have taken, and recommended actions. We will provide updates as the investigation progresses and a written summary when it closes. Where law enforcement asks us to delay notice, we will notify you as soon as we are permitted.

12. Vulnerability Disclosure

If you believe you have found a vulnerability, email security@proserus.com with enough detail to reproduce it. We will acknowledge reports within two business days and keep you informed while we fix the issue. Please follow the security-testing rules in the Acceptable Use Policy: test only against your own firm's data, do not access other tenants' data, and do not run denial-of-service or social-engineering attacks. We will not pursue legal action against researchers who act in good faith and within those rules.

13. Compliance and Roadmap

• SOC 2 Type I: in progress. Proserus is not yet SOC 2, ISO 27001, or HIPAA certified and does not claim to be.
• Penetration testing: commitment to an annual third-party penetration test of the application, with a summary letter available to customers on request.
• Business Associate Agreement: available on request for qualifying plans where a firm handles protected health information.
• Data Processing Addendum: a standard-form DPA is available at /dpa; our subprocessors are listed at /subprocessors.
• Data location: all Proserus-operated processing is in the United States.

14. Contact

Proserus, Inc.
Security: security@proserus.com
Privacy: privacy@proserus.com