MyFantasy Privacy Policy
How data is handled when you use the MyFantasy website, PWA and Telegram bot.
Revision dated 20 October 2026
1. General provisions
1.1.This Policy describes the handling and protection of MyFantasy users' information, including use of the myfantasy.fans website, PWA and Telegram bot (the Service).
1.2.You should read this Policy when using the Service. If these data-handling terms do not suit you, stop using the Service and, where necessary, contact Support about your data.
2. Information that is processed
2.1.Depending on the features you use, the Service processes:
- Account details: login name, password hash, email if provided, and Telegram ID, username and name when you use or link Telegram.
- Your adult-age confirmation and selected interface language.
- Requests, characters, plots, settings, saved preferences and exclusions, continuation directions, generated stories and saved chapter versions.
- Technical information: IP address and browser-session data, generation time, model, cost and status, errors, usage events and traffic sources.
- Order information: account and payment identifiers, plan, amount, currency, payment status and Premium expiry.
2.2.The Service does not require a passport, document photograph or date of birth for its ordinary age confirmation. Email is optional where the interface supports registration with a login name.
2.3.Payment details are entered with the payment provider, not in the MyFantasy sign-in form. The Service does not ask for a full card number, card security code or banking password to create an account.
3. How information is used
3.1.Information is used for sign-in and account linking, age confirmation, creating and saving stories, tracking allowances and Premium, processing payments, support, moderation, abuse prevention, technical diagnostics and quality improvements.
3.2.The admin interface provides authorized operational access to accounts, saved requests and full story texts. This access is used for support, investigating errors and violations, maintenance and quality checks. The admin interface is not public, and the Service does not promise complete anonymity from its Administration.
3.3.Yandex Metrica may be used for visit statistics and technical events. Request and story texts are not included in external analytics-goal parameters; traffic statistics may contain technical identifiers and traffic-source parameters.
4. Providers and data transfers
4.1.Requests, character descriptions, preferences and story context needed for generation are sent to OpenRouter and the relevant AI providers. The amount of context depends on the requested generation or continuation. Those providers have their own data-processing and retention terms.
4.2.When Telegram is used, messages and identifiers are also processed by Telegram. For payments, Platega or another payment provider shown in the interface receives necessary order and payer-identification information. When analytics is enabled, its provider also processes technical data.
4.3.The Administration may transfer necessary information to provide the service, with your consent, or where required by applicable law. Stories are not published publicly by default.
5. Story privacy
5.1.Completed stories are saved to the account owner's library, not a shared public feed. Website access is checked against the owner's session; operational admin access is described in section 3.
5.2.The Service does not use requests or stories to train its own AI models. This is not a guarantee that AI providers do not process or retain data: their terms apply to information sent to them.
5.3.Do not enter real third-party personal data, documents, passwords, banking secrets or other information you do not want to share with the Service or the AI provider being used.
6. Retention and security
6.1.Saved stories and preferences are retained to operate your account and library. Unregistered previews are temporary: their retention period, normally 7 days, is shown in the interface. Deleting a browser session may remove access to an unsaved guest result.
6.2.Cookies are used for sessions, age confirmation and language. Drafts, interface preferences and information needed to resume your current action may be stored in the browser. Installing the PWA does not make generation or stories available without an internet connection.
6.3.The Administration takes reasonable protective measures, including access checks and storing passwords as hashes. Absolute internet security, complete anonymity and data availability during every possible failure are not guaranteed.
6.4.Questions about accessing or deleting data should be sent to Support. You may need to verify account ownership. Certain payment, technical and security records may be retained as necessary to meet obligations, resolve disputes and comply with legal requirements.
7. Age requirements
7.1.The Service is for adults aged 18 or older only. Age is confirmed in the website or bot interface before accessing generation; confirmation information may be saved in the session and account.
8. Responsible use
8.1.You choose what information to enter and should take into account the necessary transfers to providers. Do not give other people access to your account. Contact Support if you notice an access or data-disclosure problem.
9. Policy updates
9.1.The current dated revision of this Policy is published on the website. Continued use of the Service after changes means acceptance of the updated terms to the extent permitted by applicable law.
10. Contact
10.1.For questions about data, privacy or access, contact @aifantasy_support on Telegram or use the feedback button available in the bot. Do not include your password, banking secrets or unnecessary personal information in your message.