Security & compliance

Built to hold
protected health info.

Medical records are the most sensitive data a firm handles. Chronos treats every page as PHI — encrypted, access-controlled, audited, and protected by the safeguards described below. A Business Associate Agreement is available when the parties' roles and intended use require one.

HIPAA-aligned
SOC 2 readiness program
256-bit AES
PHI · ENCRYPTED
AES-256 at rest
TLS 1.3 in transit
// Security pillars

Defense in depth, by default.

Encryption in transit and at rest

TLS 1.3 protects data in transit. Provider-managed AES-256 encryption protects database records on Aptible and uploaded files in Google Cloud Storage.

Role-based access

Each user can reach only the cases and actions they need.

Security audit logging

Security-relevant activity is recorded in a firm-scoped audit log that administrators can export for compliance review.

HIPAA-eligible hosting

Database workloads run on Aptible's HIPAA-eligible infrastructure, object files use Google Cloud Storage, and application controls isolate each firm's data.

US data residency

We store and process PHI inside the United States. We never use your records to train outside AI models.

BAA available

Firm administrators can review and sign a Business Associate Agreement (BAA) in workspace settings at no extra cost.

// HIPAA Safeguards

Mapped to the Security Rule.

Chronos uses the administrative, physical, and technical safeguards needed to handle PHI for covered entities and their business associates — defensibility that pays off across every case. See why teams choose Chronos.

  • Access controls (§164.312(a))

    Unique user IDs, automatic logoff, and encryption keep access to ePHI on a need-to-know basis.

  • Audit controls (§164.312(b))

    Hardware and software tools record and review activity in any system that holds ePHI.

  • Integrity (§164.312(c))

    Controls confirm that no one has changed or deleted ePHI without permission.

  • Transmission security (§164.312(e))

    TLS 1.3 protects ePHI from unauthorized access while it travels over networks.

// Data lifecycle

What happens to a record.

01

Upload

Records are encrypted with TLS 1.3 the moment they leave your browser.

02

Process

The AI reads your records in an isolated environment. No PHI is used to train outside models.

03

Store

Stored and encrypted with AES-256, locked to your firm with role-based access and a full audit log.

04

Delete

Deleted cases move to recoverable Trash before an administrator or the retention process permanently purges them. Account deletion has a separate recovery period.

// Data practices

What we do — and don't do — with your data.

These statements summarize the product's documented data practices and application controls.

For the full written policies behind these controls, see our security policy documents →

Authorized AI processing, not training or sale

Chronos sends the record text needed for a requested feature to the centrally configured AI route. The underlying provider, applicable agreements, and retention controls must be verified against the current production configuration. We do not use customer records to train or fine-tune models, sell them, or disclose them outside authorized processing except as required by law.

AI retention controls

The production AI route's retention, logging, and training treatment require verification against the current provider agreements and active account configuration. This page does not make a Zero Data Retention guarantee.

Customer-controlled deletion

Deleting a case or client moves it to Trash, where an administrator can restore it during the firm's configurable retention window (30 days by default, minimum 7). After that window, the nightly retention process hard-deletes its application data and attempts to remove associated stored files; an administrator can also choose Purge now from Trash. The purge result records any storage deletion failures for operational follow-up. A hard purge cannot be undone. Account deletion uses a separate 30-day recovery window.

US-only data residency

Configured vendor locations are listed on the Subprocessors page. Confirm the current production configuration and applicable agreements before relying on a data-residency commitment.

Security audit trail

Security-relevant actions are recorded in an audit log scoped to your firm. Firm administrators can export the log for compliance review.

Transparent subprocessors

We publish the vendors authorized to process customer data on our behalf, including the purpose, data categories, location, and documented BAA status for each service. View subprocessors →

Insured for the work we do

Chronos (Mahlum Innovations LLC) carries $2,000,000 in Technology Errors & Omissions and Cyber Liability insurance, including an Artificial Intelligence coverage endorsement extending E&O coverage to AI-delivered services. Certificate of insurance available on request.

// Security FAQ

Common questions.

Need our security docs?

We'll share our BAA template, security documentation package, and a security questionnaire under NDA.

Explore features