1. Which data this covers
Kaidn handles two different kinds of data, and the distinction decides who is responsible for what. For your account and billing data we are the controller. For the event data you send us about your own end users, you are the controller and we are your processor. The table below covers both; the receives column says which.
Full detail on roles and legal bases is in the Privacy Policy.
2. Third parties that receive data
| Recipient | Purpose | What it receives | Location |
|---|---|---|---|
| Contabo GmbH | Hosting — the servers the Service runs on | All account and event data, as the underlying infrastructure | Germany (EEA) |
| Paddle | Merchant of Record — payments, invoicing, sales tax | Your name, billing email, country and plan. Card details go to Paddle directly and never reach us | United Kingdom |
| Cloudflare, Inc. | DNS, TLS and Turnstile bot protection on sign-up and demo forms | For Turnstile: the visitor's IP address and challenge token | United States / global edge |
| Google (Analytics) | Website analytics on kaidn.io — never the API or your event data | Visitor IP, analytics cookie identifier, pages viewed | United States |
| Anthropic / OpenAIno personal data | AI-written reason text. Off unless narration is enabled | Signal-level evidence only — reason codes, ASN, country, line type. No email address, IP, phone number or device identifier is ever included | United States |
| Email & phone intelligence providersno personal data | Disposable-mailbox detection, domain age, and North American carrier / VoIP line type | A domain (e.g. example.com), or the first six digits of a North American number — the area code and exchange. Never an email address, never a full phone number, never anything identifying the person behind it | United States |
3. Why several rows say “no personal data”
Where an enrichment only needs a category, we send the category rather than the person. Disposable-mailbox detection is a property of the domain, so only the domain is sent. Carrier and VoIP detection is a property of the number range, so only the first six digits go — the digits that identify the subscriber never leave our servers.
The same principle applies to AI narration. The model receives reason codes and derived signals such as ASN and country. It never receives an email address, IP, phone number or device identifier, and it never makes the decision — rules decide, the model only explains what the rules found.
Where we test a domain’s mail server directly, we ask about a randomly generated address that cannot exist, never the address being checked. That probe is off by default.
4. Sources we download from (these receive nothing)
These are commonly listed as third parties by other vendors. They are not sub-processors, because data travels only one way — we fetch a file and match against it locally.
- MaxMind GeoLite2 / DB-IPIP geolocation and ASN databases are downloaded as files and queried entirely on our own servers. No IP address is ever sent to MaxMind or DB-IP.
- The Tor ProjectThe public exit-node list is downloaded and matched locally.
- FireHOL, disposable-domain and proxy-range feedsPublic blocklists downloaded on a schedule and stored locally. Matching happens on our servers.
5. Changes to this list
We will give at least 30 days’ notice before adding or replacing a sub-processor that handles customer event data, by updating this page and emailing the account owner. If you object on reasonable data-protection grounds within that period, contact us and, where we cannot offer an alternative, you may terminate the affected part of the Service without penalty.
To be notified of changes, email support@kaidn.io and we will add you to the list.