HistoryQ Contact

HistoryQ Privacy Policy

Last updated: July 18, 2026

This Privacy Policy explains how HistoryQ handles information when you use the HistoryQ mobile app. HistoryQ is a historical-figure guessing game with local progress, automatic cloud backup, community statistics, rewarded ads, and a one-time premium purchase. HistoryQ is operated by Compound G in the Netherlands. Full controller and contact details appear at the end of this policy.

Information Stored On Your Device

HistoryQ stores gameplay and app state on your device so the app can remember your progress. This may include:

This device data is used to run the app experience and is not automatically public.

Account And Cloud Save Data

The current release configuration automatically creates an AWS-backed account identifier and backs up app state without requiring email sign-up first. HistoryQ stores the following account-linked app state in AWS:

If email recovery is enabled and you choose to add it, HistoryQ stores your email address with your account profile. Password sign-up, confirmation, and verification are handled through AWS Cognito over encrypted connections. HistoryQ does not store your password, local password hash, or password salt in cloud save. Signed-in session tokens may be stored in the iOS Keychain.

We use this information to provide cloud continuity, account recovery, restore app state, and keep your progress available across supported devices or installs.

Puzzle Statistics, Leaderboards, And Feedback

After a daily puzzle or supported archive puzzle is completed, HistoryQ may submit gameplay results to create community statistics and comparison features. This may include:

HistoryQ may also let you submit puzzle feedback. Feedback may include:

Puzzle statistics and feedback are used to operate community statistics, improve puzzle quality, detect duplicate submissions, rank or compare completed runs, and understand how puzzles perform.

These records are intended to be separated from your email address, advertising identifier, and authenticated account profile. However, because they may include submission IDs, timestamps, app version, unlock method, guess sequences, and server request metadata, HistoryQ treats per-run gameplay analytics as pseudonymous data rather than anonymous data.

Do not include personal, confidential, unlawful, or sensitive information in feedback comments.

Purchases

HistoryQ uses Apple StoreKit for in-app purchases. Apple processes purchase transactions, payment information, refunds, purchase history, family sharing eligibility, and Apple ID account information according to Apple's own terms and privacy practices.

HistoryQ stores only the entitlement state needed to unlock premium app features, such as whether the Premium Pack has been purchased or restored. Cloud save may store a mirror of this entitlement state for app continuity, but Apple remains the purchase source of truth.

Ads And Consent

HistoryQ uses rewarded ads to let users unlock certain content or Archive Passes without purchasing the Premium Pack. When an ad is requested, the ad provider may process data such as device identifiers, advertising identifiers where available and permitted, approximate location, ad interactions, diagnostics, consent choices, and fraud-prevention signals according to its own policies and SDK behavior.

The shipping app includes Google AdMob and Google User Messaging Platform. Where required, HistoryQ presents a consent flow for users in the EEA, UK, and Switzerland and includes an in-app "Privacy and cookie settings" control to revisit advertising consent choices.

HistoryQ's own gameplay analytics, such as guessed figures, solve timing, streak progress, archive progress, and puzzle feedback, are first-party app data used to operate HistoryQ. They are not cross-app or cross-website tracking for App Tracking Transparency purposes.

The current HistoryQ app build does not request App Tracking Transparency permission and does not claim to track users across other companies' apps or websites. If a future version of HistoryQ uses ATT-governed tracking or personalized advertising behavior that requires ATT permission, HistoryQ will request that permission before enabling that behavior.

Notifications

If you allow notifications, HistoryQ may schedule local reminders for daily puzzles and engagement prompts. Notification settings are controlled by iOS. HistoryQ does not need to sell or share your contact details to send local notifications.

App Store Privacy Information

HistoryQ's App Store privacy details are intended to match the shipping app, this Privacy Policy, and the disclosures of its third-party SDKs. Relevant categories include gameplay content, user identifiers, purchases, product interaction, advertising data, diagnostics, coarse location, feedback comments and ratings, and other data processed by Apple, AWS, or Google as described in this policy.

Legal Bases For EU/EEA Users

Depending on the feature, HistoryQ processes personal data on these legal bases:

Where processing is based on legitimate interests, users may have the right to object depending on their location and the specific processing.

Required And Optional Information

The automatic AWS identity and cloud state are required for the cloud-backup configuration used by the current release. If this information cannot be processed, cloud backup and continuity will not work, but Apple-managed purchase restoration may still be available.

Email recovery, display name, puzzle feedback comments, notifications, ad consent choices, and rewarded-ad use are optional. Declining or omitting optional information may make the related feature unavailable but does not prevent basic gameplay.

HistoryQ does not use personal data to make automated decisions that produce legal or similarly significant effects.

Sharing

HistoryQ shares or processes information with providers needed to operate the app, including:

AWS generally processes HistoryQ cloud, API, storage, and logging data on behalf of Compound G. Apple and Google may act as independent controllers for their own App Store, purchase, advertising, fraud-prevention, consent, and platform operations, and may act as processors or service providers for other functions. Their own privacy notices also apply to the services they control.

HistoryQ does not sell your personal information.

Retention

HistoryQ keeps local data on your device until you delete it, reset the app, or uninstall the app, subject to iOS backup and restore behavior.

Cloud save data is kept while your account exists and the app's cloud services remain supported, unless you delete the account or request deletion where applicable.

HistoryQ currently uses the following retention approach for cloud and backend data:

Your Choices And Rights

Depending on your location, you may have rights to:

To exercise privacy rights, contact info@historyq.com. We may need enough information to verify the account, device, submission, or app data involved. Because per-run analytics and feedback are deliberately separated from your email and account profile, you may need to provide the relevant puzzle date, submission ID, or feedback ID so we can locate a specific record.

You can also manage certain choices directly:

Children

HistoryQ is a general-audience app and is not designed or marketed specifically to children. HistoryQ does not ask users to provide their age or date of birth and does not knowingly collect personal information from children below the minimum age required by applicable law without appropriate consent.

If you believe a child has provided personal information, contact us so we can review and delete it where required.

International Transfers

HistoryQ's primary AWS backend is configured in the European Union. Apple, AWS, and Google may also process data in the United States or other countries where they operate. Where required, those transfers rely on applicable safeguards such as adequacy decisions, the EU-US Data Privacy Framework, or standard contractual clauses. Contact info@historyq.com to request more information about the safeguards relevant to HistoryQ's processing.

Security

HistoryQ uses platform and provider security features such as encrypted HTTPS connections, iOS Keychain storage for supported session tokens, AWS-managed infrastructure controls, and access controls for cloud services. No method of storage or transmission is completely secure, but HistoryQ aims to limit collected data to what is needed for app features.

Changes

We may update this Privacy Policy as the app changes. The updated version will show a new "Last updated" date. If changes are material, we may provide additional notice in the app or through the App Store listing where appropriate.

Controller And Contact Details

HistoryQ's data controller is:

For questions, privacy requests, complaints, or deletion requests, use the email address above. You may also lodge a complaint with the Dutch Data Protection Authority (Autoriteit Persoonsgegevens).