1. Information We Process
Depending on the feature you use, BaZi Lantern may process:
- Birth date, birth time, birth place or timezone inputs needed for chart computation.
- Derived Four Pillars, ten-god, element, luck-cycle, shensha, formation, pair, and radar-lite outputs.
- Account identifiers, saved chart aliases, saved relationship slots, consultation history, invite tokens, and language preference.
- Email address when you use beta, account, support, or future payment flows.
- Usage counters such as AI follow-up quota, route viewed, plan, result band, and non-identifying error codes.
2. Sensitive Chart Inputs
Birth and chart inputs are sensitive. We use them to compute your requested output and to display or store features you explicitly use. We do not sell birth data, raw chart data, relationship data, or private questions.
The current product includes server-side computation and optional saved history. Therefore, this policy does not claim that birth data never reaches a server. Instead, the product boundary is data minimization, explicit feature use, and no raw chart data in telemetry.
3. AI Interpretation
AI may be used to explain deterministic engine output or answer follow-up questions. AI does not assign the core score, create hidden runtime rules, or silently change your chart result.
Prompts should use the smallest context needed. Private names, raw birthdays, contact information, and unnecessary location detail should not be sent to AI explanation providers.
4. Telemetry And Error Monitoring
22BW added a privacy-safe telemetry contract before any live analytics provider is connected. Allowed events cover surfaces such as chart computation, Life Audit, pair results, Radar Lite, pricing, billing shell, share rendering, and system errors.
Blocked fields include birth date, birth time, birth place, raw Four Pillars, raw BaZi, raw chart payloads, real names, email, phone, address, location, latitude, and longitude. The default telemetry sink is no-op until a future provider is explicitly wired.
5. Radar Lite And Relationships
Radar Lite currently ranks saved or sample relationships. It does not create a stranger matching pool, exchange contact information, or provide chat. If a future opt-in discovery feature is added, it must include consent, safety controls, and a separate privacy review.
6. Payment And Entitlements
Payment is not currently wired in this 22BW slice. Future payment providers may process checkout, subscription, refund, and webhook data. BaZi Lantern should store only the provider identifiers and entitlement state needed to operate Free and Pro access.
7. Service Providers
We may use hosting, database, AI interpretation, email, payment, analytics, and error-monitoring providers to operate the service. Each provider must be limited to the minimum data necessary for its role.
8. Your Controls
- You can delete local browser data through your browser settings.
- Authenticated account data and saved history should be deletable through support or future account tooling.
- You can avoid saving relationships or consultation history if you only want one-time computation.
- You can contact us to request deletion or correction of account-linked information.