Cookies & analytics
What this website measures.
The Applye app collects nothing, ever. This website counts visits two ways: one that stores nothing and identifies nobody, and one that waits for your permission. Neither sets a cookie.
Your current choice
This switch governs Google Analytics, the optional one. The cookieless counter described below is not affected by it, because it has nothing to opt out of.
You have not decided yet. Until you do, Google Analytics is off.
Strictly necessary storage
Two values live in your browser's local storage, never in a cookie, and never leave your device:
applye-theme- whether you chose the dark or light site theme.applye-analytics-consent- the choice you made on this page.
These are not tracking. They exist so the site does not forget your preference on every visit, and they are readable only by this site.
The always-on counter
Cloudflare Web Analytics runs on every visit, before and regardless of any consent decision. Its job is one number: how many people opened a page. It records the page, the referring site, and coarse device, browser and country information derived from the request itself.
Why it needs no permission:
- It writes no cookie and nothing to local storage.
- It creates no identifier - not a random one, not a fingerprint. Two visits by you are not knowably two visits by the same person.
- It cannot follow you to any other website, because there is nothing to follow.
- Nothing you type anywhere on this site reaches it.
Cloudflare serves this site, so the request already passes through them either way; the counter reads what the request already carries rather than adding a tracker on top.
Optional analytics
If, and only if, you allow it, the site loads Google Analytics 4. Before that moment no request is made to Google, no analytics cookie is written, and no identifier is created.
It answers a different question from the counter above: not "did anyone come", but "what did they do once here" - which docs page was read, which language was chosen, which button was pressed.
What it records once enabled:
- Which page was viewed, and which page referred you.
- Approximate country, from a truncated IP address (IP anonymisation is forced on).
- Device class, browser, and language.
Plus six named interactions, and no others. This is the complete list, kept in step with the code that sends them (analytics/events.ts):
page_view- a page was opened, with its path and title.download_click- a download link was clicked, with the section of the page it sat in and which desktop platform your browser reports. The download itself happens on GitHub, which we cannot see.outbound_click- a link leaving this site was clicked, with its destination.cta_click- a labelled button on this site was clicked.locale_switch- you changed the site language.consent_decision- recorded when you allow analytics. Declining records nothing, because declining means nothing is loaded to record it with.
Every event also carries the language of the page you were on. Any parameter not on this list is discarded in the browser before it is sent, so a mistake in our own code cannot quietly widen this.
What it never records:
- Your name, email, CV, profile, jobs, or anything you type into the app.
- Advertising signals. Google Signals and ad personalisation are both explicitly disabled, so this data is not used to build an advertising profile of you.
- Anything at all from the desktop app. It has no telemetry and never phones home.
Why measure anything at all
One person builds Applye. Knowing which docs pages are read and which are ignored decides what gets written next. That is the whole purpose - not growth dashboards, and certainly not selling anything. If that trade does not appeal to you, decline: the site works identically either way, and nothing is withheld.
Related
The app's own data guarantees are in Privacy, with the technical detail in the privacy docs.