Privacy Policy

RiftScope currently runs in demo/mock mode. The public demo does not use live Riot data unless that is explicitly enabled in a later production release.

Riot account linking is not currently active as a real Riot Sign On flow. Future Riot stats access will require explicit user consent before personal stats are processed or shown publicly.

RiftScope uses Google OAuth for app login when configured. Google may provide basic account information such as your name, email address, and profile image so RiftScope can create and manage your app session.

Google login identifies your RiftScope app account. It does not prove Riot account ownership and does not grant access to Riot stats.

• App account data, such as user ID, name, email, and authentication session records.
• Linked account metadata if you link an account, such as region, display name, and account identifiers.
• Consent and privacy settings, including public/private profile choices.
• Audit logs for account linking, unlinking, consent, privacy, and data refresh actions.
• Cached responses or derived tracker data if caching is enabled later.

RiftScope does not currently store Riot access tokens or Riot refresh tokens. If token storage is introduced in the future, it should be documented before activation and protected server-side.

RiftScope does not sell user data. Data may be processed by infrastructure providers needed to run the app, authentication, hosting, database, and monitoring systems.

For privacy, consent, access, correction, or deletion requests, email [email protected]. Include the email address you use to sign in so the request can be matched to the right app account.

This policy may change as RiftScope moves from demo mode toward live integrations. The app should keep privacy and consent behavior visible before any live Riot data is used.

Last updated: May 30, 2026.