YOUR DATA
Privacy Policy
Effective October 23, 2026
Cubing Comp Sim is a cubing practice app operated by Brandon True. You can practice without creating an account. Cloud transfers happen only when you choose them.
1. Information we handle
On your device: the app stores practice rounds, solve times, scrambles, penalties, settings, and offline assets using browser storage on the website and a local database in the iPhone and iPad app. The website stores its sign-in session in browser storage; the native app stores session credentials in protected operating-system storage. These records are not public.
Accounts: when you register or sign in, our authentication service processes your email address, account identifier, authentication details, and account activity. For Google or WCA sign-in, this may include your provider identifier, name, profile-picture URL, and other basic profile claims returned by the provider, including a WCA identifier when available. Your Google or WCA password is entered at that provider, not in Cubing Comp Sim. Apple sign-in processes an Apple account identifier and an email address, which can be an Apple private relay address. The native app requests name and email scopes from Apple but does not send the separately returned full-name object to our server. Authentication providers can retain profile claims as part of your account. The native app does not request access to your photo library, contacts, location, camera, or microphone.
Cloud saves: choosing Upload sends a snapshot of your practice history, including rounds, attempts, results, and scrambles, together with metadata needed to store and retrieve it. Signing in alone does not upload your history. Download replaces the history on your current device only after your confirmation.
Service operations: hosting, authentication, email, and security services process technical information such as IP addresses, request timing, browser information, response codes, and security events to deliver and protect the service. If you contact us, we receive the information you choose to provide.
2. Why we use information
We use this information to run the simulator, authenticate accounts, send confirmation and recovery emails, store and retrieve cloud saves, respond to requests, diagnose failures, and prevent abuse. We do not sell personal information, use it for targeted advertising, or use Google account information to train AI models.
3. Google, WCA, and Apple sign-in
Where a provider is offered, sign-in requests only the basic identity, profile, and email access needed for authentication. Google access is limited to openid, userinfo.email, and userinfo.profile. We do not request Gmail, Drive, Calendar, or Contacts access. WCA sign-in uses its public, OpenID, profile, and email scopes.
For Sign in with Apple, we exchange the authorization code and retain encrypted grant information needed to revoke authorization when deleting an Apple-linked account. Apple account deletion can remain pending while revocation is retried. We do not store your Apple password.
Information received from Google APIs is used and transferred in accordance with the Google API Services User Data Policy, including its Limited Use requirements. Provider information is used for account authentication and related account features, not advertising. Revoking a provider connection does not by itself delete your Cubing Comp Sim account or cloud save.
4. Providers and disclosures
We use Supabase for authentication and database services, Cloudflare for website delivery and cloud-save object storage, DigitalOcean for the cloud API server, and Resend for account emails. Apple, Google, and the World Cube Association process their own sign-in flows under their own policies. These providers process information needed to supply their services. Information may be processed in the United States and other countries where these providers operate.
We may disclose information when required by law, to address security incidents or protect users, or at your direction. We do not publish your cloud save or share it with other users as an app feature.
5. Website analytics and service diagnostics
Website: visits, daily account activity, cloud API outcomes, and basic error codes are collected automatically. A random browser identifier is stored on your device. Visit and activity records are kept for 180 days, and operational events for 30 days. These records exclude solve times, scrambles, passwords, and account tokens. Optional reporting controls do not disable this collection.
Website optional reporting: product analytics and client diagnostics are separate, opt-in settings under Settings → Privacy. When enabled and configured, PostHog receives limited product events and Sentry receives limited diagnostic events. These reports are designed to exclude your email, passwords, account tokens, scramble text, and exact solve history. The app does not use session replay or automatic form recording. Turning either setting off stops that optional reporting; essential hosting and security processing continues.
Native iPhone and iPad app: the current release does not include the website visitor counter, PostHog reporting, or Sentry reporting. Authentication services still retain account and security activity. The cloud API records request outcomes, request identifiers, response timing, and basic error codes to operate and diagnose the service. These API logs exclude authorization headers, cookies, email addresses, passwords, tokens, and save contents. Hosting and authentication providers may retain technical and security logs, including IP addresses. We do not use these records for advertising tracking.
6. Storage, retention, and deletion
Local history remains in your browser or native app storage until you delete or replace it, or the browser or operating system removes the data. Removing the native app may remove its local history. Keep a backup of history you want to preserve.
An account has one current cloud save. Uploading a replacement replaces the active save; there is no user-facing archive of previous saves. Account information and the current save are kept while the account remains active, unless you request deletion or they must be removed for service or legal reasons.
Use the account-deletion control in Account & cloud save to request removal of your account and associated cloud save. Deletion may require reauthentication and may take additional processing if a service is temporarily unavailable. It does not erase local history from your devices. Remove that separately using the app's local-data controls or browser settings, as applicable.
Limited security, operational, deletion-processing, or legally required records may remain after account deletion for the purpose they support. Infrastructure backups, where maintained, can retain older copies separately from the active service until they are removed under the applicable backup lifecycle. Cloud storage is not a guarantee against data loss.
7. Your choices and requests
You can use guest mode, export your practice history where available, choose whether to upload or download, change the website’s optional reporting settings, revoke Google access through your Google Account connections, and delete your account. Depending on where you live, you may also have rights to request access, correction, deletion, portability, or restrictions on processing. Contact us to make a request; we may need to verify that the account belongs to you.
8. Children
The online account service is not directed to children under 13. We do not knowingly collect account information from children under 13. If you believe a child has provided account information, contact us so we can investigate and remove it where appropriate.
9. Changes and contact
Updates to this policy will be posted here with a new effective date. For privacy questions or requests, contact the maintainer through the project issue tracker. Issues are public: start with a general request for private contact and do not post your email address, account credentials, tokens, or other personal information.