Skip to content
Legal

Privacy Policy

Effective date: 25 June 2026

This Privacy Policy explains how Sequoia [SEQ] ("we", "us", or "our") collects, uses, stores, and protects personal data when you use our Discord server, Discord bot, Minecraft guild chat bridge, website, and related services.

Controller/contact: Sequoia [SEQ] community administrators. Privacy and data requests can be sent to sequoia.branchmasters@gmail.com or to the Sequoia [SEQ] Discord moderation or administration team through the official Sequoia [SEQ] Discord server.

This policy is intended to describe our actual moderation and service operations. It does not replace Discord's own privacy policy or Mojang/Microsoft's policies for Minecraft accounts.

What We Collect

We collect only the data needed to operate the community, provide bot features, support account linking, and keep the server safe.

Discord data

We may process:

  • Discord user IDs.
  • Discord usernames, display names, nicknames, and role membership.
  • Discord message IDs and channel IDs for messages handled by our bot.
  • Messages sent through supported bot features or into the Minecraft guild chat bridge.
  • Moderation command usage and chat archive search audit logs.
  • Application, recruitment, moderation, reward, badge, and other guild-management records that reference a Discord account.

Minecraft data

We may process:

  • Minecraft usernames and UUIDs.
  • Guild membership and activity data relevant to Sequoia [SEQ] services.
  • Minecraft in-game guild chat messages sent through the guild chat bridge.
  • Account-linking data connecting a Discord account to a Minecraft account.
  • Wynncraft profile, guild, raid, territory, season, leaderboard, class, and activity data used by guild tools.
  • Party finder listings, party membership, party roles/classes, invite or reserved-slot records, party finder bans, and related activity.
  • Reward requests, badges, applications, war submissions, or other guild-operation records associated with a Minecraft account.
  • OAuth authorization records and encrypted Wynncraft OAuth access tokens where a user links or authorizes supported Wynncraft integrations.

Technical data

We may process:

  • Timestamps.
  • Request and service logs.
  • Authentication/session metadata needed to operate the service securely.
  • IP addresses and rate-limit/security metadata for authentication, abuse prevention, and service protection.
  • Error logs and operational diagnostics.
  • Encrypted tokens, token revocation records, one-time authentication challenges, and session identifiers needed for login and account-linking flows.

Applications, Party Finder, Rewards, and Guild Tools

Some bot and website features collect additional information because users choose to use those features.

This may include:

  • Application answers, application status, reviewer/admin actions, application channel IDs, and vote message IDs.
  • Party finder listings, party members, selected roles/classes, reservation or invite tokens, Discord thread/message IDs, party state, kicks, bans, and related timestamps.
  • Reward requests, badge grants/revocations, war submissions, leaderboard entries, guild activity records, and related admin actions.
  • Public or semi-public guild outputs, such as player cards, leaderboards, badges, activity summaries, territory/map history, season history, and guild statistics.

Some Minecraft and guild activity data may be visible to other users or publicly available through Sequoia services, including seqwawa.com, map.seqwawa.com, Discord bot responses, or other guild tools.

Chat Bridge Archive

Minecraft in-game guild chat messages that pass through the Minecraft/Discord guild chat bridge may be archived so moderators can investigate reports, find context, and identify related rule-breaking behavior. This archive is for guild chat bridge moderation, not general Discord server message logging.

The archive may include:

  • Message content.
  • Message timestamp.
  • Source, such as Minecraft or Discord.
  • Minecraft username.
  • Discord user ID, username, and nickname where available.
  • Discord message ID and channel ID where available.
  • Attachment URLs or attachment metadata where applicable.
  • Raw or imported message metadata needed to verify context.

Access to chat archive search is restricted to configured moderator roles. Searches are logged with the moderator's Discord ID, query parameters, timestamp, and result count.

Why We Use This Data

We use personal data for these purposes:

  • Operating the Discord bot and related services.
  • Bridging guild chat between Minecraft and Discord.
  • Linking Discord and Minecraft accounts.
  • Showing guild, player, and activity features requested by users.
  • Running applications, party finder, reward queues, badge systems, leaderboards, maps, and other guild tools.
  • Preventing abuse, spam, impersonation, and rule-breaking.
  • Investigating moderation reports and preserving relevant evidence.
  • Maintaining service reliability and security.
  • Auditing moderator access to sensitive search tools.

Legal Bases

Where GDPR or similar privacy law applies, we rely on one or more of the following legal bases:

  • Legitimate interests: operating the community, providing requested bot features, preventing abuse, and enforcing server rules.
  • Contract or requested service: providing features you choose to use, such as account linking or bot commands.
  • Consent: where we explicitly ask for consent for a specific feature.
  • Legal obligation: where we must preserve or disclose information to comply with applicable law.

Who Can Access Data

Access is limited based on role and operational need.

  • Ordinary users can access bot outputs and features made available to them.
  • Moderators may access moderation tools, including chat archive search, only when their Discord role is configured for that access.
  • Server administrators or maintainers may access backend systems where needed to operate, secure, debug, or maintain the service.

We do not sell personal data.

Sharing and Third Parties

We use third-party platforms and infrastructure to provide the service, including:

  • Discord, for Discord server, bot, message, and identity functionality.
  • Minecraft/Mojang/Microsoft services, for Minecraft account identity where applicable.
  • Wynncraft services and APIs, for Wynncraft player, guild, OAuth, territory, season, raid, and activity data where applicable.
  • Hosting, database, logging, deployment, and infrastructure providers used to run the backend.

We may share information if required to comply with law, protect users, investigate abuse, or respond to valid legal requests.

Infrastructure providers may process data in the regions where our services, databases, backups, and logs are hosted.

Retention

We keep personal data only for as long as needed for the purposes described above.

Retention periods:

  • Minecraft guild chat bridge archive: up to 36 months, unless needed longer for an active moderation case, safety investigation, ban review, abuse-prevention record, or legal reason.
  • Moderation case evidence: retained while the case remains relevant, then deleted or anonymized when no longer needed for moderation, safety, or abuse-prevention purposes.
  • Chat archive search audit logs: up to 12 months.
  • Minecraft guild, player, raid, season, territory, leaderboard, and activity records: retained for long-term historical, statistical, guild-management, and service-continuity purposes. These records may be kept for longer than 12 months because they are used to provide historical guild tools and activity features.
  • Account-linking records: retained while the account remains linked, then deleted or anonymized after unlinking unless needed for security, moderation, abuse-prevention, or legal reasons.
  • Wynncraft OAuth tokens: retained while the related integration or account link remains active, then deleted or revoked when no longer needed, unless a limited record must be kept for security, abuse-prevention, or legal reasons.
  • Applications, party finder records, rewards, badges, war submissions, and other guild-operation records: retained while needed to operate the feature, preserve guild history, review prior decisions, prevent abuse, or maintain service continuity.
  • Operational logs: normally up to 30 days, unless a longer period is needed to investigate security, abuse, reliability, or legal issues.
  • Backups: retained according to infrastructure backup rotation. Data deleted from active systems may remain in backups until those backups expire or are overwritten.

We may keep a limited record longer where necessary to enforce bans, prevent abuse, comply with law, or protect the community.

Your Rights and Choices

Depending on where you live, you may have rights to:

  • Ask what personal data we hold about you.
  • Ask us to correct inaccurate data.
  • Ask us to delete or anonymize data.
  • Object to or restrict certain processing.
  • Receive a copy of your data in a portable format.
  • Lodge a complaint with a data protection authority.

To make a request, contact sequoia.branchmasters@gmail.com or the Sequoia [SEQ] Discord moderation or administration team through the official Sequoia [SEQ] Discord server.

We may need to verify that you control the Discord or Minecraft account related to the request. Some requests may be limited where data is needed for active moderation, security, legal compliance, or protection of other users.

Deleting or anonymizing data may limit or disable features that rely on that data, such as account linking, party finder, applications, rewards, badges, historical player statistics, guild activity history, or moderation records.

Children's Privacy

Our services are intended for users who are old enough to use Discord and Minecraft under their applicable terms and local law. If we learn that we have collected personal data from someone who should not be using the service, we will delete or restrict that data where appropriate.

Security

We use reasonable technical and organizational measures to protect personal data, including role-based access controls for moderation tools and audit logging for sensitive searches.

No online service can guarantee perfect security. If we discover a security incident affecting personal data, we will take appropriate steps to investigate, mitigate harm, and notify affected users or authorities where required.

Changes to This Policy

We may update this policy when our services, data practices, or legal obligations change. If we make material changes, we will provide notice in an appropriate place, such as Discord announcements, the website, or repository documentation.

Contact

Questions or privacy requests can be sent to:

sequoia.branchmasters@gmail.com or the Sequoia [SEQ] Discord moderation or administration team through the official Sequoia [SEQ] Discord server.