Privacy Policy

Guest use

Qalc can be used without an account. Guest training sessions, settings, and Daily Workout progress are stored locally on the device. Guest gameplay is designed to work offline.

Accounts

If you create an account, Qalc and Supabase process your email address, username, provider identifiers, and authentication credentials. Passwords are handled by Supabase Auth and are not stored directly by Qalc. Google or Apple sign-in may provide provider identifiers and account profile data needed to create or access your Qalc account.

Training data

Guest training history remains on the device. When you sign in, completed sessions, solve-time observations, and Daily Workout progress sync to your Supabase-backed account. Offline changes wait on the device and retry later when connectivity returns.

Device storage

Qalc uses local device storage for guest sessions, signed-in sync queues, app settings, Daily Workout progress, cached entitlement state, and identifiers needed to operate the app. Deleting the app may remove local data depending on the platform.

Ads and privacy choices

Free users may receive contextual or non-personalized ads outside active gameplay. Qalc requests applicable consent choices before requesting ads and provides an Ad Privacy Choices entry in Settings when required. No Ads and Pro users receive no ads. Ads are not shown during active rounds.

Purchases and entitlements

Qalc uses RevenueCat to process purchase, restore, and entitlement status for No Ads and Pro products. Apple and Google control store purchase records, billing, cancellation, refunds, and payment details. Qalc does not receive full payment-card details.

Analytics and crash reporting

Qalc has a provider boundary for privacy-conscious crash reporting and product analytics, but remote provider names will be added only after those services are selected and configured. When enabled for a signed release, Qalc may send anonymous, coarse events such as app opens, completed rounds, and purchase or ad flow outcomes.

General analytics exclude raw questions, raw answers, passwords, auth tokens, email addresses, usernames, and payment details. Qalc uses an anonymous installation identifier for guest analytics and may alias that identifier to an opaque Supabase UUID after sign-in.

Account deletion

Signed-in users can permanently delete their cloud account and synced training history from Settings. During deletion, you can separately choose whether to remove local training history from the current device. Instructions are available at qalcapp.com/account-deletion.

Support

Privacy and account questions can be sent to [email protected]. Support requests may include the information you choose to provide, such as device platform, app version, build number, and issue description.

Updates

Qalc may update this policy when app behavior, provider integrations, legal requirements, or store disclosures change. The effective date above will be updated when material changes are published.