Sub-processor List

Last updated: 2026-07-04

PracticeLien engages the following third-party sub-processors to deliver its services. All sub-processors are bound by data processing agreements and, where applicable, HIPAA Business Associate Agreements (BAAs). We will notify subscribers of material sub-processor changes at least 14 days in advance.

Sub-processorPurposeRegionBAA
Microsoft AzureCloud compute (App Service for the web application, Container Apps jobs for background sync), managed SQL Server database (Azure SQL Database), object storage (Blob Storage), message queues (Service Bus), secrets management (Key Vault), and structured logging and monitoring (Azure Monitor and Log Analytics).centralus (United States)Yes
ClerkMulti-tenant authentication, user management, organization (tenant) management, MFA enforcement, and role-based access control.United StatesYes (available)
StripeSubscription billing and payment processing. No PHI is placed in Stripe metadata fields.United StatesYes (available for healthcare)
ResendTransactional email delivery (digest notifications, invite emails). Email content is limited to operational data and does not include PHI.United StatesYes (BAA available)
SentryApplication error monitoring and performance tracing. All events are scrubbed of PHI before transmission using Sentry's beforeSend hook and PII scrubbing configuration.United StatesYes
DocuSealElectronic signatures for lien documents and settlement authorizations. DocuSeal Cloud used with synthetic data only until BAA is executed.United StatesReview in progress

We will notify subscribers at least 14 days before adding or replacing a sub-processor. To object to a change, contact legal@practicelien.com within the notice period.

Third-party integrations (not sub-processors)

The following services are integrated with PracticeLien but are not sub-processors. The practice holds a direct contractual and BAA relationship with each.

IntegrationRelationshipRegionBAA
DrChronoEHR data source — PracticeLien reads patient, appointment, and billing data from DrChrono via its API under the practice's existing DrChrono subscription. DrChrono is not a sub-processor of PracticeLien; the practice holds the direct relationship and is responsible for its own BAA with DrChrono.United StatesCustomer-managed (DrChrono and Practice direct)