This list is maintained honestly and updated whenever it changes. There are no undisclosed processors.
1. Core infrastructure (always active)
| Provider | Role | What it processes |
|---|---|---|
| Cloudflare, Inc. | Hosting, edge compute (Workers/Pages) and database (D1) | All application data at rest and in transit — account data, business content, logs. |
| Stripe, Inc. | Payments, business verification, payouts, terminal hardware | Payment data, identity-verification data, bank details — collected by Stripe directly; never stored by Hangerline. |
2. Client-side asset CDNs
| Google Fonts | Web font delivery | Visitor IP address and browser metadata when fonts are fetched. |
| jsDelivr | Open-source library delivery (Font Awesome, Axios) | Visitor IP address and browser metadata when assets are fetched. |
3. Merchant-elected connections (active only if YOU connect them)
These providers process data only when a merchant pastes their own API key and triggers an action. They operate under the merchant's direct agreement and billing with each provider — not as Hangerline sub-processors.
| Klaviyo, Inc. | Email marketing (merchant’s own account) | Customer email addresses the merchant explicitly syncs. |
| Shippo (Popout, Inc.) | Shipping rates and labels (merchant’s own account) | Ship-from/ship-to addresses and parcel details for shipments the merchant creates. |
| Twilio Inc. | SMS sending (merchant’s own account) | Recipient phone numbers and message text for messages the merchant sends. |
4. Changes
We update this page before adding any new processor. Material additions are announced to account holders. Last reviewed: 2026-08-03.