Cookie policy
Effective · Version 1.0
In plain language
One cookie is set before you choose anything, and it is the one that remembers your choice. Everything else waits until you say yes, and stops when you say no. The list below is the whole list — if you find a cookie on this site that is not in it, that is a bug and we would like to hear about it.
Where we ask, and where we do not
If you are in the European Economic Area, the United Kingdom or Switzerland, nothing optional runs until you answer the banner. Analytics and marketing storage are denied before the tag container loads, not after it.
Elsewhere, analytics and the support chat run by default and no banner is shown. You can turn them off at any time with Cookie settings, which is in the footer of every page on this site for exactly that reason. We think it is worth being direct about this rather than implying a worldwide ask we do not perform.
Every cookie we set
- cookie_consentStrictly necessary
Records the answer you gave on the cookie banner, and when you gave it, so you are not asked again and so we can show what you agreed to. Scoped to proxyforge.io, which is what carries your answer across to the dashboard at app.proxyforge.io.
ProxyForge (first party) · expires 6 months
- referrerCodeMarketing
Remembers which partner's referral link brought you here, so that partner is credited if you go on to open an account. Set only if you allow marketing cookies, and only when you arrive on a link carrying a referral code. Scoped to proxyforge.io so it still applies when you register on app.proxyforge.io.
ProxyForge (first party) · expires 30 days
- ad_clickMarketing
Remembers which Google or X (Twitter) advert click brought you here — the gclid, gbraid, wbraid or twclid on the link you arrived on — so an account you go on to open can be matched to the advert we paid for. Set only if you allow marketing cookies, and only when you arrive from an advert. Scoped to proxyforge.io so it still applies on app.proxyforge.io.
ProxyForge (first party) · expires 90 days
- _gaAnalytics
Tells one browser from another, so a person who reads three pages is counted once rather than three times.
Google Analytics 4, loaded through Google Tag Manager · expires 2 years
- _ga_<property>Analytics
Holds the state of the current visit for one GA4 property. The suffix is the property id.
Google Analytics 4, loaded through Google Tag Manager · expires 2 years
- _gcl_auMarketing
Records which advert click brought you here, so we can tell which campaigns are worth paying for. Set only if you allow marketing cookies.
Google Ads, loaded through Google Tag Manager · expires 90 days
- cw_conversationPreferences
Keeps your support chat conversation together, so it is still there when you reload the page or move between proxyforge.io and app.proxyforge.io. Set where you allow preferences cookies, or where you are not asked and have not objected.
ProxyForge support chat, served from support.proxyforge.io (first party) · expires 12 months
- cw_user_<token>Preferences
Records that the support chat has already been told which account you are signed in to, so it does not repeat that. The suffix is the chat widget's public identifier. Written only after you sign in to the dashboard, never from this site alone.
ProxyForge support chat, served from support.proxyforge.io (first party) · expires 12 months
- cw_snooze_campaigns_tillPreferences
Remembers that you dismissed a message from the support chat, so it is not shown again straight away.
ProxyForge support chat, served from support.proxyforge.io (first party) · expires 1 hour
The categories
Strictly necessary cookies have no off switch, because turning them off would mean the site could not remember that you turned them off. They carry security and the consent record itself, and they are never used to measure you.
Analytics tells us which pages get read and where people give up. Marketing tells us which advert or search brought you here. Preferences remembers choices you made on the site so it does not ask twice, and keeps your support chat conversation together. The chat is served from our own support host, so no third party is involved in it.
How the choice is enforced
Google Tag Manager is loaded with Consent Mode v2 defaults already in place before the container script runs, not after. A tag that needs analytics or advertising storage therefore cannot fire on the way to asking you — the answer is set when the container arrives, rather than being applied a moment later.
The regional split above is enforced by Google against the network address your request arrives from, not by anything this page can measure about you. That is deliberate: it means a visitor in Munich is protected even if their browser is set to another country’s clock.
Your answer is stored in a cookie scoped to proxyforge.io, so answering here also answers for the dashboard at app.proxyforge.io. The two run separate tag containers and read the same consent.
Changing your mind
Use Cookie settings, in the footer of every page and at the top of this one. Withdrawing is one click, in the same place as giving. Clearing your browser’s cookies for this site also clears the record.
Who else sees this data
- Google Ireland Limited — Google Tag Manager, Google Analytics 4, Google Ads. Measures site usage and advert performance on our behalf.
What personal data we hold about you as an account holder, and the rights you have over it, is a separate document: the privacy notice.
Contact
Questions about this document go to [email protected], and a person answers.