ServerHive

Privacy Policy

Last updated: September 8, 2026

This Privacy Policy explains what information ServerHive collects through the website (serverhive.gg), the bot dashboard (bot.serverhive.gg), and the ServerHive Discord bot (together, the "Service"), and how we use it. We collect only what we need to run the Service — we don't run advertising, analytics, or tracking scripts, and we don't sell your data.

1. Information we collect

Account information

  • Steam sign-in (site — server owners, voters, dashboard users): your SteamID64, Steam display name, and Steam avatar image.
  • Discord sign-in (bot dashboard): your Discord user ID, username, display name, avatar, and an OAuth access/refresh token that lets us look up which Discord servers you can manage. We only request the "identify" and "guilds" OAuth scopes — we never see your Discord password.

Content you provide

Server listings and descriptions, uploaded banner images, wiki/guide pages, suggestion text submitted via the bot's /suggest command, and anything you type into a support-ticket form or ticket channel the bot manages.

Voting data

When you vote for a server, we store a one-way SHA-256 hash of your IP address combined with the server ID, plus your Steam account if you're signed in. We never store your raw IP address — the hash exists only to enforce the per-server vote cooldown and detect abuse, and can't be reversed back into an IP address.

Discord server (guild) data

To operate on a Discord server, the bot processes data belonging to that server: guild and channel IDs, role IDs (including the roles an admin offers on a role panel), ticket and suggestion messages, the Discord user IDs and tags of ticket openers and suggestion authors, and — for servers where a Discord administrator has enabled message-content access and transcripts — the content of messages inside ticket channels, so a transcript can be generated when a ticket closes. This data is controlled by that server's admins, not by the individual member.

When you click a role panel, the bot adds or removes that Discord role on your member profile in that server. It does not keep its own record of which roles you picked — your roles live in Discord, and the bot reads them from Discord each time you click.

If you set a personal bot language with /language, we store your Discord user ID, the server ID, and the chosen language so the bot can answer you in it.

Ticket transcripts

When a ticket closes on a server where transcripts are enabled, the bot renders the ticket channel into an HTML transcript (message text, attachments' links, embeds, and the participants' Discord names and avatars) and stores it on our servers. The transcript is reachable at an unguessable link (serverhive.gg/t/…) that is posted to the server's archive channel and sent to the ticket opener by direct message; anyone who has the link can open it, and search engines are told not to index it.

Cookies

We use functional cookies only: a session cookie once you sign in with Steam or Discord, and a short-lived cookie to enforce the vote cooldown for signed-out visitors. We do not use advertising or analytics cookies.

2. How we use this information

  • to authenticate you and keep you signed in;
  • to show you the servers and Discord guilds you're allowed to manage;
  • to display server listings, guides, suggestions, and vote counts;
  • to operate bot features you or a server admin enabled (tickets, suggestions, role panels, per-user language via /language);
  • to enforce vote-cooldown and anti-abuse rules; and
  • to keep the Service secure and diagnose problems.

We do not use your data for advertising, and we do not build behavioral profiles for marketing.

3. How we share information

We don't sell your personal data. We share it only with:

  • Steam, Discord, and Epic Online Services — solely to authenticate you or, for Epic, to query public ARK: Survival Ascended server status. We don't send them data beyond what those integrations require.
  • Our infrastructure providers — our database, and S3-compatible object storage used to host uploaded banner images. These providers process data on our behalf and don't use it for their own purposes.
  • Other members of a Discord server — content you post through the bot (suggestions, ticket messages) is visible to that server's members and staff by design, the same as any other Discord message. A closed ticket's transcript is visible to whoever the server's admins share its link with.
  • Legal requirements — if required to comply with a valid legal request.

4. Data retention

We keep account and OAuth-session data for as long as your account exists, and delete it if you request account deletion. Discord OAuth tokens are stored on our servers and used only to operate features you've enabled; revoking ServerHive's authorization in your Discord settings invalidates them on our side too. Suggestion content is retained until the suggestion is deleted by a server admin. Ticket transcripts are deleted automatically one year after the ticket closes (the operator may configure a different window), and immediately when the ticket is deleted from the dashboard. Vote hashes are retained only as long as needed to enforce the cooldown window. Removing the bot from a Discord server stops all new processing for that server; its stored configuration and content can be deleted on request.

5. Data security

The Service is served over HTTPS. Access to stored data, including OAuth tokens, is restricted to what the Service needs to operate and is not shared outside the providers listed above. No online service can guarantee absolute security, but we take reasonable technical measures to protect your data.

6. Your choices

  • You can sign out at any time, which clears your session cookie.
  • You can revoke ServerHive's access to your Steam or Discord account from that platform's own account settings.
  • A Discord server admin can remove the bot from their server at any time, which stops it from processing new data there.
  • You can request access to, correction of, or deletion of your personal data by emailing [email protected]. Content posted inside a Discord server (tickets, suggestions) may also need to be removed by that server's admins, since it's part of their Discord server.

7. Children's privacy

The Service is not directed at children, and we do not knowingly collect personal information from children under 13. If you believe a child has provided us personal information, contact us and we'll remove it.

8. Changes to this policy

We may update this Privacy Policy from time to time. If we make material changes, we'll update the "Last updated" date above. Continuing to use the Service after changes take effect means you accept the updated policy.

9. Contact

Questions about this Privacy Policy, or a data request? Email us at [email protected].

Privacy Policy — ServerHive · ServerHive