pqlq.com

Privacy notice — what this mirror logs, what it avoids, and the signals it respects.

The short version

pqlq.com shows you your own request details. We don’t sell data, we don’t build advertising profiles, and we don’t run third-party trackers beyond the analytics described below. Geo / ASN / network lookups happen locally on our server from downloaded databases — your IP is never sent to a third-party lookup API.

What we log

Access logs
Standard web-server logs: timestamp, requested path, status code, your IP, and User-Agent. Used for abuse prevention, debugging, and aggregate traffic stats. Rotated and retained for a limited window.
No account data
There are no accounts, no passwords, no email collection on the public site.
No cross-site tracking
We set no advertising or cross-site tracking cookies. The only cookies that can be set are first-party functional/test cookies that you explicitly trigger via a same-origin or direct-client call to the /cookies/set testing endpoint. Cross-site browser-triggered writes are rejected; test cookies expire after an hour and are never read for tracking.

Analytics

We use Google Analytics (GA4) with IP anonymization enabled to understand aggregate traffic — which pages are popular, rough geographic distribution, and referral sources. We do not use it to identify individuals.

We honour Do Not Track and Global Privacy Control. If your browser sends DNT: 1 or Sec-GPC: 1, the analytics script is never loaded for your visit — no request to Google is made at all. You can verify this on the home page: those signals are shown under “Privacy & preferences.”

DNS leak, WebRTC & fingerprint features

The “DNS leak test,” “WebRTC probe,” and “Browser fingerprint” sections exist to show you what your browser and network may reveal. The fingerprint is computed client-side and displayed to you; we don’t store it. The WebRTC probe uses public STUN servers (Google, Cloudflare) to discover your public IP. The DNS leak test uses unique probe hostnames on our authoritative DNS service and watches which resolvers query them; it is a heuristic, not a perfect statement of your browser’s active DNS path.

Data sources

Geolocation and network data come from local copies of public databases: DB-IP Lite (CC BY 4.0), the five Regional Internet Registries, PeeringDB, RPKI validated ROAs, the Tor Project exit list, published cloud-provider IP ranges, IPinfo Privacy Detection when configured, Spamhaus DROP lists, and Googlebot/Applebot published crawler ranges. See About for the full list and licensing.

Contact

Privacy questions: [email protected]
Security reports: [email protected] (see security.txt)