Documentation

Privacy Policy

What we collect, why we collect it and the choices you have.

Last updated 17 November 2026.

This Privacy Policy explains what data Signal Core (the "Bot"), run by HunterCorlett ("we", "us", "our"), collects, why, and how it's handled. It applies to anyone who uses the Bot or is in a server the Bot has been added to. It covers the Discord bot, the dashboard and our public pages (home, FAQ, docs, verification, appeal, roster and rules pages). The Bot used to be called HighPixel Core, and this Policy covers data collected under either name.

1. Data We Collect

We only collect what the enabled features need in order to work:

  • Identifiers: Discord user IDs, usernames, display names, avatars, and server, channel and role IDs.
  • Dashboard login: when you sign in, Discord gives us your user ID, username, avatar and the servers you can manage, so we can show you the right servers and check you're allowed to manage them.
  • Verification and appeals: the "Continue with Discord" step uses a narrower Discord authorization that only confirms your user ID and username. It doesn't read your server list or email. If a server turns on alt account detection, the verify page also sends a scrambled (hashed) device signature, never the details behind it, which we keep for 90 days to spot one person verifying several accounts. Appeals also store the reason you write and whether it's for a ban or a mute.
  • Tickets and applications: ticket messages for transcripts, application answers, ratings and reviews. When a ticket channel is deleted by hand, we record that the ticket was closed for that reason.
  • Server settings: things like log channels, support roles, welcome messages, embed colors and review channels.
  • Logging and moderation: if a server turns logging on, the Bot may briefly process message content (recent messages are held in memory only, never written to the database, so deleted and edited messages can be shown in the log), edits, deletions, joins and leaves, channel and role changes and voice activity to post them to a staff-chosen channel. Warns, kicks, bans and mutes are saved as case records for that server's staff. The honeypot records who posted in the trap channel and what was done about it.
  • Backups: when an administrator runs a backup, the Bot exports the server's channels, roles and message history.
  • Staff rosters: each listed member's Discord ID and name, their rank, any notes staff add, shift start and end times, and leave requests. A roster's public page shows names, ranks and who is on shift to anyone with the link, and the Bot can post the same list in a Discord channel. Server staff choose who is on it.
  • Rules pages: the rules text, layout and look a server's staff write. The page is public to anyone with the link, and shows when the rules last changed.
  • Voice channels: who owns a temporary channel and its settings, such as lock, hide and user limit.
  • Engagement and community: chat XP and level standing, counting progress, giveaway entries, which emoji reaction a member used to take a role, suggestions and votes, tag text, game results, invite counts, and the IDs of connected YouTube, Twitch or RSS feeds.
  • Public home page: totals only, like server counts, ban counts and which features are used most. Apart from the reviews below, it never shows names or IDs.
  • Bot reviews: if you rate the bot on the home page, we store your star rating, what you wrote, your Discord user ID, your username and display name, and a link to your Discord profile picture. Your name, picture, rating, text and the date are shown publicly on the home page. You choose whether to write one, you can change it or take it down yourself at any time, and we can remove it for you on request.
  • Partner ads: the name, picture and member count of a partner server, read from its public Discord invite. Nothing about you is sent to a partner when the ad is shown.
  • Messages sent to members: announcements and mass DMs are sent to members through Discord. We keep a record of how many were sent, delivered and failed, not a copy of each member's inbox.

We do not take payments, so we don't collect payment details. We also don't intentionally collect government ID numbers, precise location or other sensitive data. We don't read or store content from servers, channels or DMs the Bot wasn't given access to or asked to act on.

2. Cookies & Sessions

The dashboard uses a session cookie to keep you signed in after you authorize with Discord, and a security cookie that protects forms from cross-site request forgery. The live preview sets one more small cookie, demo_sid, that links you to your temporary demo data. None of these are used for advertising or tracking you on other sites, and none are sold or shared. They're removed when you log out or expire.

3. How We Use Data

We use the data above only to:

  • Run the features a server has turned on;
  • Show information back to server staff through the Bot or dashboard;
  • Find and fix bugs, and keep the logs we need to investigate abuse or technical problems;
  • Enforce our Terms and this Policy, and protect the Bot, its operators and its users from abuse.

We use data because it's needed to run the features server staff switch on, and to keep servers and the Bot safe from abuse. We don't sell personal data, use it for advertising, or share it with others for their own marketing.

4. Where Data Is Stored

  • Database: tickets, applications, settings, case records and logs, kept as long as needed to run the service or until deleted under Section 7.
  • Files on disk: ticket transcripts and server backups, stored on our server. Backups can't be downloaded from the dashboard.
  • Memory only: live preview data. It isn't written to the database and is cleared after a couple of hours without use or when the service restarts.
  • Discord: messages the Bot sends, like log embeds, ticket messages, panels and DMs, are stored by Discord under Discord's Privacy Policy, separately from us.

5. Data Sharing

  • With the server: data the Bot collects, such as tickets, logs, applications and cases, is visible to the staff of the server it belongs to. That is the point of the feature.
  • With us: bot owners and administrators we've designated can open any server's dashboard data for support, moderation, security or debugging, whether or not they're in that server.
  • Service providers: we may use outside services, such as database hosting, only to run the Bot. They don't use the data for their own purposes.
  • Legal reasons: we may share data if the law, a subpoena or valid legal process requires it, or to protect our rights, safety or property, or those of our users or others.
  • Discord: the Bot sends and receives data through Discord's API as part of normal operation.

6. Your Choices

  • Server administrators decide which features are on and can turn off logging, backups and other data features at any time.
  • You can avoid creating ticket, application, voice and verification data by not using those features. If staff have switched on logging, public channels may still be processed, as with any logging bot.
  • You can leave a server, or ask its staff to remove the Bot, whenever you like.
  • You can undo a reaction role by removing your reaction.

7. Retention & Deletion

  • Ticket and application data stays until an administrator deletes it.
  • Roster entries, shift history and rules pages stay until server staff remove them, or the Bot is removed from the server.
  • Log messages in a log channel follow that channel's own message history and Discord's limits. Log files the Bot keeps itself are pruned regularly, currently after 14 days.
  • Backup files stay until an administrator deletes them.
  • A review of the bot stays until you take it down, or until we remove it.
  • Verification and appeal confirmation sessions are short-lived (minutes) and are cleared once used or expired.
  • Device signatures from alt account detection are kept for 90 days after they were last seen, then deleted.
  • If a server removes the Bot, that server's settings and related records are deleted from our database.
  • To ask us to delete data about you, contact us in our support server. We'll remove what we can, unless we must keep it for legal reasons or it's under a server's own control.

8. Verification Checks & Automated Decisions

When a server turns on alt account detection, the Bot gives each verification attempt a risk score from things like account age, a default profile picture, how soon after joining someone verifies, and whether the same device was used for another account in that server. Depending on the server's setting, the Bot lets the member in and warns staff, or turns them away.

When that happens, the server's mod log gets a message with the member's mention, the score, the reasons, and the other account that shares the device if there is one. Only that server's staff see it. The score is a warning sign and not proof, and server staff stay responsible for what happens next. The honeypot also acts automatically on anyone who posts in its trap channel. If you think one of these decisions was wrong, ask the server's staff, or contact us in our support server and we'll look at it.

9. Your Rights

You can ask us, at any time, to:

  • Tell you what data we hold about you, and give you a copy in a common format;
  • Correct data that is wrong, where it's something we store and can change;
  • Delete data about you. Some records belong to a server's own staff, like moderation cases and ticket transcripts, and we may have to keep some data for security or legal reasons, so we'll tell you what we could and couldn't remove;
  • Stop using your data. Because verification and moderation run live, the simplest way is to leave servers that use the Bot and stop using its features;
  • Have a decision looked at by a person, if you think an automatic check treated you unfairly.

To ask, contact us in our support server. We'll answer as soon as we reasonably can. If you're unhappy with how we handled your request, you may also contact the data protection authority where you live.

10. Security

We take reasonable steps to protect your data. Access to the database and the Bot's settings is limited to the people who run it. Sign-ins use Discord, forms are protected against cross-site request forgery, and device signatures are one-way scrambled values, so the details behind them can't be recovered. No system is perfectly secure, so we can't promise absolute security. If we learn of a breach that affects you, we'll tell the people affected and the servers involved where we reasonably can.

11. Children's Privacy

The Bot isn't aimed at children below the age Discord requires (currently 13, or higher where local law says so). We don't knowingly collect data from anyone below that age beyond what Discord already holds for an account to exist.

12. International Users

If you use the Bot from outside the country where our systems are hosted, your data may be moved to and processed in that country. By using the Bot you agree to this.

13. Contact & Data Requests

For questions about this Policy, or to ask for access to or deletion of your data, contact us in our support server.

14. Changes to This Policy

We may update this Policy. Changes are shown by updating the "Last updated" date above. Using the Bot after a change takes effect means you accept the revised Policy.

© 2026 Hunter Corlett. All Rights Reserved.
Copying, changing, distributing or reselling this software, in whole or in part, is not allowed without written permission.

Nothing on this page matches that. Try a different word.