Cookie Policy
This Cookie Policy explains how Maxinodes (“we”, “us”, “our”) uses cookies and similar technologies on maxinodes.com and its subdomains: our website, the Client Area at my.maxinodes.com, our analytics host at stats.maxinodes.com, and our Help Centre at support.maxinodes.com, which is operated for us by Zendesk, Inc. It does not cover our webmail at webmail.maxinodes.com or the cPanel control panel on our hosting servers, including the webmail built into cPanel. What they keep in your browser is only what they strictly need: the session and security cookies that keep you signed in and, in webmail, browser storage that remembers its layout and keeps a copy of a message you are writing until you send or save it. Of our own cookies, our webmail reads, and can set, only one: your language choice, described in section 4. This policy sits alongside our Privacy Policy, which describes more fully how we handle personal data. Where this policy refers to “you” or “your”, it means any visitor to our site, whether or not you are a Customer.
We want to be straightforward about this. On our website and in the Client Area, two things run on every visit, whatever you choose in our cookie banner: our self-hosted, cookieless analytics, and advertising measurement that tells Meta (Facebook and Instagram) when one of our ads led to a visit, an enquiry, a sign-up or a payment. We will not pretend that second one is harmless: it is genuine advertising technology operated by a third party, and it runs without asking you first. Our banner asks about one thing only — the live-chat widget, which does not load until you allow it — and you can change that choice at any time using the Cookie settings button below. We never sell your browsing data. Our Help Centre is a separate case and we say so in section 3 rather than hiding it: it runs on Zendesk’s platform, which sets its own cookies as the page loads, before our banner there can act. This policy explains exactly what we set and the choices you have.
1. What cookies are
A cookie is a small text file that a website asks your browser to store on your device. When you return to the site, your browser sends the cookie back, which lets the site recognise your session, remember choices you have made, or keep you securely signed in. Cookies cannot run programs or carry viruses, and they cannot read other files on your device.
Cookies are usually classified in two ways:
- By who sets them. A first-party cookie is set by the website you are visiting (in our case, maxinodes.com). A third-party cookie is set by a different domain — for example an analytics or advertising provider embedded in a page. The Meta advertising cookies described below sit awkwardly across that line: they are written on our own domain, so your browser treats them as first-party, but the data they carry is read by Meta. Apart from those, we permit third-party storage on maxinodes.com and its subdomains in only two places: the Zendesk chat widget, and only if you allow live chat; and the card form of our payment provider, Whop, together with the Google Pay frame Whop’s form loads, on the Client Area page where you pay a new order by card. Our Help Centre at support.maxinodes.com is a separate case: it runs on Zendesk’s own platform, and Zendesk — together with the network provider it puts in front of that site — sets its own cookies there. Those are listed in section 4.
- By how long they last. A session cookie is temporary and is deleted when you close your browser. A persistent cookie remains for a set period, or until you delete it.
Where this policy refers to “cookies”, it also covers similar technologies that store or read information on your device for comparable purposes. These include browser localStorage and sessionStorage, IndexedDB, pixels, tags, software development kits, and device or browser fingerprinting. The same rules in this policy apply to all of them, regardless of the specific technology used.
2. Categories of cookies
Cookies and similar technologies fall into four categories, described in plain English below. Strictly necessary, analytics and marketing run on every visit to our website and the Client Area; live chat is the one category our consent banner asks you about, and it runs only if you opt in. We use one marketing technology — the Meta pixel and its server-side equivalent — and it is described below.
Strictly necessary
These cookies are essential for the website and Client Area to work. They do things like keep you signed in, protect forms and sign-in requests against cross-site request forgery, and remember the steps you have completed in a checkout or order — and they remember which language you are reading the site in, and the cookie choices you make here. Without them, core features simply will not function. Because they are essential to deliver a service you have asked for, these cookies do not require consent under EU and Irish law — but we still tell you about them here.
Functional / preferences
These are not essential but make the site more useful — in practice, running our live-chat widget so you can message us. We load them only after you opt in to the relevant category, and you can withdraw at any time.
Analytics
These help us understand how visitors use the site — which pages are useful and where things break — in aggregate, to improve it. Ours is self-hosted Matomo: it is cookieless, anonymises IP addresses, never tracks you across other sites, and is never shared with advertisers. Its measurement script runs on every visit to our website and the Client Area; it does not wait for a choice in our banner.
Marketing
These cookies are used to measure the effectiveness of advertising campaigns and, on the advertising network’s side, to build a profile of your interests and show you advertising across different websites. We use one such tool: the Meta pixel, which lets us see which visits and sign-ups came from our Facebook and Instagram ads so we stop paying to advertise to people who have already found us. It loads on every visit to our website and the Client Area, whatever you choose in our banner.
We also send the same events to Meta from our own server (Meta calls this the Conversions API), because browser-based measurement is frequently blocked and, for a payment that confirms minutes after you close the tab, there is no browser left to report it. It is the same kind of information about the same events, but it does not depend on your browser: an ad blocker can stop the pixel, but not these. From our server we report the page views and other events the pixel records, enquiries made through our contact form, new Client Area accounts and paid invoices.
3. What we use today
As at the date at the top of this page:
- Strictly-necessary cookies (always on). First-party cookies required to run the website and Client Area — a session cookie and a security / CSRF cookie — plus a small cookie that remembers your consent choice so we do not have to ask on every page, and one that remembers which language you are reading the site in. The content-delivery and security edge in front of our own websites (Microsoft Azure Front Door) sets no cookies of its own; it does log request data, and our Privacy Policy explains what it records and where. These cookies need no consent under EU and Irish law.
- Analytics (always on). Self-hosted Matomo, used to measure aggregate traffic. It is cookieless and anonymises IP addresses, never tracks you across other sites, and is never shared with advertisers. Its measurement script runs on every visit to our website and the Client Area, whatever you choose in our banner.
- Live chat (only with your consent). The Zendesk chat widget, so you can message us. It loads — and sets its cookies and similar storage — only after you opt in to the live-chat category. If you opt in, it shares your IP address and browser details with Zendesk, Inc., a Delaware corporation established in the United States, which handles support conversations on our behalf. Your conversation, and the contact record it creates, currently sit in Zendesk’s Europe (Ireland) region, but we have not obtained a contractual commitment to that region and Zendesk reserves the right to move account data between its regions; personal data reaches the United States in any event, through Zendesk’s own operations and the United States sub-processors it uses to run the service. Our Privacy Policy and our Subprocessors page set out the safeguards we rely on for that. If you do not opt in, the widget is not loaded at all.
- Advertising measurement (always on). The Meta pixel, plus equivalent events sent from our server, used to measure whether our Facebook and Instagram advertising works. On every visit to our website and the Client Area, whatever you choose in our banner, this shares your IP address, browser details and the pages you view with Meta Platforms Ireland Ltd, together with scrambled (hashed) forms of the details you have given us: your email address, and for Client Area accounts also your name, telephone number and country. Meta acts as a joint controller with us for this and may transfer data outside the EU. It sets the
_fbpand_fbccookies listed below. Section 5 explains what you can still do about it. - Whop’s card form (only when you pay a new order by card). When you pay a new order by card, you enter the card on our payment page in the Client Area, in a card form that our payment provider, Whop, runs inside that page from its own servers (cdn.whop.com), together with a payment frame from Google (pay.google.com) for Google Pay. To do that, Whop’s script on that page sets one cookie of its own on the Client Area’s address,
_whop_ssk: a random session key that Whop’s fraud check uses to keep the checks on your payment together, which expires after 20 minutes. The form, the Google frame, and the card processor and 3-D Secure check behind them, also set their own cookies and similar storage, and may collect details about your device and browser, to take the payment, protect it against fraud and let your bank confirm that it is you paying. They are strictly necessary for the payment you asked for, so they need no consent. Whop and Google set them under their own terms, and apart from the one named above, their names are theirs to choose and change, so section 4 describes them by what they do. Our payment page itself loads neither our analytics nor the Meta pixel. Section 5 of our Privacy Policy says what Whop receives. - Our Help Centre is a separate platform. support.maxinodes.com is run for us by Zendesk, Inc. on its own infrastructure. Zendesk, and the network provider it puts in front of that site, set their own cookies when you visit it — they are listed in section 4. Our consent banner does run there, and it records the same choice as this one, so a decision made on any of our three sites applies to all of them. But what it can act on there is narrower: it holds the chat widget back until you allow live chat. Neither our analytics nor the Meta pixel runs on the Help Centre. It cannot stop the cookies the platform sets for itself — Zendesk’s Help Centre session, Zendesk’s own measurement of that site, and Cloudflare’s bot protection all load with the page, before any of our code runs. We would rather say that plainly than let you assume the banner covers more than it does. Those you can still control in your browser (see section 6).
- No third-party fonts. We self-host our fonts on our website and in the Client Area, so loading a page there does not send your IP address to any third-party font service. This does not extend to the Help Centre, which loads its assets from Zendesk.
You can review or change these choices at any time using the Cookie settings button near the top of this page. The Client Area at my.maxinodes.com applies the same consent choice and sets its own strictly-necessary session and security cookies to keep you signed in and protect your account.
One consequence of sharing cookies across our subdomains. Our consent record (mx_consent), your language choice (mx_lang) and Meta’s _fbp cookie (with _fbc, if you came from one of our ads) are all stored for .maxinodes.com and every subdomain of it. That is what lets one choice cover our website, the Client Area and the Help Centre, but it also means your browser attaches those cookies to every request for our Help Centre at support.maxinodes.com, so Zendesk receives them. On the Help Centre our own banner reads your consent record, in your browser, to apply your live-chat choice there, and we do not use the language cookie there at all; but an advertising identifier reaching a support platform is worth telling you about rather than leaving you to find it. For the same reason they reach our Status Page at status.maxinodes.com, which UptimeRobot s. r. o. hosts for us, so UptimeRobot receives them too; no code of ours there reads them. Your browser also sends them to our webmail server when you open webmail.maxinodes.com, and to our hosting server node11.maxinodes.com when you open cPanel, or the webmail built into cPanel, there. Both servers are ours. Neither reads your consent record or Meta’s cookies; our webmail reads only your language choice, to show its sign-in page in the language you were reading our site in and, the first time you sign in, to start webmail in that language.
4. The cookies set on our sites
The table below lists the cookies and similar storage set across the sites this policy covers. The strictly-necessary ones are always present; the live-chat cookies appear only after you opt in to live chat; the Meta advertising cookies are set on your first visit to our website or the Client Area, whatever you choose in our banner; and Whop’s card-form cookies are set only on our payment page, when you pay a new order by card. Our own analytics is cookieless, so it has no entry here. The last two rows are different in kind: they are set on our Help Centre by Zendesk and by the network provider in front of it, not by us, and they load with the page — before the banner we put on that site can run, which is why it cannot gate them. Exact technical names can change between releases of the software that powers our site, so where a name may vary we describe the cookie by its function.
| Name | Provider | Purpose | Duration | Type |
|---|---|---|---|---|
| Session cookie | Maxinodes (first party, maxinodes.com) | Maintains your browsing session and keeps you securely signed in to the website and Client Area. Essential for navigation, ordering and account access. | Session (deleted when you close your browser, or sooner on sign-out) | Strictly necessary |
| CSRF-protection cookie | Maxinodes (first party, maxinodes.com) | Holds a security token that protects forms and sign-in and ordering requests against cross-site request forgery (CSRF). Essential for security. | Session | Strictly necessary |
Consent-preferences cookie (mx_consent) |
Maxinodes (first party, .maxinodes.com) | Remembers the live-chat choice you made in our consent banner, so we apply it and don’t ask again on every page. Shared between maxinodes.com, the Client Area at my.maxinodes.com and our Help Centre, so one choice covers all three. Because it is stored for .maxinodes.com and its subdomains, your browser also sends it to our webmail and cPanel servers, which do not read it, and to our Status Page (see section 3). |
Up to 6 months | Strictly necessary (records your consent) |
Language cookie (mx_lang) |
Maxinodes (first party, .maxinodes.com) | Remembers which language version of the site you are reading, so links without a language prefix take you to the right language and the choice carries across to the Client Area. Set on every visit, before and regardless of any consent choice, because it is needed to deliver the site in the language you chose. Our webmail at webmail.maxinodes.com reads it too, to show its sign-in page in the same language and, the first time you sign in, to start webmail in it; the language switch on that page sets it. Being stored for .maxinodes.com and its subdomains, it is also sent to our Help Centre, our Status Page and cPanel. |
Up to 12 months | Strictly necessary |
Live-chat cookies and storage (e.g. __zlcmid) |
Zendesk, Inc. (our support platform) | Set only after you opt in to the Live chat category, to run your conversation and let you continue it if you move between pages or return later. Not set unless you allow live chat. | Up to 180 days (or until you clear it) | Functional (live chat) — consent required |
| Client Area session & security cookies | Maxinodes (first party, my.maxinodes.com) | Set by the billing and account portal to keep you signed in to your account and to protect account and billing actions. Essential to operate the Client Area. | Session | Strictly necessary |
| Essential local storage | Maxinodes (first party) | Where used, browser localStorage / sessionStorage that supports core site functionality (for example holding a value needed for a single visit). No analytics or marketing data is stored. | Cleared on sign-out or when you clear site data | Strictly necessary |
Meta advertising cookie (_fbp) |
Meta Platforms Ireland Ltd (written on .maxinodes.com by Meta’s script) | Set on your first visit to our website or the Client Area, whatever you choose in our banner. Gives your browser a random identifier so Meta can tell that a visit, an enquiry, a sign-up or a payment came from one of our Facebook or Instagram ads. Meta’s script stores it for .maxinodes.com and its subdomains, so once it exists your browser also sends it to our Help Centre, where Zendesk receives it. |
Up to 90 days (often much shorter in Safari) | Marketing — always on, not consent-gated |
Meta click cookie (_fbc) |
Meta Platforms Ireland Ltd (written on .maxinodes.com by Meta’s script) | Set only if you reached us by clicking one of our ads, whatever you choose in our banner. Stores the click identifier from that ad so the visit can be matched to it. | Up to 90 days (often much shorter in Safari) | Marketing — always on, not consent-gated |
Whop card-form cookie (_whop_ssk) |
Whop, our payment provider (set on my.maxinodes.com by the card-form script Whop runs on our payment page) | A random session key that Whop’s fraud check uses for your card payment: the card form sends it with its requests, so the checks on one payment stay together. Set only on the Client Area page where you pay a new order by card. | 20 minutes | Strictly necessary (for the payment you asked for) |
| Card-form cookies and storage (names set by Whop) | Whop, our payment provider, its card processor and, for Google Pay, Google (third party, inside Whop’s card form on our payment page) | Set only on the Client Area page where you pay a new order by card, by the card form Whop runs inside it: to take the payment, check it for fraud and let your bank confirm that it is you paying (3-D Secure). Not set anywhere else on our website or in the Client Area. Whop sets them under its own terms and privacy policy. | As set by Whop under its own policy | Strictly necessary (third party, for the payment you asked for) |
Help Centre bot-management cookies (__cf_bm, _cfuvid) |
Zendesk, Inc., through the network provider (Cloudflare) it puts in front of our Help Centre | Set when you visit our Help Centre at support.maxinodes.com, to tell human visitors apart from automated traffic and filter abusive requests. Not set on maxinodes.com or in the Client Area, and not set by us: they belong to the platform our Help Centre runs on. | __cf_bm about 30 minutes; _cfuvid for as long as your browsing session lasts |
Set on our Help Centre by Zendesk — loads with the page, so our banner there cannot gate it |
Help Centre session, measurement and search storage (_help_center_session, _zdshared_user_session_analytics, recentSearches) |
Zendesk, Inc. (our support platform) | Set when you visit our Help Centre. They keep your Help Centre session, let Zendesk measure how the Help Centre is used, and remember your recent knowledge-base searches in your browser. That measurement is Zendesk’s own and is separate from our cookieless Matomo analytics. | Session, except recent searches, which stay until you clear site data | Set on our Help Centre by Zendesk — loads with the page, so our banner there cannot gate it |
Our own analytics deliberately sets no cookies on our website or in the Client Area, so it has no row here (see section 3); Zendesk’s separate measurement of the Help Centre is in the table above. Should we introduce any further non-essential cookie on our website or in the Client Area, we will list it here — with its name, provider, purpose, duration and type — before we set it.
5. Consent and your choices
We use a consent banner to manage your live-chat choice. The points below describe what it does and what it does not cover:
- What we ask your consent for. Our banner asks for your consent to one thing: the live-chat widget, which is not loaded until you give it by a clear affirmative action. Our analytics and advertising measurement (section 3) are not consent-gated: they run on every visit to our website and the Client Area, whatever you choose. Strictly-necessary cookies are set without consent, as the law permits. The banner described here runs on maxinodes.com, my.maxinodes.com and our Help Centre at support.maxinodes.com, and all three share one consent record. On the Help Centre it reaches less: the Zendesk and Cloudflare cookies in section 4 are set as that page loads, before it, so prior consent is not obtained for those and we do not claim it is.
- Declining is as easy as allowing. Our banner presents Reject all with the same prominence and the same number of clicks as Accept all, on the first screen, and live chat stays off until you turn it on.
- No cookie wall. We never block access to our website or condition the use of our Services on your allowing live chat.
- Analytics and advertising measurement. Our banner cannot switch these off. Your browser can limit them: blocking Meta’s scripts or using a content blocker stops the Meta pixel loading in your browser, and clearing or blocking cookies removes the
_fbpand_fbcidentifiers (see section 6). The events our server sends to Meta do not depend on your browser. You also have the right to object to this processing: see “Your rights” in our Privacy Policy. - Changing your mind. You can change your live-chat choice at any time, as easily as you made it, using the Cookie settings button near the top of this page, which reopens the preferences panel. Withdrawal does not affect the lawfulness of processing carried out before you withdrew. You can also clear or block cookies in your browser at any time (see section 6).
- We re-ask periodically. Consent does not last forever: we ask again at least every 6 months, and whenever the purposes change materially, so the consent we hold stays current. We keep a record of your consent for our own accountability.
We do use third-party storage in four places, and each provider also processes your personal data under its own terms: the Zendesk chat widget if you allow live chat, the Meta pixel on every visit to our website and the Client Area, the cookies Zendesk and its network provider set on our Help Centre as that page loads, whatever you choose in the banner there, and Whop’s card form on our payment page when you pay a new order by card. All four are named in section 4, and every provider we rely on is listed on our Subprocessors page, with where it processes data and the safeguard relied on.
6. Managing cookies in your browser
Separately from any consent choices on our site, your browser and device give you direct control over cookies and similar storage. You can usually view, block, limit or delete cookies through your browser settings, and most browsers let you refuse third-party cookies, clear stored data, or browse in a private / incognito window. The relevant controls are found in the privacy or security settings of Google Chrome, Mozilla Firefox, Apple Safari, Microsoft Edge and other browsers; mobile devices offer similar controls in their system settings.
Please note: some of the cookies we use are strictly necessary. If you block or delete those, parts of the website and the Client Area may not work correctly — for example you may be unable to sign in, stay signed in, place an Order, or complete account and billing actions. Blocking strictly-necessary cookies does not stop us providing the Services, but it may prevent your own browser from using them as intended.
7. Changes to this policy
We may update this Cookie Policy from time to time — for example if we change the cookies we use, introduce new technologies, or need to reflect changes in the law. The version in force is always the one published at this URL, with the version label and “last updated” date shown at the top and bottom of the page. If we introduce any further cookie or similar technology, we will update this policy before we use it. We encourage you to review this page from time to time. Nothing in this policy limits your mandatory statutory rights.
What changed in this version. Version 4.4 was published on October 20, 2026. Since September 20, 2026, our webmail has run on its own server, at webmail.maxinodes.com, and the introduction and sections 3 and 4 now say so: the introduction also describes what webmail keeps in your browser, and section 4 says that webmail reads the language cookie and can set it. Section 3 now also says that the cookies we share across our subdomains reach our Status Page, which UptimeRobot hosts for us, and that they include Meta’s _fbc cookie if you came from one of our ads. Section 3 and the consent-cookie row in section 4 no longer say that nothing on the Help Centre reads your consent record: our own banner there does, as section 3 already said. No cookie was added and nothing about consent changed. Version 4.3 was published on September 25, 2026. Whop’s card form on our payment page now runs on Whop’s newer card-form technology, which our page loads from cdn.whop.com. Sections 1, 3 and 4 now name the one cookie its script sets on the Client Area’s address (_whop_ssk) and the Google payment frame the form loads for Google Pay. Nothing else changed. Version 4.2 was published on September 21, 2026. It adds Whop’s card form, which from that date takes card payment for new orders on our payment page in the Client Area, to sections 1, 3, 4 and 5, as strictly necessary third-party storage. Nothing else changed. Version 4.1 was published on September 19, 2026. It adds one sentence to the introduction, saying that webmail and the cPanel control panel on our hosting servers set only strictly necessary session cookies and are outside this policy, and notes in section 3 that the cookies we share across our subdomains also reach them. Nothing else changed. Version 4.0 was published on September 10, 2026. Our analytics (self-hosted Matomo) and our advertising measurement (the Meta pixel and the events our server sends to Meta) are no longer switched on and off by our consent banner: from that date they run on every visit to our website and the Client Area. The banner now asks about live chat only, and sections 2 to 5 were rewritten to say so. The previous version, 3.0, was published on August 7, 2026 to record four infrastructure changes and the transfers that follow from them: authoritative DNS for customer domains moved to an EU provider on July 26, 2026; our own websites and the Client Area were placed behind Microsoft’s global edge network and our corporate DNS moved to Azure DNS on August 4, 2026; and support moved from our own self-hosted helpdesk to Zendesk, Inc. in the United States on August 6, 2026. Customer websites were not affected by any of them and are still served directly from our servers in the Netherlands. In this policy specifically, that meant removing a bot-protection cookie row attributed to Cloudflare as our own provider — the edge that replaced it sets no cookies at all — and disclosing the cookies Zendesk and its network provider set on our Help Centre. Published with that version: our consent banner now runs on the Help Centre as well, sharing one record with our website and the Client Area. It does not reach the cookies that platform sets for itself, and we say so rather than let the banner imply otherwise. The full record is in the change history on our Subprocessors page.
Contact
Questions about cookies: privacy@maxinodes.com.
By post: Maxinodes Ltd, 1 Ballycoolin Road, Dublin 15, Ireland.
Mail sent to that address reaches our own Microsoft 365 tenant in the EU and is then forwarded into our helpdesk platform, operated by Zendesk, Inc., a Delaware corporation established in the United States. Your message, anything attached to it and our correspondence about it are stored there. Our account data is currently held in its Europe (Ireland) region, but we have no contractual commitment to that region, and the provider and its named United States sub-processors can reach that data from the United States — so it is processed outside the EEA. If you would rather your message did not pass through a third-party helpdesk — for example because it includes identity documents, or because it names someone else — write to us by post at the address above, or email billing@maxinodes.com, which reaches us directly.