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 DojoBot Discord development service and the public website at dojo.cudws.ovh.

1. Information processed by the Discord bot

DojoBot processes service data needed to provide matchmaking, persistence, statistics, and moderation features. This may include:

  • Discord user IDs and Discord server IDs.
  • The Discord community from which a player entered the Dojo queue.
  • The League platform region selected by the player.
  • Queue state, match identifiers, match participants, timestamps, and user-reported match results.
  • Dojo service statistics, development rating data, and Dojo match history.
  • Administrative actions and audit records used to investigate moderation or service issues.
  • Discord channel or message identifiers where needed to operate or restore service state.

DojoBot does not need a player's Discord password and does not ask users for their Riot Games password.

2. Dojo match records and Riot data

Current Dojo match records are created from the Discord matchmaking and result-reporting workflow. They are not imported from 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.

3. 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.

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.

4. How information is used

Service information is processed to:

  • Place players in the correct regional matchmaking queue.
  • Create, operate, and restore active matches.
  • Deliver match status and result controls through Discord direct messages.
  • Maintain Dojo service statistics and match history.
  • Allow authorized community staff to resolve queue or match issues.
  • Detect duplicate actions, inconsistent results, abuse, and operational failures.

5. 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.

6. 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. Information may also be disclosed where legally required or where reasonably necessary to protect users, the service, or third parties.

7. Retention

Queue entries are temporary and are removed when a player leaves the queue or is matched. Active-match records are kept while needed to operate or reconcile a match. Match history, service statistics, and audit records may be retained for continuity, moderation, abuse prevention, dispute handling, and historical service features. Records that are no longer reasonably needed for those purposes may be removed as the service evolves.

8. 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.

9. Security

DojoBot uses scoped access controls, server-side secrets, moderator permissions, 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.

10. 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.

11. 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.