Privacy
This site measures itself, and this page says exactly how. The short version: no cookies, nothing written to your device, no advertising network, and no analytics company. The long version is below, because "we value your privacy" is not information.
Who is asking
The site is published by Adx.cool, and hosted on a server the publisher rents from Hostinger International Ltd, located in Paris, France. Your data does not leave the European Union.
Analytics, and why there is no banner
Visits are counted with Umami, an open-source analytics program running on that same server. It is not a hosted service: no third party receives anything, and the tracking script is served from this domain rather than from an analytics vendor's.
Three facts follow from that, and they are the reason this page is not accompanied by a consent dialog:
- Nothing is stored on your device. No cookie, no local storage, no fingerprint. The script reads one value — a key you can set yourself to opt out, described below — and writes none.
- Your IP address is not kept. It is used, in memory, to derive a country and to group a visit together, then discarded. There is no column for it in the database.
- You are not followed anywhere else. The tracker is pinned to this domain, and no identifier is shared with any other site.
Under the French rules on audience measurement, a first-party, self-hosted, cookieless setup of this kind does not require consent — but it does require telling you, which is what this page is for.
What is recorded
For each visit: the pages seen and in what order, the site or search engine you arrived from, your browser, operating system, device type, screen size, language, and an approximate location derived from your IP — country, region, city. Never a name, an address, or an account. Also how fast each page loaded and settled (Core Web Vitals).
The events
Beyond page views, the site records 17 kinds of event on purpose. Each exists to answer one question, and none of them identify you. Each also carries the kind of page it happened on and, on a product's page, that product:
| Event | What it carries | Why it exists |
|---|---|---|
Store click | store, product, placement, page | Which profile someone left to buy, and from which button — a catalogue card, a product page, or the simulator. |
Outbound link | url, kind (shortcutposters, video, social, elgato, other), page | Where a visitor went when it was not to a store. |
Deck pressed | page | Whether the visitor tried the simulated deck at all. Fired once per page, not once per key. |
Search empty | query, page | What someone looked for and this catalogue does not have. Sent once the typing stops, not on every letter. |
Search, Search result, Catalog search | the words typed (cut at 40 characters, dropped if they look like an email address or a phone number), how many results, which one was opened | What people look for, in the ⌘K palette and the catalogue, and whether they find it. |
Catalog filter, Currency | which filter or currency, the value chosen | Which ways of narrowing the catalogue are used. |
Deck OS, Deck theme | macOS or Windows, the theme chosen | Whether the simulator's switches are used, and which computer the visitor shops for. |
Section reached, FAQ opened, Tutorial script opened | the section's name, the question opened | How far down a page people read, and which questions they need answered. |
Profile requested | the app's name — never the email address | Which profiles are asked for, to build them in that order. |
Review sent | store | That the review form works, and from which store's buyers. |
Builder entry | placement, page | Which link brought someone to the Deck Builder — the header, the landing, the catalogue, the footer. |
Catalog profile opened | product, placement, page | Whether the Deck Builder's shortcut picker sends people on to the catalogue, or replaces it. |
Icon maker … | the model, the template, how many keys — never what is on them | How far a deck gets in the Deck Builder: started, opened, shared, exported as an icon pack. |
Profile … | the model, the computer (Mac or Windows), where the visitor came in from | The Builder Pro path: the price shown, the checkout opened, a licence checked (valid or not — never the key), a profile exported. |
Tutorial played | the chapter it started from, the page it is on | Whether the Builder Pro tutorial gets watched, from which page, and which chapter people jump to first. |
Builder error | the step that failed and a short reason code (for example sync, network) — never your deck | To see when an export, a licence check or a sync fails for people, and fix it before they have to write in. |
Sale | product, amount, currency, the button that led to it, the buyer's country — sent by Gumroad, not by your browser | Whether anyone paid. Gumroad tells this site's server about each sale; nothing about the buyer but the country is passed on. |
How long
13 months, then it is deleted automatically. Thirteen rather than twelve so that one January can still be compared with the one before it.
Opting out
Two ways, both of which work without asking anyone. Any content blocker will stop the script — it is not hidden from them, only served from a path they do not recognise. Or, in your browser's developer console on this site, run:
localStorage.setItem('umami.disabled', '1')That key is the one value the script reads. With it set, nothing is sent at all, from that browser, until you remove it.
Forms
The request, support and review forms send what you type to our own server, the one that serves this site, which keeps it and emails it to us. It is deleted six months after we have dealt with it, and after a year at most. The address you give is used to reply to you — and to tell you when the profile you asked for exists — and for nothing else. The newsletter field collects addresses for a mailing that does not exist yet — nothing has ever been sent, and if that changes you will be told before it does.
The Deck Builder
The decks you build in the Deck Builder are kept in your browser's own storage — every one of them, listed under My decks — and nothing you make or upload leaves your computer: the keys are drawn and zipped on the page itself. A share link carries the deck inside the link, after the #, which browsers never send to a server. Profile export keeps two more things in that storage: which deck used your free profile, and your licence key once it has been checked. To check a key, the page sends the key — and nothing else — to this site's own server, which asks Gumroad whether it belongs to a purchase; neither the key nor your address is written down. If you switch on sync, your decks are kept on this site's server as well — names, colours, icon names, labels and actions, a few kilobytes each, never the pictures you uploaded — in a file named after a one-way fingerprint of your licence key, so that key opens them on another computer. Delete my synced decks, under My decks, removes that file.
Third parties
Fonts and every asset are served from this domain. Nothing loads from a content network, an advertising exchange, or a font service. Three exceptions, all of which you trigger yourself:
- Elgato Marketplace and Gumroad — Only if you click through to buy. Nothing is sent before the click. The link carries a campaign tag identifying the product and the button, not you. Their policy.
Your rights
You can ask what is held about you, ask for it to be corrected or deleted, and object to it being collected. In practice the honest answer to the first question is usually "nothing that could be linked to you", since no identifier is stored — but ask anyway and you will get a real answer. Write to adxcool@pm.me. If the reply does not satisfy you, you can complain to the CNIL at cnil.fr.
Changes
This page is dated rather than versioned. Last substantive change: . If what the site measures changes, this page changes in the same commit — that is a rule the code enforces, since the facts above live in one module the pages read from.