Voxsea Privacy Policy

Last updated: October 14, 2026
Applies to: the Voxsea Discord bot (“Voxsea”, “the bot”, “we”, “us”) and the Voxsea web dashboard (the “Dashboard”). Together, the “Service”.

Operator (data controller):
Damian Guillen
Salt Lake City, Utah, USA

Contact: voxseabot@gmail.com


1. Summary

Voxsea is an opt-in voice and text assistant that runs inside Discord servers. Its core function is to hear speech in a voice channel, turn it into text, send that text to AI providers to generate a reply, and speak the reply back. It also answers typed messages, can look at recent channel text and images when relevant to a request, can search the web, can generate music, and lets you save custom personalities.

Voxsea processes information to provide the features you or your server choose to use, maintain accounts and subscriptions, and secure the Service. Voice participation is individually opt-in; see section 4 for the scope and limits of that control.

  • Voxsea does not create voice-call recordings. Audio is held briefly in memory for transcription, sent to a speech-recognition provider to produce text, and then discarded. Transcripts and replies are held in active memory for context and are also sent to AI providers as needed for the requested feature.
  • Voxsea does not maintain a persistent transcript archive in its application database. Service providers and diagnostic logs may process content as described below.
  • We do not sell your data, and we do not use it for advertising.
  • Voxsea does not use your content to train Voxsea-owned AI models. Third-party providers receive request content to provide their services under their applicable terms and settings.

2. Who this applies to

This policy applies to:

  • Server members who interact with Voxsea in a Discord server (by voice, text, or slash command);
  • Dashboard users who sign in to the Voxsea website, for example to view usage or manage personalities;
  • Server administrators who invite Voxsea or configure it.

Discord itself is a separate service with its own privacy policy. Anything you do on Discord is also governed by Discord’s Privacy Policy. We receive data from Discord’s API on Discord’s terms.

3. What we collect and process

3.1 Discord identifiers and profile data

When you use the Service, we process:

  • your Discord user ID, username, and display name;
  • the server (guild) ID and channel IDs where the bot is used;
  • Discord’s authentication of your identity for each event (we never see your Discord password);
  • for Dashboard users, the most recent login timestamp and session data needed to keep you signed in.

If you sign in to the Dashboard, Discord OAuth provides your Discord user ID and basic profile information returned by Discord, such as username and avatar. We store your Discord user ID, username, and most recent Dashboard login timestamp to link your Dashboard account to your in-server usage and maintain the account. We do not ask for or store a password.

3.2 Voice audio (opt-in only)

When you opt in (see section 4), the bot subscribes to your voice stream while you are in the channel it has joined. It holds short segments of your audio in memory, detects when you have finished speaking, and sends the audio to a transcription provider to produce text.

  • Raw audio is not stored. It is kept in memory only for transcription and is then discarded.
  • We do not create call recordings.
  • Only users who have opted in are subscribed to, transcribed, and included in voice-based model context.

Your voice stream may include nearby voices or sounds picked up by your microphone. Inform people nearby before using the feature and do not use it where you lack any permission required by law.

3.3 Transcriptions and conversation history

The text produced from your speech, the text of messages you send to the bot, and the bot’s replies form a conversation history that is used to give the bot context. Active conversation history:

  • is held in bot memory and is not stored as a persistent transcript archive in the application database;
  • is limited to recent entries and pruned automatically as new entries arrive;
  • is cleared when a voice session ends or the process restarts. /voice-optout removes your entries from the active conversation history;
  • may be included in requests to AI providers to decide whether to respond, generate a reply, or handle a music request (see section 3.9).

Opting out does not recall a request already sent to a provider, cancel work already in progress, or necessarily remove your words from a separate active music-session context. Diagnostic logs may also contain limited content as described in section 3.10.

3.4 Text messages and channel context

Voxsea requests Discord’s Message Content intent and receives messages from channels where it is present. The bot checks the author’s opt-in before using a message to reply or sending its content to an AI provider. It uses messages to:

  • detect when it is addressed and respond;
  • provide background image context for a reply: a small number of recent image attachments from recent messages in the active text channel may be supplied to the model;
  • when you ask about typed chat, retrieve recent messages from a text channel that both Voxsea and the requester can access, including message text, sender label, time, and any requested images and related metadata.

Retrieved message history is not kept as a separate archive between requests. Authors who have not opted in are excluded from this context, but a message or image may contain information about other people. Voxsea may also post a message to a text channel when asked.

3.5 Server member and voice-state data

Voxsea requests the Guild Members and Guild Voice States intents. It processes member display names and voice-channel membership to manage sessions and list who is in the call. Only opted-in members’ display names are included in model context sent to AI providers. Voxsea does not request the Guild Presences intent and does not process activity status such as games.

3.6 Opt-in records

When you opt in, we store an opt-in record containing your Discord user ID, the server (guild) ID, the opt-in timestamp, and, if you later opt out, a revocation timestamp.

/voice-optout marks your opt-in as revoked, stops future use of your text messages for replies, and stops future voice subscription. We retain a minimal revocation marker (guild ID, user ID, and revocation timestamp) until you opt in again or the operator deletes it, so a withdrawn opt-in stays withdrawn after a restart.

3.7 Personalities (Dashboard)

The Dashboard personality generator and the /personality command store a name and a prompt/character description you provide or generate. When you use the personality generator, the description you type is sent to an AI provider to produce the character text. Saved names and character descriptions are retained until you delete them (or an operator removes them).

To apply the personality generator’s daily limit, we also store your Discord user ID, the UTC date, and the number of generations used that day.

3.8 Usage and billing-tier data

We keep per-user, per-month usage counters to operate subscription quotas, including voice airtime, text chat calls, music clips generated, web searches, and your assigned subscription tier.

For subscriptions, we link your Discord account to a Stripe customer and store Stripe customer and subscription identifiers, plan, status, billing-period end, and cancellation status. Stripe processes checkout, billing/contact details, and payment details. We do not receive or store full payment-card numbers.

3.9 Requests sent to third-party services

Depending on what you ask for, the bot sends limited content to third-party services:

  • Speech recognition: opted-in users’ voice audio is sent to a transcription provider to produce text.
  • Replies and response decisions: voice transcripts, relevant conversation context, and requested channel history are sent to AI chat providers to decide whether to respond and to generate a reply. When images are included as described in section 3.4, image content and associated labels or metadata are also provided.
  • Speech synthesis: generated reply text is sent to a text-to-speech provider to produce voice audio.
  • Music generation: a music request, relevant conversation context, and the resulting music prompt are sent to a music-generation provider. The generated clip, caption, and lyrics are posted to Discord and played in the call. Posted content is visible according to the destination channel’s permissions and is subject to Discord’s handling and retention.
  • Web search: your search query is sent to a search provider.
  • Game-data lookups: the game name you ask about is sent to a game-data service.
  • Website hosting, media, and fonts: standard hosting, content-delivery, media-storage, and font services needed to serve the site may receive technical request information, such as an IP address and browser details.

AI requests are routed through our AI gateway; specific providers and routes may change as models and configurations are updated. Requests may include identifiers needed to associate a request with a session, such as Discord server or channel identifiers.

3.10 Operational logs

The bot and Dashboard produce diagnostic logs to operate and troubleshoot the Service. Logs are generally limited to timestamps, Discord identifiers, and service status, and may include limited message content where needed to diagnose an error. Raw audio is not written to application logs. Logs are retained only as long as needed for operations, subject to hosting-provider settings. Website hosts may also record standard request metadata such as IP address, browser/device information, timestamps, and errors.

3.11 What we do NOT collect

  • We do not create voice-call recordings or maintain a persistent transcript archive in the application database.
  • We do not collect advertising identifiers or use third-party ad trackers.
  • We do not intentionally collect passwords, payment card numbers, or government identifiers.

4. Voice and text processing: opt-in and control

Using a member’s messages to reply and subscribing to their voice stream require opt-in for that server:

  1. A user runs /voice-optin, addresses Voxsea in text chat and is prompted to opt in, or an eligible host runs /join and is prompted to opt in.
  2. The bot shows an opt-in message in the same Discord server with a privacy-policy link and an agreement button.
  3. An opt-in applies only to that user in that server. The bot uses that user’s addressed text messages for replies and subscribes to their voice only after agreement. Other members opt in individually.

You can withdraw at any time with /voice-optout. This marks your opt-in as revoked, stops your active voice subscription, prevents future text replies using your messages, and removes your entries from the active conversation history. A minimal revocation marker is retained to keep the opt-out in effect after a restart. It stops future subscription and processing, but it cannot cancel work that has already started or retract information already sent to a provider or posted to Discord.

Until you opt in, your voice is not subscribed or transcribed, you are excluded from opt-in-filtered channel and model context, and your messages do not receive ordinary bot replies. Discord still delivers message events to the bot for presence and routing, and limited metadata may be logged as described in section 3.10. /join remains available to show its opt-in prompt.

When the bot joins a voice channel, it posts a notice in the selected text channel explaining that only opted-in members are processed and linking this policy.

A subscription tier does not equal opt-in. A tier only affects quotas and features. You must still opt in for the bot to subscribe to your voice.

5. Why we process data (purposes and legal bases)

Where GDPR or UK GDPR applies, we process data on the applicable legal basis below. A request from one user does not by itself establish a basis for processing another person’s information that appears in channel content.

PurposeData usedLegal basis (GDPR/UK GDPR)
Provide voice featuresvoice audio, transcripts, identifiersConsent where relied on; otherwise performance of a contract for the requested feature
Reply to text and use requested channel contextmessages, images, identifiersPerformance of a contract for the requester’s request; legitimate interests in providing the requested functionality
Generate music and personalitiesprompts, relevant context, character textPerformance of a contract for the requester’s request; legitimate interests in providing the requested feature
Web and game-data lookupsyour queryPerformance of a contract for the request; legitimate interests in answering it
Apply usage quotas and manage account tiersusage counters, tier, identifiersPerformance of a contract; legitimate interests in operating and protecting the Service
Security, abuse prevention, and debuggingoperational logs and identifiers, including limited content where neededLegitimate interests in maintaining a secure and reliable Service
Comply with law and enforce our termsrelevant recordsLegal obligation where applicable; otherwise legitimate interests

Where we rely on consent, you may withdraw it at any time (section 4). Withdrawal does not affect processing already carried out.

6. Service providers and data sharing

We do not sell your personal information or share it for advertising. We share information with the platforms and service providers needed to operate the Service:

  • Platform and identity: Discord provides the bot platform and Discord sign-in.
  • Database and authentication: Supabase stores account, opt-in, usage, tier, and other records described here and provides Dashboard authentication.
  • Website hosting: the website and its server-side API routes are hosted on our website hosting provider.
  • Payments: Stripe provides checkout, subscription management, and payment processing, including billing/contact and payment details entered at checkout.
  • AI providers: AI requests for transcription, chat, speech synthesis, music, and personality generation are routed through our AI gateway to the relevant providers.
  • Search and game data: search and game-data providers handle web-search queries and game-name lookups.

Providers receive only the information needed to supply the features described in this policy. Routing, processing locations, and retention can vary by request and configuration. Some providers may process information in countries other than yours.

7. International data transfers

Voxsea and its providers may process information in countries outside your own, including the United States. Where applicable law requires a transfer mechanism or safeguard, Voxsea will use the mechanism required for that transfer. Contact voxseabot@gmail.com for information about applicable safeguards.

8. How long we keep data

DataRetention
Raw voice audioNot stored as a recording. Held briefly in memory for transcription, transmitted to the transcription provider, and then discarded. Provider retention is governed by the provider’s applicable terms.
Conversation transcripts / historyHeld in active memory and pruned automatically as new entries arrive. Cleared when the session ends or the process restarts. Opt-out removes the user’s active-history entries but cannot cancel work already sent to a provider. Diagnostic logs may retain limited content as described in section 3.10.
Opt-in stateAn active opt-in is retained until /voice-optout. A minimal revocation marker (guild ID, user ID, and timestamp) is retained after opt-out until you opt in again or the operator deletes it.
PersonalitiesUntil you delete them in the Dashboard or via the bot.
Usage countersStored by user and month and retained until the operator deletes them upon request or when no longer needed.
Personality-generator daily countsStored by user and date to enforce the daily limit and retained as needed for that purpose.
Dashboard account and login recordsStored while needed to provide and secure the account; you may request deletion from the operator.
Billing recordsSubscription identifiers and status are retained while needed to administer subscriptions, handle billing questions or disputes, and meet applicable legal obligations. Stripe separately retains payment and billing details under its own terms.
Website and operational logsRetained only as long as needed for operations, subject to hosting-provider settings.

We retain information only as long as needed for the purposes described here or as permitted or required by law.

9. How we protect data

  • Data is transmitted over encrypted connections (HTTPS/TLS) in transit.
  • Records are stored with access controls and encrypted at rest by our hosting providers.
  • Dashboard access is limited to the signed-in user’s own records; restricted operations are handled server-side without exposing secret keys to the browser.
  • Access is limited to what is needed to operate the Service.

No method of transmission or storage is completely secure, so we cannot guarantee absolute security. If a security incident affects personal data, Voxsea will notify affected users and Discord when required by applicable law or Discord’s developer terms.

10. Your rights and choices

Depending on where you live and subject to applicable law, you may have the right to:

  • Access the personal data we hold about you;
  • Correct inaccurate data;
  • Delete your data;
  • Restrict or object to certain processing;
  • Withdraw opt-in for text and voice processing at any time with /voice-optout;
  • Data portability;
  • Complain to your local data protection authority.

Controls you can use immediately:

  • /voice-optout — withdraw your opt-in, stop future text replies and voice subscription, and remove your entries from the active conversation history (subject to section 4’s limits);
  • /privacy — view this policy;
  • Dashboard — manage or delete your personalities.

For access, correction, or deletion requests, contact voxseabot@gmail.com. We may verify your identity, for example by confirming your Discord user ID. We will review and act on requests without undue delay and within applicable legal deadlines. Where a verified request requires deletion, we will delete or update data in Voxsea’s control unless a legal exception applies, and will ask service providers to delete where required and available. Deletion cannot recall content already processed by a provider or posted to Discord.

If you are in California or another US state with consumer privacy laws, you may have additional rights, including the right not to be discriminated against for exercising them. Voxsea does not sell personal information or share it for cross-context behavioral advertising. You may contact voxseabot@gmail.com to ask questions or exercise rights available under the law that applies to you.

11. Children’s privacy

Voxsea is not directed to children and must not be used by anyone below the minimum age required to use Discord in their jurisdiction (at least 13, and older in some jurisdictions). If we learn that Voxsea has processed information from someone below the applicable minimum age, we will stop the relevant processing and take steps to delete information in our control where required by law.

12. Sensitive information

Voxsea processes voice audio you knowingly provide after opting in in order to provide transcription and replies. Apart from that, do not submit sensitive personal information through Voxsea, including health, financial, or similar information. Voxsea is a general-purpose assistant and is not designed to process sensitive or regulated information.

13. Automated and AI processing

Voxsea uses automated systems to transcribe speech, decide whether to respond, generate replies, and generate media. These systems produce outputs that may be inaccurate or unexpected. Voxsea does not use your data to make legal or similarly significant decisions about you, and does not build advertising profiles.

14. Changes to this policy

We may update this policy from time to time and will post the revised version with an updated date. For material changes to data practices, we will provide notice through the Service where appropriate. Use /voice-optout to stop future voice processing.

15. Contact

Questions, requests, or complaints: