Privacy Policy

1. Data Controller

The data controller for this Service is:

· Operator: Li Dongze (李东泽), an individual trading on their own account under the laws of the People’s Republic of China

· Privacy email: 954607206@qq.com

· Registered address: not applicable (an individual trader, with no business address)

· Data Protection Officer (DPO): not appointed

This Policy covers the site’s pages and the features it offers: the free Bazi birth chart, the paid AI reading reports, and the API and MCP access offered to developers.

2. Personal Information We Collect

We collect only what the Service needs. What follows is what we actually collect.

2.1 Information you provide directly

· Chart details: your birth date, gender and birth place; the birth time if you know it (it is optional if you do not); your name, which is optional. A free chart uses these only to calculate that one chart — they are not written to a database and are not used to identify you.

· Reading details: when a report is generated, we store the birth details submitted for it (including the optional name and birth place), the chart features and traditional rules matched from them, the text of the report, and the year and areas of life it covers. These records belong to your account.

· Birth details held while a card payment for a reading is pending: from the moment you place the order until the payment is verified, the birth details for that report are held encrypted with the payment record; once the payment is verified they are used to create the report. Once the report is created, the birth details are kept with it (see the previous item) and the held copy is deleted at once; if the report cannot be created or the order fails, the held copy is also deleted at once; if you do not pay, it is deleted 24 hours after the checkout page expires (a payment that arrives late within those 24 hours is still used to create the report).

· Saved charts (My charts): the birth details a member saves and the names you give them. They belong to your account and can be deleted at any time.

· Account details: accounts are opened by an administrator, or, while self-registration by mobile number is open, by you (mainland China numbers only). If your account uses a mobile number, we collect that number; when you sign up with it, sign in with a code or reset a password by text message, we send a text-message verification code to that number and keep an SMS send record (see 2.2 below); if it uses an email address, we collect that address; passwords are stored only as a hash, never in the clear. When you sign up yourself (including an account created on the spot when you sign in with a code), we record which version of the Terms you accepted and when.

· Profile and preferences: the display name you set on the Account settings page (you may leave it unset); the avatar you use (one of eight pictures we provide — the system assigns one to start with, and uploading your own is not supported at present); and the appearance preferences you choose while signed in — day or night theme, seasonal palette, and whether the balance at the top of the page is hidden. These are saved to your account, so they apply automatically when you sign in on another device.

· Developer applications: the reason you give when you apply for developer access, together with the outcome, the time it was handled and any note our staff add.

· Transaction details: the amount, currency, time, payment status and order number of each transaction, the payment processor's order and payment references, and every entry in your balance ledger. For card payments we also keep the payment and refund notices the payment processor sends us, which contain the email address you entered at checkout and the last four digits of your card (and your billing address, where checkout asks for one); we store those notices encrypted, see Section 5. We never collect or store your full card number, expiry date or security code — those are handled by our payment processor, see Section 5.

· Communications: the emails, feedback and report ratings you send us.

2.2 Information we collect automatically

· Access logs: IP address, time, the page address requested (without the question mark and anything after it), browser type, and technical details such as the outcome and processing time. Access logs do not record which page you came from.

· Request and service logs: a request ID, the outcome, processing time, the time-conversion method you chose, the birth place’s time zone, and roughly whether the birth place is in China or elsewhere. Chart and reading request logs never record your birth date, birth time, birth place or name.

· API usage: the number and time of API and MCP calls, which key was used, which capability was called and how much was charged.

· SMS send records: for every verification text we send, one row: an irreversible digest of the number (a cryptographic hash computed with a key held on the server, not the number itself), the last four digits, the purpose (sign-in, sign-up or password reset), the time and the result of the send, and how many times the code has been checked and whether it has been used. The database never holds the full mobile number or the code itself (the code is generated and checked by the SMS provider). These records are used to stop text messages being abused (limiting how often and how many go to one number, from one source address and across the whole site) and to reconcile with the provider.

· Security-check data: on the pages where a text-message code can be requested (code sign-in on the sign-in page, the mobile-number sign-up page, the password reset page, and the part of the Account settings page where you set or reset your login password with a text-message code) we load the Alibaba Cloud Captcha 2.0 script. It runs in your browser and collects data about your device, your browser environment and how you operate the page, to judge whether the request comes from a bot; this data is processed on Alibaba Cloud's servers in mainland China (Shanghai). Alibaba Cloud's Captcha 2.0 data-collection notes list four categories: browser information (engine type and version, browser brand, User-Agent, cookies, local storage (localStorage), plug-in list, script runtime environment); device network information (IP address, connection status); device information (manufacturer, platform and model, operating system and version, processor, memory, graphics card, time zone, language, screen resolution, battery, media hardware); and interaction behaviour (mouse movement and click tracks, touch and swipe tracks, keyboard operation and the like — how you operate, not what you type). Our own server only receives one verification-result parameter, passes it to Alibaba Cloud to be checked, and does not store it. Other pages do not load this script.

2.3 What we do not collect

· We use no third-party analytics, advertising or social media plugins, and we do not track your browsing outside this site.

· We do not collect device location, and we do not offer third-party sign-in.

· We do not collect identity documents or any other data unrelated to the Service.

3. How We Use Your Information

Each purpose is paired with its legal basis (one per line: purpose — legal basis):

· Service delivery and maintenance (calculating charts, generating reports, serving API calls, and checking your mobile number when you sign up, sign in with a code or reset a password) — performance of our contract with you

· Billing, charging and payment processing — performance of contract

· Customer support and handling your requests — performance of contract / legitimate interests

· Service notifications (billing, security, policy changes) — legitimate interests

· Security and fraud prevention (rate limiting, investigating abnormal traffic, the security check and the sending limits before a verification text is sent) — legitimate interests

· Improving service quality and troubleshooting — legitimate interests

· Complying with tax, accounting and other legal obligations — legal obligation

· Marketing (not currently carried out, see Section 9) — your consent

We may aggregate or anonymise data for statistical purposes; such data cannot be linked back to any individual.

We do not use your birth details or your reports to train artificial intelligence models.

4. Cookies & Tracking Technologies

This site uses only the storage its features require. It sets no tracking, analytics or advertising cookies. Each item is listed below, with the storage mechanism actually used (one per line: name — type and purpose — can it be disabled):

· NEXT_LOCALE — strictly necessary cookie, remembers the interface language you chose (Chinese or English); it has no expiry date, so it normally ends when you close your browser, and it is not used to track you — cannot be disabled on its own (without it your language choice is not kept)

· co_session — strictly necessary cookie that keeps your session after you sign in; lasts 30 days for an ordinary account and 24 hours for an administrator account, and is HttpOnly; visitors who do not sign in never get it — cannot be disabled on its own (without it you cannot stay signed in)

· co-theme, co-season — browser local storage (localStorage), remembers the day/night theme and seasonal palette you picked. While you are not signed in they stay in your browser and are never sent to us. Once you sign in, your choice is also saved to your account (if the account has none saved yet, the choice already made on this device is saved to it), so it applies automatically when you sign in on another device; the copy in your browser is kept as well — yes, clear your browser data (the next time you sign in it is written again from what your account has saved)

· co-appearance-pending — browser local storage (localStorage), used only while you are signed in: when you change the theme or palette and the change has not yet been saved to your account, it holds that change and your account ID. It is deleted as soon as the change is saved; if saving failed, the change is saved the next time you open a page; it is also deleted when a different account signs in — yes, clear your browser data (a change not yet saved to your account is lost with it)

· Chart-to-reading hand-off data — session storage for the current tab (sessionStorage), used when an administrator starts a reading from a chart, or when a signed-in user goes from a chart to checkout, and cleared once the reading is submitted or the order is paid, or when the tab is closed — cleared automatically when the tab closes

· Checkout list, and the payment reference on the checkout, membership and top-up pages — session storage for the current tab (sessionStorage), remembers the products you ticked on the chart and a reference for this payment (so refreshing the page or retrying after a network error never charges you twice or places a second order); cleared once the payment succeeds (for a card payment, once the payment result page confirms the payment has been verified); if a card payment's checkout page expires or could not be created, only the payment reference is cleared and the checkout list is kept so you can order again; also cleared when the tab is closed — cleared automatically when the tab closes

· Alibaba Cloud Captcha 2.0 script — a third-party security-check script, loaded from Alibaba Cloud only on the pages where a text-message code can be requested (code sign-in on the sign-in page, the mobile-number sign-up page, the password reset page, and the part of the Account settings page where you set or reset your login password with a text-message code) to judge whether a request comes from a bot; while it runs it may read and use your browser's cookies and local storage, as Alibaba Cloud decides (see 2.2), and the site itself adds no cookie or local-storage item for it — yes: signing in with a password, or not using those pages, never loads it; on those pages it is a precondition for sending a code, so it cannot be disabled on its own

The site uses no analytics tool (no Google Analytics, no Baidu Tongji or similar), no advertising pixels and no social media plugins, so there are no “analytics” or “marketing” cookies and no tracking cookies requiring your consent.

The fonts and scripts the pages need are served from our own servers, so browsing the site does not send your visit information to third parties; the one exception is the Alibaba Cloud Captcha 2.0 script listed above, which loads only on the pages where a text-message code can be requested and connects to Alibaba Cloud's servers when it does.

An account's signed-in state is kept in the one co_session cookie listed above.

5. Sharing & Disclosure

We do not sell your personal information, including as defined under applicable laws such as the CCPA. We share your information only in the following circumstances:

· Payment processor: payment card data is processed exclusively by our PCI-DSS certified payment processor, Waffo Pancake, and is not stored on our servers. As merchant of record it handles your payments, refunds and disputes. When you place an order we send it only the order number, the kind of product (a reading report, membership or a top-up), the amount and currency, the checkout language and an account ID used for matching (it contains no name, phone number or email address). After payment it returns to us the order and payment references, amount, currency, time and status; its payment and refund notices also contain the email address you entered at checkout and the last four digits of your card (and your billing address, where checkout asks for one). We store those notices encrypted, use them only to verify payments and handle disputes, never show them on any page and never use them for marketing.

· AI model provider: to write a report we send the necessary material to a third-party large language model provider (currently DeepSeek). It receives only our fixed writing instructions, the traditional rules matched from your chart as text, the year and areas of life to be read, the stem-branch and start date of each month of that year, explanations of the terms involved, a flag showing whether your chart’s strength is borderline, and the report language; for the ten-year overview chapter, also the first and last calendar years of the ten-year periods it covers (years only, not their stem-branch); and, because an English report is drafted in Chinese and then translated, that Chinese draft is sent to it once more for translation. It does not receive your name, birth date or time, birth place or gender, nor your chart itself (the Four Pillars). However, because the rules were selected from your chart, they do reflect some of its features, and a few of them apply only to men or only to women. The provider handles what it receives under its own published terms. We may add or change model providers in future, and will update this Policy before doing so.

· SMS provider: when you sign up with a mobile number, sign in with a code or reset a password by text message, we pass your mobile number and the request to send a code to Alibaba Cloud's Phone Number Verification Service (SMS verification), which generates and sends the code and checks the code you enter; our database does not store the code. Alibaba Cloud handles what it receives under its own published terms.

· Security-check provider: on the pages where a text-message code can be requested, Alibaba Cloud Captcha 2.0 judges whether a request comes from a bot (what it collects is set out in 2.2). Once you pass, the page hands us one verification-result parameter and we pass it on to Alibaba Cloud to be checked, using our Alibaba Cloud account. This data is processed on Alibaba Cloud's servers in mainland China (Shanghai); Alibaba Cloud states that it stores and uses it only for the shortest time necessary to keep the function working and to troubleshoot.

· Cloud providers: our servers, database and backup storage are rented from cloud providers, who supply computing and storage only and do not use your data for their own purposes. Database backups are made once a day, kept on the server and readable only by administrators, and the birth details inside them are encrypted too; before any backup is stored outside the server, the whole backup is encrypted.

· Legal requirements: where required by law, regulation, court order or a lawful request from a competent authority.

· Business transactions: in a merger, acquisition or similar event, with advance notice and a requirement that the recipient maintain equivalent protection.

· With your consent: for any other purpose, with your explicit prior consent.

6. Data Security

We protect your information with the following measures:

· Encryption in transit: connections between you and the site use TLS / HTTPS, and plain HTTP requests are redirected to HTTPS.

· Network isolation: the database and the chart engine run only on the server’s internal network and cannot be reached directly from the internet.

· Access control: least-privilege access; reading reports can only be viewed after signing in, and an ordinary account sees only its own reports.

· Staff access: to handle a request from you or to investigate a problem, our staff may look at your account details, balance and ledger, orders, membership and API usage, and your reading reports (including the name and birth details shown on a report) in the admin console. For charts you have saved under My charts, staff can see only its name and when it was saved and last updated — not the birth details inside. When a member of staff opens one of your reports in the admin console, the system first records who opened which report and when, and only then shows it; repeat views of the same report by the same person within ten minutes are recorded once.

· Credential protection: passwords are stored only as hashes; API keys are stored only as digests and shown in full once, at creation; model provider keys are encrypted with AES-256-GCM.

· Birth details encrypted at rest: the birth details in reports and My charts, and the chart data calculated from them, are encrypted field by field in the database with AES-256-GCM (so is the copy held while a card payment for a reading is pending); the key is kept separately from the database and is never included in database backups.

· Database backups: one a day, kept on the server and readable only by administrators; the birth details inside them are encrypted too. Before any backup is stored outside the server, the whole backup is encrypted.

· Abuse protection: unusually frequent requests are rate-limited to prevent bulk scraping and abuse; a security check must be passed before a text-message code is requested, and there are limits on how many texts can go to one number, from one source address and across the whole site, to stop text messages being abused.

In the event of a security incident affecting your rights, we will notify you and the relevant authorities within 72 hours of discovery, as required by law. Please keep your credentials secure and do not share them.

No security measure is perfect.

7. Data Retention

We give concrete periods (one per line: data type — retention period — what happens at the end):

· Birth details entered for a free chart — not retained — discarded once the chart is calculated; never written to the database

· Account information (mobile number or email address, password hash, and account settings such as display name, avatar and appearance preferences) — while the account is active — deleted or anonymised within 90 days of account closure

· Birth details and reading reports — while the account is active — deleted within 90 days of account closure

· Birth details held encrypted while a card payment for a reading is pending — until the report is created, cannot be created or the order fails; if you do not pay, until 24 hours after the checkout page expires — deleted (once the report is created, the birth details are kept with it, see the previous line)

· Saved charts (My charts) — while the account is active — deleted within 90 days of account closure

· Developer application records (your reason, the outcome and any staff note) — kept while the account is active, with no automatic deletion at present; earlier applications are kept when you apply again — handled together with your account information on closure (see the Account information line above)

· Records of staff access to your reports (who viewed or acted on which report, and when; they contain no report text and no birth details) — kept while the account is active, with no automatic deletion at present — handled together with your reading reports on closure (see the Birth details and reading reports line above)

· SMS send records (an irreversible digest of the number, the last four digits, the purpose, the time and result of the send, how many times the code was checked and whether it was used; no full mobile number and no code) — 180 days — deleted automatically when they expire; you can also ask for earlier deletion (see the end of this section)

· Security-check data (the device, browser-environment and interaction data collected by Alibaba Cloud Captcha 2.0 on the pages where a text-message code can be requested) — held by Alibaba Cloud, which states that it stores and uses it only for the shortest time necessary to keep the function working and to troubleshoot; we do not store this data or the verification-result parameter the page hands us — handled under Alibaba Cloud's rules

· Transaction, top-up and charge records (including the payment processor's order and payment references and its encrypted payment and refund notices) — 5 years, as tax and accounting rules require — deleted or archived at the end of that period; these records survive account closure for the statutory period

· Support and email correspondence — 2 years — securely deleted

· Server access logs — 6 months — rotated and deleted automatically (Chinese law requires network logs to be kept for at least six months)

· Service runtime and error logs — overwritten on a rolling basis once they reach a size limit, so only the most recent part is kept — overwritten

· Database backups — at most 30 days per backup (currently 14 days) — the whole backup is deleted at the end of that period

When you ask us to delete data, we delete it from the database first; existing backups are not edited one by one, and the data in them disappears when those backups are deleted at the end of their retention period.

We do not yet offer a self-service deletion tool, so deletions are carried out by hand in response to your email request.

8. Your Data Rights

To exercise any of the rights below, email 954607206@qq.com. We respond within 30 calendar days; where a request is complex we will tell you why within that period and when to expect completion.

· Right to be informed — know what data we collect and how we use it

· Right of access — obtain a copy of the personal information we hold about you

· Right to rectification — correct inaccurate or incomplete data

· Right to erasure — request deletion where the conditions are met

· Right to restrict processing — suspend processing in certain circumstances

· Right to data portability — receive your data in a machine-readable format

· Right to object — object to processing based on legitimate interests, or to marketing

· Right to withdraw consent — withdraw consent you gave earlier (this does not affect processing carried out before you withdrew it)

To confirm that a record is yours, we may ask for the details entered when the report was created, or for your account identifier. A free chart is not stored, so there is usually nothing to access or delete for it.

Exercising these rights is free of charge. If you are not satisfied with how we handle your information, you may also lodge a complaint with your local data protection authority.

9. Marketing & Opt-Out

We currently send no marketing communications, and we do not pass your contact details to third parties for marketing.

If we start, we will obtain your consent first and include a one-click unsubscribe link in every marketing email; you can also email 954607206@qq.com at any time to stop receiving them.

Opting out does not affect essential service notifications (billing confirmations, refund progress, security alerts and policy change notices, for example), which are not marketing.

10. International Data Transfers

Our servers, database and backup storage are currently located in mainland China, and the AI model provider we use (DeepSeek) and our text-message verification and security-check provider (Alibaba Cloud) are also in mainland China.

This means that if you use the Service from outside mainland China, your information is transferred to mainland China and processed and stored there. The law of mainland China may differ from the law where you are, including in how competent authorities may lawfully request access to data. By using the Service you understand and consent to this transfer.

Card payments are completed on a checkout page hosted by Waffo Pancake; what you enter there is handled by Waffo Pancake under its own privacy policy.

The safeguards we apply:

· all transfers are encrypted with TLS;

· processors are bound by contractual confidentiality obligations and may process data only on our instructions;

· data minimisation — what we send to the model provider contains no name, birth date or time, birth place or gender.

To be clear: we have not separately entered into EU Standard Contractual Clauses (SCCs) or a comparable transfer mechanism. If the law where you are requires a specific transfer mechanism, please email us before using the Service; and if you are not comfortable with your data being held in mainland China, please do not use the Service.

If the location of our servers changes, we will give advance notice as described in Section 13 and update this section.

11. Children’s Privacy

The Service is intended for users aged 18 and above. We do not knowingly collect personal information from anyone under 18.

If you are a parent or guardian and believe that a minor has provided us with personal information without your consent, please contact us immediately and we will delete it promptly.

12. Third-Party Links & Services

The Service may include links to, or integrations with, third-party websites and services — the checkout page hosted by Waffo Pancake, for example.

This Policy applies only to the information we collect directly. We are not responsible for third-party privacy practices and encourage you to read their policies before use.

13. Policy Changes

For material changes — starting to collect a new category of information, changing model provider, moving the servers to another country, or beginning marketing, for example — we will give at least 15 days’ advance notice by a prominent notice on the site or to the contact details you registered with, and update the version number and date at the top of this page.

For minor wording changes we simply update the date at the top of this page.

Continued use after the effective date constitutes acceptance of the revised Policy.

We keep past versions of this Policy so that it can be established which version was in force at any given time.

14. Contact Us

· Privacy and data rights requests: 954607206@qq.com

· General support: 954607206@qq.com

· Security reports: 954607206@qq.com

Operator: Li Dongze (李东泽), an individual trading on their own account under the laws of the People’s Republic of China

Website: https://oracle.cyberguoxue.cn

We keep a single mailbox, and it is genuinely monitored; we do not operate a telephone helpline and do not accept postal mail. We normally reply within 2 business days, and complete data rights requests within 30 calendar days.

This Privacy Policy is for general reference and does not constitute legal advice.

Privacy Policy version 1.5 · Effective 15 October 2026 · Last updated 15 October 2026