This Remote GTM Manager cookie policy lists, plainly, which cookies and trackers are actually active on remotegtmmanager.com — nothing more. For what happens to the data these tools collect, see the Privacy Policy. There's no cookie-consent popup on this site by design; instead, this page does the same job in a more honest way, by stating exactly what's running and what isn't.
What a Cookie Actually Is
A cookie is a small text file a website or a third-party script asks a visitor's browser to store, usually to remember something between page loads — a session, a preference, or in the case of analytics tools, a way to tell repeat visits apart from new ones. Cookies on their own don't identify a person by name; they identify a browser session or device.
Currently In Use
Google Analytics 4 (GA4). Used to understand how visitors use this site — which pages get read, general traffic patterns, and aggregate behavior. GA4 sets its own cookies to distinguish sessions and visits.
Microsoft Clarity. Used for session recordings and heatmaps — a way to see, in aggregate, how people actually move through and interact with pages here, so the site can be improved based on real behavior rather than guesswork. Clarity sets its own cookies to support this.
Google reCAPTCHA (Newsletter page only). Protects the newsletter signup form from automated spam. It loads only on the Newsletter page, and only once a visitor starts using the signup form — never just for reading the page — and Google may set its own cookies (such as _GRECAPTCHA) to tell humans from bots. It is not loaded anywhere else on this site.
Not Currently In Use
Meta Pixel — not active. Pinterest Tag — not active. Google Tag Manager — not active as a separate container; GA4 runs directly. If any of these are ever enabled, this page will be updated to say so — nothing gets added to this site's tracking without this page reflecting it.
Search Engine Verification — Not a Tracker
Google Search Console and Bing Webmaster Tools are each verified with a single meta tag in the page's head, a short line of text that proves ownership of this domain. It is not a cookie and it runs no script in a visitor's browser. Neither of these involves any cookie being set on a visitor's device — they're a one-time ownership check between this domain and the search engines, invisible to anyone actually browsing the site.
Functional Cookies & Local Storage
Beyond the analytics tools listed above, this site sets two small first-party cookies, both anonymous and both used only to make a feature work. nl_voter remembers which framework a visitor picked in the "which guide should we write first" vote on the Newsletter page, so a vote can be changed or removed and is never counted twice. px_voter does the same for the Like, Love, Applause and Dislike reactions on a guide. Each holds a random ID, lasts one year, and is never used for tracking or advertising.
The site also remembers a few preferences in the visitor's own browser storage (local storage): the light or dark mode chosen with the toggle in the header (theme), and, on guides, the chosen text size (px-size) and the reading position (px-pos: followed by the guide's name) so that "Continue reading" can offer to resume. These values stay on the visitor's device, are never sent to a server, and are never used for tracking; clearing the browser's site data removes them. If another feature like this is added later, this page will say so.
Why There's No Consent Banner
Rather than asking for a click-through consent that most visitors ignore anyway, this site takes the position that transparency belongs here, in writing, permanently checkable — not in a popup that disappears after one click and is never seen again. This isn't a way to avoid disclosure; it's this site's chosen way of doing it — checkable any time, not just at first visit.
Third-Party Cookie Policies
The interactive map on the Contact page loads map tiles from OpenFreeMap. It does not set cookies, but loading the tiles does send the visitor's IP address to that service.
Google's and Microsoft's own policies govern exactly how GA4 and Clarity handle the data their cookies collect — this page describes that they're in use and why, but the full technical detail of how each company processes that data lives in their own published policies, not duplicated here.
Do Not Track Signals
Some browsers send a "Do Not Track" signal automatically. There's no universal standard for how sites are supposed to respond to it, and this site does not currently change its tracking behavior based on that signal — the honest disclosure on this page is the mechanism relied on instead.
Controlling Cookies Yourself
Most browsers allow blocking or deleting cookies through their own privacy or settings menu, and both Google and Microsoft offer their own opt-out mechanisms for Analytics and Clarity respectively. Blocking these won't restrict access to any page on this site.
Changes to This Page
Any change to which trackers are active on this site will be reflected here and in the Privacy Policy. The version published is always the current, accurate one.
Contact
Related: Privacy Policy, Disclaimer, Terms of Service. Questions about cookies or tracking on this site — anything unclear, anything that seems off, or a request to understand exactly what's being collected — email me.