Privacy policy

1. Scope This policy covers personal data collected, processed, used and protected when ResonTales provides its app and official website services. Data collected independently by third-party websites or services is governed by their own privacy policies.

2. Operator and age requirements ResonTales is operated by the ResonTales team. The app is currently available for download on the App Store and Google Play in Taiwan. Any future expansion to additional regions will be announced separately. Users must be at least 13. Where local law requires parental or legal guardian consent, that consent must be obtained first. The parental consent process is still being developed; do not use the service before obtaining required consent. Children under 13 may not use the service. Contact privacy@resontales.com with related questions.

3. Data collected and purposes ResonTales processes your account ID, email, nickname, language, stories and visibility settings, recommendation data, preferences to stop recommending specific stories, which similar stories you have opened, notification preferences, push tokens, device time zone, and policy acceptance versions and times to provide accounts, cloud storage, recommendations and notifications. The email address obtained during sign-in is used only for account sign-in and identification, so you can access stories still stored in the cloud by signing in to the same account on another device. It is not used as input for marketing, similar-story recommendations or AI analysis. We also retain daily combined public-story save counts (new stories and updates share the count; private saves are excluded) to enforce account quotas, and process contact details and messages you send to respond to inquiries or complaints. Without data required for sign-in or story storage, the corresponding functions may be unavailable. Avoid including unnecessary identification numbers, addresses, medical information or other people’s personal data in stories or correspondence. If you subscribe, we obtain your subscription status, plan, expiry time and purchase history through a subscription management service provider to provide subscription benefits; we do not receive your payment card details.

4. Story visibility and AI processing We use a third-party authentication service to manage sign-in and cloud service providers to store application data. Private stories are only stored, never analysed. Only when you choose public sharing do we send the original text to third-party AI services for analysis and to generate recommendation data. Private means hidden from other users; it does not mean stored only on your device. Public stories and nicknames may be shown to other users. Making a public story private stops its display and recommendation to other users and clears its current analysis data. AI requests already sent cannot be recalled. Historical analysis data for older private stories has not yet been cleared in bulk. Consider the content carefully before publishing: we cannot guarantee retrieval of copies saved independently by other users. AI inputs are limited to the content of the stories you choose to share publicly. We do not attach account data such as your account ID, email, account nickname, sign-in credentials or push token to AI analysis inputs. Private stories are not sent to AI. Please do not include your own or anyone else’s name, contact details or other identifying information in stories. We do not guarantee automatic detection, removal or anonymization of personal data in stories before transmission. If you include such information in a public story, it will be sent to third-party AI services along with the story content.

5. Service providers and disclosure We use third-party service providers for account authentication, cloud data storage, AI analysis and recommendation processing of public stories, and push notifications. Relevant data is processed by providers as needed for these functions. Depending on deployment and provider arrangements, processing may occur outside your country or region; specific processing locations still need confirmation before formal release. We do not sell, rent or exchange personal data for third-party marketing. Disclosure is limited to content you make public, necessary service-provider processing, your separate consent or legally required disclosure. Disclosure for investigations or to protect rights or safety must have a lawful basis and be limited to what is necessary. Subscription payments are processed by Apple or Google, depending on the store you buy through, and subscription status is managed on our behalf by that provider. We use your account ID to look up and sync subscription data with the provider, and ask it to delete that data when you delete your account.

6. Retention and deletion You can edit stories, change their visibility, adjust notification preferences, and request account deletion in Settings. Deleting an individual story removes it from display and recommendations but does not immediately erase all server data. Account deletion starts a separate background erasure process. Policy acceptance records are stored with your account. Retention: while an account remains undeleted, account and story data needed to provide the service are retained, including during inactivity. To request access, correction or deletion, contact privacy@resontales.com. Erasure plan: the target after account or individual story deletion is to erase related original text, AI-derived data, backups and identifiable user records within 24 hours. The complete erasure process and backup and log retention periods have not yet been verified. Erasure of every copy within 24 hours is therefore not currently guaranteed; current deletion behavior is described above.

7. Your rights and contact For privacy, personal data, and data deletion inquiries, contact privacy@resontales.com. At the address above, you may request access, inspection, copies, supplementation or correction, cessation of collection, processing or use, or deletion of your personal data. We handle requests under applicable law and may verify identity when necessary. Provide enough information to identify your account and request; do not email passwords. We will explain any legal reason preventing full fulfillment. Stopping necessary processing may affect related services.

8. Security and user responsibilities Account authentication and access checks restrict access to account and story data. Keep sign-in credentials secure, avoid sharing accounts, and provide accurate information you are entitled to provide. Report suspected unauthorized access or data disclosure to privacy@resontales.com.

9. Device storage, analytics and platform advertising plans The app stores sign-in credentials or necessary settings on your device to maintain your sign-in session and basic functionality. Clearing local app data may require you to sign in again or reconfigure settings. The official website provides only app information and related materials, with no account sign-in functionality. Usage analytics: the app uses Google Analytics for Firebase to understand how features are used. It is a separate choice that is off by default: you are asked once after signing in and can turn it on or off anytime in Personal settings. Declining does not affect any app feature, and turning it off also clears the analytics data collected on this device. Analytics includes an app-instance identifier, basic device and app-version information, an approximate region estimated from your network address, and events showing which features you use (such as saving a story, opening a similar story or viewing the subscription plan). It does not include story content, nickname, email or account ID, and the advertising ID is not collected, but it should not be assumed to contain no personal data. It is not used for advertising. Platform advertising plan (not yet enabled): Ad recommendations will be based only on the content of stories you share publicly, with ads selected internally by ResonTales. Private stories will not be used for ad recommendations. Before enabling this feature, we will update our data-use disclosures and obtain any required consent.

10. External links When opening external websites or third-party services, read their privacy policies. This policy does not cover their independent data processing.

11. Policy changes We may revise this policy as features or data practices change and display the version, update date and effective status on the document page. Changes requiring renewed consent under applicable law or our service flow will be presented separately. Existing consent does not constitute acceptance of an ineffective draft or future new purposes.

Basic safety protection and review records For new or re-saved public stories, we send the story text and language to a third-party AI service for basic safety checks. The analysis and recommendation stage starts only after approval. Private stories are not sent for safety checks. A story failing review has still been sent to the AI service. Authorized reviewers may read flagged story text and the AI assessment to decide whether it can proceed toward public recommendation. Pending or rejected versions are not shown to other users, but authors can still view their own stories. We retain account- and story-linked content revisions, AI categories and brief reasons, model and policy versions, review times, and human decisions, reasons and reviewer identifiers to administer reviews, investigate errors and maintain service safety. These records are not used for similar-story recommendations. Editing does not overwrite earlier review records; the new version requires review. Records are retained while needed to provide the service and are not immediately erased when an individual story is deleted. They are included in the background account-erasure process. The existing policy qualifications about deletion timing, backups and all copies still apply.

Scam review also covers suspected attempts to obtain money, credentials, verification codes or personal data through deception, such as impersonation, phishing links, guaranteed-return investment schemes and romance or job scams. Flagged content receives a reason and human review; further analysis and recommendations wait for approval. Sharing a victim’s experience, anti-fraud warnings or quoted scam messages used as warnings is not a violation merely for mentioning scams. A link, brand or financial topic alone is not evidence of fraud. AI assesses the text; it does not verify links, identities or investment claims.

Political and religious topic labels and preferences When applying basic safety checks and semantically analyzing a public story, we may generate political and religious topic labels from its text and store them with the story. We use the labels to filter similar-story recommendations and related notifications according to your preferences. The labels describe story content and are not used to determine or infer the author’s political views, religion or identity. We also store two separate settings indicating whether you accept political topics and religious topics; both are enabled by default. You may change them at any time in Settings. Labels are updated when an edited story is processed again, and are handled under this policy’s deletion process when a story or account is deleted. Private stories are not sent to AI to generate these labels.