Sub-processor list
Last updated: 2026-05-08
This page lists the Sub-processors Silux engages to deliver Silux Connect. We notify customers at least 30 days before adding a new Sub-processor or making a material change to an existing one. Subscribe via the RSS feed at /subprocessors/feed.xml or the mailing list at subprocessors-announce@siluxconnect.com to be notified.
| Vendor | Purpose | Personal data shared | Region | DPA / SCCs |
|---|---|---|---|---|
| Amazon Web Services | Primary hosting (compute, storage, KMS, RDS) | All tenant data, encrypted at rest | US, EU (Ireland), APAC | AWS DPA + SCCs |
| Hetzner Online GmbH | EU relay infrastructure | Encrypted relay traffic (ciphertext only) | EU (Germany, Finland) | Hetzner DPA |
| Cloudflare | CDN, WAF, DDoS protection, DNS | IP addresses, request metadata | Global edge | Cloudflare DPA + SCCs |
| Stripe | Payment processing, subscription management | Billing contact, billing address, payment instrument, invoices | US + EU | Stripe DPA + SCCs |
| Grafana Labs (Grafana Cloud) | Operational telemetry and dashboards | Pseudonymous metrics, request traces | US, EU | Grafana DPA + SCCs |
| PostHog | Product analytics (cookie-gated, opt-in) | Pseudonymous event stream, feature flag evaluations | EU (preferred), US | PostHog DPA + SCCs |
| Sentry (Functional Software, Inc.) | Error tracking and performance monitoring | Stack traces, scrubbed request context | US | Sentry DPA + SCCs |
| Apple Push Notification Service | iOS push notifications | Device push token, notification payload | US | Apple DPA |
| Google Firebase Cloud Messaging | Android push notifications | Device push token, notification payload | US | Google DPA + SCCs |
| Apple App Store | App distribution and in-app purchases (mobile) | App Store account identifier (when purchased through store) | US | Apple DPA |
| Google Play | App distribution and in-app purchases (Android) | Play account identifier (when purchased through store) | US | Google DPA + SCCs |
| Slack Technologies | Optional integration — alerts and notifications | Channel webhook URL, alert payload | US | Slack DPA + SCCs |
| Microsoft Teams | Optional integration — alerts and notifications | Webhook URL, alert payload | Per tenant | Microsoft DPA + SCCs |
| Vanta | Continuous compliance evidence collection | Pseudonymous configuration evidence; no Customer Data | US | Vanta DPA + SCCs |
| Atlassian (Statuspage) | Public status page at status.siluxconnect.com | Subscriber email (only if subscribed to status updates) | US | Atlassian DPA + SCCs |
| HackerOne | Vulnerability disclosure intake (see /vulnerability-disclosure) | Researcher contact, report content | US | HackerOne DPA + SCCs |
| Postmark / SendGrid | Transactional email | Email recipient, subject, body | US, EU | Vendor DPA + SCCs |
| Plausible Analytics | Marketing-site analytics (cookieless) | Aggregate, no personal data | EU (Germany) | Plausible DPA |
Notes on highlighted entries
Slack and Microsoft Teams
Treated as integrations rather than sub-processors in the strict sense (you, the Controller, configure the destination). Listed here for transparency.
How to be notified of changes
- Subscribe to the RSS feed: /subprocessors/feed.xml
- Subscribe to the announce mailing list: subprocessors-announce@siluxconnect.com
- Watch the trust-portal change-log: trust.siluxconnect.com/changelog
Objecting to a new sub-processor
Customers with a signed DPA may object to a new Sub-processor on reasonable data-protection grounds within the 30-day notice window. See §6 of the DPA at /dpa.
For other questions, contact dpo@siluxconnect.com.