Subprocessor register
Every third party in the path of an order.
A subprocessor is any third party that processes data on our behalf to deliver the service. This register names each one, why it exists, the category of data it can see, and where that processing happens. Only two subprocessors handle protected health information: the cloud that runs regulated workloads under a Business Associate Addendum, and the pharmacy of record.
Data sharedPHINo PHI
| Subprocessor | Purpose | Data shared | Region |
|---|---|---|---|
| Amazon Web ServicesPHI · under BAA | Primary cloud — compute, storage, and managed data services that run the platform. | PHI · under BAAApplication data, including PHI, encrypted per-tenant. | US |
| LifeFile / EmpowerPHI · pharmacy | Pharmacy of record. Receives the order and dispenses the prescription; the system of record for clinical data. | PHI · pharmacyPrescription and fulfillment data (PHI) for orders routed to this pharmacy. | US |
| CloudflareMetadata | DNS, CDN, web application firewall, and access control for public and staging surfaces. | Network metadata and request data for public surfaces. No PHI. | Global edge |
| StripeBilling metadata | Payment processing and subscription billing for platform customers. | Billing contact and payment metadata. Card data is handled by Stripe, not stored by NeoLife. No PHI. | US |
| ResendContact metadata | Transactional email delivery — authentication, notifications, and operational alerts. | Recipient email address and message content for transactional mail. No PHI in message bodies. | US |
| PostHogNo PHI | Product analytics, proxied same-origin to keep events first-party. | No PHIPseudonymous product-usage events. No PHI is sent to analytics. | US |
Change notice. We notify customers of material changes to this register before a new subprocessor begins handling covered data, so you always know who is in the path. This list was last updated in July 2026.
Questions about a subprocessor, our BAA, or data residency?privacy@neolife.health