Privacy Policy
Unbound: AI Life Sim | Effective August 30, 2026
This policy explains how Mark Richard Daoust ("we", "us", or "our") processes information when you use Unbound: AI Life Sim, also known as Unbound: AI Text RPG (the "App"). It covers single-player and multiplayer gameplay. Contact us at contact@jamesd.tech with privacy questions.
1. Information we collect
- Account identifiers. The App creates an anonymous Firebase account to associate your games and entitlements with an account. Registration does not require your real name, email address, or phone number. This is a pseudonymous account, not a guarantee of complete anonymity: its identifier can be linked to gameplay and service records.
- Gameplay input and saved games. We process the text, actions, choices, and character information you submit, together with generated stories, timelines, statistics, relationships, achievements, in-game finances, and other data needed to continue your game.
- Multiplayer information. We store your chosen display name, account identifier, room identifier and invitation code, room membership, host status, generated character, actions, readiness to age up, activity timestamps, shared-world history, individual story results, and game results or recaps. A generated character name is separate from the display name you choose.
- Purchase and reward records. We process product and transaction identifiers, verification status, entitlements, consumable balances, usage records, and reward eligibility. Apple or Google Play processes store payments. We do not receive your payment-card details.
- Referral information. We store referral codes, associated account identifiers, redemption status, and rewards to operate referrals and prevent duplicate or fraudulent rewards.
- Reports, feedback, and surveys. When you report content, send feedback, or respond to a player survey, we may store your message or answers, category or reason, relevant game or screen context, account identifier, and submission time. Survey records may also include dismissal status and completion time. If you email us, we receive your email address and the information in your message.
- Advertising data. Google AdMob and its advertising partners may process device and advertising identifiers, consent choices, technical information, and ad interactions to serve, measure, personalize where permitted, and protect advertisements against fraud. We also process reward-verification information when you watch an ad for an in-game benefit.
- Usage and analytics. Firebase Analytics collects app and device information and interactions such as app launches, screens viewed, tutorial progress, gameplay events, store activity, advertising rewards, survey participation, and session activity. These records may be associated with account, app-instance, or device identifiers.
- Technical and operational data. We and our service providers process information such as request timestamps, network and device information, errors, model and token usage, costs, performance, and security or abuse indicators to operate the service.
2. How we use information
We use this information to:
- Generate stories, save games, and maintain character and world state.
- Operate multiplayer rooms, coordinate player actions, and provide game results.
- Verify purchases and deliver entitlements, energy, and eligible rewards.
- Operate referrals, surveys, feedback, advertising, and support features.
- Enforce usage limits, prevent abuse and fraud, and protect the service.
- Review reported content, investigate problems, and improve content safeguards.
- Understand how features are used and improve reliability and player experience.
- Respond to privacy requests and meet applicable legal obligations.
3. AI processing
The App uses OpenRouter to access third-party AI models. Our backend sends gameplay input and relevant context to OpenRouter and the model provider selected for a request. The provider or model may change based on routing, availability, performance, safety, or other service considerations.
Context can include character details, relationships, statistics, finances, prior events, and story summaries. In multiplayer, it can also include display names, pseudonymous account identifiers, other players' fictional character states, and shared actions or history. Another player's action may require processing shared information about your character even when you are not currently taking an action.
We do not intentionally include payment-card information, purchase transaction records, advertising identifiers, or support and feedback submissions in normal story-generation prompts. However, personal information you put in a display name or gameplay text can be included in a prompt. Do not submit passwords, contact details, precise real-world locations, or other sensitive personal information through gameplay.
OpenRouter and model providers have their own privacy and retention practices. Prompt or output storage and use for service improvement or training depend on the provider and applicable account and routing settings. We do not promise that every request uses zero-retention or no-training processing. Technical request metadata may also be processed. See OpenRouter's Privacy Policy and its provider information.
AI output is generated automatically and is not individually reviewed before display. It can be inaccurate, inappropriate, or inconsistent. Generated statements about a character are fictional and should not be treated as facts about the person controlling that character.
4. What other players can access
Multiplayer is a shared experience. Other room participants can receive your display name, account identifier, generated character details, character statistics, finances, relationships, fictional location, readiness status, and game outcomes. Some story results are initially presented from an individual character's perspective. At the end of a game, the room recap can reveal submitted actions and each player's story results.
A limited in-game point of view is a gameplay feature, not a promise that your character data or actions are confidential. There is no dedicated room-chat feature in this version, but display names, actions, and their effects can still communicate information to other participants.
Anyone who receives a room code may be able to join while the room is open to new players. Share codes only with people you intend to invite. Other players may capture or share content they can access, including recaps or screenshots. We cannot control copies they make outside the App.
5. Service providers and other disclosures
- OpenRouter and AI model providers: process prompts, context, outputs, and request metadata for AI generation as described above.
- Google Firebase: provides authentication, database storage, backend functions, and analytics. See Firebase privacy information and Google's Privacy Policy.
- Google AdMob and advertising partners: serve and measure advertisements and verify eligible rewards. See Google advertising information.
- Apple and Google Play: process app distribution, purchases, restoration, and store review prompts. See Apple's Privacy Policy and Google's Privacy Policy.
We may disclose information when required by law or reasonably necessary to respond to legal process, protect rights and safety, prevent fraud, or investigate abuse. We do not sell account or gameplay information for money. Advertising-related disclosures may be treated as a sale, sharing, or targeted advertising under some privacy laws, depending on the processing involved.
6. Advertising and privacy choices
Rewarded ads are optional. Where applicable, Google's User Messaging Platform presents advertising-consent choices. Available device and operating-system controls may also let you restrict tracking or advertising identifiers. These controls do not necessarily disable all analytics or all information needed to operate the App.
Use the privacy controls available in your version of the App and your device settings, or contact us to ask about applicable privacy choices. Declining an optional feature, such as a survey, referral, or rewarded ad, avoids submitting information specifically requested for that feature.
7. Retention and account deletion
Retention depends on the type of record, whether it is needed to provide your game or a shared room, unresolved support or safety issues, fraud prevention, applicable legal requirements, and service-provider settings. We do not promise a single retention period for every category.
Delete My Data on the main menu deletes your Firebase account and the single-player saved games, associated timelines and rewind records, account entitlements, feedback, survey responses, and other records handled by that deletion process. Deletion may be irreversible and may remove access to balances or progress associated with the anonymous account.
Current multiplayer limitation: the in-app deletion process does not yet automatically erase multiplayer room records, including player entries, actions, and shared history. These records may remain on our backend after account deletion. Contact contact@jamesd.tech to request deletion of remaining information. This limitation does not waive any privacy rights you have under applicable law.
Reported content and associated moderation records may be retained for safety review, dispute resolution, or legal compliance where permitted. The deletion process removes account links from certain redeemed purchase and ad-reward records while retaining records used to prevent duplicate redemption. Deleting an authentication account alone does not necessarily make every retained record anonymous.
Deletion does not automatically erase data held independently by Apple, Google, OpenRouter, model providers, or other players. Provider records may follow separate retention rules; contact us about requests affecting information we sent to our providers. Account deletion does not issue refunds or cancel store subscriptions.
8. International processing
We and our providers may process information outside your country, including in countries with different privacy protections. The location can depend on the infrastructure and AI provider used. Where applicable law requires a transfer safeguard, an appropriate transfer mechanism is required. Contact us for information about the safeguards applicable to your data.
9. Your privacy rights
Depending on your location and applicable law, you may have rights to access, correct, delete, or obtain a copy of your information; restrict or object to certain processing; withdraw consent; or opt out of certain advertising-related uses. Some requests are subject to legal exceptions and proportionate identity verification. We do not require more identifying information than reasonably needed to handle a request.
Send requests to contact@jamesd.tech. Because accounts are pseudonymous, include enough account or room context for us to locate the records, but never send a password. You may also complain to the privacy regulator responsible for your location.
For processing subject to EEA or UK data-protection law, the relevant basis depends on the purpose: providing requested gameplay and purchases may be necessary to perform our contract with you; security, fraud prevention, support, and service improvement may rely on legitimate interests where these are not overridden by your rights; certain processing is necessary to meet legal obligations; and we rely on consent where it is required, including for applicable advertising or device access. Consent can be withdrawn without affecting the lawfulness of processing before withdrawal. These rights and bases depend on the processing and jurisdiction involved.
10. Children's privacy
The App is not intended for children under 13. The applicable store age rating or local law may require a higher age. A fictional character's age does not determine whether a real person is eligible to use the App. We do not knowingly collect personal information from children under 13. If you believe a child under 13 has provided such information, contact us so we can investigate and take appropriate steps to delete it.
11. Security
We use safeguards such as authenticated backend requests and restricted database access to protect information. No service or transmission method is completely secure. Multiplayer room codes and pseudonymous display names are not substitutes for protecting personal information.
12. Changes and contact
We may update this policy as the App or its data practices change. We update the effective date and provide additional notice or obtain consent where required. For privacy questions or requests, contact Mark Richard Daoust at contact@jamesd.tech.