Skip to main content
Back to home
Security

Data Security

How LeBrief AI protects your medical records and case data: encryption, access controls, monitoring, incident response, and the subprocessors we trust.

Last updated: November 8, 2026

01Security Overview

LeBrief AI processes some of the most sensitive data that exists: medical records tied to legal matters. Our security program is built around a simple principle, your data is never ours to use, only yours to control. Security is not a feature of the platform; it is the foundation the platform is built on.

Encryption Everywhere

AES-256 encryption at rest and TLS 1.3 in transit. Your data is encrypted before it is written to disk and stays encrypted as it moves.

Keys & Secrets Management

Encryption keys are managed through a dedicated key management service with automatic rotation. Application secrets never live in code or logs.

Strict Access Control

Access controls with the principle of least privilege. Row-level security isolates each customer’s cases so users only ever see their own data.

Session Security

Secure session handling and automatic timeout after 30 minutes of inactivity.

Backups & Recovery

Encrypted, geographically redundant backups that support recovery of your cases.

Audit Logging

Every access to PHI is recorded in an immutable audit log, and customers can review the access history for their own cases.

Patching & Updates

Security updates are applied as needed, and changes are reviewed before they ship.

BAA & Audit Support

Business Associate Agreements available on request and documentation to support your own compliance reviews.

02Encryption

  • At rest: all Customer Data, databases, and backups are encrypted with AES-256.
  • In transit: all connections use TLS 1.3. Older, weaker protocols are disabled.
  • Key management: encryption keys are generated, stored, and rotated through a managed key management service. Keys are never hardcoded or committed to source control.
  • Uploaded files: documents are encrypted before being written to object storage, and decrypted only in memory during authorized processing.

03Access Control

  • Authentication: passwords are hashed with a modern adaptive algorithm and password requirements are enforced (minimum 8 characters).
  • Authorization: role-based access control (owner, admin, member, viewer) plus database row-level security ensures users can only access cases belonging to their organization.
  • Least privilege: access to production systems is limited to the small team operating the platform, and each role can only do what it needs to do.
  • Session security: sessions expire after 30 minutes of inactivity and can be revoked remotely at any time.

04Infrastructure Security

LeBrief runs on major cloud infrastructure operated by providers that maintain SOC 2 Type II audited controls, including Firebase (database, authentication, and storage) and Google Cloud (AI processing). Our application is hosted on Cloudflare Pages' edge network. Network traffic is filtered at multiple layers.

05Audit Logging

  • Every access to PHI, by any user, is recorded in an immutable audit log.
  • Audit logs are retained for at least six years, per HIPAA documentation requirements.
  • Customers can review the access history for their own cases through the platform's audit trail.

06Vulnerability Management

  • Security updates are applied as needed, and changes to production are reviewed before deployment.
  • We welcome responsible disclosure. If you discover a vulnerability, please email legal@lebrief.ai. We ask that you give us reasonable time to remediate before public disclosure.

07Backups and Disaster Recovery

  • Customer Data is backed up automatically to encrypted, geographically redundant storage.
  • Backups are automated and designed so that Customer Data can be restored when needed.
  • We aim to restore service as quickly as possible using the automated backups described above.
  • Backups are subject to the same encryption and access controls as production data, and are included in our secure-deletion process described in the Privacy Policy.

08Personnel Security

  • Access to production systems is limited to the small team operating the platform, on a least-privilege basis.
  • Confidentiality obligations survive employment and contracting relationships.

09Incident Response

When a suspected security event is detected, we work through a defined process:

  • Detection and triage of suspected security events, with defined severity levels and escalation paths.
  • Containment and eradication, followed by a root-cause analysis for every confirmed incident.
  • Breach notification: if an incident involves unsecured PHI, we notify affected customers without unreasonable delay and within HIPAA's required timeframes so they can meet their own notification duties.
  • Post-incident review with corrective actions tracked to completion.

To report a suspected security incident, email legal@lebrief.ai.

10Subprocessors

We use a small set of carefully vetted subprocessors to operate the Services. Each subprocessor with potential access to PHI is subject to contractual data-protection terms, including Business Associate Agreements where applicable. A current list of our subprocessors is available on request, contact us at legal@lebrief.ai.

11Compliance and Assurance

HIPAA

Our technical, administrative, and physical safeguards are designed to meet HIPAA Security Rule requirements for business associates. We put Business Associate Agreements in place for covered-entity customers who need them and maintain the documentation, audit logs, and breach notification procedures HIPAA requires.

Data subject rights

Our Privacy Policy describes the rights available to you under laws such as the California Consumer Privacy Act and the EU General Data Protection Regulation, and how to exercise them. Where we act as a processor of Customer Data, we support our customers in fulfilling requests directed to them.

Ongoing review

Security is a continuous program, not a one-time project. We review our controls periodically and after any significant incident or infrastructure change, and we update this page as our practices evolve. The "Last updated" date above reflects the most recent review.

12Contact Us

For security questions, vulnerability reports, or to request our security documentation under NDA, contact legal@lebrief.ai. For general privacy inquiries, see our Privacy Policy.

Contact us

Reach our team directly and we will respond within two business days.

legal@lebrief.ai