Wave · Wave Discord bot

Privacy policy

What we process, why we need it, and the choices you have. This page is public and does not require an account.

Last updated

Who this covers

This policy describes how the Wave platform operators (we, us) process information through Wave, the Wave Discord bot, and their connected community-management features. Participating communities configure their own roles, resources, and authorized staff. Discord, Google, hosting providers, and connected AI services also have their own privacy policies.

Discord agent conversations and availability are optional features, disabled by default. Their inclusion here does not mean that your community has enabled them or that Discord has approved the required privileged intents.

Information we process

  • Discord identity and community data. User and server IDs, usernames, display names, avatars, linked-account email where supplied through sign-in, server membership, role IDs and names, and membership or role-change events. We use these to identify accounts, determine community permissions, and keep configured services consistent with Discord membership.
  • Connected resources. Linked Google email addresses, configured file and folder identifiers and names, role-to-resource mappings, permission IDs, synchronization results, and records of application-managed sharing. These support access checks and safe cleanup when eligibility changes. Unlinking an account or leaving a server is not proof that external sharing has been removed.
  • Agent workspaces. Prompts, responses, files, resource context, generated artifacts, and action or approval records that you or authorized collaborators submit through the platform. These support the conversations and tasks you request.
  • Optional Discord features. For enabled agent conversations, the text you submit in your authorized private thread and the identifiers linking that thread to your account and agent conversation. For availability, your per-community opt-in choice and current Discord status, shown only to current members of that community with a verified Discord account and agent workspace access. Activities, games, devices, and presence history are not collected by this availability feature.
  • Operational information. Authentication sessions, request metadata such as IP address and browser information, integration configuration, error and synchronization logs, and security or support audit records. We use these to operate the service, diagnose failures, and investigate misuse.

Discord privileged intents

Privileged intents control which information Discord makes available to an application. Access depends on Discord approval where required, the bot configuration, server permissions, and the feature in use. This policy alone does not enable an intent.

Server Members Intent

Current integration

The membership integration requires member information and join, leave, and update events to reconcile roles and access to connected community resources. Removal and ban handling supports revoking eligibility rather than leaving obsolete access in place. This is a membership and authorization function, not message monitoring.

Presence Intent

Optional · disabled by default

When an authorized community administrator enables availability and you individually opt in, the feature shows your current online, idle, do-not-disturb, offline, or unknown status to current members of that community with a verified Discord account and agent workspace access. Discord server membership alone does not grant access. It does not collect activities, games, devices, or presence history. Current status is valid for at most two minutes and expired observations are purged; stale or disconnected status is unknown, not assumed online.

You control your own opt-in under Organization settings → Availability and can opt out even when the community has disabled the feature. Administrators cannot opt other members in. Disabling the feature or withdrawing consent stops sharing your availability.

Message Content Intent

Optional · disabled by default

When an authorized community administrator enables the Discord agent for a linked server and an allowed text channel, a member can request an agent conversation in a private, owner-only thread. The feature processes that owner’s messages in the authorized thread and sends relevant text and conversation context to the owner’s own connected AI service. It does not ingest ordinary server conversations or another member’s messages as agent instructions.

Agent conversations are owner-only in Wave; Discord administrators retain access allowed by Discord’s own permissions. Discord agent requests cannot access credentials or deploy changes. Required approvals must be completed in the web app. Do not submit secrets in these conversations.

Sharing and AI services

Information is available to authorized community administrators, collaborators, and platform operators according to their permissions. Configured integrations receive the information needed for their function, such as a linked Google email and resource identifier for a Drive permission change. Providers may process information in countries different from your own.

When you use the platform’s agent workspace or an enabled Discord agent thread, your connected AI service receives prompts and task context needed to generate responses. The Discord agent uses the requesting member’s own model connection, not an administrator’s shared account. Check the privacy and data controls of the AI service connected to your workspace, and do not submit secrets or information you are not authorized to share.

We do not sell Discord API data or provide it to advertising networks or data brokers. Discord message content obtained through its APIs must not be used to train machine-learning models without Discord’s express permission. We may disclose information when legally required or necessary to address a security incident or protect users.

Retention and deletion

We retain information needed to operate configured features, maintain accounts and conversations, resolve access problems, and meet security or legal obligations. There is not one automatic expiry period for every account, synchronization, conversation, or audit record.

Availability observations are valid for at most two minutes. Expired observations are no longer shown as current status and are purged during reads, ingestion, and periodic maintenance while the service is running. Your opt-in choice is stored separately so it can be honored until you change it; presence history is not retained. Discord agent messages submitted to a conversation follow the conversation retention practices above, and Discord retains its own copies under its policies.

Leaving a Discord server, removing the bot, or unlinking Google does not automatically erase historical records. In particular, permission identifiers and ownership evidence may need to remain until application-managed sharing can be safely reconciled. Audit records and backups may remain after active records are removed.

You can request access, correction, or deletion through the contact process below. We may need to verify the request and explain any records that must be retained. Removing Wave records cannot independently remove content or permissions controlled by Discord, Google, another community, or another service.

Security and support access

We use authenticated service connections, permission checks, and credential protections to limit access. No system can guarantee complete security. Do not place passwords, bot tokens, API keys, or unnecessary personal information in prompts, screenshots, or diagnostic descriptions.

Authorized diagnostic agents can use named support accounts to view the platform as an eligible user. Impersonation is time-limited, read-only by default, and recorded with the support actor, selected user, reason, mode, and allowed or denied requests. Explicitly authorized write sessions are real changes, not a sandbox. Support audits are retained for accountability.

Your choices and privacy requests

You can stop using the bot or platform, manage your Discord authorizations, unlink supported external accounts, and ask your community administrator about configured integrations. Server owners can remove the bot or disable optional features. These actions may affect access to community resources.

For privacy questions or requests to access, correct, or delete your information, contact Wave staff through your participating Discord community and ask for the platform operator responsible for the Wave Discord bot. Include your Discord user ID, the affected server, and the request. Do not send passwords, bot tokens, or API keys. If the server is managed by another community, ask its administrator to forward the request to the Wave platform operators.

Policy changes

We will update this public page when data practices or features change and show the revised date above. We will provide appropriate notice in the affected feature or community when its data practices change. Describing an optional feature here does not enable it or mean that Discord has approved it.