In one paragraph
We use a small set of first-party cookies. One remembers your consent choice so the banner does not pop up on every page. A handful are strictly necessary to keep the site working (a session token if you submit the contact form, for example). One optional cookie is set, only if you accept, to count visits through a self-hosted, privacy-friendly analytics engine. We do not set any advertising, profiling, or social-media tracking cookies. Your choice can be changed at any time from the preferences switch on this page.
What we do not set
We do not load Google Analytics, Google Ads, Meta pixels, TikTok pixels, LinkedIn Insight tags, or any other third-party advertising and profiling cookie. We do not embed YouTube videos with default cookies, we do not load Google Fonts from Google's CDN (they are self-hosted), and we do not pull Chart.js from a CDN either (the CGT simulator and similar tools use a locally bundled copy). The net effect is that on a fresh visit with the banner refused, the site sets exactly zero optional cookies.
Your current preferences
Use the two buttons below to change your analytics choice at any time. The change is stored in the rc_consent cookie and takes effect on the next page load.
Current status will be shown by the banner at the bottom of the page when a change is pending.
Browser-level controls
Every modern browser lets you inspect and delete cookies per site. In Chrome and Edge, open the page, click the lock icon in the address bar, select "Cookies and site data," and review the list. In Firefox, use "Tools, Page info, Security, View cookies." In Safari, "Preferences, Privacy, Manage website data." Removing rc_consent makes the banner reappear on your next visit so you can choose again. Removing all cookies signs you out of any form session in progress.
A worked example of the consent flow
Imagine you land on the fee page on the fifteenth of 2026. The banner appears because no rc_consent cookie exists yet. You click "Reject non-essential" because you are just browsing. A single strictly necessary cookie is set, rc_consent, with the value reject, expiring in twelve months. No analytics cookie is issued. You read three pages, close the tab, and return two days later. The banner does not reappear because your previous choice is still valid. No optional cookie is set during that second visit. In a month you decide to enable audience measurement to support the site; you come back to this page, press "Accept audience measurement," rc_consent is updated to accept, and the two _pk_* cookies are created from that page load onwards.
One pitfall to watch
A browser extension that blocks cookies indiscriminately can also block rc_consent, which means the banner will appear on every single visit no matter what you click. If that happens, whitelist the domain representatives-compare.com in the extension so the strictly necessary cookies survive. We have no way to remember your choice if the browser does not let us write the cookie that records it.
Pro tip: the banner is honest
The banner does not use a dark-pattern "confirm my choices" button that silently enables trackers. If you press "Reject," you reject. There is no hidden list of legitimate-interest vendors and no second screen that re-enables categories. That is a deliberate choice, and if a future regulator updates the rules we will adjust this page the same day.
Changes to this policy
If we add or remove a cookie, we will update the table above and bump the version string. The version currently in force is v1, published for 2026. If a change is material (a new category or a new vendor) we will also show a notice in the banner for thirty days so returning readers notice the shift.
Quick questions readers ask
Why do you set a session cookie on the contact form?
To protect the form against cross-site request forgery. Without a session token, a malicious third-party site could trick your browser into submitting the form on your behalf. The cookie disappears when you close the tab.
Is the audience-measurement data really anonymous?
Yes. The self-hosted engine truncates IP addresses before they hit the database, the identifiers are site-scoped, and we do not enrich them with any third-party source. We cannot tie a visit to a named person.
Does Do-Not-Track (DNT) have any effect?
The official DNT standard is deprecated, and most browsers no longer send it. If your browser does send it, we treat it as a reject signal and do not set the optional cookies even before the banner interaction.
Where do I read the broader privacy notice?
The privacy policy covers everything outside cookies: contact-form handling, server logs, retention, and your GDPR rights.