Privacy Policy

Last updated: October 11, 2026

This policy describes the data handled by the current Super Security bot, dashboard and verification website. The service is operated by the Super Security Developer.

Discord and server information

The bot uses Discord user and server IDs, profile names and avatars, membership and role information, and channel identifiers to deliver commands, display dashboards and check permissions. It stores server configuration and dashboard access grants. Discord sign-in provides account information needed to identify you; the service does not ask for your Discord password.

Verification: IP address and browser location

After you accept the verification screen, grant browser location permission and complete the CAPTCHA, the verification service saves your connection IP address, latitude, longitude, reported accuracy, consent time and update time, linked to your Discord user ID and that server. The data can be saved before you finish confirming your code in Discord. The one-time code is stored as a hash and expires after ten minutes; code expiry alone does not delete the saved verification record.

If you decline browser location permission, the verification flow does not save a new verification IP or location record and cannot complete. Website infrastructure may still process your IP address to deliver the page, prevent abuse and produce request logs.

Optional location updates start only after you explicitly start them on a verified, visible verification page. Updates replace the saved coordinates and update time. Stop the update control, hide or close the page, or revoke browser permission to stop browser location updates.

The service keeps the latest verification reading and a history of consent-based readings for that member and server. The Developer can view the latest 100 readings from the past 90 days. Older history is cleaned up when the bot starts or a new reading is saved. Revoking verification deletes both the latest reading and that server's location history. Browser readings are estimates, not exact addresses.

Games, rewards and community features

DM and group-DM Activity play uses a personal wallet separate from server points. The service stores personal and per-server points balances, daily reward times, game bets and outcomes, points adjustments, XP and level records. Invite tracking stores attributed inviter IDs, invite codes, join times and rewards. Giveaways store entry and winner IDs. These records support game settlement, reward limits and prevention of duplicate awards.

Where enabled, the bot processes message activity for XP. Support tickets store ticket metadata and transcripts, including author IDs, message text, timestamps and attachment links. Do not put sensitive information in a ticket unless it is needed for your request. Poll and other public command content may be visible to members who can view the channel.

A ticket transcript can include messages captured before their later deletion in Discord. Closing merges accessible channel history with messages already recorded by the bot. If reading that history fails, the ticket stays open and the earlier transcript is preserved.

How information is used and who can see it

Information is used to provide verification, account access, support, moderation, games and configured community features, and to investigate service errors or abuse. Within the dashboard, saved verification IP addresses and coordinates are visible only to the Developer account; server managers can view verification status and update time. Authorized server staff can access relevant ticket transcripts and server records. Hosting administrators may have technical access to stored data and operational logs.

The current bot does not include an advertising, personal-data sale or third-party analytics feature. Personal data is not made public by the verification dashboard. Server staff are responsible for how they use information available to them.

Streaming connections and overlays

When you connect a streaming account, Stream Tools stores the account identifier, channel name, encrypted OAuth credentials, server association and alert settings. It processes supported viewer events, including names and chat or event text, for alerts and goals. Server dashboard managers can control their server’s connections. Private overlay URLs grant access to alert content: share them only with trusted broadcasting software and rotate them if exposed.

Alert history is limited to 100 entries per connection and event deduplication records expire after seven days. Disconnect removes local credentials and connection history; provider authorization and subscriptions may require separate revocation. Operational logs and backups are separate. Twitch, Google/YouTube and Kick process authorization and event data under their own policies. The optional unofficial TikTok connector also uses an external signing service.

Live notifications store the account, selected channel, message ID, stream session and available title/category metadata so the same post can be updated. Failed posts may be queued for retry while the stream remains live. Disconnection removes local pending notifications and announcement settings; messages already posted to Discord remain there.

Optional native chat replies use the authorized Twitch, YouTube or Kick account to post configured command responses. YouTube chat posting requests an additional write scope; identity-only viewer linking remains read only. Chat command logs, delivery status and wallet transactions are stored for server administration. Wallet history and lifetime level totals remain after a stream account is disconnected; unlinking stops future account-linked rewards. Private OBS bridge tokens authorize named scene/source jobs. Your OBS password is entered on your PC and is not sent to the dashboard. Bridge jobs expire after thirty seconds.

Community controls and redemption records

Optional community tools store role-panel mappings, suggestion authors and text, votes, staff status decisions, scheduled message text and times, and highlight message mappings. Approved public highlights copy a text excerpt and original Discord message link into the selected destination. Deleting a source message removes its highlight when Discord reports that deletion; disabling the feature alone leaves existing Discord posts.

Moderation history stores actor and target IDs, action, reason and timestamp for recorded dashboard and community actions. These records expire after 90 days and are limited to 5000 per server. Creator live-role bindings store account-to-member assignments and bot-role ownership for cleanup. Reward catalogs store configured costs and approved OBS actions. Redemption and refund records link the member, server, reward, cost, delivery status and wallet transaction. These records may remain after account disconnection; refunds never erase transaction history. They do not include verification IP addresses or coordinates.

Optional music and command prices

Paid live-chat commands use linked platform account IDs and the server’s Discord wallet. Command prices, charges and refunds are stored with the relevant server and account. Music requests store viewer identity/name, query, selected song, price and delivery status. Uploaded library audio, song titles and artist names are stored for the chosen streaming profile and can be removed by its server dashboard managers. Private music-player URLs authorize audio access and playback status updates; treat these URLs as secrets.

Optional Spotify sign-in stores encrypted authorization and refresh tokens, account display name and the selected device ID. The app requests account information and playback read/write scopes to search tracks, list devices and control personal Spotify playback. Spotify processes those requests under its own policies. Track metadata, artwork, links and provider delivery status may be displayed in the dashboard. This integration does not download or export Spotify audio. Local disconnection removes Spotify credentials; revoke the provider grant separately if desired. Financial-style virtual-point history and request records can remain after disconnection.

When a dashboard manager searches the Jamendo catalog, the service sends the entered search text and the operator’s Client ID to Jamendo. This metadata integration does not connect streamer accounts, store Jamendo OAuth tokens, charge points or deliver audio. Search results and license metadata are shown to the requesting manager.

Service providers and security

Discord processes sign-in, messages, commands and account information under its own policies. Cloudflare provides website delivery and Turnstile CAPTCHA services; hosting providers process data needed to operate the bot and websites. These providers may process network and request information under their own policies. See Discord’s Privacy Policy and Cloudflare’s Privacy Policy.

The verification website uses HTTPS and a secure, HTTP-only session cookie for sign-in and request protection. Sessions expire after 24 hours; logging out invalidates the current session. The service uses permission checks and hashed verification codes. No security measure guarantees that all risks are eliminated.

Retention and your choices

The current software does not automatically delete all records after a fixed retention period. Verification records remain until revoked or otherwise deleted. Ticket, game, wallet, level, invite and moderation records have separate storage and may remain after verification is revoked. Expired sessions are cleared during session creation. Operational logs and any backups are separate from live verification records and may not be erased by the revoke command.

Use /revoke in the affected server, or the website’s revoke control, to delete that server’s saved verification record, including IP, coordinates and location history, and remove verification access. Revocation does not automatically erase ticket transcripts, game balances, reward history, separate website IP blocks, Discord’s copies of messages, or records held by service providers.

For access, correction or deletion of other records, contact the Developer and identify the relevant Discord account and server. Identity may need to be confirmed before data is disclosed or changed. The operator will handle requests under applicable law and Discord’s developer requirements; any necessary limits on a request will be explained. You can also stop using the service and revoke its authorization in Discord.

Age requirements, changes and contact

The service is intended for people who meet Discord’s age requirements in their country. Do not submit another person’s data without authorization. Updates to this policy will be posted here with a revised date. Contact the Developer with privacy questions or requests.

Contact the Super Security Developer through /open_ticket in a server using the bot and ask staff to forward your request. You can also use the Developer’s Discord profile. Include your Discord user ID and the affected server ID; do not send passwords, bot tokens or unnecessary location information.