TaleYouFeedback
Draft for reviewNot published. Final policies and release data practices remain under review.

Privacy policy

Draft updated 5 November 2026 · Effective date not set

This policy describes how TaleYou handles information in the app and on this website.

Who operates TaleYou

TaleYou is operated by 刘晨, an individual based in China. In this policy, “we” refers to this operator. For privacy questions or requests, email leovince57@gmail.com.

Information handled by the service

  • Account and authentication: a TaleYou account identifier, the identifier supplied through Sign in with Apple, session and verification records, and a display name you choose. These support sign-in, account security and deletion. Credentials used to revoke Apple authorization during deletion are stored in encrypted form.
  • Reading and library: saved-story references, reading positions, content versions and sync records. These let you keep a library and continue reading across devices. Reading preferences and downloaded content can also be stored locally on your device.
  • Subscriptions: Apple transaction and renewal information, purchase-verification records, the link between a transaction and its TaleYou account, and access status. These verify purchases, restore access and prevent a purchase from being reassigned to another account. Apple handles App Store billing; TaleYou does not request your payment-card details to verify a purchase.
  • Interactive stories: submitted text, relevant story context, choices, saved progress, generated results and operation records. These support generation, review of candidate responses, saved story state and recovery from interrupted requests.
  • Service operation: request identifiers, routes, statuses, timings and security or task records, used for reliability, security and troubleshooting. Sign-in rate limiting uses a hash of the connection address; that record may still relate to a person or connection.
  • Feedback email: your email address, message and any attachments you choose to send for product feedback, reported issues or privacy questions.

Service providers and interactive AI

  • Apple: processes sign-in and App Store purchases. TaleYou exchanges authentication and transaction-verification information with Apple to provide these functions.
  • Alibaba Cloud: provides the current backend’s hosting, database, private object storage, queues and logging infrastructure, which process service data for those functions.
  • DeepSeek: provides the current interactive model workflow. Requests can contain your submitted text, the current story scene, relevant earlier inputs and responses, confirmed story choices and continuation plans. Review and correction requests can also include candidate generated responses. The workflow may make multiple requests; the information sent is not limited to your latest sentence.
  • Google (Gmail): hosts the feedback address. If you send email, the message and attachments you choose to send are processed through email services. The website’s email links do not automatically attach diagnostics or story content.

Interactive requests send content to an AI provider for processing. You can use ordinary reading without submitting an interactive request. Avoid including personal or sensitive information in story input. Choosing not to start another request does not cancel a request already being processed or delete information sent earlier.

Before personal data is shared with third-party AI, the released app must explain the sharing and obtain any required explicit permission. This policy does not obtain that permission; the in-app flow is still being prepared.

Providers have their own retention and deletion practices. TaleYou’s cleanup of a local or server record does not by itself remove a provider’s copy. The final API-specific data-use conditions remain under review; no zero-retention or no-training guarantee has been verified for the current endpoint.

Provider information: Apple privacy, Alibaba Cloud privacy, DeepSeek API terms, DeepSeek privacy and Google privacy. These documents do not replace TaleYou’s explanation of its own processing.

International processing

The operator is based in China. Service providers may process information outside the country where you live. Hosting and AI processing can take place in different locations; the final locations and any required transfer safeguards must be confirmed for the released service.

Protecting information

We use authenticated account access, account-specific access checks, hashed session secrets and encryption for certain provider credentials and temporary interactive content. Device sign-in credentials use the iOS Keychain.

Retention and deletion

  • Account and reading data: support your active account and sync. Once account deletion is accepted, the account is disabled, its sessions are revoked, and its display name and account-linked library, reading progress and interactive records are cleared from the live database. Identity and credential cleanup continues in the background. Limited account-deletion and guest-transfer ownership records remain to prevent old requests or transferred reading history from being applied to a new account.
  • Temporary interactive content: temporary uploads, results and review copies have expiry and cleanup rules. Saved progress is handled separately. Requests whose outcome is still being resolved may need to be retained for recovery. An expiry time does not mean that every copy, including backups, has been physically removed.
  • Purchases: transaction-ownership and verification records remain separate from account deletion so an old purchase is not reassigned to a new account. Some original purchase proofs are cleared when verification finishes. Original signed store notifications currently remain stored in encrypted form; their retention and cleanup schedule still needs to be finalized. Account deletion does not automatically erase all purchase records or cancel Apple billing.
  • Other records: technical logs support troubleshooting and security. Feedback emails and attachments support the issue or request you contact us about. These records, backups and provider-held copies have separate retention and deletion rules; unnecessary information should be removed when its purpose ends, subject to applicable retention requirements.

A session or temporary result expiring is different from deleting the stored record. Final retention periods and physical-deletion windows for the categories above have not been approved and must be completed before this policy takes effect.

This website

These draft pages do not include a feedback form, advertising or analytics scripts, or code that sets cookies. A public hosting service can still process connection and access information to serve the pages. Its actual logging practices and retention will be included before publication.

Your choices

You can edit your display name, manage local reading data and initiate account deletion in the app. Signing out or clearing a download does not delete your cloud account. Account deletion has no undo period; a later registration does not restore deleted history or automatically inherit old purchases. See Data & account choices for the steps.

For questions or requests to access, correct or delete information, contact leovince57@gmail.com. We may need to verify that the request concerns your account before disclosing or changing account information. Use the in-app flow to initiate account deletion; an ordinary feedback email does not start that flow.

Depending on applicable law, you may also request a copy of your personal information, restrict or object to processing, withdraw consent, or raise a concern with the relevant privacy regulator. Withdrawing consent applies to future processing and does not automatically erase information already processed. Contact the same email address to discuss a request and the choices available for your situation.

Changes and contact

We will update the date on this page when the policy changes. Material changes will be explained in the app or in App Store update notes. If a change requires new consent, that consent must be obtained before the related processing starts. The operator and privacy contact are identified at the start of this policy.