Subprocessors
Last updated: May 22, 2026
AIDentalClaims uses the following third-party service providers ("Subprocessors") to operate the Service. Some of these Subprocessors may receive Protected Health Information (PHI) in the course of providing services to us. This page is the canonical list referenced by our Business Associate Agreement § 6.
We will provide at least thirty (30) days' notice before adding any new subprocessor that will handle PHI. If you are a Covered Entity and you object, we will work to address your objection or, if we cannot, you may terminate the Service Agreement on written notice without penalty.
| Subprocessor | Purpose | Region | Receives PHI | BAA |
|---|---|---|---|---|
| Railway | Backend application hosting + PostgreSQL database Railway's underlying infrastructure runs on HIPAA-eligible AWS regions. A direct Railway BAA is in negotiation; until executed, do not use AIDentalClaims for real patient claims if your compliance posture requires an executed BAA with every subprocessor. | United States | Yes | Pending |
| Cloudflare | Frontend static hosting (Pages), DNS, edge security Cloudflare terminates TLS at the edge. Authenticated API traffic flows through Cloudflare to Railway. | United States (US-only routing) | Yes | Pending |
| Anthropic | Large-language-model API (fallback narrative generation) Receives only PHI-scrubbed input per HIPAA Safe Harbor (45 CFR 164.514(b)(2)). Anthropic does not train on inputs by policy. | United States | No (de-identified text only) | Pending (enterprise plan) |
| Google (Gemini API) | Default LLM for narratives; vision extraction for treatment plans, EOBs, perio charts, insurance cards Text inputs are PHI-scrubbed. Image inputs go through unmodified because the image itself often contains the data we are trying to extract (CDT codes, fees) — until BAA is executed, do not upload images that contain identifying patient information. | United States | Image only (vision) | Pending |
| Claim.MD | Clearinghouse for 837D claim submission Submissions to a real payer are blocked from production until the Claim.MD BAA is executed. | United States | Yes | Pending |
| Stripe | Payment processing + billing meter PCI-DSS Level 1. | United States | No | Not required (no PHI) |
| Sentry | Error monitoring Configured with PII scrubbing. | United States | No | Not required (no PHI) |
Notification of changes
To be notified whenever this list changes, email security@aidentalclaims.com and ask to be added to our subprocessor-change distribution list. We will email subscribers at least thirty (30) days before a new PHI- handling subprocessor is added.