Data Security & Compliance Hero Banner
Data Security & Compliance back
Charged Bot GuideDoc. 01
CONFIDENTIALp. 24
Data Security & Compliance

Coming soon

Intents/Data Security & Compliance

Data Security & Compliance

Zero-retention architecture, authenticated AES-256 encryption, and strict non-AI policy disclosures.

Data Security & Compliance Visual

Zero-retention architecture, authenticated AES-256 encryption, and strict non-AI policy disclosures. Charged processes required Discord gateway events exclusively in real-time to execute automated community workflows configured by authenticated server administrators.

All gateway event payloads are evaluated purely in-memory and discarded immediately upon completion. Under no circumstances does Charged maintain persistent member archives, track behavioral analytics, or train generalized artificial intelligence models.

Verification Deep Link

Technical Architecture & Feature Breakdown

  1. Zero Persistent Message Storage

    No message bodies, attachments, or user transcripts are written to persistent disk or external database stores.

  2. No AI / ML Model Training

    Discord message payloads are strictly excluded from any machine learning, model tuning, or automated profiling.

  3. Authenticated AES-256 Encryption

    OAuth tokens and sensitive administrative configurations are secured using AES-256-GCM encryption in Supabase PostgreSQL.

Official Verification Justification

Compliance and Developer Policy Disclosures for Charged: 1. Message Content Storage: NO. Charged does not store, archive, index, or profile message content outside of Discord. All pattern matching is executed in-memory in real time. 2. Machine Learning & AI Training: NO. Message content is strictly never used to train or fine-tune artificial intelligence or machine learning models. 3. User Opt-Out: YES. Because no message or member tracking occurs, data is not retained. Server administrators can deactivate features globally or per-channel at any time. 4. Data Encryption: YES. All database entries (OAuth credentials, server settings) are stored with industry-standard AES-256-GCM encryption. 5. Deletion Inquiries: Users and server managers can request instant deletion via discord.gg/HyxSXFKBag or chargedlnch.com/contact.

Developer Policy & Privacy Disclosures

Do you encrypt stored data in compliance with Developer Policy?

YES. All sensitive configuration records and OAuth tokens are stored using AES-256-GCM encryption.

How do users submit data deletion requests?

Users can request immediate data purging via discord.gg/HyxSXFKBag or chargedlnch.com/contact.

Back to Guides
PrivacyTerms