Privacy Policy

Last updated: October 11, 2026

This Privacy Policy explains what information slime.hq ("we," "us") handles, how we use it, and the choices you have. slime.hq is a volunteer community project. We aim to collect as little as possible, and most of what we display is information you have already made public on Discord or Twitch.

1. Information We Handle

From Discord (for members with the @creator role)

• Your Discord user ID, display name/nickname, and avatar image;
• Your @creator role membership;
• Only if you opt in via /settwitch: the Twitch handle you choose to provide.

From Twitch (public data, opted-in creators only)

• Your public live/offline status, and when live, your public stream title, game/category, and viewer count;
• Publicly available game box-art images for display.

Community events

• Scheduled events created in our Discord server (name, time, description): public server data.

Community media

• Clips, recordings, or screenshots captured in our community spaces that we feature on the Service or our official social channels may include your voice, username, avatar, gameplay, or chat. See the Community Media section of our Terms; you can ask us to remove media featuring you at any time (see Contact below).

If you contact us

• If you email us (for example, via the "Apply" button), we receive your email address and whatever you include in your message.

From the guild application form

• If you submit the guild application at /slime69, we collect what you enter: your in-game character name and Discord username (required), and any optional details you choose to add (weapon combo, combat power, region/timezone, and your message). We use this only to review your application and to contact you on Discord about joining the guild. Applications are not public: they are seen only by our guild officers, stored in our database, and may be delivered to a private officers channel in our Discord. We also keep a one-way, truncated hash of your IP address solely to rate-limit spam submissions. You can ask us to delete your application at any time (see Contact below).

From Slime Chat (anyone who posts)

• The message text you post and the time. Messages are public: they are shown to other visitors and are delivered into the #watch-party channel of our Discord server, where Discord stores them under Discord's Privacy Policy.
• As a guest: the temporary display name you type. It is not an account and is not verified; your browser keeps it for the session, and we keep it with your message as described under retention. We also keep a truncated, one-way hash of your IP address (not your IP itself), used only to rate-limit and curb spam and abuse. We cannot reverse it back into your IP.
• If you connect with Discord: Discord tells us your Discord user ID, username, display name, and avatar, and you grant the "Join servers for you" permission, which we use once to add your account to our server. We then read your server nickname and roles to show community badges. We never see your Discord password or email, and we do not keep the Discord access token. Your connected identity is held in a signed cookie in your browser (a functional sign-in cookie, not a tracking cookie) for up to 30 days or until you choose Disconnect; we re-check it every few hours and stop treating you as connected if you have left the server. With each message you post we record your Discord user ID, display name, avatar link, and badges.
• Messages posted in #watch-party: if you post in that channel of our Discord server, your message, Discord display name, and avatar are shown publicly on slimehq.live, as the channel's topic and pinned message state. The site reads them from Discord when the page asks and holds them for only a few seconds of caching; we do not archive them.

Creator link sync (optional, creators only)

• Creators can optionally sync their public profile links to their slime.hq creator card by signing in with Discord and granting the connections permission. Discord then tells us which connected accounts you display publicly on your Discord profile (for example Twitch, YouTube, Instagram, Spotify), and we store just those account names and links so we can show them on your card. We never see connections you have set to private, and we do not store the Discord access token after the sync.
• Syncing is entirely optional and re-runnable; your card otherwise shows only links set up manually with an admin. To remove synced links at any time, use the "clear my links" option on the sync page or contact us, and they are deleted.

From the Guild Portal (members-only area, if you sign in)

• When you sign in with Discord to open a members-only page (such as our Throne & Liberty guild portal), Discord tells us your Discord user ID and username and your roles in our server, which we check once to confirm you hold the required guild role. We never see your Discord password, and we do not store the Discord access token after that check.
• If the check passes, we set a signed sign-in cookie in your browser containing your Discord user ID so you stay signed in. It expires after 30 days (or when you log out). It is a functional login cookie used only to keep you signed in; it is not a tracking or advertising cookie, and we keep no server-side copy of it.
• Some portal panels can remember choices you make (such as ticking which game items you own) in your browser's local storage, on your device only. Nothing in it identifies you, none of it is ever sent to us or anyone else, and clearing your browser data removes it.
• Portal content panels such as the per-card Wear These item loadouts read only the game-data records served with the page; they add no separate data collection beyond the sign-in described above. Archboss weapon and dedicated core build recommendations, including Ramux Spear with Sword & Shield (Steelheart), a heroic Orb build using Enraged Tevent's Corruption, Morokai Gladiator comparisons, and Staff & Dagger Spellblade GvG build comparisons (including the post-4.15 review of passive triggers, captured equipment values and finite candidate plans), are shared game guidance based on public game information. These cards and comparisons add no new profile fields, tracking, or third-party data sharing. The refreshed build catalog, compact search, and relocation of existing reference tools to Misc change shared game guidance and its presentation; they add no new personal-data collection. The build-card eligibility audit, visible core assignments and empty-slot explanations, core comparisons, and revised core and rune explanations use the same shared public game records and add no new personal information. Repairs to selected-form defense, control opportunities, conditional uptime and matchup scoring use those existing shared game records and add no new profile fields, tracking or data collection. Joint Spellblade skill and gear-core assignments use the same shared public game records and add no new personal information. Joint GvG candidate reviews and newly indexed ordinary native weapon records use public game snapshots and declared build-role criteria. They add no new profile fields, personal-data collection, tracking or third-party sharing.
• Frontline protection, avoidance and objective-role comparisons use shared public game records and stated combat and capture assumptions. These recommendations add no new profile fields, personal-data collection, tracking or third-party sharing. The Discord sign-in and guild-access practices described above continue to apply.
• Crucifix guild-boss recommendations use shared public game records and stated single-target damage assumptions. This content adds no personal-data fields, damage-log uploads, profile collection, tracking or third-party sharing. Existing Discord sign-in and guild-access practices continue to apply.
• The Guild Portal presentation refresh updates visual hierarchy, navigation, typography, colors and responsive layouts. It adds no personal-data fields, collection, tracking, sharing, font providers or authentication behavior. The browser can match locally installed Turkish Microgramma and Eurostile to draw text, with readable fallbacks; the Portal does not collect an installed-font inventory or supply those font files. The existing Google Fonts requests for Bricolage Grotesque, Hanken Grotesk and Space Mono and the existing sign-in and guild-access practices continue to apply.
• Scout group-burst packet models, published effect delays and conditional build choices use the same shared public game records and stated scenario assumptions. This comparison feature adds no new profile fields, personal-data collection, tracking or third-party sharing. The existing Discord sign-in and guild-access practices described above continue to apply.
• Scorpion group-burst packet models, published effect delays and conditional build choices use the same shared public game records and stated scenario assumptions. This comparison feature adds no new profile fields, personal-data collection, tracking or third-party sharing. The existing Discord sign-in and guild-access practices described above continue to apply.
• The portal displays guild game information compiled from the in-game guild members panel and member submissions: character names, combat power, guild reputation and activity figures, last-seen times, and member memos. It is visible only to signed-in guild members. If you are a guild member and want your entry corrected or removed, contact us (see below).
• The portal also shows a measured gear model for the game (recommended heroic armour, accessories, gear cores and armour-set layouts per build), distilled from the same public game data. The per-build Your Specializations planner is the same model applied to the card's own points table to produce a settable end state. Since October 3, 2026 the recommendations are weighted by a damage model computed from the same public game data and from aggregate statistics of character builds that their authors shared publicly on questlog.gg; it uses no information about you, and nothing about those authors beyond each build's public link, kept as the source. They add nothing to the information listed above.
• If you use the portal's weekly raid boss vote, we store your Discord user ID alongside the bosses you picked, the week you picked them for, and the time you saved them. We use this only to enforce the limit of three picks per member per week and to total the votes. Your individual picks are never shown to other members, and no totals at all are shown to anyone until voting closes; after that only the combined vote counts per boss are displayed, never who voted for what. You can change your picks any time before voting closes, and saving an empty ballot removes them. Ballots are deleted automatically about four weeks after they are cast, and you can ask us to delete yours sooner (see Contact below).

Technical data and Cloudflare Web Analytics

• Our host, Cloudflare, processes standard technical data (such as IP address and browser type) to deliver and secure the site.
• We use Cloudflare Web Analytics to count page views. It is a privacy-first, cookieless measurement tool: it sets no cookies, stores no identifier on your device, does not collect personal data and does not fingerprint you. It does not follow you to any other site. It tells us that a page was viewed, roughly from where, and on what kind of browser, in aggregate. It is never joined to your Discord identity, your email, or anything you post in Slime Chat.
• To be exact about where it runs: the Cloudflare Web Analytics script is present on every page of this site, including the store pages. It is injected by our host at the edge rather than written into any page here, so it is turned on and off in a Cloudflare setting rather than in a file. An earlier version of this bullet said it was not on the store pages. That was wrong, and it was corrected as soon as a real browser was used to check: a plain command line fetch does not receive the injected script, which is how the error was made. The store pages still load no advertising tag and no tracking pixel, which is the promise made below and is a different and stronger claim: Cloudflare Web Analytics is cookieless, sets nothing on your device and shares nothing with an advertiser.
• This is separate from the advertising described below. Cloudflare Web Analytics is not an advertising tool and shares nothing with an advertiser. The Google ad tag and the Meta Pixel are a different thing, they do use cookies, and they are described in their own sections so the two are never confused.

Advertising & the Meta Pixel

• We use the Meta Pixel on slimehq.live. It sets cookies and sends Meta (Facebook/Instagram) standard events, such as page views, so we can measure and improve our ads and reach people who have already visited the site. It does not capture what you type, and we do not send Meta sensitive information.
• Your controls: adjust your Meta ad preferences, use your browser's tracking-prevention settings, or opt out of interest-based ads via the DAA and EU tools.

Our own promo card (Recommendations)

The homepage player and any slime.hq live-stream promo use the same recent public live-status check. If no creator is live, the player offers recent videos and the promo links to our creators; if the check is unavailable, we say so without claiming a stream is live. This display choice adds no new visitor information or browser storage.

• The home page can show a small card promoting our own stuff (a stream, a page on this site). Which one you see is chosen by software we run ourselves at adamp.cuttadj.com. It is not an ad network, no outside advertiser is involved, and nothing about you is sent to a third party.
• To make that choice it receives only: whether you are on a phone or a desktop, the hour of day, and which slot on the page the card sits in. It does not receive your name, your email, your IP-based location, or your chat messages, and it does not build a profile that follows you across other websites.
• It stores two small values in your own browser: the id of the last card you were shown (so a click can be matched to the right card) and, if you dismiss the card, a note not to show it again for the rest of your visit. You can clear both at any time by clearing site data in your browser.
• We record whether a card was shown and whether it was clicked, so the software learns which of our promos is worth showing. That counting is aggregate.
• The same software also keeps aggregate counts about the Google ads on our pages: whether an ad unit displayed (a status Google's own ad code marks on the page) and whether one was likely clicked. Those counts are bucketed only by site, device type, and time-of-day band, live on our own server, contain no identifiers and no per-visitor records, set no cookies of their own, and are never sent to any third party.

Google ads

• Some pages show advertising served by Google. Google and its partners use cookies or similar technologies to serve and measure those ads.
• Ads on slime.hq are non-personalized. Because our community includes people under 18, we tell Google not to use browsing behaviour to target ads here. Non-personalized ads are based on the page's content and rough location, not on a profile of you, and they still use a cookie for frequency capping and fraud prevention.
• You can review or change ad settings at Google Ads Settings, and opt out of other vendors' interest-based ads at aboutads.info/choices.
• If you are in the European Economic Area, the United Kingdom, or Switzerland, you will be asked for your consent choices before ads are shown, and you can change those choices at any time.
• Global Privacy Control (GPC). If your browser sends a GPC signal, we honour it automatically: ads stay non-personalized (as they always are here) and the Meta Pixel is not loaded at all for that visit, so no page-view events are sent to Meta.
• We do not give advertisers your Discord identity, your email, or anything you post in Slime Chat.

We do not collect payment information, and we do not sell your personal information.

2. How We Use Information

Solely to operate the Service: to display participating creators, detect and show public live status, embed and link streams, list community events, run and moderate Slime Chat (including rate-limiting and blocking abuse), verify Discord guild membership and roles to control access to members-only pages, run the members-only weekly raid boss vote (to enforce one ballot of three picks per member per week and to total the votes), and respond to messages you send us.

3. Consent & Opt-In

Featuring is opt-in. You provide your consent by joining our Discord, accepting the @creator role, and/or running /settwitch. Much of the information we display is already public within our Discord server or on Twitch; featuring it on slimehq.live makes it visible to visitors of the site.

3b. The Store

If you buy something from the store, more is collected than anywhere else on this site, and only for that order:

• Card details go to Stripe, our payment processor, and never to us. You type them on Stripe's own hosted checkout page. We receive a payment reference and the last four digits.
• Your name, shipping address, email address and phone number are collected at checkout and passed to the third-party print manufacturer that makes and ships your order. That is the entire purpose.
• The store pages carry no advertising tag and no tracking pixel. /store.html, /order.html and /store-policies.html deliberately load neither, unlike the rest of this site.
• We do not sell your personal information and we do not share it for cross-context behavioural advertising.

Full terms of sale, shipping, returns and refunds: store policies.

4. How Information Is Shared

We do not sell your data. Information is processed by the service providers that make slime.hq work: Cloudflare (website hosting and email routing), Discord, Twitch, Meta (the Meta Pixel, for ads measurement and audiences), Google (advertising, as described in the Google ads section above), and, for store orders only, Stripe (payment processing) and our print-on-demand manufacturer (making and shipping what you bought). Messages you email us are delivered to our operators' inbox. We may disclose information if required by law or to protect rights, safety, or the integrity of the Service.

5. Data Retention

We keep your linked Twitch handle and recent live history only while you participate. When you opt out (via /removetwitch, leaving the Discord, or having your role removed), we stop displaying your information and remove your linked handle, subject to short technical caching delays.

Slime Chat messages live in the #watch-party channel of our Discord server, under Discord's retention, and the site shows only the current week's messages. For messages posted on the site we keep a short label record (the guest name or Discord identity and badges, plus the hashed IP or Discord user ID used for rate limiting) for up to 14 days, then delete it automatically; we keep no long-term archive. A message deleted in Discord disappears from the site. Messages from the earlier guest-only version of Slime Chat are no longer shown and will be deleted by October 11, 2026. To have a message removed sooner, ask a moderator in our Discord or contact us.

Guild portal sign-ins live only in the signed cookie in your own browser (up to 30 days); we keep no server-side session record. Guild roster figures shown on the portal come from periodic snapshots and remain until replaced by a newer snapshot or removed on request.

Store order records (what you bought, the reference, and the address it went to) are kept as long as needed to fulfil the order, handle a return and meet tax and record-keeping duties, then no longer. Ask us to delete anything not legally required and we will.

Raid vote ballots (your Discord user ID, the bosses you picked, the week, and the time you saved them) are kept only as long as they are useful for running the raid and settling any question about the result. They are deleted automatically about four weeks after they are cast. You can clear your own ballot at any time before voting closes by saving an empty one, or ask us to delete it (see Contact).

6. Your Choices & Rights

• Opt out anytime: use /removetwitch, leave the Discord, or ask an admin to remove your @creator role.
• Access or deletion: email us to request access to, correction of, or deletion of information we hold about you.

7. Children

The Service is not directed to children under 13, and you must meet the minimum age required by Discord and Twitch to participate. We do not knowingly collect personal information from children under 13. If you believe a child under 13 has provided us personal information (for example, by posting it in Slime Chat), contact us (see Contact) and we will delete it promptly.

8. Security

We take reasonable steps to protect information, but no method of transmission or storage is completely secure, and we cannot guarantee absolute security. You use the Service at your own risk.

9. Third-Party Services

The Join community link opens our existing Discord invite. Discord handles that visit and any decision to join under its own terms and privacy policy.

The Service links to and relies on Twitch, Discord, Cloudflare, and Google (for advertising), each of which has its own privacy practices that we do not control. Please review their policies. slime.hq is not affiliated with or endorsed by Twitch, Discord, Amazon, or Google.

10. Changes

We may update this Policy; the "Last updated" date reflects the current version.

11. Contact

Privacy questions or requests? Email apply@slimehq.live.

slime.hq · Home · Terms of Service · Disclaimer