Information we keep
CRPS stores an immutable internal account ID and your CRPS username and display name. For each connected sign-in identity, we store the provider name and its stable user ID, together with profile information we retain, such as username, display name and avatar URL. Your CRPS profile is separate from your provider profile.
When you use challenges, we store participant account IDs, challenge and match times, submitted choices and results to operate matches and maintain their history. Your public profile shows your CRPS username, display name, avatar, member-since date and aggregate completed-game record. Individual completed results are public and shareable. Your full history is private; signed-in players can see only their own head-to-head history with you. Open-challenge links intentionally show the creator’s public CRPS identity and availability. Their locked moves stay secret until resolution. Other incomplete matches and locked choices remain private to their participants, and an opponent cannot see your choice until both players have submitted. Deleting either participating account removes the shared match record. While retained, match classification never changes; only competitive matches count towards public statistics.
Discord and Google are our current sign-in providers. We request basic identity and profile scopes, not email access. We do not collect email addresses through the current sign-in flow, store passwords, or automatically link or merge accounts based on matching email addresses.
Guest play
You can create and accept Open Challenges as a guest without registering. We store a temporary guest identity, your chosen or generated nickname and a hashed session token. An essential Secure, HttpOnly cookie keeps the guest session active for 24 hours. Guest nicknames are public, not unique, and labelled Guest. Completed guest games are casual: they appear in the registered participant’s history and public results but do not affect statistics. Expired guest credentials and unused guest identities are removed during request-driven cleanup; guest nicknames on shared challenges and completed results remain part of the shared game record. A guest session can own one outstanding Open Challenge, available for 24 hours even if the session ends. Losing the session removes management access, not the shared link.
Authentication and security
We use essential cookies to keep you signed in and secure the sign-in process. Your light, dark or system appearance preference is stored locally in your browser. Server-side records include hashed session tokens, account references, authentication and activity times, expiry and revocation status, and temporary sign-in verification data. Session cookies last at most seven days; sessions also expire after 24 hours of inactivity. Temporary sign-in and pending-registration cookies expire after five minutes. For a new identity, we temporarily keep the verified provider ID and profile while you decide whether to create a CRPS account. Cancelling deletes this pending record. Expired pending records cannot be used and are removed during request-driven cleanup.
We use a short-lived hash derived from your IP address to limit repeated authentication attempts and record limited operational and security events. Our hosting services also process technical request information needed to deliver and protect the site. Provider access tokens are used during sign-in and are not persistently stored by CRPS.
Why we use this information
We use this information to authenticate you, manage your account and connected identities, operate CRPS, prevent abuse and investigate security or service problems. We do not sell personal data.
Retention and deletion
Account and connected-identity records are kept while your CRPS account exists. Signing out revokes your session but does not delete your account. You can delete your account in Account settings after an explicit confirmation. When a CRPS account is deleted, its connected identities and session records are also removed.
Expired sign-in and rate-limit records are removed during request-driven cleanup. Expiry stops a session from working; it does not necessarily immediately erase its database record. We aim to retain personal data only as long as reasonably needed for the purposes above, including resolving security issues or meeting applicable obligations.
Third-party services
CRPS uses hosting and database services to run the application. External authentication providers process information under their own privacy policies. Discord and Google handle sign-in to their respective services and provide the identity and profile information described above. Displaying a provider-hosted avatar also sends a request to that provider. See Discord’s privacy policy and Google’s privacy policy.
This policy describes CRPS as it works today. We will update it when our data practices change.