Don’t trust our privacy policy. Check the script.
Everything below is computed live from the exact file your visitors’ browsers download from https://t.aydex.cloud/script.js. No marketing copy — string checks, a hash, and the exact fields that leave the browser.
Live checks on the served script
- ✓Never reads or writes cookiesNot present in the served script
- ✓No canvas fingerprintingNot present in the served script
- ✓No audio fingerprintingNot present in the served script
- ✓No WebGL / GPU fingerprintingNot present in the served script
- ✓No font enumerationNot present in the served script
- ✓Does not log keystrokes or form inputNot present in the served script
- ✓No session recording (no DOM serialization)Not present in the served script
- ✓Sends data only through image / beacon requests to its own collectorNot present in the served script
- ✓Uses no browser storage unless you opt in with data-storageStorage code exists but only runs when data-storage is set
0c4d8f02314f34f1b9ca1d18faecc46b48b5ce6c1ccc21418a9913b3becd69e8Verify it yourself:
curl -s https://t.aydex.cloud/script.js | sha256sum
The script is ~11 KB, unminified and readable. If the hash ever changes, the script changed — pin it with Subresource Integrity if you want to be told.
Exactly what leaves the browser
One image or beacon request per event, parameters in the query string:
- s
- Your site’s tracking id
- p
- Page path and query string
- r
- Referrer (the server keeps only the host name)
- w
- Screen width, to tell phone from desktop
- e / ep
- Event name and small JSON properties — only when you call aydex.track() or a behaviour signal fires
- v
- Random visitor id — only if you opt in with data-storage
Open your browser’s network tab on any tracked site and compare. Behaviour signals (rage clicks, dead clicks, JS errors, scroll depth, outbound and download clicks) send a count and a CSS selector or sanitised message, nothing else.
What is never collected
- ✓Cookies, fingerprints, canvas / audio / WebGL / font probing
- ✓Keystrokes, form fields, page text or screenshots — there are no session recordings
- ✓Stored IP addresses — the IP is used to derive a daily-rotating hash and a country code and is never written to the analytics database; it only appears in a short-lived rate-limit counter that expires within about a minute
- ✓Cross-site identifiers — a visitor on one site can never be matched to another site
Scope of this proof. The checks above cover what the script can do in a visitor’s browser. How the server handles a request (hashing, discarding the IP, retention of two years) is defined in the open-source tracker; you can read it and, if you self-host, run it yourself.
Respect Do Not Track by adding data-respect-dnt="true" to the snippet.