Privacy Policy

To generate a chart and reading, you may enter birth date, optional birth time, birth place (search or coordinates), timezone, and gender (including “prefer not to say”).

We do not ask for your name or account password on the reading form. Separately, you may optionally submit an email address only if you choose to join Premium early-access notifications. That email is used solely to notify you about Premium launch / early access — not for automatic purchase or a hidden subscription. Early-access submissions store only the normalized email plus coarse metadata (locale, optional country code when already available from trusted geo, source page, consent version, and timestamps) — not birth details, chart data, or report text. Joining the waitlist is not a purchase. A support email (support@bazimuse.com) is also published on the Contact page when configured.

From your birth details we calculate a BaZi (Four Pillars) chart and related structural information, and may generate a short self-reflection / entertainment-oriented reading.

These outputs are produced for your request in that session. They are not a scientific personality assessment, medical diagnosis, or guaranteed prediction.

We use the information you submit to calculate your chart, generate the requested reading, apply basic abuse-prevention limits on report generation, and keep the service running.

We do not sell your birth details. We do not use them for advertising profiles in the current product.

When you request a free reading, our servers may send chart-derived interpretive data to an AI language provider (currently configurable as DeepSeek or OpenAI) so the reading can be written in natural language. That provider processes the request to return text to us.

Place search may call a geocoding service (Photon) with the place text you type, so we can suggest locations and resolve coordinates and timezone.

We do not send your data to advertising networks. We do not claim that “nothing is ever shared with any third party,” because AI and geocoding providers necessarily process request data to provide those features.

Birth details and readings are primarily handled for the request you make. On the client, we store a locale preference in localStorage; we do not currently use cookies for analytics or advertising.

On the server, an in-memory cache may temporarily keep a hashed form of recent free-report requests so repeated identical requests can reuse a generated reading without calling the AI again. This cache lives in the application process memory and is not a long-term personal archive. Exact retention length is not a fixed published policy yet and may vary with server restarts and capacity limits.

If you join Premium early access, your email and the coarse metadata above are stored in a durable database so we can notify you later. We do not publish a fixed retention period for early-access emails in this policy, and we do not claim automated deletion. Privacy requests can be made via the Contact page when a support channel is configured.

A best-effort in-memory rate limiter may use a hashed network identity (or a shared anonymous bucket) to reduce abuse. Raw IP addresses are not returned in API responses.

We currently use localStorage for locale preference only. We do not set analytics or advertising cookies in the current product.

You may access the service from different countries. Chart calculation and reading generation run on our servers and may involve AI providers that process data in their own regions. This notice is informational and is not a claim of GDPR, CCPA, or other certification.

BaziMuse is intended for adults interested in traditional self-reflection and entertainment-oriented readings. It is not directed at children. We do not knowingly collect birth details from children for accounts, and we do not operate an age-verification system.

You can choose not to submit birth details. You can leave birth time unknown. For privacy questions or requests related to this policy, use the Contact page. Response channels depend on whether a support email has been configured for the deployment.

We may update this Privacy Policy as the product changes. The “Last updated” date at the top will change when we do. Continued use after an update means you acknowledge the revised policy.