Privacy Policy

What YUAN processes

• Your name or nickname, birth date, birth time, birthplace, selected time zone, optional gender, and optional personal question when you submit the birth form.
• A derived BaZi chart, generation context, generated Free and Premium content, generation status, and a private reading identifier.
• Your email, invitation and entitlement records when you claim complimentary access, plus marketing consent only if you choose it.
• Ratings, choices, price intent, and an optional comment when you submit feedback.
• Limited operational records needed to prevent duplicate requests, control access, recover failures, and investigate service errors.

How the information is used

Your submitted birth inputs are processed on YUAN's server to calculate the chart. The raw birth date, time, birthplace, name, selected time zone, and gender are not written to the reading database. The optional question is stored privately and may be used to classify and personalize the reading.

The derived chart, optional question, and approved generation context are sent to OpenAI to generate and validate the reading. YUAN does not send OpenAI your name, email, raw birth date, raw birth time, or birthplace as part of the reading-generation payload.

Your email is associated with your entitlement and reading-access recovery record when you claim a complimentary Blueprint. This replaces an earlier design promise that email would never be associated with a reading. Marketing consent is separate and optional.

Location lookup

If the entered city is not resolved from YUAN's local city list, the birthplace text is sent from YUAN's server to the public Nominatim service operated by the OpenStreetMap Foundation. YUAN requests only the first latitude/longitude match and does not forward your birth date, birth time, name, email, personal question, browser User-Agent, or owner cookie in that request. Nominatim use is subject to the Nominatim Usage Policy and the OpenStreetMap Foundation Privacy Policy.

Service providers

• Vercel hosts and delivers the web application and may process ordinary request metadata such as IP address, request time, route, and browser headers in platform logs.
• Supabase stores private readings, hashed owner-access tokens, contacts, invitations, entitlements, feedback, and operational records.
• OpenAI processes the derived chart, generation context, and optional question to classify and generate reading content.
• Google Fonts serves the site fonts from Google domains; requesting those font files exposes ordinary network metadata, including IP address and browser headers, to Google.
• OpenStreetMap Foundation's Nominatim service processes birthplace text only when the server needs a location match.
• Creem is present only in test-disabled payment code. No live payment is offered in the current private beta.

YUAN currently has no advertising tracker, session-replay tool, or product analytics SDK in the application.

Retention and deletion

A new Free reading is available for seven days. The raw birth inputs listed above are not stored in the reading database, but the derived chart, generated reading, optional question, feedback, and related access records are managed under the database lifecycle rather than being deleted when you close the page.

A complimentary entitlement normally lasts 30 days. Premium content can be retained for up to 30 days after the applicable entitlement expires or is revoked so the lifecycle can complete safely. A future paid entitlement can extend access for the configured purchase period; live payment terms have not been approved or enabled.

Feedback is linked to the private reading and is deleted when that reading is deleted. An email without marketing consent receives a deletion timestamp, but deletion waits until no entitlement still references the contact. Marketing-consented contacts do not currently have an automatic deletion date. Database cleanup is operator-run; the repository does not prove that a cloud scheduler runs it automatically.

You may request deletion through the route described on the Contact page. Verified lifecycle deletion removes the reading and dependent Premium and feedback records. Provider logs, backups, and third-party retention may follow their own controlled schedules.

Cookies and sharing

YUAN uses an HttpOnly owner cookie to restrict a reading to the browser that created it, and a short-lived signed invite-state cookie during an invitation claim. These are access-control cookies, not advertising cookies.

Sharing uses only a canonical elemental archetype label and the public product home page. It does not include your reading text, question, email, birth inputs, or private reading URL.