This page describes the tracking technologies WebmasterID uses (and does not use) in the browser. It covers both the WebmasterID tracker as installed on customer sites and the marketing site you are reading now.
Summary
WebmasterID does not currently rely on cookies, localStorage, or fingerprinting for browser analytics. The tracker is a small JavaScript file that posts an anonymous, aggregate page-view event to the ingest API and exits.
What the tracker does
- Sends a single
page_viewevent per page load. - Hooks
history.pushState,replaceState, andpopstateto fire one event per client-side route change. - Submits the event as a plain string body via
navigator.sendBeaconwithContent-Type: text/plain;charset=UTF-8— a CORS-safelisted MIME, so no preflight is required. - Honors Do Not Track (DNT) and Global Privacy Control (GPC): opted-out browsers send nothing.
What the tracker does NOT use
- No HTTP cookies (first-party or third-party).
- No localStorage or sessionStorage tracking identifiers.
- No IndexedDB, no service-worker fingerprinting.
- No canvas, audio, font, or device-entropy fingerprinting.
- No cross-site identifier of any kind.
- No third-party scripts loaded from outside our origin.
"Similar technologies"
Cookie-policy templates often refer to "cookies and similar technologies." For the WebmasterID tracker — the product you embed on your own site — the only browser-side technology used is the JavaScript tracker file itself. There are no pixels, no web-beacons, no local-storage-backed identifiers, no Web SQL fallbacks, and no embedded third-party SDKs. This is a property of the product and is unaffected by anything this marketing site does.
This marketing site is a separate matter: with your explicit opt-in it can load an advertising pixel that does use a cookie. That is described in full below, and it never applies to the tracker running on your site.
This marketing site
The WebmasterID marketing site (this site) presents a consent banner when you first visit. It offers two independent purposes, and nothing in either is loaded until you choose. Your choice is stored as a first-party preference under the key webmasterid_consent_v2 in localStorage, as JSON of the form {"analytics":false,"marketing":false}. The value is purely a preference (so the banner does not reappear) and is never sent in analytics payloads, never used as a visitor ID, and never shared.
Analytics loads this site’s own copy of the WebmasterID tracker and records one anonymous page_view per page load — exactly what is described above. It is same-origin and sets no cookies.
Advertising loads the Meta Pixel from connect.facebook.net. This is a third-party script. It sets an _fbp cookie on this domain, and it reports page views and conversions to Meta so we can measure advertising campaigns. It is the one place where cross-site advertising technology is used, it applies to this marketing site only, and it is off unless you switch it on.
Necessary only loads neither: no tracker, no pixel, no analytics or advertising request from your browser.
The two purposes are recorded separately, so accepting analytics does not grant advertising. If you previously accepted analytics under our earlier single-choice banner, that preference is preserved and you are asked once more about advertising, because you were never asked before. If your browser sends a Global Privacy Control or Do Not Track signal, the advertising pixel is not loaded even if consent is stored. You can clear your localStorage for this origin to be re-prompted.
DNT / GPC
When a browser signals DNT or GPC, the tracker exits early client-side and the ingest API additionally discards anything that arrives with those headers. This applies on every site that runs the WebmasterID tracker.
Operator responsibilities
WebmasterID is designed to minimise the privacy surface, but site operators (controllers) remain responsible for their own compliance. Depending on jurisdiction and implementation, you may be required to disclose analytics in your own privacy notice and, in some cases, obtain consent for certain tracking technologies. We do not claim that "no consent is ever needed."
If we add cookies later
If WebmasterID introduces cookies, persistent identifiers, or other tracking technologies in the future, this policy will be updated before those changes are deployed. Material changes will be reflected in the "Last updated" date at the top of the page.
Contact
Questions about this policy can be sent to info@helperg.com. See also our Privacy Policy, Data Processing page, and Terms.
This page is provided in good faith and reflects the actual product behaviour as of the last-updated date. It is not legal advice. Final review by qualified counsel is recommended before public SaaS launch.