Home

PRIVACY POLICY

Privacy policy

Updated and effective

This Privacy Policy explains how Hangzhou Cool Monkey Network Technology Co., Ltd. (the operator of FateSays, ‘we’, ‘us’) handles personal information when you use fatesays.com, the FateSays app and related account, chart, AI reading and purchase services. It describes our practices; it is not a blanket consent to every use of your information. Where a separate permission is required, we ask for it separately.

On this page

1. Information we collect

We collect information you provide, information returned by sign-in and payment services, and limited technical information generated while the service operates.

  • Account information: email address, account identifiers, optional name, and the identifiers and verification details provided by Apple or Google when you choose those sign-in methods. Apple may provide a private relay email instead of your actual email. We maintain login sessions and, for supported native sign-in, encrypted authorization credentials needed for account management.
  • Birth profiles and chart inferences: nickname, gender used for chart calculation, date and time of birth, selected birthplace and its coordinates, calendar and solar-time settings, and the calculated BaZi and Zi Wei chart parameters. Creating a birth profile is requested when you use personal readings; it is not required just to explore your account, the store or settings.
  • Content: questions you submit, generated answers, saved conversations, Life Books, Annual Books and reading progress. Free text may contain personal or sensitive information that you choose to include. Do not submit unnecessary health, financial, identification or other sensitive details.
  • Transactions and entitlements: product, order and transaction identifiers, purchase channel, available payment amounts and currency, payment/refund status, membership expiry, book/profile associations and redemption records. Apple and Stripe handle payment credentials; we do not receive full payment card numbers from their checkout systems.
  • Referrals and partner services: referral code and attribution, referred registration and order records, commissions, withdrawal requests and status. Partners who request a withdrawal provide the payee name and payment account, such as an Alipay phone number.
  • Technical and support information: request timestamps, IP-related security and rate-limit information, browser or device information supplied with requests, errors, task status, usage counters and information you voluntarily send to support. We do not request device GPS permission for birthplace search.

2. Why we use information

We use information to authenticate accounts, calculate charts, deliver requested AI readings, save and restore content across devices, prepare purchased books in the background, verify purchases, maintain entitlements and quotas, process partner commissions and withdrawals, and respond to support or privacy requests.

We also use operational metadata to prevent fraud and abuse, diagnose failures, measure generation reliability and registration-to-use-to-purchase conversion, reconcile payments and meet legal obligations. These operational reports do not need to read the text of your questions, answers or birth profiles. We do not use your conversations to train our own AI model, and we do not use chart readings to make decisions about employment, credit, insurance or other legal eligibility.

3. AI processing and your permission

AI features send your current question, relevant calculated BaZi and Zi Wei parameters, necessary birth date/time and gender information, the selected reading language and the instructions for the requested feature to the configured model service. A book request also includes its chapter topic and, for an Annual Book, its year. The standard question flow does not automatically send your complete conversation history, unrelated profile memories, nickname, account email, sign-in credentials, payment records or withdrawal information. Details you put into the question yourself will still be part of the request.

Our current integrations support OpenAI models through APIMart and OpenRouter gateways, including primary/backup routing. Those gateways process requests in transit and are separate recipients from the model provider. The recipients and model configuration may change; the AI permission flow identifies the current configuration and requires renewed permission when the recorded configuration changes.

You can decline AI processing and still manage your account, browse the store and use non-AI chart calculation. You can withdraw AI data-sharing permission in Settings. Withdrawal stops new authorized AI requests; it does not recall requests already delivered to a provider or automatically erase saved readings. Purchased books awaiting permission will not begin AI generation until permission is given.

FateSays does not promise zero retention, a fixed provider deletion period or that a gateway/provider will never use data for its own purposes. Each recipient’s handling depends on its actual service terms and settings. Contact us for the current recipient information or a data request involving a provider; we will assist as required by applicable law. Do not treat the generated content as anonymous merely because account identifiers are excluded.

4. Service providers and other disclosures

We disclose the information necessary for the following functions: Cloudflare provides hosting, security and task queues; Neon hosts the database; Resend delivers sign-in and service emails; Photon/Komoot processes the text used to search for a birthplace; Apple and Google support their selected sign-in methods; Stripe and Apple process and verify purchases; and the AI recipients described above generate readings. Providers may also have their own obligations and privacy notices for services they provide directly to you.

We may disclose information to authorized support or administrative personnel, professional advisers, or authorities when reasonably necessary for service security, a legal obligation, lawful requests or the protection of rights. A business transfer may require information to move to a successor, subject to applicable protections and notice. We do not make private birth profiles, conversations or books publicly visible through the service.

5. Referral attribution and partner visibility

The first valid referral is recorded using a signed cookie or a referral code supplied during registration when that option is enabled. There is no 30-day registration cutoff. Registration fixes the attribution for later purchases and renewals; the same referral code does not give the partner access to your account.

The attributed partner can see an internal customer identifier, a masked email, registration time, purchase counts and relevant order information, including product, amount, currency, payment/refund status and timestamps. Masking does not make this information completely anonymous. Partners cannot use their dashboard to see your birth profiles, questions, answers or personal book content. Administrators can review attribution and financial records to operate the program.

Referral financial records may be retained with the account link removed after account deletion. They may still include transaction identifiers and accounting details. If you object to nonessential referral disclosure or want to exercise an applicable privacy right, contact us; we will assess the request and any accounting or legal exception.

6. Cookies, local storage and privacy signals

We use cookies and local/session storage for sign-in, security, language and interface preferences, temporary drafts and request recovery, and referral attribution. Removing or blocking them can sign you out, erase unsent local drafts or prevent referral attribution, but it does not by itself delete server-side records.

The current service uses its own account and task records for operational reporting. It does not load third-party advertising trackers or optional advertising analytics, and it does not use an advertising identifier for cross-app tracking. If we introduce optional tracking, we will update this notice and provide the choices required by law before activating it.

We do not currently change essential processing in response to a browser’s Do Not Track (DNT) flag. DNT is different from Global Privacy Control (GPC). Where applicable law requires an opt-out preference signal for a sale, sharing for cross-context advertising or targeted advertising, a valid GPC signal must be respected. We do not currently carry out cross-context behavioral advertising; privacy opt-out requests for any other legally covered disclosure can be submitted through the contact method below.

7. Retention and deletion

We retain account, profile, conversation, book and progress information while it is needed to provide account history and purchased access, unless you delete it or request deletion. Other records are retained according to their purpose: security and diagnostic needs, resolving payments and disputes, keeping financial records or meeting applicable law. Retention depends on the record and the circumstances; we do not promise one deletion period for every system.

Deleting a birth profile removes associated personal content from the application database. Account deletion removes the account and related profiles, conversations, readings and login sessions, and revokes stored Apple authorization tokens as part of the deletion process. Temporary task snapshots, shared search caches and provider backups have separate handling and may not disappear immediately. Accounting, fraud-prevention or dispute records and records independently maintained by payment providers may remain where legally permitted or required.

Deleting an account is not a reliable substitute for managing subscriptions. Apple subscriptions must be cancelled through Apple. Our website account-deletion process attempts to stop renewal of associated Stripe subscriptions; you should check the cancellation confirmation in the billing portal. See the Terms for how to cancel before deleting an account.

8. Security

We use measures such as encrypted transport, restricted administrative access, verification of authentication and payment data, and account/profile access checks. No internet service can guarantee absolute security. Keep your sign-in accounts secure and do not send passwords, verification codes, full card numbers or identity documents unless a necessary and secure verification process has been agreed.

If an incident triggers a legal notification obligation, we will notify affected people and authorities using the method and timing required by the applicable law.

9. Your choices and privacy requests

You can edit or delete birth profiles, view saved records and purchases, manage AI permission, and request account deletion through supported account/settings screens. For a copy of information, correction, deletion, portability, an objection, an opt-out or a request you cannot complete in the interface, email kuhou@protonmail.com with the subject ‘Privacy request’ and the account email or another way to locate the account. Do not include your password or payment card information.

We may verify identity using information proportionate to the request. Authorized agents may submit requests with evidence of authority where the law permits. We respond within the deadline for the particular request and applicable law. Access, correction and deletion requests under many U.S. state laws generally allow 45 calendar days; opt-out requests can require a shorter response. GDPR/UK GDPR requests generally require a response within one month. Any permitted extension, refusal or exemption will be explained. We do not discriminate for exercising a protected privacy right. Where a right to appeal exists, reply with ‘Privacy appeal’; we will explain the review result and the available regulatory complaint route.

You can also stop providing optional information, withdraw an applicable consent, manage browser storage and use unsubscribe instructions if an optional marketing message is sent. Necessary account, security and transaction communications may continue while you use the service.

10. U.S. state privacy information

Depending on your residence and whether the relevant law applies to our processing, you may have rights to know/access, correct, delete and obtain a portable copy of personal information; opt out of sale, legally defined sharing or targeted advertising; limit specified uses of sensitive information; or opt out of qualifying profiling for decisions with legal or similarly significant effects. Applicable exceptions and identity checks may apply. The collection categories, sources, purposes and recipients for our current service are described above.

We do not operate a business selling private birth profiles or conversations, and we do not use personal information for cross-context behavioral advertising. Referral and other disclosures are described separately and must not be confused with fully anonymous statistics. If a disclosure is legally classified as a sale or covered sharing in your jurisdiction, you can exercise the applicable opt-out through the privacy contact above. We do not use sensitive information to infer a medical condition or to determine eligibility for a regulated service.

California residents may use the contact above for rights available under the CCPA/CPRA where that law applies, and for a request concerning direct-marketing disclosures where applicable. We do not provide personal information to third parties for their independent direct-marketing campaigns. These statements do not assert that every state law applies to every user or waive a right that does apply.

11. International processing and EEA/UK rights

FateSays serves U.S. and international users and is operated by the company named above. Our operator and service providers may access or process information in the United States and other countries. Your information may be processed outside your country of residence. Where a particular transfer safeguard is required, transfers are subject to a legally valid mechanism under applicable law. Contact us for information about the processing locations and safeguards applicable to your information.

Where GDPR or UK GDPR applies, the operator named above is responsible for the processing described in this notice. The relevant legal bases include performing the service you request, compliance with legal duties, legitimate interests in security and reliable operation where those interests do not override your rights, and consent for processing that requires it. A consent can be withdrawn without changing the lawfulness of earlier processing. The AI permission in the service controls whether new AI requests may be sent. It does not, by itself, establish a lawful basis for every recipient’s independent processing or replace required international-transfer safeguards.

Subject to the applicable conditions, you may request access, correction, erasure, restriction or portability, object to processing based on legitimate interests, and complain to your competent data-protection authority. Our cultural readings do not constitute solely automated decisions that determine legal or similarly significant eligibility.

12. Children and other people’s information

FateSays is intended for adults aged 18 or older who can enter a valid contract. It is not directed to children, and we do not knowingly collect personal information from children under 13. Do not create an account or submit a birth profile for a child. If we learn that a child’s information has been collected contrary to these rules, we will take appropriate steps to stop the processing and remove it, subject to applicable law. A parent or guardian can contact us using the privacy contact below.

Only provide another adult’s information when you have permission and a lawful basis to do so. A birth profile is not proof of identity; accurate birth data and authority to provide it remain important.

13. Changes to this policy

We publish updates here with their effective date. For material changes, we provide a prominent service notice or another appropriate notification before the change takes effect where required. We obtain a new permission when the law or the relevant AI authorization requires one; a policy update alone does not silently authorize a new consent-based use.

14. Contact

Operator: Hangzhou Cool Monkey Network Technology Co., Ltd. Privacy and support email: kuhou@protonmail.com. Support page: https://fatesays.com/support. Identify the request and a safe way to locate your account; we will provide a suitable contact or complaint route when additional information is needed.