Privacy Policy

Information SQC handles

Account and profile information

SQC uses Clerk for sign-in and account management. Depending on how you sign in, Clerk and SQC may handle an account identifier, email address, name, username, profile image, authentication session information, and the sign-in provider you choose. Authentication cookies or equivalent session storage are used where needed to keep you signed in and protect account-only features.

Chess and quest information

If you add one, SQC stores your public Lichess or Chess.com username. SQC also stores information needed to run the product, such as your display name and bio, active and completed quests, proof attempts and results, game identifiers, timestamps, ratings snapshots, unlocked rewards, custom quests, likes, and Multiplayer Side Quest participation, invitations, standings, and host records.

Support messages

Signed-in support messages are stored with your account and can include the text you submit, submission time, account email and display name, source (web or mobile), and any diagnostics you choose to include. Mobile diagnostics currently include app/build details and account-state summaries such as connected usernames and active-quest counts. Do not send passwords, private invite codes, or information you do not want included in a support thread.

Product analytics and technical information

SQC records limited first-party product events, such as page views, profile saves, quest starts and outcomes, community browsing actions, the relevant path or quest/game identifier, event time, source, and a coarse device category inferred from the browser user agent. For signed-in users, compact event totals and a limited recent-event history are stored with the account. Anonymous events are written to application logs and are not attached to an SQC account.

The current application does not include a third-party advertising or behavioral-analytics SDK. Standard hosting, security, and request logs may still be created by the services that operate SQC.

Chess game verification

When you ask SQC to check a quest, SQC sends the public chess username or public game identifier needed for that check to the public Lichess or Chess.com interfaces. It reads public profile, rating, archive, PGN, move, result, color, and game-time information as needed to determine whether a quest rule was completed and to create a proof result.

SQC does not ask for or receive your Lichess or Chess.com password. Lichess and Chess.com process requests under their own terms and privacy policies. Connecting a username does not connect your chess-site login credentials to SQC.

How SQC uses information

• Authenticate users and keep account features synchronized across web and mobile.
• Find eligible public chess games, verify quest rules, save progress, and display proof and rewards.
• Operate public, invite-only, and account-related community and Multiplayer Side Quest features.
• Respond to support requests, diagnose problems, secure the service, and understand product reliability and feature use.

The implementation reviewed for this draft has no advertising feature or targeted-advertising integration. Whether SQC should make a broader legal statement about sale or sharing of personal information requires owner/legal confirmation.

When information is visible or shared

SQC sends information to Clerk for authentication and to Lichess and Chess.com when retrieving public chess records. The deployed application also necessarily passes requests through its hosting and delivery infrastructure; the complete production vendor list and contractual roles require owner confirmation.

Some SQC features are intentionally social. Depending on what you create, join, publish, or share, other people may see your SQC display name, public chess username and provider, avatar, custom or Multiplayer Side Quest content, participation, progress, standings, completed quests, and proof details. Public proof links can include a game identifier, provider, result, timestamps, board position, and move evidence. Review a link or quest’s visibility before sharing or publishing it.

Retention and deletion

SQC keeps account and quest information while it is needed to provide the account and product features. Implemented limits currently keep up to 30 signed-in support messages, a compact analytics history of up to 12 recent events and 12 quest-stat records, and up to 500 account likes. Those limits do not by themselves delete the rest of an account.

Current launch limitation: SQC does not yet expose self-service account deletion in the website or mobile app. You can request deletion or correction through privacy support. The exact response period, backup/log deletion schedule, and any legally required retention exceptions must still be confirmed by the product owner before this policy is treated as final.

Your choices

• You may browse public quest pages without creating an account.
• You can replace connected public chess usernames in account settings. The current product requires at least one username to remain; complete removal requires contacting SQC and the deletion process still needs owner confirmation.
• You can choose not to publish custom content or share proof links.
• You can contact SQC about access, correction, or deletion of information associated with your account. The request process and response timeline still require owner confirmation.

Children and international use

Launch confirmation required: SQC’s intended minimum user age, parental-consent approach, operating legal entity/controller identity, and primary processing country have not been established in the implementation reviewed for this policy. These facts must be confirmed before final publication or app-store submission.

Changes to this policy

This page should be updated when SQC practices change. The final notice process and effective date require owner confirmation.