Vela

Last updated: June 11, 2026

1. Acceptance

By inviting or using Vela ("the Bot") on any Discord server, you agree to these Terms of Service ("ToS"). If you do not agree, do not invite or use the Bot.

2. Description

The Bot is an automated moderation tool that scans messages and images for scam content, including fake giveaways, phishing URLs, crypto scams, and other fraudulent patterns. When a scam is detected, the Bot may delete the message, log the incident, and optionally apply moderation actions (timeout, kick, or ban) as configured by server administrators.

3. Server Responsibility

• Server administrators who invite the Bot are responsible for configuring it appropriately for their community.
• Administrators control whether the Bot applies no action, timeout, kick, or ban upon scam detection.
• Administrators control which channel receives moderation logs.
• The Bot will act within the permissions granted to it. It is the administrator's responsibility to ensure these permissions are appropriate.

4. Acceptable Use

The Bot is provided "as is" for the purpose of scam detection and community protection. You agree not to:

• Attempt to bypass, circumvent, or interfere with the Bot's detection mechanisms.
• Use the Bot to harass, target, or unfairly moderate users.
• Reverse engineer, decompile, or attempt to extract the Bot's source code beyond what is publicly available.
• Use the Bot in violation of Discord's Terms of Service or Community Guidelines.

5. False Positives

The Bot uses pattern matching and OCR text analysis. False positives may occur: legitimate messages may occasionally be flagged as scams. Server administrators should monitor their log channels and adjust the moderation action (none, timeout, kick, or ban) to suit their community's tolerance level. The Bot's creators are not liable for messages incorrectly deleted or users incorrectly moderated as a result of false positives.

6. Limitation of Liability

The Bot is provided free of charge and without warranty of any kind. The creators shall not be liable for any damages arising from the use or inability to use the Bot, including but not limited to:

• Incorrect moderation actions
• Missed scam detections
• Service interruptions or downtime
• Data loss from guild configuration files

7. Changes to Terms

These Terms may be updated at any time. Continued use of the Bot after changes constitutes acceptance of the new Terms. Server administrators will be notified of material changes via the Bot's status message or announcement channel.

8. Termination

Server administrators may remove the Bot at any time by kicking it from their server. The Bot's operators reserve the right to block access to the Bot for any server or user that violates these Terms.

9. Contact

For questions about these Terms, contact the Bot operator through the support channel.

Last updated: June 11, 2026

1. Data We Collect

The Bot collects and processes the following data temporarily in memory during normal operation:

Message Content

• The text content of messages sent in channels the Bot can read. This is read in real-time and checked against scam patterns. It is not stored beyond the moment of processing.
• If the message is not flagged as a scam, no record is kept.
• If the message is flagged as a scam, a summary is posted to the configured moderation log channel (containing the first 1024 characters of the message, the user's name and ID, and the channel name). This log post is a Discord message: the Bot does not maintain its own database of scam incidents.

Image Data

• Image attachments from messages are downloaded temporarily into memory, processed through Tesseract OCR for text extraction, and then discarded. Images are not saved, stored, or archived.
• If a QR code is detected, its decoded text is analyzed against scam patterns. No image data is retained.

User Information

• User ID and Username: visible to the Bot as part of standard Discord message objects. Used only for logging moderation actions and identifying message senders.
• Guild (server) membership: accessed only when applying moderation actions (timeout/kick/ban) to a user who sent a flagged message.
• DM channel: used only to deliver a warning embed if a user's message is deleted as a scam. The Bot does not proactively DM users.

Guild Configuration

• Guild ID and per-guild settings (log channel ID, auto-mod action, timeout duration) are stored in a local guild_configs.json file. This file contains no user data, only server-level configuration.
• This data is stored locally on the machine running the Bot and is not transmitted or shared with any third party.

2. Data We Do NOT Collect

The Bot does not collect, store, or transmit:

• ✕ Passwords, tokens, or authentication credentials
• ✕ IP addresses
• ✕ Email addresses
• ✕ Discord presence data (online status, activities, games)
• ✕ Voice or video data
• ✕ Message history (only current messages are processed)
• ✕ Direct messages (the Bot ignores DMs)
• ✕ Any data for analytics, advertising, or profiling purposes

3. How Data is Used

All data processing serves the single purpose of detecting and preventing scam content on Discord servers that have invited the Bot.

4. Data Sharing

The Bot does not share any data with third parties. All processing happens on the machine running the Bot's instance. No data is sent to external APIs, analytics services, or advertising networks.

The only external services used are:

• Discord API: for reading messages, sending messages, and applying moderation actions (standard Discord bot operation).
• Discord CDN: for downloading image attachments (via standard HTTP).

5. Data Retention & Deletion

• Message content: processed and immediately discarded (no storage).
• Image content: processed and immediately discarded (no storage).
• Moderation log posts: once a scam log is posted to a Discord channel, its retention is controlled by Discord's platform (the Bot does not maintain its own copy).
• Guild configuration: stored until the Bot is removed from the server. If the Bot is removed, the guild's config entry remains in guild_configs.json but is never accessed. To request manual deletion, contact the Bot operator.
• User-specific data: the Bot does not maintain user profiles or databases, so there is nothing to delete at the individual user level.

6. Data Security

The Bot runs on the operator's infrastructure. Guild configuration files are stored locally and are not exposed to the internet. The Bot uses Discord's standard authenticated API and does not expose any web endpoints.

7. User Rights

Since the Bot does not maintain a user database, there is no personal data to access, correct, or export at the individual user level. Users concerned about specific moderation actions should contact the server administrator where the incident occurred.

8. Third-Party Services

• Discord: the Bot interacts with Discord's API. Your use of Discord is governed by Discord's own Privacy Policy.
• Tesseract OCR: runs locally on the host machine. No data is sent to external servers.
• No other third-party services are used.

9. Changes to This Policy

This Privacy Policy may be updated. Material changes will be communicated through the Bot's status message or the project's repository. Continued use of the Bot after changes constitutes acceptance of the updated policy.

10. Contact

For questions about this Privacy Policy, data handling, or to request guild config deletion, contact the Bot operator through the designated support channel.