Privacy Policy

1. What is processed at the edge

When your browser requests this site or its API endpoint (/api/me), the request is handled on Cloudflare edge infrastructure. The application reads the technical metadata that every web request carries — your IP address, network details, approximate IP-based geolocation, and the headers your browser sends — and reflects it back to you so you can see it.

The /api/me response is returned only to the client that made the request, with private, no-store caching directives so it is not stored by shared caches. The application keeps no server-side log of these requests.

IP-based geolocation is approximate. It is derived from network registration data, not GPS, and typically resolves to a city or region at best.

2. What stays in your browser

The browser-side diagnostics shown on the page — canvas, audio, WebGL, font, and WebRTC signals, along with device and display details — are computed locally by scripts running in your own browser. The application never transmits these values to any server.

You can copy or download your own report from the page. That copy is created locally and stays entirely under your control.

3. The visitor counter

To show aggregate visitor numbers, the service stores one-way salted hashes derived from the IP address (and from the IP address combined with the user agent) in Cloudflare Durable Object storage. These hashes are used solely to count distinct IPs and devices in aggregate.

Raw IP addresses are not stored for this counter, the hashing is one-way and salted so the stored values cannot be reversed into an IP address, and the hashes are not used to identify or profile individual visitors.

4. Visit notifications

On each visit, the operator of kuick.online receives a real-time notification. It contains the technical details already shown to you on this page — your approximate IP-based location (IP address, country and city), your browser, operating system and device type, your timezone and language, your screen and viewport size and color-scheme preference, and the referring URL. It also includes a random visit identifier stored in your browser, together with a count of your visits and the city of your previous visit.

This is used to monitor and understand the site’s traffic. It is derived from the same request metadata that every website receives; the random identifier is stored locally in your browser’s local storage and can be cleared by clearing this site’s data. No account, name, email address or precise GPS location is involved.

5. Analytics, cookies and opt-out

The page loads a third-party analytics script that is enabled by default. To measure how the service is used and help improve it, the analytics service may set first-party cookies, use local storage entries and a device identifier, and record usage events (such as page views and interactions) and, depending on its configuration, session snapshots or replay.

You can opt out of analytics at any time using the control on the Cookie Policy page, and collection stops on that device. The integration also honors the Do Not Track and Global Privacy Control browser signals, as described below.

Separately from analytics, the cookie notice shown on the page stores a single acknowledgment flag in your browser’s local storage so the notice is not shown again on this device. The Cookie Policy describes everything the site places in your browser.

6. Do Not Track and Global Privacy Control

The analytics integration honors the Do Not Track (DNT) and Global Privacy Control (GPC) signals. If your browser sends either signal, it is respected. The page also shows you whether your browser is sending these signals, as part of the diagnostics.

7. Hosting infrastructure

The site runs on Cloudflare, which provides the hosting and CDN infrastructure. Like any network provider, Cloudflare processes standard network metadata (such as IP addresses and request information) to deliver and secure the service, under its own terms and privacy policy. That processing is performed by Cloudflare as an infrastructure provider and is separate from what this application itself stores.

8. Data retention

• Request logs: the application keeps no server-side log of raw requests, IP addresses, or headers.
• Visitor counter: the salted, one-way hashes described above are retained in aggregate to keep the distinct visitor counts working.
• Analytics: data collected by the third-party analytics service is handled according to its configuration; collection stops on devices that opt out or send a Do Not Track or Global Privacy Control signal.

9. Your choices

• Opt out of analytics: use the opt-out control on the Cookie Policy page at any time; collection stops on that device.
• Send a privacy signal: enable Do Not Track or Global Privacy Control in your browser; the analytics integration honors both.
• Manage cookies in your browser: block or delete cookies and site data for kuick.online in your browser settings.
• Keep your report local: the copy and download features produce a local file that is never uploaded by the application.

10. Changes to this policy

This policy may be updated as the service evolves. The date at the top of this page shows when it was last revised. Material changes will be reflected here. Use of the site is also subject to the Terms of Service; cookies and similar storage are covered in the Cookie Policy.