← HomeLegal document

Privacy Policy

Last updated: October 5, 2026

Operator contact: contact@antiscam.dev. This is the MOD BOT/Antiscam operator’s email address; it is not a Discord email address and is not provided or managed by Discord.

1. Controller and scope

MOD BOT (the bot’s displayed name is Antiscam) is an independent Discord bot operated by the application owner. MOD BOT/Antiscam is not created, endorsed or operated by Discord. This policy describes data processed by the bot and website; the website host may also process technical connection data under its own policy. Discord processes data under its own Privacy Policy.

2. Data processed

Messages scanned: text, links, Discord identifiers needed for processing, image filenames and image data. To detect scams, the bot may read messages in the server where it is installed and analyze relevant image attachments.
Detection results: reasons and risk scores, detected domains and perceptual image fingerprints. The Discord context-menu action “Report as scam” analyzes the selected message, adds non-allowlisted domains to the blocklist, stores fingerprints of attached images, then attempts to delete the message. It confirms privately to the moderator and does not send a report to the bot operator.
/report submissions: members can send a link, image and optional context. The bot sends the member’s Discord name and ID, source server and channel, link/context and, if included, a copy of the image to the operator’s central report channel. Reports are for human review and are not automatically confirmed as scams.
Server settings: server, channel and role IDs; language; thresholds; allowlists and blocklists; moderation options; counters; and ticket, temporary voice room and statistics settings.
Dashboard changes: when settings are saved from the dashboard, the bot posts the account name, Discord ID and changed fields in the configured log channel. These logs remain on Discord until deleted.
Moderation: for saved warnings, the member and moderator IDs, reason and date. Bot actions may also be sent to the logging channel selected by the server team.
Tickets: the ticket channel ID, opener’s member ID and status. Ticket messages are hosted by Discord in the created channel; the bot does not copy them into its configuration file.
Dashboard, when enabled: Discord account ID, display name and avatar, plus the server list and permissions needed to verify access. After authorization, a short-lived OAuth token is stored encrypted in an HttpOnly cookie for the session, for up to one hour. Bot settings and the channel/role information needed by the interface are synchronized to Cloudflare D1.

Technical logs: the website records the IP address provided by Cloudflare for every request, including requests made while signed out; the Discord user ID is associated only when a valid session is active, the date and time, HTTP method, page or API path, and response status. Query parameters, cookies, tokens and form contents are not logged. Bot logs record successful or failed commands with the user, server and channel Discord IDs, along with service events and errors; Discord does not provide members’ IP addresses.

3. Purposes

This data is used to scan messages and images for scams, maintain each server’s settings, perform features requested by its administrators, keep warnings, show configured statistics, restore ticket buttons after a restart and diagnose service errors.

4. Temporary processing and retention

Message content and image data are used during analysis. The bot temporarily keeps information in memory to detect repeated messages and resolve shortened links. It does not keep a general archive of all scanned messages in its configuration file.

Server settings, counters, domain lists and reported-image fingerprints are saved in the bot installation’s local configuration file until the operator deletes them. When the dashboard is enabled, a copy of the settings needed to run it remains in Cloudflare D1 until deleted by the operator. Reports and attached images remain in the central Discord channel until deleted there and are subject to that server’s Discord retention settings. Dashboard sessions expire within one hour; logging out removes the session cookie. Warnings remain saved until a moderator clears them or the operator deletes the data file. Logs posted in Discord are subject to Discord’s and the server’s retention settings.

Website logs are stored in Cloudflare D1 and copied to %LOCALAPPDATA%\Antiscam\logs\web.txt on the bot host. D1 entries are deleted after 30 days, and local daily archives are limited to 30 days. Bot logs are stored in %LOCALAPPDATA%\Antiscam\logs\discord.txt with daily archives limited to 30 days. Access to these files is limited to the operator’s Windows account, SYSTEM and local administrators of the machine.

5. Sharing and third-party services

The bot does not sell personal data. The dashboard uses Discord for authentication and Cloudflare Workers/D1 to host the page, API and synchronized settings. The OAuth token is not sent to the page’s JavaScript. If a Google Safe Browsing API key is configured, checked URLs are sent to Google Safe Browsing for lookup. If a VirusTotal API key is configured, the link domain (without its path or query parameters) is looked up on VirusTotal for available reports; VirusTotal may process the queried domain under its own terms and retention rules. The bot may make network requests to shortened URLs to inspect their destination, without downloading page content. Public phishing-domain feeds are downloaded. Detection logs are sent to the Discord channel configured by administrators.

See the policies of Google, Discord and Cloudflare for their respective processing.

6. Access, deletion and requests

Server administrators can review or change settings and warnings using the available commands. To request access to or deletion of data saved by MOD BOT, contact its operator at contact@antiscam.dev with the server ID and enough information to locate the data. Requests about Discord message content or Discord logs should also be directed to the relevant server administrators and, where appropriate, Discord.

7. Security

Bot configuration files are stored on the machine hosting the bot. The dashboard enforces Discord access checks on the server and encrypts OAuth tokens in an HttpOnly cookie. OAuth credentials and the synchronization secret must stay in Cloudflare secrets; the bot token and API keys stay in the operator’s private local environment file. None of these secrets are embedded in the public site files.

8. Minors and changes

MOD BOT is a Discord server moderation tool and is not intended to collect data from children outside normal Discord use. This policy may change as the bot’s features evolve; the update date at the top of this page will be revised.

9. Contact

For privacy questions, contact contact@antiscam.dev.