Privacy Policy
This policy covers the Rift Record website, Discord bot and associated desktop application. Rift Record is operated by koko (@alostkoko on Discord). For privacy questions or data deletion requests, contact the operator on Discord.
Information we process
- Discord account identifiers, usernames, display names and avatars provided through sign-in; sign-in credentials such as OAuth tokens and sessions where needed for account access.
- Discord server and channel identifiers, community settings, relevant membership information and role configuration used by participating communities.
- Connected League account identifiers, region, verification status, profile icons, ranks, match history and related gameplay statistics from Riot Games. Public League accounts may also be looked up or added to a community as unclaimed accounts.
- Preferences, looking-for-group posts, reports and moderation records you submit, plus service activity and security records needed to operate and protect the service.
- Essential session cookies, an anonymous visitor identifier used for visit counts, and browser storage for preferences and cached information. Requests also expose ordinary connection information, such as IP addresses, to our hosting infrastructure.
How we use information
We use this information to sign you in, verify account ownership, display profiles and statistics, maintain community leaderboards, check membership eligibility, manage optional rank roles, publish configured match announcements and LFG posts, and investigate technical problems or abuse. The bot does not request Discord message-content or presence intents and does not collect private direct-message conversations.
What others can see
League profiles and gameplay statistics can be publicly accessible. Community leaderboards, member information, LFG posts and bot announcements may be visible to website visitors or members of the relevant Discord server, depending on the feature and your sharing settings. Server managers can access community configuration and participation information. Authorized site administrators can access information needed for support and moderation.
Services and sharing
The service runs on an OVHcloud VPS and stores operational data outside Discord. We exchange information with Discord for authentication, membership checks, bot commands and configured posts, and with Riot Games to retrieve League data. Asset requests may go to Discord or Riot-hosted services. Those providers process requests under their own policies. We do not sell your personal information or use Discord API data for advertising or AI model training.
Storage and retention
Account links and community settings persist until removed or a deletion request is handled. Cached gameplay history can remain available independently of an account link. LFG posts stop being active after 30 minutes; associated moderation or operational records may remain longer. Sessions and verification challenges expire according to their configured limits. Database backups rotate, with up to 14 backup sets retained. Removing a link or hiding a profile does not automatically erase all historical data, logs, backups or Discord messages already posted.
Your choices and deletion requests
You can manage connected accounts and sharing preferences in Account settings, and revoke the app through Discord's Authorized Apps settings. To request access, correction or deletion of your personal data, contact @alostkoko on Discord with your Discord user ID and the affected League accounts. Do not send passwords or tokens. We may need to confirm ownership before acting. Requests are handled manually; limited records may need to be retained for security, abuse prevention or legal obligations. Public match records involving other players and messages held by Discord may require separate handling.
Desktop app and clips
The desktop app uses the Rift Record service for authentication and profiles. Imported footage and exported clips are handled locally; this policy does not promise a cloud clip-storage service. Any future upload or recording feature will be described when introduced.
Security and changes
We use HTTPS, restricted server access and protected credential storage. No service can guarantee absolute security. We will update this page when our data practices change and show the revision date above.