Privacy
This site keepsalmost nothing.
What this website keeps about you, and what it doesn't. The Horizon launcher and game have their own rules, set by the Horizon project: they are on Horizon's privacy page (opens in a new tab).
In short
- No cookies for visitors. Signing in, as a staff member or to submit or rate a mod, sets one session cookie.
- No analytics, trackers or ads.
- One thing is kept on the server: a one-way hash of your IP address when you open a release, so each release counts each visitor once.
- A few choices you make stay in your own browser, and never leave it.
Release views
Each release on Releases shows how many people opened it. When you open one, the server turns your IP address into a one-way hash, using a secret key that stays on the server, and keeps that hash next to the release. The address itself is never stored, and the hash can't be turned back into it. The same address opening the same release again counts once.
The hashes are used only to keep those counts, are not linked to anything else, and are never shared. Only the number of views is shown.
What stays in your browser
The site remembers three choices in your browser's local storage. They stay on your device and are never sent to the server:
horizon:seen-releases: which releases you have opened, so the list can mark new ones.horizon:partners-hidden: that you hid the partner banner.hub:detail: whether the Hub reads in simple or technical words.
Clearing this site's data in your browser removes them.
What your browser loads from GitHub
Contributors' and mod authors' pictures come from avatars.githubusercontent.com, mod icons from horizon-rust.github.io, and every download from github.com. Those requests go from your browser to GitHub, and GitHub's privacy statement (opens in a new tab) covers them. Nothing else on this site is loaded from another company, except in the shop (/shop and /shop/pay): once you start a claim or a purchase there, it loads Paddle.js from cdn.paddle.com, and Paddle's checkout runs in it under Paddle's privacy policy (opens in a new tab). The face shown to confirm a Minecraft account is that account's skin, loaded from textures.minecraft.net (Mojang).
Signing in
The staff dashboards and the mod registry's sign-in are run by the Horizon project's own services; this site only passes your requests on to them. Signing in to the dashboards sets an HttpOnly session cookie from Kira, Horizon's Discord bot, that ends after 12 hours without use and 7 days at most. Signing in with GitHub to submit or rate a mod sets the registry's session cookie for 12 hours, or until you sign out. Both go only to the service that set them, and the Horizon project is responsible for what those services keep.
What the server fetches
To show releases, the roadmap, contributors and mods, the server fetches them from GitHub, from Horizon's mod registry and from the registry's ratings. The Players page's counts come from Horizon's telemetry server through this site's server too, so your browser never contacts it. Those requests carry nothing about you.
The launcher, the game and Discord
What the Horizon launcher and game can send, the “I'm playing” ping, the mod registry's sign-in and Horizon's Discord are run by the Horizon project, and Ludovic Marie is responsible for them. Read Horizon's privacy page (opens in a new tab) for what they keep, and write through lu4ovic.com (opens in a new tab) about it.
Cosmetics and purchases
Horizon's cosmetics service is run by Ludovic Marie, who is responsible for what it keeps. You claim and buy cosmetics on this site's shop, without signing in: your browser sends the Minecraft name you type to the service (cosmetics.playhorizon.dev), which looks it up in Mojang's public profiles and keeps the answer in memory for ten minutes. For each Minecraft account, keyed by its UUID, the service keeps:
- the items it owns and since when, what it wears, whether its cosmetics are hidden, and when it claimed the founder set;
- if the founder set was claimed in the launcher's Wardrobe because Paddle doesn't serve your country: that country's two-letter code. The service finds it from your IP address in a database it holds itself (IP geolocation by DB-IP (opens in a new tab), CC BY 4.0) and keeps the country only, never the address;
- for each order: Paddle's transaction id, the item, the amount and currency paid, its state (paid, refunded, disputed) and its date, so the launcher can show your purchase history and refunds can take the item back.
Nothing else: no name, email, address or payment details. Paddle.com, the merchant of record, takes the payment and keeps your email, country and payment details under Paddle's privacy policy (opens in a new tab); of what Paddle sends, the service keeps only the lines above. Orders are kept as long as tax law requires a record of them. To see or delete what the service holds about your account, write to [email protected].
Who is responsible, and your rights
This website is developed and run by Anthony S of DezerX (opens in a new tab), who is responsible for what it keeps. You can ask what it holds about you, or have it deleted, through dezerx.com. Because only a hash of your address is kept, include the IP address you used, so your entry can be found. You can also complain to the data protection authority where you live.
Last updated on 4 November 2026.