Privacy Policy — ChronaLife

Effective date: May 25, 2026
Last updated: May 25, 2026

This Privacy Policy describes how Andrew Wade ("we", "us", or "our") collects, uses, discloses, and protects information in connection with ChronaLife—our life-simulation game and related websites, mobile applications, and online services (collectively, the "Service").

By using the Service, you agree to this Privacy Policy. If you do not agree, do not use the Service.

1. Who we are

Item	Detail
Product	ChronaLife
Operator	Andrew Wade
Contact	[email protected]
Website	https://playchrona.app

2. Scope

This policy applies to:

Our native apps on Apple iOS and Google Android;
Our website at playchrona.app;
Backend and sync features provided through our servers and service providers.

It does not govern third-party sites or services that we link to or that you use outside the Service (for example, your email provider or app store account).

3. Information we collect

We collect information in the following categories. Exact fields depend on which features you enable and how you use the Service.

3.1 Account and authentication

When you use the Service, we support:

Anonymous play with an internal player identifier and optional device identifier, plus session tokens stored securely on our servers to keep you signed in;
Email sign-in with one-time codes (OTP) sent to the address you provide. We store a verified email on your player record when you complete verification.

We link your player account to your verified email when you complete email sign-in, to enable cloud backup, sync, account recovery, and support.

App purchase: ChronaLife is sold as a one-time paid app (currently USD $1.99, or local equivalent) through the Apple App Store or Google Play. We do not receive your full payment card number. The platform may share with us purchase-related metadata (for example, that a purchase occurred, product identifier, and general transaction status) to confirm you own the app. We do not offer in-app subscriptions.

3.2 Gameplay, saves, and sync state

To operate cloud sync, backups, leaderboards, and related features we store game-derived data on our backend, including but not limited to:

Identifiers: player account, life, save slot, and session identifiers where used;
Character and world snapshots (for example, name, location settings, difficulty settings);
Economy summaries for leaderboard or analytics (for example, net worth, cash, debt, portfolio values, character display name, country);
Life events, asset sync data, lottery participation, fame/social-sim metadata, and other simulation records;
Operational telemetry tied to gameplay systems, separate from usage analytics unless combined in support tickets.

Local play: Much of the simulation runs on your device. Save data may be stored locally in addition to any cloud copy.

3.3 Cloud save backups

If you sign in with a verified email, you may upload cloud save backups to our servers. This is included with your one-time app purchase—no separate subscription is required.

Backups are stored as compressed, encrypted payloads with integrity checks. At the application layer these blobs are opaque, but they are still personal data because they can contain your in-game choices, character names, and any text you entered in-game.

Cloud backup requires an active authenticated session and a compatible app version. Sign out clears your session on the device but does not by itself delete cloud backups. Delete account (in Settings → Account) permanently removes your verified email, cloud backups, and linked server-side records as described in our Terms of Service.

3.4 Push notifications

If you opt in on a supported device, we may collect and store a push token associated with your player account to deliver notifications (for example, lottery or activity reminders).

3.5 Bug reports and support

When you submit an in-app bug report, we may collect:

Title, description, category, severity, reproduction steps;
Route/screen name, app version, platform, OS version, device model;
Optional screenshot and optional debug snapshot (trimmed game-state excerpts designed not to include auth tokens—but may still include character, finances, career, and other simulation summaries).

3.6 Usage analytics

The Service may collect usage analytics such as screen views and custom in-app events. Events may include:

Route/screen names;
App version, platform, and build metadata;
A session identifier;
Optional linked gameplay identifiers (such as life or save slot id) when available;
Timestamps.

Analytics is controlled by an in-app Usage Analytics toggle in Settings (on by default unless you turn it off). Analytics is used to understand product usage and improve stability—not to sell your personal information.

3.7 Automatic / technical data

We and our service providers may process:

IP address, approximate location derived from IP, user-agent, timestamps;
Device type, OS, app version;
Diagnostic logs on servers.

If we add additional analytics or crash-reporting services, we will update this policy and, where required, provide consent or settings controls.

4. How we use information

We use information to:

Provide, maintain, and improve the Service;
Authenticate users, operate cloud save backup, sync, and account deletion, and prevent abuse;
Confirm app ownership where the platform provides purchase metadata;
Sync game state, run server-mirrored logic where applicable, and restore backups;
Operate leaderboards and server-backed features (for example, shared lottery draws) where you use them;
Send transactional emails (sign-in codes) and optional push notifications you have enabled;
Collect usage analytics when you have not disabled the in-app toggle;
Debug, secure, and operate our infrastructure;
Comply with law and respond to lawful requests;
Communicate with you about the Service.

We do not sell your personal information to data brokers. We do use service providers (see Section 7) who process data on our behalf.

5. Legal bases (EEA/UK, if applicable)

If GDPR/UK GDPR applies, we rely on one or more of:

Contract (providing the Service you request);
Legitimate interests (security, fraud prevention, product improvement, internal analytics), balanced against your rights;
Consent (for example, optional push notifications);
Legal obligation.

6. Sharing and disclosure

We may share information with:

Service providers listed in Section 7, under contractual safeguards;
App stores (Apple, Google) for distribution, payments, and refund policies they impose;
Authorities when required by law or to protect rights, safety, and security;
Corporate transactions (merger, acquisition, restructuring), with notice where required.

We may disclose aggregated or de-identified information.

7. Service providers

We use third-party providers to operate the Service, including for backend hosting, authentication, transactional email, app store distribution, and push notification delivery. These providers process data on our behalf under contractual safeguards and are subject to their own privacy policies.

8. International transfers

If you access the Service from outside the country where our servers or service providers are located, your information may be transferred internationally. Where required, we implement appropriate safeguards (for example, Standard Contractual Clauses).

9. Retention

We retain information as long as needed to provide the Service, comply with law, resolve disputes, and enforce agreements. Examples:

Account data: until you delete your account or we delete inactive accounts per policy;
Cloud saves: until you delete them, delete your account, or we remove them per storage policy;
Analytics events: for a limited operational window, unless a longer period is needed for security or legal reasons;
Bug reports: for a defined support window unless a longer period is needed for security or legal reasons;
Session tokens: rotated or purged per security policy;
OTP codes: short-lived; verification codes expire and are not retained as plaintext secrets.

10. Security

We use reasonable administrative, technical, and organizational measures (encryption in transit, access controls, hashed session tokens, integrity checks on uploads) appropriate to the risk. No method of storage or transmission is 100% secure.

11. Your rights and choices

Depending on jurisdiction, you may have rights to access, correct, delete, port, restrict, or object to processing of personal data, and to withdraw consent where processing is consent-based.

Account / email: use in-app Settings → Account to sign in, sign out, or delete your account (permanent deletion of verified email, cloud backups, and linked server data when signed in with email).
Analytics: toggle Usage Analytics in Settings where offered.
Push: disable in system settings or revoke permission in-app where offered.
Requests: email [email protected] with sufficient detail for us to verify you.

California residents (CPRA): you may have rights to know, delete, and correct personal information, and to limit use of sensitive personal information if applicable. We do not sell or share personal information for cross-context behavioral advertising as defined in CPRA.

12. Children

The Service is not directed at children under 13 (or the age required in your jurisdiction). We do not knowingly collect personal information from children. If you believe we have, contact us and we will delete it.

13. Changes

We may update this Privacy Policy. We will post the new version with a revised Effective date and, where required, provide additional notice. Continued use after the effective date constitutes acceptance unless law requires explicit consent.

14. Contact

Andrew Wade
Dallas, Texas
United States
Email: [email protected]