A clear record of what is stored.

Veyra stores Discord account IDs, server IDs, settings, staff member/role grants, premium code hashes, account entitlements, code redemptions, moderation cases, appeals and staff decisions, proof links or files, ticket transcripts, giveaway entries, owner-composed announcements and team messages with delivery reports, and administrative audit records needed to operate enabled features.

Sign-in and access

Discord sign-in requests your basic profile and server list. The backend uses the bot to verify your membership in whitelisted roles. OAuth tokens are encrypted on the server, and session cookies are HTTP-only. Your server membership and permissions are verified before protected data is returned.

Evidence and transcripts

Proof and transcripts may contain personal information. Server managers control staff access. Veyra does not make these records public. Moderation cases, associated appeals, proof, case notes, and associated warning records expire after 90 days. The maintenance process removes expired records hourly. Case lookups reject expired records between sweeps. Minimal administrative audit records remain, with expired case references scrubbed. Active punishments are not reversed by record expiry. Unattached proof uploads expire after 24 hours. The bot schedules deletion of its own case-channel posts after 90 days; Discord cleanup requires the bot to remain connected with access to those messages.

External proof links are hosted by their respective providers. Removing a link from Veyra does not delete the provider’s file. Ticket transcripts have a separate lifecycle and are not covered by moderation-case expiry.

Appeals and platform operations

Signed-in members can view limited summaries of their own cases and submit appeals without current server membership. Staff proof, moderator identities, and internal appeal notes are excluded from the member view. Authorized server staff see the appeal inbox. Platform-owner access provides operational totals, premium administration, and public support settings; it does not grant private case or evidence access.

Owner announcements and team messages

Server managers explicitly choose which text or announcement channels may receive messages from Veyra’s platform owner. The owner console lists approved destination names and message delivery results; it does not read channel history, private cases, or evidence. Approval is checked again before delivery. Owner-composed content and delivery reports are retained for 90 days and then removed by maintenance. Expired history is hidden from dashboard reads immediately. Removing dashboard history does not delete posts already sent to Discord. Minimal administrative audit records contain message identifiers and delivery totals, without message content.

Self-hosted deployments

The deployment operator controls the database and backups. Backups may retain records removed from the live system until the backup expires. Before a public launch, the operator must publish a contact method and a backup retention and deletion policy. Public support details are managed in the owner console. An email address is optional and is displayed only after it has been configured.