Who operates traffic.cx
traffic.cx is operated by Karthick, based in Erode, Tamil Nadu, India. This notice covers information used to operate the service and information customers send through analytics and revenue integrations.
For privacy questions or requests, email karthisclan@gmail.com. If your question concerns a website using traffic.cx, contact that website’s operator about its collection choices.
Information we process
We use information to provide reports, connect traffic to revenue, manage accounts and teams, provide support, and protect the service from abuse.
- Account information: your name, email address, profile image if supplied, team memberships, permissions and settings. Sign-in records can include IP addresses, browser user agents, session identifiers and connected sign-in provider information.
- Analytics: page addresses, referrers, campaign tags, timestamps, pageviews, engagement, custom events and properties, approximate location, browser/device information, and visitor and session identifiers.
- Revenue: payment and order identifiers, amounts, currencies, refunds, subscription events and attribution links. Connected providers may send customer identifiers or email addresses. Normalized records use keyed customer identifiers and masked display hints; provider payloads can contain additional personal information during processing and retries.
- Support and subscriptions: messages you send us and information needed to manage your plan, billing enquiries and refund requests.
Cookies and visitor identification
The default analytics tracker does not set a visitor cookie. The collector processes IP addresses and user agents for location, filtering, rate limiting and a site-specific visitor identifier derived with a rotating daily secret. Previous-day identifiers can help continue a session across midnight.
The main analytics event record does not contain a raw IP-address or raw user-agent field. Account sessions and infrastructure logs are separate; this is not a claim that no personal data is processed anywhere in the service.
Optional cookie mode uses a first-party tcx_vid cookie with a configured lifetime of up to 400 days, refreshed when written. Browsers may shorten this. The tracker does not write this cookie when it detects Global Privacy Control. Dashboard sign-in uses separate authentication cookies; account sessions are configured for 30 days and may renew through use.
Whether consent is required depends on the website, tracking configuration and applicable rules. Website operators are responsible for their notices and permissions.
Information chosen by website owners
The tracker sends page URLs for processing. Most query parameters are removed from stored page paths by default, while campaign tags and explicitly retained parameters are processed separately. Paths, custom properties and tracked link URLs can still contain personal information.
Do not send passwords, secrets, sensitive information or unnecessary personal data through analytics. Team permissions govern access to reports. If you enable a shared dashboard, review what its link exposes before sharing it.
Hosting and other providers
The documented hosting setup uses a Hostinger VPS in India and Cloudflare for website delivery and traffic routing. Requests pass through Cloudflare’s infrastructure, so processing is not limited to a single country. We do not promise EU-only hosting.
Optional Google sign-in involves Google. Revenue integrations exchange information with the payment providers you choose to connect. Dodo Payments is the provider selected for traffic.cx subscriptions; its terms and privacy information apply when you use its checkout.
Information is shared as needed to provide these functions, respond to your requests, protect the service or meet applicable legal requirements. Contact us if you need information about processing arrangements for your organization before sending data.
Retention and deletion
Historical analytics, payment records and account records do not currently have a general automatic expiry. Deleting a site disables it in the application; it does not automatically erase its historical analytics or payment data. Canceling a subscription or receiving a refund is also separate from deleting data.
Successful or ignored revenue webhook processing clears the stored payload body. Failed payloads may remain for retry. Eligible delivery records are scheduled for cleanup after 30 days, except failures still awaiting retry. A separate intermediate revenue-event table expires after 30 days; the main analytics and payment records do not share that expiry.
To request account closure or deletion, email karthisclan@gmail.com. We will review the request, establish which records it concerns and explain any records that must be retained for legal obligations or an unresolved dispute. Do not treat a site-removal button as confirmation of complete erasure.
Your questions and choices
Contact karthisclan@gmail.com to request access to or correction of account information, deletion, or to raise an objection or other privacy concern. We may need information to verify your identity and authority over the affected account. Rights and exceptions depend on applicable law. You may also raise concerns with the relevant data-protection authority where that right applies.
We will update this notice when our practices change and display the revision date on this page. Changes do not remove rights provided by applicable law.