Sub-processors for customer data
These providers process the analytics and revenue data that website owners collect with traffic.cx, under the Data Processing Agreement. Each one is bound by its own data-processing terms.
| Provider | What it does | Data it handles | Where |
|---|---|---|---|
| Hostinger | Hosts the virtual private server that runs the application and its databases. | All analytics, revenue, Search Console and account data stored by the service. | Mumbai, India |
| Cloudflare, Inc. | DNS, website delivery, the edge Worker that receives tracker events, and the encrypted tunnel that carries every request to the server. | Requests in transit: IP addresses, user agents, page addresses and event contents. The edge adds approximate location from the IP address. | Cloudflare’s global network; company in the United States |
| Cloudflare R2 | Stores nightly backups of the databases. | Full copies of the stored data, kept for 30 days. | Western Europe |
Other providers
These providers handle information about traffic.cx customers themselves: account emails, support messages and subscription purchases. The privacy notice covers this information.
| Provider | What it does | Data it handles | Where |
|---|---|---|---|
| Resend | Sends account emails, such as sign-in links and invitations. | Recipient email address and the message. | Stores email logs and account data in the United States |
| Cloudflare Email Routing and Google (Gmail) | Forwards mail sent to support@traffic.cx to the operator’s Google mailbox, where support is answered. | Whatever a support message contains. | Cloudflare’s global network; Google’s data centres |
| Dodo Payments | Merchant of record for traffic.cx subscriptions: checkout, invoices, sales tax and refunds. It acts as its own controller for the purchase. | Purchaser name, email, billing address and payment details. traffic.cx never receives card numbers. | See Dodo Payments’ privacy policy |
| Optional “Sign in with Google”. Google acts as its own controller for your Google account. | Your Google account’s name, email address and profile image, shared with your consent. | Google’s data centres; company in the United States |
Services you connect
Payment providers you connect for revenue attribution (Stripe, Dodo Payments, Lemon Squeezy and Polar) and Google Search Console are your own providers, not ours. traffic.cx reads from them with the access you grant and only for your reports. Disconnecting stops that access.
Not sub-processors
Some services supply data to traffic.cx without receiving any personal data from it.
- DB-IP Lite: an IP-to-location database. Our server downloads the database files once a month and looks addresses up locally; no IP address or other data is sent to DB-IP.
- DuckDuckGo icons: our server fetches the small icons shown next to referring websites, asking only for the website’s domain name. Your dashboard never contacts DuckDuckGo, and no visitor data is sent.
- European Central Bank: our server downloads public exchange rates for currency conversion.
Changes to this list
We tell team owners by email at least 30 days before a new sub-processor for customer data starts processing, and update this page at the same time. The Data Processing Agreement explains how to object. Hosting is planned to move to a dedicated server; that change will be announced the same way.
- 19 October 2026: list first published.