Privacy policy

1. Visiting the website and hosting

When you visit the website, technically necessary requests are sent to the hosting infrastructure. In particular, IP address, time, requested address and browser and device information may be processed. genMC runs at genmc.app on Cloudflare (Workers, D1, R2 and Durable Objects); database and storage are located in Western Europe. The processing serves the secure delivery and operation of the website (Art. 6(1)(f) GDPR). Cloudflare may also process data outside the European Economic Area. Details on processing by Cloudflare are in the Cloudflare privacy policy.

genMC used to run at genmc-studio.kolio.chatgpt.site. Visiting that address redirects to genmc.app. If you built there without signing in, your browser passes on the pseudonymous identifier of your drafts once (as a hash, signed and valid for ten minutes), so that your builds and skin drafts are assigned to you again on genmc.app. No other data is transferred.

2. Cookies and local storage

The cookie genmc_session assigns private drafts and projects to a browser. It is limited to one year. When you sign in, genmc_auth is added for the session (at most 90 days); Google sign-in briefly uses genmc_oauth for the return trip (ten minutes). These cookies serve the studio you actively use and signing in. They are not used for advertising. The legal basis for the related processing is Art. 6(1)(b) GDPR; for security measures Art. 6(1)(f) GDPR. Strictly necessary storage is covered by § 25(2) TDDDG.

Your chosen appearance, language and settings are stored in this browser's localStorage. An optionally imported texture pack and intermediate results may be kept in this device's IndexedDB. An agent session you connected yourself and which skin is open in a tab are kept temporarily in sessionStorage. You can delete this data in your browser settings; deleting an anonymous session cookie can end access to the related private projects.

3. Studio, gallery and feedback

Private skins, builds, maps and agent requests are stored so that projects can be continued and edited. A secret build link gives everyone with that link access to the linked project. Published skins and builds, including names, content, origin and, where applicable, the AI model used, are visible in the public gallery; builds also show the username you chose (3–20 letters, digits and underscores). Please do not choose your real name. Likes and reports are assigned to the account so each account counts only once; they are not publicly linked to the username. When a build is reported, the operator receives a notification with the build and username, without email addresses.

Feedback sent through the feedback form contains the text you entered, the type of feedback, the page path without parameters and, only if given, an email address for a reply. It is intended for the operator only, is not linked to any account and is deleted after twelve months at the latest, earlier on request. The legal basis is Art. 6(1)(b) GDPR for studio and publishing features you request and Art. 6(1)(f) GDPR for feedback, abuse prevention and moderation. Content is generally stored until the user deletes it or on a justified request; legal obligations may require longer retention.

4. Sign-in and external services

An account is optional and has no password. For email sign-in we send a six-digit code that is valid for ten minutes and stored only as a hash. For delivery, the address is passed to Resend. In the account itself we do not store the address in plain text, only as a one-way hash additionally formed with a secret key (HMAC). The key is kept separately from the database. This lets an account be found again at the next sign-in, but the address cannot be recovered or displayed, not even in the admin area. Even with a copy of the database, it cannot be checked without the key whether an account exists for a known address. Because the operator knows the key, this is still pseudonymised rather than anonymous data. Older accounts are switched to this storage automatically.

The optional Google sign-in only redirects to Google once you choose it; afterwards we receive an identifier of the Google account and the confirmed email address, of which we likewise store only the hash. The account also includes its creation time, username and sign-in sessions. If an account is blocked for abuse, all sessions end and its gallery builds, likes and reports are deleted. The hash of the address or the Google account identifier is kept with a block note, so the same person cannot register again.

If Cloudflare Turnstile is set up, it is loaded only in the email sign-in form and processes technical browser signals and the IP address to protect against automated requests. More information is in the privacy notices of Google and Cloudflare. The legal basis for sign-in is Art. 6(1)(b) GDPR, for abuse prevention Art. 6(1)(f) GDPR.

Only when a Minecraft player lookup is triggered does the server request profile data from Microsoft/Mojang's Minecraft services and, where needed, from the public profile caches playerdb.co and, as a last resort, mc-heads.net. The entered player name is sent to these services; the server, not your browser, asks them, so they do not see your IP address. The skin image itself comes from Mojang's texture server (textures.minecraft.net) whenever possible. Only when you click “Load textures” in the offer shown on your first visit or “Load from Minecraft.net” in the settings does the browser download the block textures directly from Microsoft/Mojang's download servers (piston-meta.mojang.com, piston-data.mojang.com); these receive the IP address and technical browser data. genMC itself does not receive these files. When you voluntarily connect an external agent, the studio data and requests you share may be processed by that agent service. Its own privacy notices also apply.

5. Usage statistics

genMC measures usage with its own cookieless statistics. It records page views and individual studio events (downloads, connecting an agent, tool calls of a connected agent). For each event it stores the time, the path without parameters and project identifiers, the referring website or a campaign tag (utm_source), the country according to the hosting provider and the device type (desktop, tablet, mobile). To count visitors per day, a shortened hash is formed from IP address and browser identifier together with a random value created anew each day. The random value is deleted the next day; the IP address itself is not stored. There is no recognition across days, no profile and no link to accounts.

Nothing is stored on or read from your device for this; no cookies, no local storage and no third-party services are used. The data is kept in the deployment's database (section 1), visible to the operator only, and deleted after 180 days. The legal basis is the legitimate interest in improving the service and shaping it to demand (Art. 6(1)(f) GDPR). You can object to this processing at any time at contact@genmc.app.

6. Retention and your rights

Sign-in codes expire after ten minutes, sign-in sessions after at most 90 days, statistics events after 180 days, feedback after twelve months. Protection against abusive requests uses limited counters; their keys may contain hashes of IP addresses. Expired counters are removed at the next protected request. Private project and account data is kept until deleted or until a justified deletion request, unless legal obligations prevent this.

The fastest way is to do it yourself: under Settings → Privacy you download all data stored about you as a file (access and data portability) or delete your account, skins, builds, maps and gallery posts immediately and for good. Without an account, this covers the data of this browser.

Data subjects can request access, rectification, erasure, restriction and data portability, and can object to processing based on legitimate interests. They can also lodge a complaint with a data protection supervisory authority. Please send requests to contact@genmc.app.