Privacy Policy

1. Introduction

HistorIQly ("we," "our," or "us") respects your privacy and is committed to protecting your personal data. This privacy policy explains how we collect, use, and safeguard your information when you use our AI-powered educational platform and related mobile apps, including HistorIQly Past Lives, HistorIQly Geo and HistorIQly Dynasties. Data practices depend on the product and features you use; HistorIQly Geo is described in Section 15 and the Dynasties Android app in Section 16.

2. Data Controller

Contact: HistorIQly
Email: privacy@historiqly.com

3. Data We Collect

3.1 Information You Provide

• Account Information: Email address, name (optional), password, and an optional Google profile-photo URL when you choose Google sign-in
• Payment Information: Processed securely by Google Play for Android in-app subscriptions and by Stripe for web subscriptions; we do not store complete card details
• Conversation Data: Messages you send to our AI characters, including in-chat searches and feedback or reports you submit
• Voice Inputs: Audio you choose to record is sent for transcription and is not stored by HistorIQly after the transcription request is processed
• Document Attachments: Files you choose to attach to a chat are uploaded so we can extract and use their text in that conversation. We discard the original file bytes after extraction and retain the extracted text with the related conversation until that conversation or account is deleted
• Photo and Image Inputs: Your Google profile image when you choose Google sign-in; photos you choose or take in the web HistorIQly: AI Photo Maker; optional profile details you enter for poster generation; and generated image outputs
• Preferences: Theme, notification settings, accessibility options, device-local credit balances, and saved poster settings

3.2 Information Collected Automatically

• Usage Data: Message counts, feature usage
• Technical Data: IP address, browser type, app version, device information
• Performance Data: Page load times, error reports
• App Analytics: App interactions, purchase events, session statistics, approximate location derived from network information, and app-instance or device identifiers collected through Firebase Analytics to understand and improve the mobile experience
• Notification Data: A device push token and your notification preferences when you enable notifications

3.3 Mobile App Permissions

On Android, HistorIQly: AI History Chat may request access to the microphone for voice input and permission to save a generated poster to your photo library. Documents are selected only when you choose to attach one. The Android app does not use the camera for AI Photo Maker uploads. The separate web AI Photo Maker may request browser camera or photo access when you choose those actions.

• Photo Library: Used on Android only to save a generated poster when you request it. The web AI Photo Maker can access a photo only after you select or capture one.
• Microphone: Used only when you choose voice input for transcription.
• Files: Used only when you choose a document to attach to a chat.
• Notifications: Used only when you opt in to push notifications.
• Device Storage: Generated posters and credits are stored locally on your device unless you choose to share or save them elsewhere.

4. How We Use Your Data

5. AI Data Processing

When you use our chat features, your messages are sent to third-party AI providers (including OpenRouter, Google, and DeepSeek) to generate responses. When you use the web HistorIQly: AI Photo Maker, the photo and details you submit are sent to our backend and to AI image providers through OpenRouter to generate the artifact you requested. We configure supported OpenRouter inference requests to exclude providers that declare they collect request content. AI, transcription, image-generation, and optional search providers still process the inputs needed to provide their features under their own retention, safety, and legal policies.

We do not make automated decisions that significantly affect you based solely on AI processing. Our AI provides educational content only.

6. Data Sharing

We share your data with:

• Google Play: Android subscription billing, purchase verification, and subscription management
• Stripe: Web subscription payment processing
• OpenRouter/AI Providers: Conversation and image generation processing
• Resend: Email delivery
• Neon: Database hosting (AWS US-East-1)
• Google/Firebase: OAuth authentication (if you choose Google sign-in), mobile analytics, push notifications, app integrity checks, and diagnostics
• Expo: Mobile push-notification delivery

We do not sell your personal data. We do not share your data with advertisers.

7. Data Retention

• Account data: Until you delete your account
• Conversations: Retained while your account is active until you delete the conversation or your account
• Web AI Photo Maker uploads: Processed to generate the requested artifact and not intended for long-term storage on our servers; generated posters are saved locally unless you choose to share or save them elsewhere
• Payment records: As required by law (typically 7 years)
• Voice recordings: Forwarded for transcription and not retained by HistorIQly after processing
• Document attachments: Original file bytes are discarded after text extraction; extracted text is retained with the related conversation until you delete that conversation or your account
• Security logs: 2 years for compliance

8. Your Rights

Under GDPR and CCPA, you have the right to:

• Access: Request a copy of your data
• Rectification: Correct inaccurate data
• Erasure: Delete your account and data
• Portability: Export your data in a common format
• Object: Opt out of certain processing
• Restrict: Limit how we use your data

To exercise these rights, go to Settings > Account for account-based services or email privacy@historiqly.com.

9. Cookies

We use:

• Essential cookies: Required for authentication and security
• Preference cookies: Remember your settings (with consent)
• Analytics cookies: Understand usage patterns (with consent)

You can manage cookie preferences using our cookie consent banner or browser settings.

10. Security

We protect your data using:

• AES-256-GCM encryption for sensitive fields
• Argon2id password hashing
• TLS encryption for data in transit
• Multi-factor authentication (optional)
• Rate limiting and fraud prevention

11. International Transfers

Your data may be processed in the United States. We ensure appropriate safeguards through Standard Contractual Clauses with our processors.

12. California Residents (CCPA)

California residents have additional rights:

• Know what personal information is collected
• Know if personal information is sold or disclosed
• Say no to the sale of personal information (we do not sell PI)
• Access your personal information
• Equal service regardless of privacy choices

13. Changes to This Policy

We may update this policy periodically. We will notify you of material changes via email or in-app notification.

14. Contact Us

For privacy questions or to exercise your rights:
Email: privacy@historiqly.com

For EU residents, you have the right to lodge a complaint with your local supervisory authority.

15. HistorIQly Geo History Puzzles

This section applies to the Android game HistorIQly Geo History Puzzles (com.historiqly.games). Geo does not require a HistorIQly chat account. The AI conversations, chat attachments and Firebase app analytics described for our other products are not features of Geo puzzle play.

• One-time collection purchase: Google Play handles checkout. Geo uses RevenueCat to process purchase history, verify collection access and restore purchases. RevenueCat generates an anonymous customer identifier when its SDK initializes; purchase checks can initialize it before you decide to buy. Purchase-related processing includes purchase analytics and is separate from local game progress.
• Local progress: Scores, discoveries, unfinished games and preferences are saved in app storage on your device. A local checkout reminder records only whether a payment needs checking and cannot unlock the collection. Geo does not operate a progress-sync service. Your operating system may separately back up app data according to your device settings.
• Map answers: The pin you place is a game answer, not a request for your physical location. Geo puzzle play does not request GPS access or send guesses to a gameplay analytics service.
• Optional external actions: Source links, support email, store reviews, Atlas and sharing open the relevant website, app or system interface when you choose them. Those destinations have their own data practices. Atlas is a separate app; Geo does not receive your store review text or confirmation that you submitted a review.

Restoring a purchase restores access, not your local scores or discoveries. Clearing game storage does not delete purchase records held by RevenueCat or Google Play, and does not refund a transaction. For Geo purchase support or questions about purchase-related data, contact historiqly@cyril.page. You can also use the privacy contact in Section 14. Please identify the app as HistorIQly Geo so your request can be routed to the appropriate product.

16. HistorIQly Dynasties

This section applies to the Android app HistorIQly Dynasties, listed as HistorIQly: Royal Family Tree (com.historiqly.dynasties). It does not require a HistorIQly account. The account, AI conversation and Firebase app analytics features described for our other products are not part of this native app. The Dynasties website has separate account and membership features.

• One-time lifetime purchase: The bundled collection is free. Google Play handles checkout for the optional lifetime unlock; this is a one-time payment, not a subscription. RevenueCat processes purchase history to verify access, restore purchases and provide purchase analytics. RevenueCat generates a random anonymous customer identifier when its SDK initializes. Purchase checks can initialize it before you choose to buy. We do not receive your complete payment-card details.
• Local app data: Saved people, connections and successions, recent history, preferences, review-prompt choices and cached historical content are stored on your device. The native app does not operate an account-based synchronization service for these records. Your operating system may separately back up app data according to your device settings.
• Historical sources: Online searches, records, articles and images are requested from Wikidata, Wikipedia and Wikimedia Commons. These requests send the requested search or resource and normal network information to those services, which have their own privacy practices. The app also checks HistorIQly-hosted collection updates.
• External actions: Source links, support email, ratings and Atlas links open the relevant website, app or system interface when you choose them. Atlas is a separate app. Dynasties does not receive your store review text or confirmation that you submitted a rating.

Restoring a purchase restores access, not your local saved views or history. Clearing app storage does not delete purchase records held by RevenueCat or Google Play, and does not refund a transaction. For purchase support, contact contact@historiqly.com. For questions about purchase-related data or to request its deletion, contact privacy@historiqly.com. Identify the app as HistorIQly Dynasties so we can help locate the relevant records. Google Play retains its own transaction records under its policies and applicable requirements.