Privacy policy

Who to contact

Rogue operates this website. For questions about your account or personal information, contact [email protected].

Account information

We use Clerk to authenticate accounts and maintain sign-in sessions. When you register or sign in, Clerk processes your email address, authentication information, and security information about the sign-in. Passwords and verification codes are handled by Clerk; the Rogue application does not store them in its database.

Our private account records contain your Clerk account identifier, verified email address, profile image when available, the public username you choose, account role, and account activity timestamps. These records let us identify your account, protect access, and associate account activity and any purchases with the correct person. Roles are assigned by the server, not by your Google profile.

Sign in with Google

Google sign-in is optional. You can also use email and password. If you choose Google, Google shares your identity, email address, and basic profile, including your name and profile image, with Clerk to authenticate you. Rogue synchronizes your verified email, account identifier, and profile image. Your public Rogue username is chosen separately; we do not copy your Google full name into your public Rogue profile.

We request only the openid, email, and profile permissions. We do not request access to Gmail messages, Google Drive files, calendars, or contacts. Google account data is used for sign-in, account linking, profile synchronization, account support, and security. We do not sell this data, use it for advertising, or use it to train AI models.

You can remove Rogue's Google access in your Google Account's third-party connections settings. This stops future Google authorization; it does not by itself delete your Rogue account or existing account records. Arrange another sign-in method before removing your only method.

Browser storage and technical information

Authentication and security services use cookies and similar storage to maintain sessions and protect the site. Your browser stores your cart selections locally. The live visitor counter uses a randomly generated browser identifier that renews after 24 hours; it counts recent activity across tabs without displaying your identity.

Our hosting and security services process technical request information, such as IP addresses, request times, browser information, and requested URLs, to deliver the website, diagnose errors, and prevent abuse. These are not used by Rogue for advertising profiles.

Who processes information

Clerk processes authentication and account-security information. Supabase stores the site's private account and store records. Cloudflare provides website delivery, attack protection, and media storage. Our website host processes requests needed to run the service. Google processes Google sign-in under its own privacy policy. These services may process information outside your country.

Authorized administrators can access account information needed for support and administration. Public reviews, if you submit them, display your chosen username and review content. Links to Discord, game artwork, and other external services are governed by those services' own privacy practices.

Retention and your choices

We keep account information while needed to provide your account, support, and security. Account and transaction history may need to remain after access is disabled to preserve purchase records, resolve disputes, prevent fraud, or meet applicable requirements. Deleting an authentication account disables its access and removes its linked email and avatar from Rogue's synchronized profile; it does not automatically erase every historical record.

Contact [email protected] to request access to, correction of, or deletion of your information, or to ask about retained records. We may need to verify account ownership before acting. You can clear local cart and visitor storage through your browser; clearing authentication cookies signs you out.

Changes

We will update this page when our data practices change. Any additional Google permissions or new uses of Google account data will be disclosed before we request your authorization.