Back to home

Cookie Policy

The cookies, browser storage and third-party tags this site actually uses.

Last updated: 31 October 2026

1. What this policy covers

This policy covers cookies and the equivalent browser storage the site uses — primarily localStorage — plus the third-party measurement and advertising tags that load on this site. It lists each item and each tag, what it is used for, and how to remove it or block it. It matches what the site actually runs; nothing is listed that is not used.

2. Strictly necessary storage

These are set by MaxonForge itself and are required for the Service to work:

  • mf_token — your signed-in session token, kept in local storage so the dashboard can call the API. Without it you would be signed out on every page load. Removed when you sign out.
  • mf_consent — records your opt-out choice (whether you have turned analytics and advertising measurement off in this browser). It is written only when you use the opt-out control below; measurement is on when no choice is stored.
  • mf_session_id and mf_session_ts — a random session identifier and its last-activity timestamp, used to group a visit into one 30-minute analytics session. They contain no personal data.

3. Optional analytics and marketing

Measurement is on by default. The tags below load automatically on every visit, without an in-site consent prompt and without waiting for you to accept anything. You can turn them off for this browser with the opt-out control in section 5 (or block them in your browser — see that section).

  • Google Tag Manager — container GTM-PTZCGRPF. Loads and manages the Google measurement and advertising tags configured for this site. It receives the page URL, the referring page, device and browser information, interaction events, the approximate location derived from your IP address, and first-party identifiers used to group a visit.
  • Google Analytics 4 — measurement ID G-ZKKJVDM5YC. Records page views, page paths and titles, session information, device and browser information, approximate location derived from your IP address, and interactions such as clicking a sign-up or pricing action. It is used to understand which pages and features are used.
  • Google Ads — conversion ID AW-18462456083 with the conversion linker. Measures advertising performance: when a visitor who arrived from a Google ad signs up or pays, the conversion (with its value, currency and transaction id) is reported so we can see which campaigns produce customers. Google’s conversion linker stores click identifiers such as gclid, gbraid and wbraid in first-party storage so that sign-up and purchase can be matched to the ad click that produced them.
  • Meta Pixel — pixel ID 1647316260137207. Records page views and events such as sign-up, checkout start and purchase, together with browser/device information and identifiers Meta sets in its own cookies. It is used to measure and attribute advertising on Meta and to let Meta optimise delivery of those ads.
  • OpenAI Ads Pixel — pixel ID 7oykYsCXH7kVAR7ay66mCh. Loads the OpenAI measurement script (oaiq) from bzrcdn.openai.com on every page and sends page views (page URL and title, device and browser information, and the first-party cookies the pixel sets such as __obref). It is used to measure and attribute advertising on ChatGPT.
  • OpenAI Ads Conversions API (server-side). When you register an account, start a checkout, or complete a verified payment, our server sends the confirmed conversion (registration_completed, checkout_started, order_created) to OpenAI at bzr.openai.com. These requests carry the conversion value and currency, a unique event id, the page you came from, a pseudonymous customer id hashed with SHA-256, your email address hashed with SHA-256, your IP address and browser user-agent, and the advertising references described below (such as the OpenAI oppref click reference and the pixel’s __obref browser reference) where they exist. No raw email address, password, API key or payment card data is ever sent. If the ad account’s pixel is changed, this policy is updated with the new ID.
  • First-party attribution. A random identifier (mf_anonymous_id) and the campaign parameters in the link you arrived on (utm_*, gclid, fbclid and similar click ids) are stored by our own system so a sign-up or purchase can be attributed to the campaign that produced it. This identifier is not used to sign you in.

Where the Google tag is configured for Enhanced Conversions and an event carries an email address, that address is hashed with SHA-256 in your browser before it is sent — we do not send the raw address to the advertising tags.

4. Third-party cookies

The Google, Meta and OpenAI tags described in section 3 may set their own cookies or equivalent identifiers when they load, governed by those companies’ policies rather than by this one. Payment providers may also set cookies during checkout on their own pages.

We do not control those third-party cookies. You can review the providers’ policies at Google’s partner sites policy, Meta’s privacy policy and OpenAI’s policies.

5. How to change or clear your choice

You can turn analytics and advertising measurement off for this browser at any time. The control below stores your choice and reloads the page, so the tags above are not loaded on the next page view; our server also records the choice and stops sending marketing events for you.

Your measurement choice in this browser

Measurement is currently on in this browser: the tags listed above load on page views, as described above.

  • Block the tags in your browser. Browser settings, tracking-protection modes, and extensions such as uBlock Origin or Privacy Badger can block Google, Meta and OpenAI measurement scripts. The site keeps working without them.
  • Clear site data. Clearing site data in your browser settings removes mf_token, mf_consent, mf_anonymous_id, mf_session_id and mf_session_ts. Clearing mf_token signs you out, and clearing mf_consent puts measurement back to its default (on) in that browser.
  • Blocking strictly necessary storage will break sign-in, because the dashboard cannot authenticate without mf_token.

6. More information

See the Privacy Policy for the full picture of what we collect and why, and Contact & Support if you have a question about a specific item.