1. Data We Collect
Abyss acts as an automated autonomous security operations bot. To safeguard server environments and execute commands efficiently, we process the following data points directly from Discord:
- User & Server Metadata: User IDs, usernames, server (guild) IDs, channel IDs, user role hierarchies, timestamps, and account creation dates.
- Message Content: Text messages are parsed temporarily in real-time to check against our internal word blacklist filter.
- Direct Messages (DMs): All direct text interactions and image attachments sent to the bot are intercepted and routed to a dedicated internal staff logging channel for central tracking, infrastructure protection, and support queries.
- Image Attachments: Images sent in text channels are processed dynamically via the Gemini neural network API to scan for severe violations (NSFW, extreme violence, scams, or malicious payload distribution).
2. How We Use Your Data
Your data is solely processed to enforce infrastructure protection, execute system automated moderation, and log security operations:
- Text message caching and regex patterns are used strictly to run the automated Word-Filter system and maintain warning scores (10-point system).
- User IDs are checked against a Global Blacklist (Shadowban system) across all linked network nodes to instantly mitigate raiding and harmful cyber actions.
- Image data payloads are securely queried over the Gemini flash API to flag hazardous visual material before admin moderation routing.
- Direct Message (DM) monitoring prevents malicious infrastructure jailbreak exploits and facilitates logging workflow transparency.
3. Data Retention & Deletion
We believe in strict data minimization. Message contents and image files processed for filter analysis are handled completely in-memory and are never stored permanently on disk.
Persistent storage or volatile long-term RAM allocation is limited exclusively to technical configuration files, active server lists, temporary warning points trackers, and the Global Blacklist infrastructure IDs. If you require your manual server logs or associated interaction tracking to be cleared from our developer cache channels, please reach out via our official developer support portals.
4. Third-Party Data Disclosures
Abyss strictly values user confidentiality. We never sell, rent, or trade user data. However, certain security operations rely on third-party API configurations:
- Google Gemini API: Image evaluation data, flagged message content blocks, and administration triggers are transferred to Google's GenAI endpoint to determine compliance verdicts.
- Cloudflare Workers: Basic heartbeat status tracking updates are routed to our designated API worker to confirm continuous operations.
- Discord API: Standard bot operations, log transmission embedded messaging, and moderation executions (bans, kicks, timeouts) pass directly through Discord's core architecture.
5. User Rights
In alignment with global data protection laws, all interactive users maintain full control over their metadata ecosystem. You can request the extraction of your linked operational profiles, clear active warning logs, or appeal global structural blacklists by contacting the Abyss Development team. Deleting the bot from your server or closing your communication lanes will immediately end active in-memory operational metadata tracking for your guild node.