Privacy Policy

This Privacy Policy outlines how Arizona Bot collects, processes, and safeguards information when operating in Discord servers. We practice strict Data Minimization — only storing what is strictly necessary to provide bot commands and server management functionality.

When Arizona Bot operates in your server, the following data may be stored in our localized SQLite and Redis databases:

• Guild Settings: Discord Guild ID, custom server prefix, language settings, and active feature flags.
• Ticket & Recruitment Configs: Dedicated ticket channel IDs, staff ping role IDs, transcript settings, and custom application form questions.
• Staff & Permissions Data: Role IDs authorized for administrative panels and category permissions matrix.
• Temporary Voice Sessions: In-memory track queues and requester Discord handles (cleared immediately when playback ends or the bot leaves the voice channel).
• No-Prefix Whitelists: User IDs permitted to execute commands without standard prefix syntax, with expiration timestamps.

To preserve complete user safety and confidentiality:

• We DO NOT read, log, or store private direct messages (DMs) or general channel chats.
• We DO NOT collect personal passwords, payment details, or real-world identities.
• We DO NOT sell, rent, or distribute any user or server data to advertisers or third-party marketing brokers.

All database instances and telemetry layers are hosted on dedicated, encrypted ArcHost high-performance server clusters protected with firewall layers and DDoS mitigation.

Access to raw databases is strictly restricted to certified Arizona core development personnel under secure key authentication.

Guild configuration data is retained for the duration of the bot's membership in your server. If the bot is removed or kicked, data is automatically purged or marked inactive.

Server Owners can request immediate manual data eradication of all tickets, logs, and server records at any time by contacting our support desk.

Arizona interacts with Discord's Official REST and Gateway APIs, as well as standalone Lavalink audio streaming nodes. These third-party protocols operate under their respective privacy policies.