Website traffic privacy
We use first-party analytics managed directly by Kathaka to understand website traffic and distinguish likely people, automation, declared assistant crawlers and suspicious requests.
What is recorded
Requested page paths, response codes, approximate browser and device types, referrer host, optional campaign label, and page interactions such as download clicks and reported time on page. We never read form inputs, passwords, account details or drawing content for traffic analytics. Page query strings are discarded.
A date-scoped cryptographic hash of the connection address and browser identifies visitor-days. It is a pseudonymous estimate, not a count of unique people. Browser session identifiers use session storage and are not reused for cross-day tracking. For new visits, the analytics database also retains the connection IP address alongside that anonymous visitor ID. Authorized studio staff can see it in the activity grid. Older records are not backfilled. Country and city may be recorded from a reliable local lookup; location is approximate and unavailable without that lookup.
Retention and control
Analytics events expire after 90 days. Local request logs have restricted access, rotate daily and expire after seven days. Do Not Track and Global Privacy Control signals opt out of analytics collection.
Classification limits
Client names and browser signals can be spoofed. Reports show the evidence and confidence for each class. Known search crawlers can be verified through network identity checks; other declared crawler identities remain unverified. Country and city are not inferred from browser language.
Questions: support@kathaka.studio.