Sub-processors
Last updated 2026-04-30
Wrendex engages the following sub-processors to deliver the Service. Each entry lists the processing purpose, the type of data the sub-processor sees, and the region where the data is processed. We notify customers thirty days before adding a new sub-processor.
Active sub-processors
| Sub-processor | Purpose | Data accessed | Region |
|---|---|---|---|
| Stripe, Inc. | Subscription billing, payment processing. | Billing contact name + email, payment method, billing address. | United States |
| Hetzner Online GmbH | Cloud hosting and compute for our production servers, including the self-managed database cluster that stores crawl results, audit metadata, and account data. Every server uses full disk encryption. | All customer data at rest in our production database and logs. | Hetzner EU (Helsinki, Finland) |
| Wasabi Technologies, Inc. | Object storage for crawl archives and customer exports. | Stored crawl archive files and export files customers generate. | EU |
| Mailgun (Sinch) | Transactional email delivery (audit alerts, password resets, billing receipts). | Recipient email address, the body of the email being sent. | EU |
Each name links to that company’s privacy policy.
Optional, customer-configured
The following are integrations the customer chooses to enable. Wrendex acts as a data exporter only when configured.
- Slack: alert delivery to the customer’s Slack workspace; data exposed is the alert body the customer composed.
- Microsoft Teams: alert delivery via incoming webhook; data exposed is the alert body the customer composed.
- PagerDuty: severity-mapped paging; data exposed is the alert title and severity.
- Customer-provided webhooks: outbound HTTPS webhooks to URLs the customer configures.
Notifications & objections
We notify customers of new sub-processors at least thirty days in advance. Customers with reasonable grounds for objection may raise them via /contact. If we cannot satisfy the objection, the customer may terminate the affected service.