Privacy Policy

Who I am

Operator: Ryan (Vyriv), United Kingdom.
Contact for privacy requests: Discord DM or GitHub.

Where data comes from

• Discord-related data comes from Discord's APIs when the bot operates in a server or a user interacts with a Vyriv feature.
• Minecraft usernames/UUIDs may be provided by the user or obtained from public Minecraft-related APIs after the user provides an identifier.

What data is processed

Depending on the feature, this may include:

• Discord user IDs, usernames, and display names
• Discord guild and role IDs needed for role or supporter features
• Minecraft usernames or UUIDs you choose to link for supporter cosmetics
• Message content only when a specific Discord feature needs it (for example tester feedback routing or other explicitly enabled in-server functionality)
• Basic technical logs such as timestamps, request errors, and health checks

Why it is processed

• To run Discord bot and website features you use
• To manage supporter entitlements and cosmetics
• To provide admin tools such as role cleanup plans in specific guilds
• To keep services secure and working

Legal bases under UK GDPR where they apply:

• Legitimate interests for operating, securing, maintaining, and administering Vyriv services and Discord admin features.
• Contract / providing a requested service where someone explicitly uses an optional feature such as linking a Minecraft account.
• Consent only where a feature genuinely relies on consent.

What is not done

• No selling of personal data
• No advertising profiles
• No use of Discord message content or member data to train AI or machine learning models
• No bulk public member directories kept as a product feature

Storage and retention

Data is kept only while reasonably required for the relevant feature, administration, security, or dispute handling, then deleted or anonymised where appropriate. Temporary admin artifacts (for example a carrier role cleanup plan or result log) are created for that run and are not kept as a permanent member tracking database.

Message content used for in-Discord features is processed to provide that feature. It is not archived as a long-term message history product outside Discord.

Security

Data in transit is protected using HTTPS/TLS where applicable. Production systems, databases and credentials are access-controlled, and access to production systems is limited to me and necessary infrastructure providers.

Sharing

Data may be processed by hosting and infrastructure providers needed to run the services (for example server hosting, database hosting, and Discord itself when using Discord APIs). It is not sold or shared for marketing.

Your rights

Under UK GDPR you can ask for access to your personal data, correction, deletion, or restriction where applicable. Where processing relies on legitimate interests, you also have the right to object. You can complain to the UK Information Commissioner's Office (ICO). To request deletion of activity data tied to your Discord account, contact me on Discord or GitHub and include your Discord user ID.

You can also stop using features, leave relevant Discord servers, or unlink optional account connections where those options exist.

Children

These services are not directed at children under 13. Do not provide personal data if you are under the age required by Discord or applicable law.

Changes

This page may be updated when services change. The date at the top will be updated when that happens.