Signing in sets one cookie. It is strictly necessary to the service you asked for, so the ePrivacy directive exempts it from consent, and it is used for nothing else. Only the Google Ads cookies ask for your consent: the banner asks at your first visit, and refusing changes nothing on the site.
Last updated
Your theme and your language, in the browser's local storage. The theme is read by this page alone; the language also travels with anything you send us through the contact form, since a message carries the language it was written in.
Signing in sets the session cookie, which keeps you signed in from page to page. No script on this page can read it. Signing out removes it.
Starting an account sets one more, and only for as long as the confirmation is outstanding: it lets the page you started on notice you have opened the link in your mail and carry on without you. It is strictly necessary to the registration you asked for, no script on this page can read it either, and it carries nothing about you. It goes when the registration finishes, when you clear the browser's data, and a day after it was set in any case.
Writing to the site assistant puts the conversation's reference in the session storage of this tab, at your first message and not before: it lets you carry on the same conversation from page to page. It is strictly necessary to the service you asked for, carries nothing about you and goes when you close the tab.
Your answer to the cookie banner, in the browser's local storage, for six months: after that, the banner asks again. It is strictly necessary so the question is not asked on every page, and it carries nothing about you.
Clearing the browser's data removes them all, and signs you out.
The private pages the association uses to manage the catalogue set a session cookie of their own, on the same terms. Nobody else opens them, and this site therefore does not count its cookies on your behalf.
Without your consent to the Google Ads cookies, no third party is contacted while you read this site: no font, no image and no script is fetched from anywhere else. Writing to us is the exception, because the contact form forwards your message to a private Discord channel, and the site assistant has its answers written by Anthropic, to whom our server forwards your messages; the privacy page sets out both. For the assistant, your browser talks to our site alone.
Paying is the other exception. The payment step of the order page, which also renews a server and pays for an option by card, paying for an order or confirming a payment from the My servers page and the payment step of the Credits tab load Stripe.js, our payment provider's script; no other page loads it. Stripe.js then sets its own cookies, __stripe_mid, kept for a year, and __stripe_sid, kept for thirty minutes, which detect fraud on the payment you are making, as payment rules require of our provider. They are strictly necessary to that payment, which you asked for, so they do not ask for your consent (article 82 of the French Data Protection Act).
Google Ads is the one exception that asks for your consent. If you accept it in the banner, every page loads Google's script from googletagmanager.com. It sets the _gcl_au cookie, kept for 90 days, which ties an order to the ad that brought you, and Google may read its own cookies on its domains, such as google.com and doubleclick.net. For each paid order, its number and amount go to Google. Until you answer, and if you refuse, none of this is loaded. You can change your mind at any time through the Cookie settings link in the footer; withdrawing your consent removes _gcl_au.
Our web server keeps short technical logs of the requests it serves, so that we can spot an outage or an attack. How long they are kept is set out on the privacy page.
Horizon Hosting is an independent host, with no link to any game publisher. Game names, logos and images belong to their publishers and only show which game a server runs. Not an official Minecraft service. Not approved by or associated with Mojang or Microsoft.