Privacy Policy

1. Data we collect

Account data: email address, interface language, sign-up and sign-in times, and the version of the terms you agreed to when signing up.

If you sign in with LINE: your LINE user ID, display name and the email address you agree to share. We also store, encrypted, the access token LINE issues to the Service, used only to tell LINE to end the connection when you delete your account or unlink LINE.

If you sign in with Google: your Google account ID, email address and its verification status, and name. We do not access your Gmail, Drive, contacts or other Google data, and we do not store Google tokens.

Reading data: the topic you choose, your question, the casting numbers or time, your time zone, and the resulting hexagram, hexagram reading, full report and follow-ups. Questions and readings are encrypted before they are stored in the database.

BaZi and Zi Wei Dou Shu chart data: the birth date and time you enter (or the two-hour period, or unknown), birthplace (city, or time zone and longitude), sex (used only to set the direction of luck cycles and decade cycles) and an optional chart name. BaZi and Zi Wei Dou Shu share the same data. If you create a chart without signing in, the data is calculated once on the server and not saved. Once you save a chart, the birth data, chart name and chart results are stored encrypted. If you save a chart for someone else, you must confirm that you have their consent or are their legal representative.

Credits and transactions: credit balance and change history, top-up orders (credit pack, amount, currency, status) and refund records. Payments are processed by our payment provider, Dodo Payments; we never receive or store your full card number.

Top-up records: for each top-up we record your raw IP address, full browser identifier (user agent), country or region and interface language at that moment, plus the versions of the Terms of Service and Refunds policy you agreed to and when you agreed.

Sign-in and report-access records: the time, sign-in method, IP address, browser identifier and country or region of each successful sign-in; and the time, report ID, IP address and browser identifier when you open a paid report.

Payment dispute records: the dispute or chargeback ID, status, amount and outcome reported by our payment provider.

Technical data: cookies needed to keep you signed in; a hash of your IP address to prevent abuse; and the country or region provided by Cloudflare. Apart from the top-up, sign-in and paid-report records above, we do not store your raw IP address for ordinary browsing.

Invite data: invite codes and invite relationships (who invited whom, progress and reward results). An inviter sees only a friend's masked email (for example a***@gmail.com) and progress, never the friend's readings. To prevent abuse, we also store hashes (which cannot be reversed) of the friend's network and browser.

Usage statistics: records of your actions in the Service (for example the type of page viewed, completing a hexagram, unlocking a report, and why an action succeeded or failed), your device type (phone, tablet or computer, operating system, browser, and whether it was opened inside an app such as LINE), and the referring site and campaign tag from your first visit. We record only event names, simple categories and page types (plus the report ID when you open a report). This does not include your questions, report content, email or IP, and we do not store the full browser identification string.

Support data: what you send us when you ask a question or make a complaint, your contact details, and our records of handling it.

If you don't provide data: signing in requires an email address, a LINE account or a Google account; without one of them you cannot sign in. Without a question and casting data, we cannot generate a reading. We collect only the data needed to provide the Service.

2. How we use your data

Providing the Service: sign-in, casting, generating and saving readings, credits and top-ups. Data from LINE or Google sign-in is used to create and identify your account, recover it and prevent duplicate accounts.

Security and abuse prevention: human verification, usage limits and detecting unusual activity.

Support and troubleshooting: when handling your questions, complaints or failed generations, authorized staff may view the related activity logs. They view the content of a specific reading or report only when truly necessary to resolve that issue, and every view is logged.

Improving the Service: understanding, in aggregate, which features are useful and where things tend to go wrong.

Transactions and support: adding and deducting credits, payments, refunds, transaction inquiries, complaint handling, and fulfilling our contract and legal record-keeping obligations.

Preventing payment fraud and handling payment disputes: the IP address and browser information recorded at top-up, sign-in and report access are used only to detect card fraud and to handle refunds and chargebacks. If a payment is disputed, we provide the transaction and usage records for that order and the 90 days before and after it (order and payment details, the IP address, browser and country at payment, the version of the terms you agreed to and when, sign-in records, and report-access and credit-usage records) to our payment provider, Dodo Payments, which passes them to the card issuer and card network as evidence. We do not provide the content of your questions.

Contacting you: sending sign-in codes and necessary service notices. We will not send marketing emails without your consent.

We will not use your data for purposes with no reasonable connection to the above.

3. Data processing

To generate readings, your question, topic and hexagram data are sent to the data models we use for processing. Only what is needed for generation is sent; your email is not included.

These data models process data under their own terms of service. We prefer service plans that do not use submitted data to train models.

For BaZi and Zi Wei reports, we send only the chart data the program calculates (for BaZi: stems and branches, Ten Gods and luck cycles; for Zi Wei: palaces, stars, transformations, decade and annual cycles). We do not send your birth date, time, birthplace, sex or chart name.

We will not use your questions or birth data for marketing or for any purpose unrelated to providing the Service.

4. Third-party services and data location

Cloudflare: website hosting, database (stored mainly in the Asia-Pacific region), human verification (Turnstile) and cookie-free traffic statistics (Web Analytics).

Resend: sending sign-in codes.

LY Corporation (LINE Login) and Google LLC (Google Sign-In): identity providers that confirm who you are when you choose to sign in with their accounts.

Dodo Payments (payment provider): processes top-up payments, receipts, refunds and payment disputes; card and other payment details are handled directly by them. If a payment is disputed, the evidence we provide is passed through Dodo Payments to the card issuer and card network.

These providers may process data in countries or regions other than where you live. We give each only the data its service requires and require them to protect it under applicable law.

Cross-border transfers: given this setup, your data may be transferred to other countries or regions for processing. We confirm the legal basis for such transfers under applicable law (for example, the Personal Data Protection Act of Taiwan) and take necessary security measures.

Who uses your data and how: only we and the service providers listed above, processing, storing and retrieving it through electronic systems. If an authority with legal power requests data under the law, we will respond as the law requires. We do not sell your personal data.

5. Cookies

__Host-xs_session: keeps you signed in for 180 days after your last use (extended automatically while you keep using the Service). If you cast a hexagram without signing in, it also identifies you as a guest on this device and expires after 7 days; if you sign in later, your guest records are merged into your account.

xs_locale: remembers the language you chose.

xs_aid: a randomly generated anonymous ID used to measure the usage flow before and after sign-in, for 1 year. It is not used for advertising or shared with third parties.

xs_vid: an ID for a single visit that expires after 30 minutes of inactivity, used to count the steps taken in each visit.

xs_src: remembers where you first came from (for example LINE, Google or a campaign tag) and the type of the first page you opened, for 180 days.

__Host-xs_oauth: security check when signing in with LINE or Google, 10 minutes.

xs_login_result: tells the page that sign-in is complete, 1 minute.

xs_auth_preview: preview of a sign-in method under testing (internal testing only), 1 day.

Local storage: xs_last_method remembers the sign-in method you used last time (no personal data) and stays only on your device.

We do not use third-party advertising or tracking cookies.

6. How long we keep data

Readings and hexagram readings that are not unlocked and have no follow-ups: deleted automatically 72 hours after creation.

Readings with an unlocked report or follow-ups (including the report and follow-ups): kept until you delete the record or your account.

Charts and BaZi and Zi Wei reports: kept until you delete the chart or your account; no birth data is kept after deletion.

Sign-in method data (LINE and Google IDs, display names and encrypted tokens): kept until you unlink the method or delete your account.

Sign-in codes: expire after 10 minutes and are deleted regularly. Sign-in status: 180 days after your last use (extended automatically while you keep using the Service).

Email sending logs (used to limit how often verification emails are sent; we keep only the time sent and a keyed hash of the email address, not the message content): deleted after 30 days.

Usage statistics events: deleted after 180 days. Program error logs: deleted after 30 days.

Records that prevent claiming the free report more than once: we keep only keyed hashes of the email address, network address and browser ID, which cannot be turned back into the originals. To prevent repeat claims after an account is deleted, these are kept even after account deletion.

Transaction records (top-up orders, credit deductions and returns, and whether each report or follow-up was generated successfully; no questions or reading content): kept even after you delete a single reading or your account. After account deletion, the email address is replaced by an irreversible hash. They are kept for the period required by tax and accounting rules (currently 5 years), used only for legal record-keeping, refunds and dispute handling, and then deleted or de-identified.

Payment evidence records (IP address and browser information at top-up, sign-in records, paid-report access records and payment dispute records): kept for 5 years, the same as transaction records, including after you delete your account, used only to prevent payment fraud and handle refunds and disputes, and deleted when the period ends.

Holds during a payment dispute: while a payment dispute (chargeback) on your account is open, the account is suspended to preserve evidence. Your account, readings and charts cannot be deleted for now, readings that would expire are not deleted automatically, and report content is kept until the dispute is closed. The normal rules above apply again once it is closed.

7. Your rights

You can delete a single reading at any time in My records, or delete your account and all data on the Account page. While a payment dispute is open, deletion is postponed until the dispute is closed (see section 6).

You can also email support@wene.app to request, as provided by law, to inquire about, review, receive a copy of, supplement or correct your personal data, to stop its collection, processing or use, or to delete it. After verifying your identity, we will reply within the period required by law. Where the law provides otherwise or there are lawful grounds to refuse, we will act according to the relevant law.

8. Security

All traffic uses HTTPS. Questions, readings and BaZi birth data are encrypted with AES-256-GCM before storage. Sign-in uses no passwords, and only hashes of codes and sign-in tokens are stored. No system can guarantee absolute security. If a data breach that may affect your rights occurs, we will notify you as required by law.

9. Minors

The Service is only for users aged 18 or older. If we find data belonging to a minor, we will delete it.

10. Updates and contact

When this policy is updated, we will post the new version and its effective date on this page, and notify you separately of material changes.

For questions about your personal data, email support@wene.app.