Providers & subprocessors
Who supports Outloop’s services, and how those providers differ from the tools your business connects.
This operational overview combines providers named in the current Privacy Policy with the reviewed Website and Cloud integrations. It is not an executed DPA schedule or a guarantee of a particular processing location.
| Provider | Role | Information involved |
|---|---|---|
| Google Cloud / Firebase | Website and Cloud hosting, compute, database, authentication and operational services. | Account and operational data; feature-specific data where enabled. |
| Paddle | Checkout, payment processing and subscription billing. | Payment and billing information; Outloop receives billing identifiers and status. |
| TikTok | Authorization exchange when you connect TikTok Ads. | Authorization code and resulting tokens during connection; see the data-flow overview. |
| Postmark | Account, onboarding and lifecycle email. | Recipient details and email content. |
| PostHog | Website and configured product analytics. | Usage events and allowed metadata; website recording subject to the current cookie disclosures. |
| Google measurement services | Tag Manager, Analytics and Ads measurement. | Website usage and attribution under the current cookie disclosures. |
| Meta | Website advertising measurement. | Visit information through the Meta Pixel; see the Cookie Policy for current controls. |
| MailerLite | Guide sign-ups and marketing email. | Contact details, subscription state and email interactions. |
| n8n / Airtable | Receiving and organizing website submissions. | Fields submitted in website forms. |
| Calendly / Zoom | Optional bookings and live sessions. | Details you provide or share when using those services. |
Provider use depends on the service and features you use.
Google Cloud / Firebase
- Role
- Website and Cloud hosting, compute, database, authentication and operational services.
- Information involved
- Account and operational data; feature-specific data where enabled.
Paddle
- Role
- Checkout, payment processing and subscription billing.
- Information involved
- Payment and billing information; Outloop receives billing identifiers and status.
TikTok
- Role
- Authorization exchange when you connect TikTok Ads.
- Information involved
- Authorization code and resulting tokens during connection; see the data-flow overview.
Postmark
- Role
- Account, onboarding and lifecycle email.
- Information involved
- Recipient details and email content.
PostHog
- Role
- Website and configured product analytics.
- Information involved
- Usage events and allowed metadata; website recording subject to the current cookie disclosures.
Google measurement services
- Role
- Tag Manager, Analytics and Ads measurement.
- Information involved
- Website usage and attribution under the current cookie disclosures.
Meta
- Role
- Website advertising measurement.
- Information involved
- Visit information through the Meta Pixel; see the Cookie Policy for current controls.
MailerLite
- Role
- Guide sign-ups and marketing email.
- Information involved
- Contact details, subscription state and email interactions.
n8n / Airtable
- Role
- Receiving and organizing website submissions.
- Information involved
- Fields submitted in website forms.
Calendly / Zoom
- Role
- Optional bookings and live sessions.
- Information involved
- Details you provide or share when using those services.
Customer-selected AI and connected services
Your AI model provider and the services connected to a Workspace process the information sent to them under the applicable account agreements and configuration. They are separate from Outloop Cloud. A customer-selected provider is not automatically an Outloop subprocessor merely because Outloop connects to it.
For example, a cloud model may process prompts or returned business data; an advertising platform processes requests to your account. Optional model-assisted login has its own external model path. See the data-flow overview.
Procurement details
Request the applicable legal entity names, processing roles, locations, contractual safeguards and current provider scope through document requests. These details must be confirmed for your agreement. Merchant-of-record and independently selected services should not be assumed to have the same legal role as a contracted subprocessor.
Website analytics and consent behavior are described in the Cookie Policy. This page does not expand those controls or change existing privacy commitments.