This Policy explains how IE VOLOSHINSKII MAKSIM handles personal data when you use Fableturn, its cloud gameplay and sharing features, this legal website, or our support service. The iOS app identifier is com.voloshinskii.adventure.
Live gameplay sends your action and relevant story context through OpenRouter to an AI inference provider. Your adventures are private within the service unless you publish a story template. Avoid putting real secrets or sensitive personal information into a story.
1. Who is responsible
The controller for the processing described here is IE VOLOSHINSKII MAKSIM, an individual entrepreneur registered in Georgia.
IE VOLOSHINSKII MAKSIMTax identification number (TIN): 105534636
Ponichala-3 settlement, Block 5, Entrance II, Floor IV, Storeroom
Krtsanisi district, Tbilisi, Georgia
Privacy and support: me@voloshinskii.com
This Policy covers our processing. Apple and other providers may also process information for their own purposes under their notices. Their roles and relevant links are described below. The Terms of Use explain the service agreement; this Policy is not a request for blanket consent.
2. Data we collect and create
| Category | What it includes and where it comes from |
|---|---|
| Account and authentication | Our account identifier, random device credential identifier and secret hash; authentication challenges, token hashes and session records. If you connect Apple, we also store its app-specific sign-in identifier and an encrypted token used to revoke access. The current sign-in flow does not request your name or email address from Apple. |
| Story content | Your world selection or custom premise, title, language, opening, character name, description and goal, actions and drafts; AI-generated narrative, choices, locations, inventory, character details, remembered facts, and a memory summary. Information about real people becomes personal data if you put it in these fields. |
| Gameplay records | Adventure and turn identifiers, timestamps, state revisions, generation request identifiers, request status, saved results, and error codes. These records support saving, recovery, and prevention of duplicate turns. |
| Subscriptions and usage | Your app or RevenueCat identifier, product and transaction information, purchase and renewal status, entitlement expiry, store environment, purchase restoration events, and free or paid turn usage. This comes from your device, Apple, RevenueCat, and our server. |
| Publication and moderation | A submitted template snapshot, publication status and identifier, review decisions and reasons, content reports, associated account and story references, and timestamps. |
| Device and technical information | Network and request information, including IP addresses available to delivery and security providers; app, operating system and SDK information; authentication failures, request timing, and diagnostic errors. Our rate limiting uses hashed identifiers, including an IP-derived hash for some authentication requests. These hashes are pseudonymous, not a guarantee of anonymity. |
| Consent records | Adult self-attestation, the accepted Terms version, permission or withdrawal for AI processing, notice versions and timestamps. We do not collect your date of birth through this self-attestation. |
| Preferences and support | Language, appearance, onboarding state and local draft preferences; your email address, messages, and any attachments or account details you choose to send to support. |
We do not receive your Apple Account password or full payment-card details. The current app does not request access to your contacts, microphone, photo library, or precise location for gameplay. It has no advertising SDK or separate behavioural analytics SDK. Subscription processing still involves the technical and purchase information described here.
3. What is sent to AI services
For a live turn, our backend assembles your action and enough context to continue the story. This can include the selected world or custom setting, opening, character details, language, current location, inventory, known characters and facts, a memory summary, and recent actions and responses. Earlier text may be summarised or omitted to fit the context limit.
The request goes to OpenRouter, which routes it to an inference provider that runs the selected model. The current model is DeepSeek V3.2; the hosting provider can vary between requests. A model’s developer and the company serving a request are not necessarily the same organisation.
Our generation payload does not deliberately include your Apple sign-in identifier, app account identifier, purchase receipts, or payment details. It can nevertheless identify you or someone else if your story text contains identifying details. OpenRouter also receives technical information associated with our server request.
We do not train our own AI models on your stories. Provider handling of inputs and outputs depends on its terms, retention practices, and the route and privacy settings in use. Some providers may retain content or use it for model improvement. The current service does not promise that every request uses a zero-retention or no-training endpoint. See OpenRouter’s provider data policies and data collection explanation.
Responses are returned to you and successful turns are saved with the adventure. Private gameplay is not publicly listed, but it must be processed by our server and the AI providers; it is not end-to-end encrypted in a way that prevents them from reading it. Authorised personnel may access relevant records when necessary to resolve a report, provide support, or investigate misuse.
Do not submit passwords, payment credentials, health records, or private information about other people. You can stop new AI transfers by switching off AI story generation in Profile or by not submitting live actions. Permission is requested separately before generation, and acceptance or withdrawal is recorded with the notice version and a timestamp. Withdrawal does not undo requests already sent. Deleting an adventure removes the service’s active copy as described below; it cannot retrospectively undo a request already processed by a provider. Any separate permission required by applicable law or platform rules must be obtained separately from this Policy.
4. Data on your device
The app stores preferences, story snapshots, drafts, and pending-request details locally so it can display saved content and recover interrupted actions. Authentication credentials are stored in the iOS Keychain. Story files and preferences use the app’s local storage and are subject to iOS device protections; they are not all stored in the Keychain.
A guest profile is created automatically without Apple sign-in. The app generates a random 256-bit device secret and stores it in device-only Keychain; our database stores its hash and a credential identifier. The secret is exchanged for session tokens over an encrypted connection and is not sent to RevenueCat or AI providers. The profile is pseudonymous, not untraceable: it remains linked to its stories, usage and technical records. Connecting Apple is optional and supports recovery on other devices. Without a linked account, loss of the device credential may make recovery impossible.
Signing out or deleting an account on one device clears its account session and associated account story cache, but preferences or local drafts may remain. Copies on other devices or in device backups are governed by those devices and backup settings. Uninstalling the app does not delete a cloud account or necessarily erase every Keychain or backup copy.
5. Apple and RevenueCat
Apple handles App Store payments. RevenueCat validates and manages subscription access on our behalf. The app supplies RevenueCat with a pseudonymous app account identifier for both guest and Apple-linked profiles; the device authentication secret is never used as that identifier. RevenueCat processes purchase and receipt information, entitlement status, and device and app information needed for its service.
Our backend stores entitlement and usage records and limited webhook processing records, such as event identifiers and processing status. We use these to grant access, apply turn limits, handle renewals or revocations, and avoid processing the same event twice.
Apple and RevenueCat can retain purchase records for billing, accounting, fraud prevention, and legal obligations. Deleting your Fableturn account does not automatically delete their transaction history or cancel an Apple subscription. Contact us if you want assistance with a privacy request concerning RevenueCat records; Apple account and purchase requests may need to be made directly to Apple.
Read Apple’s Privacy Policy and RevenueCat’s Privacy Policy. We do not configure advertising-ID collection or advertising integrations in the current app.
7. Purposes and legal grounds
Where applicable law requires a legal basis, we rely on the basis appropriate to the specific processing:
- Providing the requested service: account authentication, story generation and saving, publication you request, purchase verification, and usage allowances are used to perform our agreement with you or take requested steps before it.
- Legitimate interests: proportionate security controls, fraud prevention, error investigation, moderation, support, and establishing or defending claims help us operate a reliable service and protect users. We must weigh these interests against your rights and use less intrusive means where reasonably available.
- Legal obligations: records or disclosures required by applicable tax, accounting, consumer, data-protection, or other law.
- Consent: processing for which separate consent is required, or an optional feature expressly offered on that basis. You may withdraw that consent for future processing without affecting processing that was lawful before withdrawal. Withdrawing permission needed for a feature may prevent that feature from working.
We do not use acceptance of the Terms as consent to advertising, unrelated model training, or every possible use of personal data. Story generation and automated usage checks support entertainment and access management; we do not use the game to make legal or similarly significant decisions about your employment, credit, health, or eligibility for public services. You can ask for human review of an account or moderation dispute.
8. Who receives data
- Cloudflare: hosts the backend, database, and legal website and provides network delivery, security, and operational logging. See its Privacy Policy.
- OpenRouter and the selected inference provider: receive story context and technical request data for live generation, as explained in section 3.
- Apple and RevenueCat: process authentication or purchase information as relevant to their respective services.
- Telegram: delivers the operator's moderation and service notifications as described in section 6.
- Support and operational providers: email delivery and other tools used to respond to your request or maintain the service receive the information needed for that task. Do not send unnecessary sensitive information in support messages.
- Other players or link recipients: receive the template you choose to publish after approval.
- Authorities, advisers, or a lawful successor: may receive limited information where required by law, reasonably necessary to protect rights or address a security incident, or necessary for a legitimate business transfer subject to applicable safeguards and notice requirements.
We do not sell personal data or share it for cross-context behavioural advertising. We do not use your private story as a public advertisement. Service-provider access and the publication you request are different from a sale of your information.
9. International processing
The Operator is in Georgia. Cloud infrastructure, Apple, RevenueCat, OpenRouter, their service providers, and inference hosts may process information in the United States and other countries. Live AI traffic is not guaranteed to stay in your country or in the European Economic Area. Privacy laws and government-access rules differ between countries.
Where the law restricts a transfer, an applicable transfer mechanism and any required additional safeguards are necessary. Depending on the recipient and jurisdiction, this may involve an adequacy decision, contractual safeguards such as standard contractual clauses, or a limited legal exception. This Policy is not itself a transfer safeguard, and using the app does not waive transfer protections.
Contact us to ask about recipients, processing locations, or the safeguards relevant to your data, or to request a copy where you are entitled to one. We may redact information needed to protect another person’s rights or confidential security arrangements.
10. How long data is kept
We use the following retention rules and criteria. A token’s expiry is not necessarily the deletion date of its associated database record.
| Record | Retention approach |
|---|---|
| Cloud adventures and generation records | Kept while the adventure exists so you can continue it and recover saved turns. Deleting the adventure or account removes its associated active database records. |
| Account, sessions and usage | Account-linked records remain while needed to operate the account, enforce allowances, and handle sessions, and are removed from the active database through account deletion. Expired sessions and earlier usage periods are not necessarily erased immediately on expiry. |
| Authentication challenges and rate-limit records | Short-lived control records. Scheduled cleanup removes these after they have been expired for about one day; a failed or delayed cleanup can extend that interval. |
| Publications and reports | Kept for the publication, review, report, or related dispute. Withdrawing a publication removes its publication and review records. Deleting an adventure or account removes the reports linked to it. |
| Moderation notifications | Delivered notification queue records are removed from our database after approximately 30 days. Unsent records remain for delivery retries; removed source templates are not forwarded. Telegram copies follow the moderation need, any applicable preservation requirement, and Telegram's own retention practices. |
| Account deletion awaiting Apple revocation | If Apple token revocation fails, a restricted account record and encrypted revocation token can remain while the service retries. Gameplay access is disabled and associated active gameplay data is removed. The remaining account record is deleted when revocation completes, subject to any legal need to retain specific information. |
| Operational logs and backups | Cloudflare Workers application logs currently have provider retention windows of up to seven days. Other security or incident records may follow a different necessary retention period. D1 recovery history can retain prior database states for up to 30 days under the provider’s plan-dependent window. Recovery history ages out rather than being individually edited for each deletion. |
| Billing and webhook records | Limited webhook event records may remain to prevent duplicate processing. Apple and RevenueCat maintain separate purchase histories under their retention rules. Records required for accounting, tax, fraud prevention, or claims are kept for the period required or justified for those purposes. |
| Support correspondence | Kept to answer the request and, where necessary, document its resolution, address repeat problems, or handle legal obligations and disputes. We assess the need based on the subject and sensitivity rather than promising indefinite retention. |
| Device copies | Remain until cleared by the app, you, or the device’s storage or backup lifecycle. Other players’ copies of published material are not controlled by your account deletion. |
A specific legal preservation requirement or a genuine dispute can justify retaining limited information longer. Such information should be restricted to that purpose. We do not promise immediate erasure from every backup or third-party system. Contact us if you need information about a particular record or deletion request.
11. Your controls and account deletion
- Delete an adventure from the app’s library to remove that adventure and its associated active cloud records.
- Withdraw a published template to disable its share link.
- Use the account deletion action in Profile to request deletion of your account and associated active gameplay data. The app signs you out on the requesting device after a successful deletion request.
- If you cannot use the app, email me@voloshinskii.com for assistance. We will need enough information to verify the account, not your password or verification codes.
Account deletion does not automatically erase RevenueCat’s customer and transaction records. Ask us if your request should also cover information held there on our behalf; we will handle it under applicable law and the provider’s process, including any necessary retention exceptions. Requests about Apple’s independent records should also be directed to Apple.
Cancel subscriptions separately. Use Apple’s subscription controls to stop renewal. Deleting an account or uninstalling the app does not cancel a subscription. Keep a copy of any story you want before deleting it; we do not promise recovery of deliberately deleted content.
12. Privacy rights and complaints
Depending on the law that applies to you, you may have rights to obtain information about processing; access and receive a copy of your data; correct inaccurate data; request deletion or restriction; receive eligible data in a portable format; object to processing based on legitimate interests; and withdraw consent where processing relies on it. These rights are subject to legal conditions and exceptions.
Send requests to me@voloshinskii.com. Describe what you need and the account or story concerned. We may request proportionate verification to protect your data from someone impersonating you. Please do not send a password, one-time code, payment-card number, or identity document unless a specific, necessary verification process has been agreed.
We will respond within the period required by applicable law and explain a refusal or permitted extension. Where the EU or UK GDPR applies, the usual response period is one month; complex or numerous requests can allow an extension with notice. Other laws may require a different or shorter period. We do not charge for ordinary requests unless the applicable law permits it and we explain the basis.
You may complain to the competent data-protection authority or seek a judicial remedy without first contacting us. In Georgia, data-protection supervision is assigned to the State Audit Office of Georgia. If EU or UK law applies, you may also contact the authority competent for your location, including the UK Information Commissioner’s Office. We will not deny a protected right because you made a privacy request or complaint.
Where a US state privacy law applies to our processing and grants you additional rights, such as an authorised-agent request or an appeal, you may exercise them through the same contact address. We do not claim that every jurisdiction’s rules apply to every user or that a statutory exception removes rights that remain applicable.
13. Security
Our safeguards include encrypted network connections, authenticated account access, server-side authorisation, hashed device credentials and session tokens, encryption of the Apple revocation token, request validation, and rate limits. The app uses the iOS Keychain for session credentials. Access to service infrastructure is limited to authorised operators and providers.
These measures reduce risk but cannot guarantee that no loss, unauthorised access, or service error will occur. Story content must be readable by the systems that generate and save it. Keep your device and Apple Account secure, and report suspected unauthorised access promptly. We will assess incidents and make notifications required by applicable law.
14. Adults-only service
Fableturn is intended for people aged 18 or older. We do not knowingly offer accounts to children or seek their personal information. The age restriction is a service rule, not a claim that every user’s age has been technically verified.
If you believe a person under 18 has provided personal data through the service, contact us with enough information to locate the account or content. We will investigate and take appropriate steps to restrict access and remove information, subject to legal requirements. Please do not send additional sensitive information about the child unnecessarily.
15. This website and external links
The legal pages use static HTML and CSS. We have not added advertising, analytics scripts, tracking pixels, or our own cookies to these pages. Cloudflare processes network requests to serve and secure the site and may use security mechanisms, including cookies where needed. Your browser may also cache public files.
Following a link to Apple, RevenueCat, OpenRouter, or another external site brings you under that site’s own practices. Sending email opens your email service; it is not a private form hosted on this website.
16. Changes to this Policy
We may update this Policy to reflect service changes, provider arrangements, or legal requirements. The effective date and version appear at the top. Material changes will receive additional notice where required, and separate consent will be sought where legally necessary. Publishing an update does not by itself authorise an incompatible new use of previously collected information.
This version is published in English. For questions about its meaning or how a request applies to you, contact me@voloshinskii.com.