TaleActive Privacy Policy

The short version

• Your full game save, journal notes, raw activity evidence and camera analysis stay on your device unless TaleActive support requests a Full Support Bundle and you choose to send it. Broad progress signals are sent only through optional usage sharing or a Support Snapshot you deliberately submit.
• TaleActive uses activity and motion sensors to make real-world activity affect the game.
• Camera access is used only when you deliberately start Capture Exercise. Images are analysed on your device, are not saved by TaleActive and are not uploaded. TaleActive does not record audio.
• On a physical device, optional usage information is sent only if you enable it. You can turn it off at any time.
• Support in Help lets you deliberately submit a ticket, receive replies and attach files. A Support Snapshot is included by default and can be turned off. Support may later request an updated Support Snapshot or a Full Support Bundle; neither is sent until you choose to send it.
• The website collects information when you submit a form or use the browser demo. Each form explains what it asks for before submission.
• TaleActive does not sell personal information, serve behavioural advertising or use advertising identifiers.

Information processed on your device

TaleActive processes the following locally to provide the game:

• step-counter and step-detector readings used to recognise walking;
• motion, linear-acceleration and air-pressure readings used to recognise stairs and reduce false rewards;
• Android activity-recognition results used as movement context;
• camera frames and derived pose or movement analysis while Capture Exercise is running;
• derived activity events, activity totals, Challenge progress, Momentum and Reserves;
• your game save, story position, choices, quests, inventory, settings and journal notes; and
• local recovery checkpoints and backups used to protect the save.

This information is stored in TaleActive's private app storage. Android cloud backup and device-to-device transfer are disabled. Clearing TaleActive's app data or uninstalling the app removes this local information, including local recovery backups.

Camera frames are processed only while Capture Exercise is active. TaleActive does not save or upload those frames and does not record microphone audio.

Optional Android usage information

On a physical device, TaleActive sends usage information only after you enable Share optional usage information. If sharing is off, the app does not collect or upload these events. You can change the choice from Help at any time.

When enabled, events may include:

• a random TaleActive Installation ID and temporary session ID;
• TaleActive, build, story-content, Android and device versions;
• language or locale, time-zone offset, display size, density and font scale;
• available sensors and app features;
• screens and mechanics used, audio-control settings and broad story progress;
• fictional scene, quest, Challenge, choice, inventory and map identifiers;
• aggregated activity totals and derived classifications, but not raw sensor readings;
• diagnostic and performance information; and
• limited crash details such as exception type, shortened message, thread name and stack trace.

Our hosting provider processes the network connection, including the IP address needed to receive the request. For abuse investigation, TaleActive retains the source IP address and the network number and organisation supplied by Cloudflare for up to 30 days. An IP address identifies a network exit, not a particular phone or person: it may change as a phone moves between networks or leases, and several installations may share one public address. TaleActive also stores an approximate country and data-centre code. TaleActive does not request Android location permission or collect precise location.

Normal collection records compact events rather than repeatedly uploading the full game state. If a problem needs closer investigation, TaleActive may temporarily enable fuller game-state snapshots for a limited period, either for a particular Installation ID or for affected app versions. This switch cannot collect anything outside the categories above, automatically expires within seven days, and still requires usage sharing to be enabled on a physical device.

Usage events do not include your name, email address, account details, save file, journal text, camera images, photos, audio or raw sensor stream. Turning sharing off stops future collection; it does not automatically delete events already received. You may request deletion as described below.

Information submitted through the website

The website provides contact, release-notification and Android beta-application forms. When you deliberately submit one, we receive:

• Contact form: any name, email address, subject, message or explanation of how you heard about TaleActive that you choose to provide, plus your random TaleActive Installation ID if you deliberately carry it over from the app.
• Release notification: your email address and how you heard about TaleActive.
• Android beta application: your name if you choose to provide it, email address, time zone, phone model, phone-carry habits, broad activity and exercise ranges, story-game experience, testing availability and preferences, referral source, and the answers or comments you write.

The beta form uses broad activity ranges to select a varied test group and assess whether TaleActive works fairly for people with different routines. Please do not include medical diagnoses or other sensitive information.

Forms use Cloudflare Turnstile and rate limiting to deter abuse. Cloudflare processes connection information, including the IP address needed to assess and deliver a request. TaleActive stores short-lived keyed hashes derived from email and network addresses for rate limiting rather than storing those addresses in abuse records. A beta application retains a keyed network hash with the application for abuse investigation. Submissions may create private notification emails so they can be reviewed.

The release-notification list is used for one release email, not a newsletter. A duplicate signup does not create another entry or reveal whether an address is already listed.

Browser demo usage information

The playable browser demo sends usage events so we can understand whether it works and where players become stuck. Events may include:

• a random ID stored in that browser and a temporary session ID;
• demo version, fictional scenes and locations, choices and interactions;
• completion and interaction timing;
• viewport size, local hour and time-zone offset;
• the browser's standard user-agent string; and
• an approximate country code derived from the connection.

Browser demo events do not include your name, email address, precise location, Android game save, sensor readings or activity history. TaleActive does not store the full IP address in the browser-demo usage table.

Support tickets, feedback, and bug reports

TaleActive also checks for developer updates and Beta Feedback questions using a random Installation ID and private inbox credential. These checks send essential app, build and content versions and test-build status, independently of optional usage sharing. They send no activity or game-state diagnostics. Updates expire from the Journal; private ticket conversations continue after an invitation expires. Expired developer messages leave server history after six months. Inbox credentials remain bound to their original installation to prevent an old address being reassigned.

Choosing Support / Feedback in Help opens TaleActive's in-app support system. You can submit a problem, question, or other feedback, optionally provide a name, read replies from TaleActive support, reply in the same conversation, and deliberately attach additional files through Android's file picker. A submitted name is remembered in private app storage and prefilled for the next ticket; submitting the field blank removes it. No TaleActive account is required. The app stores a secret ticket-access token in its private storage so only that installation and authorised support staff can read the conversation.

When you submit a ticket, Include support snapshot is enabled by default. The app shows the exact screenshots currently available before you submit. A Support Snapshot contains app and device details, relevant permission and sensor availability, activity-tracking status and aggregate totals, current fictional scene and visible choices, inventory quantities, Challenge progress, map state, Quest progress, and the available main-screen screenshots. It does not contain the full saved game or player-written Journal notes. Support can request an updated Support Snapshot in the conversation; it is sent only after you press Send Updated Support Snapshot.

Support can separately request a Full Support Bundle. It contains the complete portable saved game, checkpoints, player-written Journal notes, story progress, inventory, map pins, Quests, Challenges, retained activity history and raw activity evidence, game settings, training progress, diagnostic records, and the screenshots shown before sending. It excludes ticket access tokens, paired-device credentials, telemetry identifiers, Android encryption keys and camera images. The Full Support Bundle is sent only after you press Send Full Support Bundle and confirm. If you turn off the initial Support Snapshot, only the optional name, ticket message, random Installation and session identifiers, essential app version information, and files you deliberately provide are sent. Sending either bundle does not enable ongoing usage sharing.

Android permissions

Depending on your Android version and the features you use, TaleActive may request:

• Physical activity: to count walking and receive movement context;
• Notifications: to keep background activity observation visible and show relevant activity notices; and
• Camera: only when you choose Capture Exercise.

A foreground health service lets Android continue activity observation while the app is closed or the screen is off. Android displays a persistent notification while it is active. You can manage permissions in Android Settings. Camera permission is not required for ordinary walking or automatic stair observation.

Connected companion devices

If you use a supported companion device such as Even G2 glasses, TaleActive may display selected game state, story text, maps, inventory, choices and activity summaries on it. The Android bridge is restricted to the phone's local loopback connection. TaleActive does not upload your save or raw sensor data for this feature. The companion platform and its software may have their own privacy terms.

How we use information sent to us

We use submitted information to operate requested website services; assess beta applications; understand compatibility, crashes, defects and performance; assess game progression and broad play journeys; investigate feedback; and protect the service from abuse.

We do not use it for targeted advertising, credit, insurance, employment or medical decisions or diagnosis.

Sharing and service providers

TaleActive does not sell or rent information and does not share it for behavioural advertising.

We use infrastructure providers to host the website, APIs, protected database, anti-spam checks and notification email. They process information to provide and secure those services on our behalf. We may also disclose information where reasonably necessary to comply with law, protect users or the service, or establish or defend legal rights.

Retention

• Information stored only on your device remains there until you delete it, clear the app's data or uninstall TaleActive.
• App and browser-demo usage events are retained for no longer than six months after receipt, unless a shorter period is sufficient or a specific event must be kept longer for an active security or reliability investigation.
• Source IP addresses and Cloudflare-provided network ownership details associated with Android usage requests are retained for no longer than 30 days and used only for abuse investigation and service protection.
• Support tickets, messages, diagnostic bundles, attachments, contact messages, beta applications, release-notification signups and private notification copies are retained for no longer than six months after their latest activity, unless still needed to resolve the request, administer an active beta place, send the requested release notice, investigate an active issue, or meet a legal obligation. We delete them sooner when practical.
• Keyed contact-form and release-signup abuse records stored by TaleActive are deleted after seven days. Infrastructure providers may apply their own short operational retention periods to security records.
• Irreversibly aggregated or de-identified statistics that can no longer be linked to an Installation ID may be retained longer.

TaleActive runs an automatic deletion schedule for server-held usage events and website submissions. Private notification emails are managed under the same six-month limit.

Your choices and deletion requests

You can leave optional usage sharing disabled or turn it off from Help; submit a support ticket without its diagnostic bundle; avoid attaching files; refuse or revoke Android permissions; avoid submitting support, feedback, or website forms; avoid the browser demo; clear local app data; or uninstall TaleActive.

To request access to, correction of, or deletion of server-held information, contact us. Include the random Installation ID shown in the app if your request concerns app usage or feedback. We may ask for reasonable information to verify a request.

Deleting or resetting the app changes or removes its local Installation ID but does not identify information previously sent under the old ID. Copy the ID before clearing the app if you want us to locate that information. Where applicable law gives you additional rights, including restriction, objection, portability or withdrawal of consent, you may use the same contact page.

Security and international processing

TaleActive uses Android private app storage, HTTPS, restricted administrative access, service-side validation and rate limiting. No system can guarantee absolute security, but we limit collection and access to what is needed.

Infrastructure providers may process information in countries other than the one where you live. Where required, we use protections available through those providers and applicable law.

Children

TaleActive does not ask for a player's name or age through the game. The website forms are not intended for children to submit without appropriate permission. If you believe a child has submitted personal information, contact us so it can be removed.

Changes to this policy

We may update this policy when TaleActive's features or data practices change. We will update the date above and provide any additional notice or consent required by law before materially different processing begins.

Contact

Privacy questions, rights requests and deletion requests can be submitted through taleactive.com/contact.