Chronos uses a small set of vetted third-party vendors to operate the platform. This page summarizes the vendors and configured routes currently documented for Chronos, the categories of data they may receive, and the status of our current verification work. Provider identity, geographic residency, and Business Associate Agreement (BAA) scope are not established by this page alone; confirm the executed agreements before sending PHI. We update this page whenever our documented processing configuration changes.
Published by Mahlum Innovations LLC · Last updated: August 20, 2026. Questions? Email security@medchronosai.com
| Vendor | Purpose | Data processed | Location | BAA status |
|---|---|---|---|---|
| Aptible | HIPAA-eligible cloud hosting and managed database | API server runtime, Postgres database containing all case and user data | Configured US location; verify against the executed production agreement. | Current BAA scope requires verification against the executed production agreement. |
| Google Cloud Storage | Object storage for uploaded medical records and generated exports | Uploaded medical record files (PDFs, images, DOCX), generated PDF/Word exports, user avatars | Configured US location; verify against the active storage configuration and agreement. | Current BAA scope and applicable service addenda require verification against the production configuration. |
| Aptible AI Gateway | Managed routing for chronology extraction and AI assistant | Text extracted from uploaded medical records, processed during chronology generation and case chat. Retention, logging, and training treatment require verification against the active provider contract. | Underlying provider/model location requires verification; Aptible routing location is not a provider-residency guarantee. | Provider, BAA scope, underlying model, and retention terms require verification against the current production routing contract. Do not rely on this listing as a contractual representation. |
| Clerk | User authentication and identity management | Email addresses, passwords (hashed), MFA secrets, session tokens. No medical record content or case PHI is processed by Clerk. | United States (authentication service configuration; verify current scope) | Not required — Clerk processes authentication data only (emails, hashed passwords, MFA secrets, session tokens); no medical record content or case PHI reaches Clerk, so a BAA is not applicable. Clerk does offer a BAA to healthcare customers should scope ever change. |
| Stripe | Payment processing and subscription billing | Credit card data (handled directly by Stripe, never touches Chronos servers), billing addresses, subscription status. No PHI or medical record content. | United States (billing-service configuration; verify current scope) | Not applicable — Stripe processes billing information only, not PHI. Stripe is not a Business Associate under HIPAA. |
| Replit | Development and CI/CD environment only | Source code and development tooling only. Replit is NOT used in the production environment — production runs on Aptible. No real PHI is processed in the Replit environment. | Development tooling configuration; not a production residency statement. | Not applicable to production (dev environment only) |
Clio, Filevine, and Litify are case management integrations that a firm may optionally connect. When a firm connects one, Chronos transmits finished chronologies, demand packages, and summaries to that system only at the firm's direction. These vendors act as the firm's own service providers, not as Chronos subprocessors, and each firm is responsible for its own agreement with them.