Privacy
To be completed by the operator before going live. This document describes exactly what data the site handles, as it appears in the code. What remains is the controller's identity, the host, the email provider and the retention periods, marked
[…].
- Data controller:
[legal name and address] - Contact: [email protected]
What we collect
For your account
| Data | Why | Required |
|---|---|---|
| Email address | Sign-in, password reset, moderation notices | Yes |
| Password | Sign-in. Stored hashed, never in clear, unreadable by the team | Yes, unless using Discord |
| Username | Publicly identifying the author of a preset | Yes |
| Display name, avatar | Taken from your Discord profile on sign-in | No |
| Habbo name and hotel | Showing your Habbo name on your profile, once verified | No |
| Bio | Introducing yourself on your profile | No |
| Language | Serving the site in the right language | Yes (detected) |
For running the site
Downloads and views. Each counted download records the preset, the date, the country (two-letter code) and the referring host — never the full URL of the page you came from.
IP address. Your IP is never stored in clear. It goes through an HMAC-SHA256 with a server-side salt, and only that digest is kept. It serves two purposes: rate-limiting forms (sign-in, registration, password reset) and avoiding counting the same download ten times. Without the salt, the digest can't be traced back to an IP.
Moderation log. Every moderation decision — publishing, rejecting, suspending — is recorded with its author, target, date and reason. That's what makes a decision challengeable.
What we don't collect
No advertising trackers, no third-party analytics, no cookie other than the session one. Nothing is sold or passed to a data broker.
Cookies
One cookie: the session cookie, set when you sign in, which keeps you signed in. It's essential to the service — without it you'd be signed out on every page — so it doesn't require prior consent. Signing out removes it.
A YouTube video embedded on a preset page is not loaded until you click it:
while the thumbnail is showing, YouTube receives nothing. On click, playback
goes through youtube-nocookie.com, and Google's rules apply from there.
Where data goes
- Database and file storage:
[host and country]. - Email delivery: Lumail (
lumail.io), a provider relaying via Amazon SES, for verification, reset and moderation messages. The recipient address is passed to this provider for delivery; it creates a transactional contact per unknown address — that's how it works. - Discord, if you choose to sign in with it: WiredHub receives your ID, name and avatar. Nothing is sent back to Discord.
How long we keep it
| Data | Retention |
|---|---|
| Account and published content | As long as the account exists |
| Deleted account | Erased; published presets are withdrawn or anonymised, at the author's choice |
| IP digests for rate limiting | The length of the window, a few minutes to an hour |
| Download log | [retention chosen by the operator, e.g. 24 months] |
| Moderation log | Kept, so a decision can be justified |
Your rights
You can request access to your data, its correction, its erasure, its portability, or object to a processing operation, at any time. Most of this is available directly in your account settings. For the rest, write to [email protected].
If a disagreement persists, you can lodge a complaint with your data protection authority — in France, the CNIL.
Security
Passwords are hashed. Reset links expire and work only once. Public forms are rate-limited. Uploaded images are re-encoded server-side, which discards booby-trapped files. None of this makes a breach impossible: should an incident affect personal data, the people concerned and the competent authority will be informed.
Minors
The site isn't meant for under-13s. If an account belonging to someone under 13 is reported to us, it is deleted.