Outway · Policies
Providers & Subprocessors
Identified services supporting Outway and the distinction between active delivery and configured integrations.
Last updated: 10 October 2026
Service-provider information
This page lists identified providers and connected services. It is not a certification of a complete production infrastructure audit or a promise that every integration is active. A provider’s legal role depends on the service and agreement; a customer-authorized data source is not automatically our subprocessor.
| Provider or service | Purpose and information involved | Current scope |
|---|---|---|
| Cloudflare | Website delivery, request security and website measurement; request and device information | Observed in the public website delivery path. Current settings and processing locations require operational confirmation. |
| Hetzner | Configured email transport and S3-compatible storage; email delivery data and stored artifacts when enabled | SMTP relay access and storage bucket access have been checked. These checks do not establish complete production activation or residency guarantees. |
| Stripe | Subscription checkout and billing; customer, subscription and payment-status information when enabled | Sandbox integration configured. Live payments are not established by sandbox testing. Stripe’s own terms and privacy notice also apply. |
| Optional customer-authorized Search Console and Google Ads reports | Separate connection and approval required. Google is a data source; access is not enabled merely by creating an Outway account. | |
| Your chosen AI service | Data accessed using the permissions and sharing choices you grant | Customer-selected recipient, not an automatically enabled Outway provider. Review that service’s terms before granting access. |
Core collection is implemented by Outway. Firecrawl is not a runtime dependency. Optional external search or model providers are not implied to be active by the presence of an adapter.
Business processing and changes
For the complete provider, hosting-location and contractual information applicable to your deployment, contact [email protected]. Specific subprocessor authorization, change notification, objections and international-transfer safeguards belong in an agreed Data Processing Agreement. We will update this page when relevant provider arrangements change.