We keep our subprocessor list short and deliberate. Each provider below supports a specific function of the platform. Providers that may handle protected health information ("PHI") are covered by an appropriate agreement; providers that act only as a transport conduit do not have access to readable PHI; and providers used only for non-PHI functions are marked accordingly. For how this fits our overall posture, see our HIPAA & BAA statement.
| Subprocessor | Purpose | Data scope | PHI handling |
|---|---|---|---|
| OpenAI | AI extraction of structured orders from inbound messages | Inbound message content (may contain PHI) | Signed |
| Telnyx | SMS / MMS carrier for inbound and outbound messaging | Message content (transport conduit) | Conduit (no PHI access) |
| Mailgun | Transactional email (sign-in codes, notifications, the contact form) | Account & operational email — no PHI by policy | No PHI |
| Cloudflare | DNS, TLS termination, and edge protection | Encrypted transport metadata | Conduit (no PHI access) |
| Mapbox | Maps and geocoding for live tracking | Coarse address/coordinate lookups | No PHI |
| Wasabi | Encrypted off-site storage for database backups | Encrypted backups (may contain PHI) | In progress |
Changes to this list
We may add or replace subprocessors as the platform evolves. When we make a material change involving PHI, we will update this page and notify affected carriers as required by the applicable Business Associate Agreement. The "Last updated" date above reflects the most recent change.
Questions
For a subprocessor review, a security questionnaire, or to request advance notice of changes, reach us through our contact page.