Privacy and analytics

Website measurement

Where enabled, Google Analytics 4 uses analytics cookies and sends device/browser information and activity to Google. This is not anonymous or cookieless measurement. CKERS sends generic page names and section-to-section navigation labels, with URL queries/fragments and personal page titles removed. Account names, email, support messages, buyer notes, precise location, authentication codes and tokens are not analytics event inputs.

CKERS does not enable Google Signals or advertising personalization in its integration. Standard Google Analytics processing still applies. See Google's privacy policy.

The initial no-popup policy enables browser analytics only for eligible US traffic. Global Privacy Control and Do Not Track disable it. In other or unknown locations, and on token-bearing connection/recovery pages, CKERS omits the Google tag and uses first-party aggregate request counts. No consent popup is shown. Analytics cookies are configured to expire after 90 days without extending expiry on later visits.

Aggregate service counts

CKERS records daily page-request and AI integration request/outcome totals. These counters contain fixed section, method and agent-category labels, not IP addresses, visitor IDs, full URLs, request arguments or message contents. They do not measure unique people or sessions. First-party totals pool current and legacy service traffic without a host dimension. A connect page listed by CKERS can bind that agent to the connection. Other agent labels require an operator-reviewed connection mapping; unverified attribution is Unknown. When a measurement secret is configured, the same fixed labels are also sent to Google Analytics as mcp_rpc events under one shared client id, not an account or token. Reports cover up to 90 days; historical aggregate rows are retained. Aggregates are available only to the authorized analytics viewer.