Trust and data flow

Community members interact with Airwavy through Discord commands, messages, buttons, scheduled automations, and voice. Server managers use the dashboard to choose settings, destinations, roles, and feature behavior.

• A dashboard save changes configuration; it does not bypass Discord permissions or role hierarchy.
• A Discord action is evaluated against the current server, channel, member, feature, and access context.
• Results return through the surface appropriate to the feature, such as a public channel, private command response, direct message, voice channel, or dashboard confirmation.

Discord is the source of truth for account identity and server authority. Dashboard operations are authenticated and server access is checked again before configuration is read or changed.

• A stale browser session does not create permanent server access.
• Losing Discord management authority can remove a server from the dashboard.
• Bot permissions, channel overwrites, role hierarchy, premium state, and feature-specific rules are checked independently where applicable.

Airwavy keeps the configuration and feature state needed to provide enabled functionality. Some features also process member-provided text, images, Discord profile context, or activity as described in their individual guides.

• Channel visibility controls the audience for content posted back to Discord.
• Private or ephemeral delivery is stated explicitly in the relevant command or feature guide.
• Optional external processing, such as AI generation, is called out where it affects privacy or expectations.
• Deleted channels, roles, messages, or lost permissions can invalidate a previously saved destination.

• The dashboard manages authenticated server configuration.
• The Discord bot handles commands, community automation, scheduled delivery, and voice activity.
• Protected product services store settings and feature state and coordinate bounded rate limits and scheduled work.
• Dedicated media capabilities render visual cards and optional generated images.
• The music capability handles requested voice playback and queue state.

The diagram explains customer-visible trust and data flow without publishing credentials, hostnames, ports, private deployment topology, or defensive implementation details.