Last updated: September 29, 2026
AlertKick uses a small number of third-party providers to run the service. This page lists each one, why we use it, what data it sees, and where it runs. It forms Annex III of our Data Processing Agreement.
| Provider | Purpose | Data processed | Location |
|---|---|---|---|
| Hetzner Hetzner Online GmbH (Germany) | Infrastructure hosting: dedicated servers running the AlertKick platform, databases, and message queues. | All Customer Data, stored in the region the customer selects. | EU accounts: Helsinki, Finland. US accounts: Ashburn, Virginia, USA. |
| Cloudflare Cloudflare, Inc. (USA) | DNS, TLS termination, DDoS protection, edge routing, and rate limiting for alertkick.com and tenant subdomains. | Traffic metadata and request content in transit; no storage of Customer Data at rest. | Global edge network; requests are routed to the customer's home region. |
| Amazon Web Services Amazon Web Services EMEA SARL (Luxembourg) / Amazon Web Services, Inc. (USA) | AI inference through Amazon Bedrock for AI Features (analysis, triage, incident summaries); object storage and CDN for agent package downloads. | Event and alert content submitted for analysis (transient, not retained by AWS for model training); no Customer Data in package distribution. | Bedrock: eu-west-1 (Ireland). Package CDN: global edge. |
| Mailgun Sinch Email (Mailgun Technologies, Inc.), EU region | Transactional email: alerts, invitations, verification, billing and account notices. | Recipient email addresses, message subject and body (which may include alert content). | EU (smtp.eu.mailgun.org). |
| Stripe Stripe Payments Europe, Ltd. (Ireland) / Stripe, Inc. (USA) | Payment processing, invoicing, and subscription management. | Billing contact details, payment method (held by Stripe, not by AlertKick), invoice history. | EU and USA. |
These providers receive data only when the relevant feature is turned on: an administrator of your account connects the integration or enables the channel, or, for website analytics, a visitor accepts analytics in the cookie banner. Turning the feature off stops the flow.
| Provider | Purpose | Data processed | Location |
|---|---|---|---|
| Twilio Twilio Ireland Limited / Twilio Inc. (USA) | SMS and WhatsApp alert delivery and phone-number verification. | Phone numbers and message content for users who enable SMS or WhatsApp. | USA and regional carrier networks. |
| Expo Expo (650 Industries, Inc., USA), relaying to Apple Push Notification service and Firebase Cloud Messaging | Mobile push notification delivery for the AlertKick app. | Device push tokens and notification title/body (alert summaries). | USA. |
| Slack Slack Technologies, LLC (Salesforce, USA) | Alert delivery, acknowledgement, and the Kicker assistant inside a Slack workspace the customer connects. | Workspace and channel identifiers, bot token, alert content, and the email of members who act on alerts (for attribution). | USA (or the data residency region of the customer's Slack workspace). |
| Microsoft Clarity Microsoft Ireland Operations Limited / Microsoft Corporation (USA) | Usage analytics and session replay on the marketing website (alertkick.com), loaded only after the visitor consents in the cookie banner. Not used in the application. | Website visitor interactions (clicks, scrolls, page paths), device and browser information, IP address (truncated by Microsoft), Clarity cookies. Typed text is masked. | EU and USA. |
| AI Chat for Website Chat service at app.aichatforwebsite.com, under common ownership with AlertKick Ltd; hosted on OVHcloud infrastructure (USA) | Chat widget on the marketing website (alertkick.com): visitor questions answered by an AI assistant and by our team. Loads on every page of the website. Not used in the application. | Website visitor page views (page address, title, referrer, UTM tags, language, time zone, screen size), a random visitor ID held in local storage, IP address, and whatever the visitor types into the chat. | USA. |
| Telegram Telegram FZ-LLC (UAE) / Telegram Messenger Inc. | Alert delivery to Telegram chats the customer connects. | Chat identifiers and alert content. | Global (Telegram data centres). |
If you choose to sign in with a third-party identity provider, that provider processes the sign-in as an independent controller under its own privacy policy. We receive your name, email address, and a provider user ID.
When you create an account you choose a home region, EU or US. Your account database, event store, and message queues live on dedicated servers in that region and stay there. Requests from other regions are routed to your home region at the edge. Providers marked as global (Cloudflare edge, package CDN) handle data in transit only.
We will update this page before adding or replacing a sub-processor that will process Customer Data, and give customers with a paid plan at least 30 days' notice by email to account administrators. If you object on reasonable data-protection grounds and we cannot offer an alternative, you may terminate the affected subscription as described in the Data Processing Agreement. To receive notices of changes, or to ask about a provider, email privacy [at] alertkick [dot] com .
Internal tooling that does not process Customer Data (for example our CI system, source hosting, and internal monitoring) is not listed.