HISTORYSIM PRIVACY POLICY

Last Updated: March 2, 2026

This Privacy Policy explains how HistorySim LLC ("HistorySim," "we," "us," or "our") collects, uses, shares, and otherwise processes information in connection with the HistorySim mobile application for iOS and related services (collectively, the "Services").

If you have questions about this Privacy Policy or our privacy practices, contact us at:
Email: support@historysim.com

1. SCOPE AND KEY CONCEPTS

This Privacy Policy applies to information processed when you use the Services. It does not apply to third-party apps, websites, or services that you choose to access through iOS sharing features or other integrations.

"Personal information" (or "personal data") generally means information that identifies, relates to, describes, is reasonably capable of being associated with, or could reasonably be linked (directly or indirectly) with you or your device.

"Tracking" has a specific meaning under Apple's App Tracking Transparency (ATT) framework. In general, it refers to linking user or device data collected from our app with user or device data collected from other companies' apps/websites for targeted advertising or advertising measurement, or sharing user/device data with data brokers. When we refer to "Tracking" in this Policy, we mean Tracking as defined by Apple.

2. NO ACCOUNT / NO LOGIN (AND HOW WE IDENTIFY A DEVICE)

HistorySim does not require an end-user account or login at this time. Instead, the app generates a pseudonymous identifier on your device (an app_user_id).

Even without an account, some information (such as device identifiers and usage data) may still be considered personal information under certain laws.

3. INFORMATION WE COLLECT AND PROCESS

A) Information you provide or generate when using the Services

Onboarding and preferences. You may provide or generate onboarding/profile data such as goals, selected era/region/type/frequency, interests, prompt topics, motivation, preferred time, notification preferences, "local-history" and "this-day-in-history" preferences, and a selected onboarding course. If you enable location-based personalization, onboarding/profile data may also include latitude/longitude and a location label.

Gameplay and simulation content. When you play, you may generate gameplay data such as scenario prompts, characters, objectives, mission trackers, turn choices, event history, scenario source/date, and course/timeline episode context.

Advisor chat content. If you use advisor chat features, we process your messages along with relevant conversation history and scenario context to provide responses.

Content reports and feedback. If you report content, we process the report text you provide and may include the full scenario payload you reported to help us investigate and improve safety and quality.

Sharing content. If you use sharing features, we process generated share text, ratings/accuracy breakdowns, and (if applicable) share image prompts and image URLs.

Important note about what you type: If you voluntarily include sensitive or identifying information in prompts, chats, reports, or other free-form text, we will process that information to provide the Services. Please avoid including information you do not want processed (for example: government IDs, financial account numbers, or highly sensitive health details).

B) Information collected automatically from your device or through your use of the Services

Pseudonymous identifiers and device identifiers. We process the locally generated app_user_id. Depending on permissions and device settings, we and our analytics/attribution partners may also process device identifiers (such as Apple's IDFA if you grant ATT permission) and other device-related identifiers used for analytics, fraud prevention, attribution, and measurement.

Usage and analytics data. We collect event and interaction data such as app events, event properties, page paths, and scenario metadata. This helps us understand how the app performs and how features are used.

Session replay data (analytics feature). We use Mixpanel session replay. This may record certain in-app interactions (for example, taps, gestures, navigation patterns, and how screens are used) to help diagnose issues and improve user experience. In our current configuration, session replay is enabled on a limited percentage of sessions and is configured with automatic masking for text, images, web views, and maps, and is set to record on Wi-Fi only. Even with masking, session replay should be treated as potentially capturing in-app activity.

Location data (with permission). If you grant location permission, we collect and process your precise location (latitude/longitude) and may derive a location label (for example, a city/region label) to personalize "local history" experiences. If you do not grant location permission, you can still use the Services, but location-based personalization may be limited or unavailable.

Notification-related data (with permission). If you enable notifications, we store your notification preferences and local scheduling identifiers to deliver reminders you request (for example, daily reminders).

Local storage and cached media. The app stores certain information on your device using local storage (e.g., onboarding completion, streaks/badges, last play date, recent prompts, course snapshots, billing snapshots, and an active session state). The app also stores cached/generated media (including share images) in local directories on your device.

Diagnostics and security data. We may collect diagnostic information related to reliability and security, such as crash reports, error logs, and troubleshooting information (which can include information about the action being performed and technical context).

C) Information we receive from third parties

Subscriptions and billing providers. Purchases are processed through Apple's App Store. We use RevenueCat to manage subscriptions and entitlements and to synchronize purchase and subscription status. We receive information such as entitlement/product status, renewal/expiration timestamps, credit balances/periods, and related identifiers used for subscription management.

Analytics and attribution partners. We use Mixpanel for analytics (and session replay) and AppsFlyer for attribution and measurement. These services may provide aggregated reports and/or event-level data to help us understand marketing performance and app usage.

Service providers supporting AI generation. We use third-party providers for text generation and content safeguards and for image generation. These providers process inputs we send (which may include gameplay prompts, scenario context, chat messages, and image prompts) and return generated outputs.

4. HOW WE USE INFORMATION

We use information to operate, maintain, and improve the Services, including to:

- Provide the core experience. Generate and deliver scenarios, timelines/courses, advisor chat responses, and sharing outputs.
- Personalize content. Use onboarding/preferences (and, if enabled, location) to tailor scenarios and recommendations, including local-history experiences and daily prompts.
- Manage subscriptions, entitlements, and credits. Determine whether you have an active entitlement (e.g., "HistorySim Pro"), track credit balances, prevent duplicate or fraudulent credit consumption, and provide customer support for billing issues.
- Analyze and improve performance. Understand feature usage, app performance, and user experience; debug issues; and improve reliability, safety, and quality (including through analytics and session replay).
- Marketing measurement and attribution. Measure how users discover the app and how campaigns perform, including attribution of installs/subscriptions where permitted.
- Safety, security, and compliance. Detect, prevent, investigate, and respond to abuse, policy violations, fraud, security incidents, and other harmful activity; comply with legal obligations; and enforce our terms and policies.

5. HOW WE SHARE INFORMATION

We share information in the following circumstances:

Service providers and processors. We share information with vendors that process information on our behalf to provide the Services, including:

- Supabase
- OpenRouter
- Fireworks
- RevenueCat
- Mixpanel
- AppsFlyer

These providers process information under contractual terms intended to protect it and limit its use to providing services to us (subject to each provider's own terms and technical constraints).

Legal and safety reasons. We may disclose information if we believe in good faith that disclosure is necessary to comply with law, respond to lawful requests, protect the rights and safety of HistorySim, our users, or others, or to investigate fraud or security issues.

Business transfers. If we are involved in a merger, acquisition, financing, reorganization, bankruptcy, or sale of assets, information may be disclosed as part of that transaction, consistent with applicable law.

Aggregated or de-identified information. We may share information that has been aggregated or de-identified such that it cannot reasonably be used to identify you.

6. APP TRACKING TRANSPARENCY, TRACKING, AND YOUR CHOICES

ATT permission. The app may request permission under Apple's App Tracking Transparency framework. If you allow tracking, we (and our attribution/analytics partners) may access and use the IDFA and engage in Tracking for attribution/measurement as configured. If you do not allow tracking, we will not access the IDFA, and tracking-related functionality may be limited. You can change your choice at any time in iOS Settings.

Attribution and mirrored events. Our app's analytics implementation may send certain events (including subscription-related events) to both Mixpanel and AppsFlyer to measure performance and understand how users interact with the app.

"Do Not Track." Some browsers offer a "Do Not Track" signal. Because the Services are primarily a mobile app and because there is no consistent industry standard for responding to such signals, we do not respond to Do Not Track signals as a general rule.

7. LOCATION AND NOTIFICATIONS

Location. You can allow or deny location access at any time through iOS Settings. If you allow location, we use it to personalize local-history experiences and may store location data (including precise latitude/longitude and a location label) along with onboarding or scenario personalization context.

Notifications. You can enable or disable notifications in iOS Settings. If enabled, we use notification preferences to schedule reminders.

8. DATA RETENTION

We retain information for as long as reasonably necessary to provide the Services and for the other purposes described in this Privacy Policy, including complying with legal obligations, resolving disputes, enforcing agreements, and maintaining security.

Because the app does not use a traditional account system, retention may be tied to pseudonymous identifiers (like app_user_id) and device identifiers. Some data stored on your device is limited (for example, certain local lists are capped), and the app clears some session data when a simulation ends. Server-side retention periods may vary by data type and operational needs, and we may retain certain records (such as billing and security logs) for longer periods when required or appropriate.

9. DELETION, ACCESS, AND CORRECTION

A) On-device deletion

You can remove locally stored app data by deleting the app from your device. You may also have in-app controls for deleting certain items (such as badges or timelines) where available.

B) Server-side data requests

Even without an account, we may store certain information on our servers associated with your app_user_id (for example, billing entitlement snapshots, credit state/ledger entries, analytics events, onboarding suggestion batches, and content reports). Currently, the app may not include an automated "delete all server data" control.

You can request access to or deletion of server-side data by contacting us using the contact details above. To help us locate your data, we may ask for information such as:
- relevant subscription identifiers (if you contacted us about billing), and/or
- device and usage context needed to verify and process the request.

We will respond consistent with applicable law and may need to retain certain information for legal, billing, security, or fraud-prevention purposes.

10. SECURITY

We use reasonable administrative, technical, and organizational safeguards designed to protect information we process. No method of transmission or storage is 100% secure, and we cannot guarantee absolute security.

11. INTERNATIONAL DATA TRANSFERS

We and our service providers may process and store information in countries other than where you live (including the United States). These countries may have different data protection laws. Where required, we take steps designed to support lawful data transfers (for example, by using appropriate contractual protections).

12. CHILDREN'S PRIVACY

The Services are not directed to children under 13 (or under the age required by local law), and we do not knowingly collect personal information from children. If you believe a child has provided personal information to us, contact us and we will take appropriate steps to address it.

13. REGION-SPECIFIC DISCLOSURES

A) EEA/UK/Switzerland (GDPR) — legal bases and rights

If you are located in the EEA, the UK, or Switzerland, we rely on the following legal bases (as applicable) to process personal data:

- Contract necessity: to provide the Services you request (e.g., generating scenarios, providing subscription entitlements/credits).
- Consent: for certain permissions (e.g., precise location, notifications) and, where applicable, for ATT-based Tracking.
- Legitimate interests: to improve the Services, conduct analytics, maintain security, prevent fraud, and support marketing measurement (balanced against your rights).
- Legal obligations: to comply with applicable laws (e.g., accounting and tax obligations for subscription records).

Your rights may include the right to request access, correction, deletion, portability, and restriction or objection to certain processing, and the right to withdraw consent. You also may have the right to lodge a complaint with a supervisory authority.

B) United States state privacy laws (including California)

Depending on where you reside and subject to exceptions, you may have rights to access, delete, and correct certain personal information and to opt out of certain forms of processing.

Sale/sharing for targeted advertising. We do not "sell" personal information in the traditional sense. We may share identifiers and usage information with analytics and attribution partners to measure marketing and app performance. To the extent such sharing could be considered "sharing" under certain state laws, you can limit it by denying ATT permission (where applicable) and by adjusting device privacy settings. You may also contact us to request additional assistance.

Sensitive information. Precise geolocation is considered sensitive under some laws. We collect precise location only if you grant location permission, and we use it for personalization as described above.

14. CHANGES TO THIS PRIVACY POLICY

We may update this Privacy Policy from time to time. If we make changes, we will update the "Last Updated" date above. If changes are material, we will take additional steps as required by law (for example, providing an in-app notice or requesting consent where appropriate). Your continued use of the Services after an update means you accept the updated policy to the extent permitted by law.

CONTACT

HistorySimLLC
Email: support@historysim.com