Subprocessors and other service providers
This page distinguishes between providers that may process customer personal data on Wodby’s behalf and providers used primarily for Wodby’s own business operations.
How to read this page
This page distinguishes between subprocessors used for customer personal data and other Wodby service providers used for Wodby’s own operations.
Wodby uses third-party providers both to deliver customer-facing services and to operate Wodby's own business. Not every vendor used by Wodby is a subprocessor for customer personal data in every context.
This page therefore separates:
- Subprocessors for customer personal data, where a provider may process customer personal data on Wodby's behalf in connection with the services.
- Other Wodby service providers, where a provider is used primarily for Wodby's own controller-side business operations such as marketing or billing.
Subprocessors for customer personal data
These providers may process customer personal data on Wodby’s behalf, depending on the services and features used.
| Provider | Purpose | Typical data involved | Location |
|---|---|---|---|
| Amazon Web Services, Inc. | Cloud infrastructure, compute, storage, backups, and related hosting functions | Account-related data, support data, customer workload data, backups, and operational metadata depending on service usage | United States |
| Google LLC | Cloud infrastructure, compute, storage, backups, and related hosting functions | Account-related data, support data, customer workload data, backups, and operational metadata depending on service usage | United States |
| DigitalOcean, LLC | Cloud infrastructure, compute, storage, backups, and related hosting functions | Account-related data, support data, customer workload data, backups, and operational metadata depending on service usage | United States |
| Intercom, Inc. | Customer support communications and support workflow | Support contact details, ticket content, troubleshooting information, and related communications | United States |
| Functional Software, Inc. d/b/a Sentry | Error tracking and incident diagnostics | Error metadata, logs, stack traces, and related technical diagnostic information | United States |
| Slack Technologies, LLC | Internal operational notifications and support coordination | Account identifiers, event metadata, signup or subscription events, support context, and limited task details pushed into internal notification workflows | United States |
| Bird.com Inc. d/b/a Pusher | Real-time messaging and event delivery | Real-time event payloads, identifiers, and related application or platform messaging metadata | United States |
| GitHub, Inc. | Source code hosting, CI workflows, and issue tracking for services or workflows that use GitHub-based repository or CI features | Repository contents, CI metadata, issue content, and related project collaboration data where customer workflows depend on GitHub | United States |
Other Wodby service providers
These providers are used primarily for Wodby’s own marketing, billing, or business operations rather than as default subprocessors for customer workload data.
| Provider | Purpose | Typical data involved | Location |
|---|---|---|---|
| The Rocket Science Group LLC d/b/a Mailchimp | Email marketing and newsletter delivery for opted-in contacts | Marketing contact details, email address, campaign engagement data, and subscription preferences | United States |
| Stripe, Inc. | Billing, payment processing, invoicing, and related account administration | Billing contact data, transaction identifiers, invoice data, and payment-related account information | United States |
Important notes
Actual provider usage can depend on deployment model, purchased features, region, and customer workflow choices.
Not every customer uses every provider listed above. Provider usage can depend on the service model, purchased plan, enabled features, region, and whether the customer uses Wodby Cloud, customer-owned infrastructure, specific support channels, or GitHub-based workflows.
For customer-owned infrastructure, the customer may also separately engage cloud or server providers under the customer's own direct agreement. Those direct customer-provider relationships are not always the same thing as a Wodby subprocessor relationship.
Updates and questions
Wodby may update this page as provider relationships and processing activities evolve.
Wodby may update this page from time to time as services and provider relationships evolve. Questions about subprocessors or service providers can be sent to [email protected].