Bot Privacy Policy

1. Operator, controller, and scope

This Privacy Policy explains the processing of personal information by the rebzyyx.site Discord bot, including its commands, event handlers, connected-account features, moderation tools, and integrations with rebzyyx.site (the “Bot”). “We,” “us,” and “our” mean Soundvia LLC, a Wyoming limited liability company, United States, which operates the Bot and is responsible for the processing described here.

The address is the company’s published registered-agent/correspondence address; it does not identify the location of the Bot’s servers or the residence of community staff. Operational support is available at rebzyyx.site/support and through the community Discord server. Identify your request as concerning the rebzyyx.site Discord bot.

This notice covers information about server members, command users, ticket participants, people mentioned in reports, and people whose information is made available to the Bot through permitted Discord functionality. Processing can occur when you interact with the Bot or are a member of a server where relevant features operate, even if you have not created a website account.

Discord and Spotify operate their own services under their own privacy notices. The rebzyyx.site website policy covers website features; the Soundvia privacy policy covers Soundvia’s music platform. Common ownership does not mean that every service collects the same information or that every preference applies across all services.

2. Information sources and Discord access

We receive information from Discord’s API and gateway events, your commands and submissions, staff actions, authorized Spotify connections, and the rebzyyx.site services used by Bot features. Other members may provide information about you in reports, tickets, replies, or community submissions.

The Bot enables Discord intents for guilds, members, messages, message content, and presences. These allow it to receive membership events, process accessible message content, and see activities such as Spotify listening status. Actual access depends on Discord’s rules, the permissions granted to the Bot, channel permissions, and the features enabled in the relevant server.

The Bot does not obtain unrestricted access to your Discord account. It cannot read every private conversation or every server you belong to. Messages sent directly to the Bot and messages in channels it can access may be processed. Discord controls the data available through its platform; changing a Discord status setting affects what Discord shares but does not erase information already stored.

3. Categories of information processed

The categories below describe information used by available features. They are not a statement that every category is collected from every person or that every event is permanently saved.

A Discord ID is personal information even if your real name is not known. Usernames, music choices, and message content can identify you or reveal information about you when combined with other records. The Bot does not receive your device’s IP address merely because it receives a Discord presence event; websites you visit for authentication or support can process their own web-request data.

4. How listening tracking works

4.1 Discord presence tracking

In the main community server, the Bot checks Spotify activities made available through Discord presence updates. For configured tracked artists, currently Rebzyyx and xnti, eligible track changes can be recorded against your Discord ID and username. Records can include per-track and total counts, track names, identifiers, and timestamps. Duplicate checks and current-track state help reduce repeated counting.

Artist and title checks also identify configured impersonator profiles and blacklisted tracks. Depending on settings, the Bot can maintain impersonator-listening statistics or send related warnings. These automated labels are based on configured matching rules and can be incorrect; contact support to dispute a record or classification.

4.2 Direct Spotify connections

If you authorize a Spotify connection through the Bot, the connected-account tracking feature polls Spotify’s current-playback endpoint, ordinarily every 30 seconds when the account is eligible for tracking. It can retrieve playback even when Discord is not displaying Spotify as your status. Direct Spotify connection and Discord’s built-in Spotify connection are separate features.

Access and refresh tokens allow the Bot to make authorized Spotify requests without receiving your Spotify password. Token maintenance can continue while your connection exists, including when listening tracking is opted out. Opting out stops tracking; disconnecting removes the Bot’s saved connection. Spotify’s own authorization and revocation controls remain separate.

4.3 Uses and limitations of the counts

Listening events can support community leaderboards, reports, website profiles, live listening announcements, virtual-pet progress, and virtual-currency rewards. The Bot may also select eligible Spotify activity for its own listening status. These are community statistics, not verified Spotify stream counts, royalty calculations, or complete records of your listening history. Missed events, unavailable services, repeats, disconnects, and matching limitations can affect results.

5. Opting out, opting in, and disconnecting

r optout

Disables new automated listening collection through Discord presence and the connected Spotify tracker for your Discord ID. It suppresses listening-channel posts, the associated new listen rewards, and your appearance in r lr/r nl live views. Current Bot tracking state is reset. The choice is saved and survives restarts.

r optin

Re-enables listening tracking for your Discord ID. Eligible future events can be counted again when the feature next observes your activity. It does not reconstruct activity from the period when tracking was off.

r disconnectspotify

Removes your stored Spotify connection from the Bot. To prevent tracking through Discord presence as well, use r optout. You can also revoke the app’s access in Spotify’s account settings.

r notifications

Displays or manages feature-specific notification preferences. Muting a notification alone does not disable collection of listening statistics. Use r optout for that purpose.

Tracking is enabled by default unless your Discord ID is opted out. Merely joining a server, displaying a Spotify status, or reading this policy is not presented as affirmative consent to every type of processing. Where consent is legally required, it must be obtained through an appropriate choice.

The opt-out applies to this Bot’s automated listening features, not to all Bot functions. It does not disable moderation, member/message counts, support, games, requested AI interactions, or other records described here. It does not conceal your Discord status from Discord, other members, other applications, or all features that can process a user-requested message or publicly available status.

Existing statistics and previously published messages are retained unless separately removed. Old statistics may remain in leaderboards, reports, website profiles, backups, or AI lookups of stored records. Opting out does not revoke a Spotify token or retroactively undo completed rewards or already sent messages. For deletion of specific records or posts, follow Section 15.

You do not have to leave the server to use these controls. Leaving the main server generally stops new presence-based collection there, but does not automatically erase historical records. Removing a website account is also not a reliable way to delete every Bot record. If a command cannot save your preference or is unavailable, contact our privacy address so the request can be handled manually.

6. Purposes and grounds for processing

We process information to deliver commands and requested features; maintain community games, content, statistics, and rewards; respond to support requests; administer permissions and applications; protect the server against abuse; investigate and review moderation actions; preserve relevant evidence; respect privacy and notification settings; and diagnose operational failures.

Where EU or UK data-protection law applies, the grounds relevant to those purposes are:

• Legitimate interests: running the community’s stated Bot functions, providing expected statistics, preventing abuse, maintaining service security, and resolving support issues, where necessary and after considering your rights and reasonable expectations. These interests do not override your rights automatically.
• Consent: optional authorizations or processing that requires consent. You can withdraw an authorization or choice through the relevant controls or privacy contact.
• Contract necessity: only where processing is necessary to deliver a feature under an actual agreement with you.
• Legal obligations: where a specific applicable law requires particular processing or retention.

A server administrator adding the Bot does not by itself provide blanket consent on behalf of every member. Discord permissions and Spotify authorization scopes describe technical access; they do not remove our responsibility to have a lawful basis. You can ask which ground applies to a particular record and object to processing based on legitimate interests.

For background, see the European Commission’s guidance on lawful grounds. This notice does not waive any statutory right or authorize processing prohibited by applicable law or Discord’s developer rules.

7. Public and community visibility

Bot responses are normally visible wherever they are posted. People with access to the relevant channel may see command text, mentions, listening announcements, statistics, leaderboards, game activity, and community submissions. Some commands let members request another member’s stored statistics. The Bot and linked website can associate displayed results with your username or Discord ID.

Website-linked information may be visible outside Discord, subject to the relevant website feature and its settings. A website profile-visibility setting does not necessarily hide separately posted Discord messages or Bot leaderboards. Posting an introduction in the designated channel may copy text to your linked website bio; consider that audience before submitting it.

Recipients can copy, screenshot, download, or redistribute material they can access. We cannot guarantee recovery of every independent copy, but requests to remove information we control will be assessed under applicable law. For records involving multiple people, we may redact information to protect others’ rights.

Confessions are anonymous to their intended public audience, not necessarily to the operator or authorized moderators. The system stores author identifiers internally for review and abuse prevention. Do not treat an anonymous-publication feature as a guarantee of anonymity from administrators.

8. Moderation, security, support, and applications

Staff tools and automated security features can process message excerpts, audit-log events, user and staff IDs, warnings, sanctions, reasons, timestamps, reports, and appeal explanations. The purpose is to apply community rules, prevent raids or destructive actions, investigate incidents, and allow review of mistakes.

Support and report tickets can contain your messages, other participants’ messages, attachment references, claim/close actions, and ratings. Closing a Discord ticket may create a text transcript in a staff log channel. A transcript can include participant names and IDs, message content, timestamps, attachment filenames and URLs, and relevant embed details. Closing the channel does not necessarily delete its transcript.

When moderators purge messages, the tool can create an archive of deleted content for staff review. Deleting a Discord message therefore does not necessarily remove a previously generated archive, transcript, report excerpt, operational log, or database record.

Staff applications, training workflows, appeals, and confessions retain submitted answers or explanations as relevant to their workflows. Provide only information needed for the request. Authorized staff can access feature-specific records according to their responsibilities and Discord/channel permissions; support tickets are not a suitable place for passwords, authorization tokens, or unnecessary sensitive documents.

9. AI assistance, searches, and media requests

The Bot includes AI assistance. A request can cause your prompt, relevant recent conversation context, information retrieved for the answer, and associated community data to be sent to an external AI provider. Responses can be posted in the channel where the feature was invoked. Do not send confidential material that you do not want processed for that request.

The implementation includes OpenAI and provider-specific or fallback integrations for Google Gemini, GitHub Models, and Hugging Face. The provider actually used depends on configuration and availability; not every request is sent to every provider. Search and page-reading functions can send query text or requested URLs to search services, website operators, or Jina’s reader service. Prompts or URLs containing personal information can disclose it to those recipients.

Some image-related flows can upload an image to Imgur to produce a shareable URL. A shareable media link may be accessible to anyone who receives it. Media providers and linked websites process their services under their own terms and notices.

The assistant keeps a limited recent conversation history in Bot memory, currently up to five exchanges per user, for conversational context. This is separate from messages that remain on Discord, diagnostic logs, or records maintained by an external provider. We do not promise that provider-side retention ends when the Bot restarts.

We do not use Discord message content to train our own machine-learning models. Sending a prompt to a provider for inference is separate from model training. This policy does not represent that every provider uses identical retention or training rules; contact us for the provider used for a particular request and applicable information. AI answers can be inaccurate and should not be treated as a final moderation decision or authoritative legal, medical, or financial advice.

10. Recipients and service providers

Information may be disclosed to the following categories of recipients to provide the described features:

• Discord: receives Bot messages, interactions, moderation actions, uploaded transcripts, and other API requests. Discord also supplies the relevant source data.
• Spotify: receives authorized playback/token requests and processes its own account and playback information.
• Infrastructure and database providers: process hosted files, logs, and database records. The Bot uses local JSON storage and MongoDB, including a MongoDB Atlas connection; the Bot’s database arrangement is not necessarily the same as Soundvia’s music-platform storage.
• Unbelievaboat: receives identifiers, balance updates, and reasons required for applicable virtual-currency reward features.
• AI, search, website, and media services: receive the feature-specific material described in Section 9.
• Community staff and feature audiences: receive information needed for moderation/support or information displayed by the feature, as described in Sections 7 and 8.
• Legal recipients: may receive information where required by valid legal process or applicable law, or as lawfully necessary to protect rights and address a security incident.

The rebzyyx.site website and Soundvia LLC’s administrative team may process shared operational or support information to provide the Bot. Common ownership does not authorize unrelated use of Bot data for all Soundvia services.

We do not sell Discord API data or disclose it to data brokers or advertising networks. We do not use Bot listening records for cross-service advertising targeting. Service-provider disclosures and feature publication remain subject to applicable law and the Discord Developer Policy and Developer Terms.

Providers can act as processors for some activities and as independent controllers for their own services. You may separately exercise rights with Discord, Spotify, or another provider over records they control. A request to us does not automatically delete your account with them.

11. International processing

Soundvia LLC is organized in Wyoming, United States. Bot operation, administration, Discord, Spotify, cloud databases, and external AI/media services can involve processing or access in the United States, Europe, and other countries used by the relevant provider. Our registered address is not a promise that all Bot data is stored in the United States or exclusively in one jurisdiction.

Restricted international transfers must have a valid legal mechanism where applicable. Depending on the transfer, this can include an applicable adequacy decision, approved contractual safeguards, or another legally permitted basis. UK transfers can require UK-specific safeguards. A company’s US registration, a provider’s brand name, or publication of this policy does not itself establish a lawful transfer mechanism or certification.

Contact our privacy address for information about the location, recipient, and safeguards relevant to a specific transfer, and a copy or explanation of applicable safeguards where you are entitled to receive it. Any necessary redactions should protect confidential terms without preventing meaningful information about the safeguards.

12. Storage and retention

Bot records are stored in local files, MongoDB records, Bot memory, and relevant Discord channels or uploaded transcripts. Some records are synchronized with rebzyyx.site or sent to the providers described above. Copies in those systems may need separate handling when a correction or deletion is requested.

The Bot does not currently enforce one automatic expiry period for all stored data. Listening statistics and several community/moderation records can remain until removed through an administrative process. We do not claim that they automatically expire after a stated number of days, disappear when you leave the server, or are all deleted by r optout.

Retention must remain limited to a lawful, necessary purpose; indefinite technical persistence is not a separate justification to keep personal information. Applicable law and Discord’s developer requirements can require earlier deletion. Relevant factors include the feature’s ongoing need, unresolved incidents, a verified request, and any specific legal duty to preserve particular material.

For a deletion request, active records, synchronized copies, staff-channel records, and any backups must be considered as appropriate. Information retained for a valid exception should be limited and used only for that purpose. Fully anonymized statistics can remain where they cannot reasonably be associated with you; simply replacing your username with a Discord ID is not anonymization.

13. Security and incidents

Access to Bot infrastructure and administrative records should be restricted to authorized operators. Discord roles and channel permissions govern access to many staff records. Privacy-preference updates are saved atomically to reduce the risk of a partial write; if the Bot cannot safely read the privacy-preference file, the listening check stops tracking rather than treating the failure as permission.

Connected-account tokens are security-sensitive. Do not send passwords, Discord user tokens, Spotify tokens, or private keys in commands or tickets. We do not need your account password to process a privacy request. Contact us immediately if you believe a token, record, or transcript was disclosed improperly.

No security measure provides an absolute guarantee. This notice does not assert end-to-end encryption, universal encryption of stored files, a particular security certification, or that staff cannot access information needed for their work. If a personal-data incident occurs, we will assess containment, remediation, and any required notices to affected people, regulators, and Discord under applicable obligations.

14. Your privacy rights

Depending on applicable law, you may be entitled to:

• Know whether we process your information and obtain access to it and information about its use.
• Correct inaccurate information or complete relevant incomplete records.
• Request erasure where the legal conditions are met.
• Request restriction of processing in applicable circumstances.
• Receive eligible data in a portable, machine-readable form.
• Object to processing based on legitimate interests, and withdraw consent for consent-based processing.
• Exercise applicable protections concerning automated decisions and request review.
• Complain to a competent data-protection authority or seek an available legal remedy.

Rights can have conditions and exceptions; withdrawing consent does not retroactively invalidate earlier lawful processing. Refusing an optional feature can affect that feature’s availability. Exercising a privacy right is not a reason to retaliate against you. You can exercise rights through our privacy contact even if a command or website feature is unavailable.

See the European Commission’s information on individual rights for an explanation of GDPR rights.

15. How to request access, correction, or deletion

1. Email [email protected] with the subject “Rebzyyx Bot Privacy Request.” You may also use website support or a Discord support ticket. Email and postal contact remain available if you cannot use those services.
2. Provide your Discord user ID if known, the type of request, and enough detail to locate the records. For a specific message or transcript, include the relevant link, channel, date, or ticket reference when available.
3. Tell us whether you also want future listening tracking disabled. Deleting past information and disabling new collection are separate actions; using r optout first helps prevent new listening records while the request is considered.

We may reasonably verify account control before disclosing or changing records. Provide only necessary verification information; never send account passwords or access tokens. Requests made by authorized representatives may require proportionate evidence of authority. We may need to redact third-party information from an export.

We handle requests without undue delay and within applicable deadlines. Where GDPR applies, the usual response period is one month. Lawful extensions require an explanation within the initial period. Requests are ordinarily free; any refusal or permitted fee must have a lawful reason. We will explain material limitations and available complaint routes.

Deletion of Discord API data is also subject to Discord’s developer requirements: it must be removed promptly when the user or Discord requests it or it is no longer needed, except where applicable law requires retention. A generic interest in preserving statistics does not automatically defeat a deletion request.

We can address records under our control, including relevant database entries and Bot-created posts or transcripts where we have access. We cannot delete your Discord or Spotify account for you, guarantee deletion of independent screenshots, or claim that removal from one database erases every provider’s copy. Where a specific legal retention duty applies, we will explain the category retained and the reason where lawful.

16. Regional provisions

16.1 European Economic Area and United Kingdom

EU GDPR or UK GDPR can apply according to their territorial scope even though the operator is a US company. Sections 6 and 14 describe relevant grounds and rights. You may object to legitimate-interest processing for reasons relating to your situation. Our company correspondence address is not presented as an appointed EU/UK representative or a designated data-protection officer.

You may contact the supervisory authority competent for your residence, workplace, or the alleged infringement. UK users can contact the Information Commissioner’s Office; EU/EEA users can locate their authority through the European Data Protection Board’s authority directory. Contacting us first can help resolve a matter but is not a condition for exercising a statutory complaint right.

16.2 California and other US states

Where the California Consumer Privacy Act or another applicable state privacy law covers the processing, eligible residents may have rights to know/access, correct, delete, obtain a portable copy, and opt out of covered sales, sharing, targeted advertising, or specified profiling. Additional rights and appeal procedures depend on the law concerned.

We do not sell Bot personal information or share it for cross-context behavioral advertising. The categories, purposes, recipients, and retention criteria are described above. This notice does not claim that every state law applies to Soundvia LLC regardless of its statutory scope or thresholds. Submit an applicable state-law request or appeal through the privacy contact, identifying the decision you want reviewed. See the California Attorney General’s CCPA information.

16.3 Other jurisdictions

Other national or regional laws may provide additional rights, complaint routes, or different response requirements. Contact us with your request and relevant jurisdiction so it can be assessed under the applicable law. Nothing in this policy limits a mandatory protection that applies to you.

17. Children and sensitive information

The Bot is not directed to children under 13 or people below Discord’s applicable minimum age in their country. Server features can have additional age restrictions. A server role or Discord membership is not a guarantee that an individual meets every applicable age requirement.

If you believe information has been collected from a person below the applicable age, contact us so we can investigate and handle the records under applicable law and platform requirements. A parent or guardian can contact the privacy address, subject to proportionate verification and the child’s applicable rights.

Do not submit unnecessary health information, identity documents, financial account details, biometric information, or information about another person’s private life in confessions, AI prompts, applications, or tickets. Free-text submissions can contain sensitive material even when a feature does not request it; such information requires appropriate handling and is not permission for unrelated use.

18. Automated functions and review

Automation is used to match artists and tracks, detect duplicates, calculate ranks and game progress, apply virtual rewards, process commands, and flag or respond to suspected abuse. Anti-raid and moderation tools can use configured thresholds, audit events, and message rules to trigger alerts or server actions.

These mechanisms can make mistakes. They do not verify all facts about you or establish your real-world identity, character, or legal responsibility. Music-profile classifications and game results are feature outputs, not findings about criminal conduct or eligibility for real-world services.

If a warning, sanction, classification, or other output is wrong, use support or the community appeal process to request staff review and correction. Where the law gives you protections against solely automated decisions with legal or similarly significant effects, those protections remain available.

19. This policy page, cookies, and external links

You can read this page without signing in. Visiting rebzyyx.site sends normal request information, such as your IP address, browser headers, requested URL, and request time, to the site and its infrastructure. Existing authentication cookies may be used to display the site navigation if you are signed in. Website account/session handling is covered by the website privacy policy.

This page does not add an analytics script or a new advertising tracker. The shared navigation uses the site’s normal resources, including an external icon stylesheet from a CDN; fetching that resource can disclose technical request information to the CDN. Following an external link or completing an OAuth flow brings you to another service, which can process its own request and account information.

Bot listening settings do not govern separate Soundvia music playback, website archive listening, website age-verification features, or another Discord application. Consult the notice and controls for the feature you use. Account linkage and common ownership do not make separate privacy settings interchangeable.

20. Changes, interpretation, and contact

We may update this policy when the Bot’s features, providers, data practices, or legal requirements change. The effective date, update date, and version identify the current notice. Material changes should be communicated through an appropriate community notice or feature interface. Where a new use requires consent, publishing an updated policy or your continued server membership is not a substitute for obtaining it.

This is a privacy notice, not a waiver of liability, statutory rights, or platform protections. If a provision conflicts with a mandatory requirement, that requirement controls. A new policy does not retrospectively make unlawful processing lawful.

End of policy · Version 1.0 · September 27, 2026