This updated policy is currently available in English. Translations of earlier versions are not shown here.
Airwavy operates the Discord bot, dashboard, backend and image-generation API described in this policy. We explain what these services process, why, who can receive it and how you can request access, correction or deletion. The separate Website Privacy Policy covers the marketing website, newsletter and status subscriptions. Contact [email protected] with privacy questions or requests.
Information We Collect
User Data
Depending on the features you use, we process Discord user and server IDs, usernames, avatars, server membership and permissions, profile and birthday settings, AFK messages, reminders, linked Roblox account details, playlists, suggestions, giveaway participation, polls and role selections. Records may come from you, Discord, a linked provider or a server administrator. Processing can occur when you participate in a server using the bot even if you have not signed into the dashboard.
Messages and AI features: Commands, configured moderation, tickets and chatbot features can process message text, attachments or image URLs. Chatbot prompts, relevant conversation context, images and responses may be sent to the configured AI inference service. Web-search features may send derived queries to configured search providers, including Exa, Tavily, Serper or DuckDuckGo. Local chatbot conversation memory has a 30-minute expiry refreshed by activity; separate audit records, reports, Discord messages and provider records can remain longer. Do not include passwords, access tokens or sensitive information in prompts. We do not promise that provider-held records are erased when local conversation memory expires.
Usage Data
We record command and interaction names, Discord user/server IDs, timestamps, success or failure and operational activity needed for support, reliability and abuse prevention. Error records can include technical context; we redact recognized credentials, but logs and user-submitted reports can still contain personal information. The Snipe feature temporarily holds eligible deleted or edited message text and related author/channel metadata in bot memory for up to 30 minutes. Your privacy preferences can stop future capture; existing cached entries expire within that period plus a cleanup sweep of up to 30 seconds. Other moderation logs, transcripts or Discord copies are separate records.
Guild Data
Server administrators configure channels, roles, moderation rules, logging, tickets, messages and related settings. These can include server and channel IDs, invite information, user references and text supplied by administrators. Server configuration and shared records are distinct from your personal profile.
Ticket Transcript Data
Where ticket transcripts are enabled, records can include participants, message text, timestamps, attachments or their URLs and ticket actions. Retention follows the stored transcript expiry and server configuration; there is no universal guarantee that every transcript is deleted after 30 days. Authorized server staff can access transcripts, and a share link can make a transcript available to its recipients according to the sharing configuration. Copies posted to Discord or downloaded by others are outside our direct control. Requests involving other participants require review and possible redaction.
Channels, roles and image generation
We use channel, category and role IDs for the features a server enables. The image API receives the names, avatars, image URLs, profile statistics and text needed to render requested cards, banners or CAPTCHA images. It may fetch supplied assets from their hosts. Image-request handling, rate limits and error logs can process request identifiers and network metadata. Standard render telemetry reports the render type, result, latency and timestamp; it does not include the complete rendered image or request payload.
Economy & Leveling Data
Economy balances, inventories, transaction records, achievements, reputation, XP, levels and related activity are linked to Discord IDs and, where applicable, server IDs. Some records reference other participants. Personal exports omit or flag fields requiring review to protect other people.
Moderation & Safety Data
Moderation cases, warnings, reports, evidence, anti-scam signals, blacklist entries, verification outcomes and security/audit records can identify affected users, moderators and reporters. Server staff can see records relevant to their server according to permissions. Authorized Airwavy operators can review records for support, safety and enforcement. Configured automated rules can flag content, restrict features or trigger moderation actions; contact support to request correction or review of an Airwavy decision, and contact the relevant server staff about their moderation decisions.
Dashboard Access, Sessions & Administrator Visibility
The dashboard uses Discord sign-in. Account and session stores can contain your Discord ID, display name, avatar, email supplied by Discord, login times, IP address and browser/device user-agent. OAuth account records can contain access or refresh tokens needed for authorized provider access. Airwavy does not receive your Discord password. Dashboard and website authentication records may be held in separate stores. Access depends on your identity, server permissions or granted role. Authorized Airwavy administrators can access account/session metadata for security and support; they are separate from ordinary server administrators.
Premium Subscriptions & Billing Data
Stripe processes payments. We do not directly collect full payment-card numbers or card security codes. Airwavy stores billing and entitlement records such as Discord user/server references, plan, provider customer/subscription/checkout identifiers, payment state and relevant dates. Stripe can hold additional customer, contact, billing and payment details. Exporting or deleting billing data, cancelling a subscription and removing a bot profile are separate operations; a privacy deletion request does not itself cancel billing. Some records may need to be retained for accounting, disputes, fraud prevention or other legal obligations.
Legal Basis for Processing
Where UK or EEA data protection law applies, the basis depends on the purpose: providing a service you request, legitimate interests in operating and securing the service and supporting server features, consent for optional processing where required, and legal obligations such as applicable billing retention. You can withdraw consent for consent-based processing and request a review of other processing. Using the service is not blanket consent to every use of personal data.
How We Use Your Data
We use information to deliver requested bot and dashboard features, enforce permissions, render images, maintain accounts and entitlements, answer support requests, process privacy requests, investigate failures and prevent abuse. Server administrators select the features used in their communities. Removing a profile does not necessarily prevent new records from being created if you continue using features or participating in an Airwavy-enabled server.
Data Sharing and Disclosure
We do not sell personal data. Relevant information is processed through Discord, Stripe for payments, Resend for transactional email and any configured hosting, storage, AI or search providers needed for the feature used. Provider-held information is subject to their own terms and retention. Profile information, leaderboards, messages and server records can be visible to other users or server staff according to the feature and permissions. We may disclose information when legally required or necessary to investigate abuse or protect people. Contact us for questions about the providers processing a particular request.
Data Retention
Retention varies by record. Current automatic retention settings include 14 days for raw usage events, 30 days for application error records, 90 days for music audit activity, 365 days for economy transaction history and ended/cancelled giveaway history, and 730 days for separate giveaway-entry rows. Transcript and reminder retention follows their individual expiry or cleanup settings. Database expiry and cleanup run asynchronously rather than at an exact second. Profiles, settings, safety records, shared records, account data, billing records and provider copies can have different retention or require individual review; server departure alone does not guarantee deletion. Backups and legacy copies require separate handling and are not immediately erased by a live-record change. Contact support for retention information about your specific records.
Your Rights
Use /privacy in Discord or the personal privacy page at dashboard.airwavy.xyz/privacy to view available data categories, request an inventory or a copy of supported fields, change privacy preferences, submit correction/review or selected/full deletion requests, and track their status. Preferences include Snipe capture opt-out, random-mention opt-out and birthday visibility/announcement/DM settings. Automated exports may be partial: shared transcripts, safety records, separate login/website stores, billing, provider records, live caches, backups and legacy sources can need further review. Ask support for the remaining data; a partial export does not close that request. Copies are encrypted in private export storage, require account authorization to download and expire for download after 24 hours. Expired encrypted files are normally removed by hourly cleanup. Optional status emails go only to a verified account email and contain a status link, not the archive. Deletion requests require confirmation and review; full deletion requests have a 24-hour waiting period. Submission or confirmation does not mean erasure has occurred. Pending requests can be withdrawn until review is claimed. Closed request metadata normally expires after 90 days; unresolved review requests remain until resolved. Access, correction, erasure, restriction, objection, portability and withdrawal of consent may be available under applicable law, subject to relevant conditions and exemptions. Contact [email protected] if the tools are unavailable, a rate limit is reached, you need a complete response or your request covers another service. Tool quotas and export limits do not limit statutory rights. You may also complain to your relevant data protection authority, including the UK Information Commissioner where applicable.
Open your personal privacy controls
Messaging Policy
Airwavy sends messages or DMs when needed for an interaction, configured server feature, support or a service notice. Optional reminders, birthday messages and privacy-request email notifications depend on the relevant settings or request. Privacy notifications do not subscribe you to marketing. Newsletter consent is managed separately. Using the bot is not blanket consent to promotional messages.
Data Security
We use authentication, permission checks, restricted personal-data routes, request limits and operational logging to reduce unauthorized access and misuse. Generated privacy archives are encrypted at rest, have limited download availability and require ownership checks; dashboard archive downloads also require a recent login. These controls do not mean that every database field or provider record is encrypted in the same way, and no system can guarantee prevention of every breach. Report suspected exposure to [email protected].
International Data Transfers
Our services and the third-party services used for a feature may process information in different countries. Location, applicable transfer rules and safeguards depend on the provider and processing involved. Contact support for information about your data and any applicable transfer safeguards; the use of a provider does not by itself establish that every transfer has the same protection.
Children's Privacy
Airwavy is intended for people who meet Discord’s minimum age requirement in their country and is not directed at children under 13. If you believe a child below the applicable age has provided personal information, contact support so we can investigate and address it.
Changes to This Privacy Policy
We may revise this notice as features and data handling change. The date above identifies this version, and material changes will be communicated through the website or relevant service channels. A policy update does not itself provide consent for new optional processing.
Contact Information
Privacy support: [email protected]. Include the service and type of request, and your Discord ID if relevant. We may need proportionate verification before disclosing or changing records. Do not send passwords, tokens or payment-card details. Server administrators may separately hold records or make decisions about their community; we can explain which parts of a request need their involvement.
This notice explains our data handling and your choices. It does not waive your rights or treat use of the service as consent to optional processing.