Trust

Sub-processors.

Current and proposed service providers for the pilot. An active account agreement does not mean every service or patient-data flow is approved. Proposed patient-call and messaging providers remain blocked until their agreements and settings are verified.

Last updated · October 15, 2026

Vendor

Purpose

Data

Agreement evidence

Location

Amazon Web Services ↗

Production compute (ECS on Fargate), PostgreSQL database (RDS), encrypted storage (S3), keys, logs, and transactional email (SES). Account Business Associate Addendum accepted September 21, 2026; each PHI flow is still verified before use.

PHI-capable

Active—scope open

US East (Ohio)

Retell AI ↗

Proposed patient-call voice service. No live patient calls until agreement and configuration are verified.

PHI-capable

Unverified

To verify

Twilio ↗

Proposed patient phone and SMS service. Account edition, covered services, and agreement remain unverified.

PHI-capable

Unverified

To verify

Clerk ↗

Staff authentication. Patient information must stay outside auth profiles and telemetry unless the boundary is reviewed.

Operational

Boundary review

To verify

Stripe ↗

Business billing. Source production configuration disables patient deposits; deployed runtime still needs verification.

Billing

Boundary review

To verify

Google Workspace ↗

Business email and files. Patient information must stay out until the Workspace agreement and settings are verified.

Operational

Unverified

To verify

PostHog (optional) ↗

Marketing analytics when enabled, without patient content or session replay.

Operational

Boundary review

To verify

Sentry (optional) ↗

Error monitoring when enabled; patient-content exclusion requires verification.

Operational

Boundary review

To verify

Subscribe to updates

For provider updates or a customer-specific notice commitment, email trust@louneh.ai with subject “Provider updates”. Notice terms in an executed customer agreement control.