DojoBot
Legal

Privacy Policy

This policy explains what information DojoBot processes, why it is needed, and how it is used. It applies to the current public DojoBot Discord service and the public website at dojo.cudws.ovh.

1. Information processed by the Discord bot

DojoBot processes service data needed to provide matchmaking, lobby coordination, persistence, statistics, rating, community configuration, staff approval, moderation, and platform administration. This may include:

  • Discord user IDs and Discord server IDs.
  • The Discord community from which a player entered the Dojo queue.
  • Community configuration such as the configured moderator-role ID, log-channel ID, and queue-channel ID.
  • Community staff-approval records, including approval status, a per-request identifier, requester and decision-maker Discord user IDs, request and decision timestamps, and an approval or rejection reason where one is recorded.
  • Community metadata used when a staff-approval request is reviewed, such as the community name, owner account information available through Discord, member count, configured moderator role, and configured log channel.
  • The League platform region selected by the player.
  • A self-reported Riot ID, consisting of game name and tag line, stored for the League region where the player uses it.
  • The selected Dojo ruleset, queue state, match identifiers, participants, timestamps, Host/Guest assignment, lobby readiness state, coordination issues, and user-reported match results.
  • Dojo service statistics, regional Dojo 1v1 rating data, and Dojo match history.
  • Administrative and moderation actions, including audit records used to investigate service or access-control issues.
  • Discord channel or message identifiers where needed to operate or restore service state.

The current manually entered Riot ID is used for lobby coordination and is not treated as verified Riot identity. DojoBot does not need a player's Discord password and does not ask users for their Riot Games password.

2. Community staff approval workflow

Player access to Dojo matchmaking is open when the bot is installed and does not depend on community staff approval. A Discord community administrator can separately request Dojo moderation access for that community.

When a staff-approval request is submitted, DojoBot stores the request state and sends a private review message to configured Dojo Platform Admin accounts when delivery is possible. That review message may include the community name and ID, owner information, member count, requester information, configured moderator role, configured log channel, and the requested access type.

An approval or rejection decision is recorded in the community configuration and audit log. A rejection requires a reason. DojoBot attempts to notify the requester by Discord direct message and may also send the decision and reason to the community's configured Dojo log channel. Delivery success or failure may be recorded as operational metadata.

3. Opponent message relay

During an active Dojo match, a player can use the Message opponent control to submit a short message through a Discord modal. DojoBot processes that text transiently so it can deliver the message to the other player's Discord direct messages.

The relay message content is not written to DojoBot's persistent audit log. The audit record for a relay stores operational metadata such as whether delivery succeeded, which player sent the relay, and the message length. Discord necessarily processes the message content as part of delivering the direct message under Discord's own terms and privacy practices.

4. Dojo match records and Riot data

Current Dojo match records and rating are created from the Discord matchmaking and player-reported result workflow. They are not imported from Riot Ranked data or Riot's custom-match history API.

If Riot account linking or Riot-derived custom-match information is introduced later, the implementation and this policy will be reviewed before activation. Any future sharing of Riot-derived custom-match data will follow applicable Riot account-linking and player opt-in requirements.

5. Future Riot account information

Riot account linking is not active in the current deployment. If Riot Sign On is approved and enabled in the future, DojoBot is designed to retain only identifiers needed to maintain a verified account link, such as a Riot account PUUID, Riot ID display fields, platform identifier, and verification timestamps.

Verified Riot Sign On identity is separate from the current self-reported Riot ID. DojoBot will not ask players to provide their Riot password. Authentication will be performed through Riot's approved sign-on flow when and if that feature becomes available to the project.

6. How information is used

Service information is processed to:

  • Place players in the correct regional and ruleset-aware matchmaking queue.
  • Show opponents the Riot ID needed to coordinate a League custom lobby.
  • Create, operate, persist, and restore active lobby and match state.
  • Deliver Host/Guest instructions, lobby status, readiness controls, coordination actions, and result controls through Discord direct messages.
  • Relay short opponent messages when a player explicitly uses the relay control.
  • Maintain Dojo service statistics, regional rating, and match history.
  • Maintain community configuration and distinguish open player access from separately approved community moderation access.
  • Route community staff-approval requests and decisions between community administrators and Dojo Platform Admins.
  • Allow approved community staff to resolve relevant local queue or match issues and allow Dojo Platform Admins to administer or arbitrate across the network.
  • Detect duplicate actions, stale approval actions, inconsistent results, abuse, and operational failures.

7. Public website data

The public website is a static Cloudflare Pages deployment. DojoBot does not run advertising trackers, application analytics, account registration, or application cookies on the current site. Cloudflare may process normal request and security information, such as IP addresses, timestamps, user-agent information, and network metadata, as part of delivering and protecting the website under Cloudflare's own terms and privacy practices.

8. Data sharing

DojoBot does not sell player data. Information may be processed by infrastructure providers required to operate the service, including Discord for bot interactions and Cloudflare for public website delivery.

An opponent receives the Riot ID and any relay message that a player provides for the active match because those items are necessary for the requested lobby coordination. Configured Dojo Platform Admins may receive community staff-approval request metadata. A community approval decision and rejection reason may be sent to the requester and the configured community log channel. Information may also be disclosed where legally required or where reasonably necessary to protect users, the service, or third parties.

9. Retention

Queue entries are temporary and are removed when a player leaves the queue or is matched. Active-match records, including lobby coordination state, are kept while needed to operate or reconcile a match. Region-specific self-reported Riot IDs remain in the player profile until changed or removed as the service evolves.

Community configuration and staff-approval records may be retained while the community remains known to DojoBot and for audit, abuse-prevention, dispute-handling, and service-integrity purposes. Match history, service statistics, rating records, and audit records may also be retained for continuity and moderation. Relay message content is not stored in persistent DojoBot audit records.

10. User requests

Privacy and data requests can be sent to privacy@cudws.ovh. Where applicable, requests may include access, correction, deletion, restriction, or other data-rights questions. Some records may need to be retained where required for security, dispute resolution, legal obligations, or the integrity of shared match history and audit trails.

11. Security

DojoBot uses scoped access controls, separate community staff approval, Platform Admin authorization, server-side secrets, persistent audit logging, and HTTPS for the public website and any future Riot API communication. The service is designed to minimize sensitive information and limit access to operational data, although no technical measure can guarantee absolute security.

12. Age and third-party services

DojoBot is intended for users who are permitted to use Discord and League of Legends under the terms and age requirements applicable to them. Discord, Riot Games, and Cloudflare are separate third-party services with their own terms and privacy practices.

13. Changes to this policy

This policy may change as DojoBot develops, particularly if Riot Sign On, Riot API functionality, or additional public service features are introduced. The effective date will be updated when material changes are published.