Overview
This policy explains how the bot handles personal data when people use the service.
Fanfic Swipe operates Fanfic Swipe. The bot is offered through Telegram and generates fanfiction-style text in response to user prompts and selections.
This notice is written to be readable first and still cover the main issues users expect: what is collected, why it is used, who receives it, how long it is kept, and how to ask for deletion, access, or correction.
Data we collect
The bot only works by storing a small set of identity, usage, and content data.
- Telegram account and chat identifiers, plus profile fields Telegram sends such as username, first name, last name, and language code.
- Conversation inputs needed to run the flow, including fandom selections, character selections, trope choices, inline-search suggestions, custom characters, feedback, and other prompt text sent to the bot.
- Generated outputs such as saved fanfics, usage counters, payment-related state for Telegram Stars credits, and subscription metadata if enabled.
- Operational data such as error logs, timestamps, anti-double-submit state, abuse-prevention markers, and webhook security metadata.
How we use the data
Each category maps to an operational need inside the bot.
- To authenticate Telegram webhook traffic, route updates correctly, and keep chat state consistent across interactions.
- To generate stories, return results, save history, and enforce quotas, credits, anti-abuse limits, and recovery from stale in-flight jobs.
- To review catalog suggestions, feedback, and operational issues, and to improve reliability, safety, and moderation over time.
- To meet legal, accounting, fraud-prevention, or platform obligations connected to payments, disputes, or security incidents.
Legal bases for EU and UK users
If EU or UK privacy law applies, the main bases are service delivery, legitimate interests, and legal compliance.
- Performance of a contract or steps requested by the user when the bot needs data to provide story generation, credits, or account features.
- Legitimate interests for service security, abuse prevention, debugging, analytics at an operational level, and review of suggestions or feedback.
- Legal obligations where records must be kept for accounting, tax, payment disputes, fraud prevention, or regulatory requirements.
- Consent where a law specifically requires it for a certain processing activity.
Who receives the data
The bot depends on a few external service layers.
Telegram receives and transmits messages because it is the messaging platform. An OpenAI-compatible model provider receives prompt content and generation context so the bot can produce stories. The service may also use hosting, database, monitoring, and logging vendors that process data on the operator's behalf.
- We do not treat this legal center as a promise that no third party ever touches the data. The service works by using infrastructure providers.
- Any sharing outside those service-provider relationships should happen only when legally required, to prevent fraud or abuse, or when needed to enforce the service terms.
Retention
Retention should be limited to what the product and compliance need.
- Chat-state data is kept while it is useful for the user experience, state restoration, quotas, anti-abuse controls, and saved history.
- Generated stories, suggestions, and feedback may remain in the database until deleted by the operator, the user, or a retention policy.
- Security, payment, and fraud-prevention records may be kept longer where necessary to investigate incidents or meet legal obligations.
- The operator should shorten retention where practical and avoid keeping raw prompts forever without a product or compliance reason.
International transfers and rights
Users may have region-specific rights depending on law and location.
Because messaging, model inference, and hosting vendors may operate in multiple countries, personal data can be processed outside a user's home country. Users may ask for access, correction, deletion, or a copy of their data, subject to legal exceptions and identity verification.
The current request path is [email protected] or @AlisherAm. The bot also exposes /privacy, /terms, and /delete_my_data to make those paths easy to find.
Children
This bot is not designed for young children.
The service is not intended for children under 13 and should not knowingly collect personal data from them. If the bot is made available to minors, the operator should review whether local youth-consent or parental-consent rules apply.