To cast a reading we process the birth details you enter (date, time, place, gender) and, if you choose to save readings or claim a founding seat, your email address. Gift and Bond invites store the name and optional message you provide so the recipient sees who invited them.
If you are signed in, we also keep the question you asked and anything you write in your journal — a wish, a worry, a thing you are holding. This is the most personal material we hold, and we are explicit about it rather than burying it: we keep it so your journal can show you what you asked, and so a later reading can open on the thing you actually care about instead of a blank chart.
Since 13 September 2026 we also keep the reading itself when you are signed in, so your journal can show you what Jade actually said rather than only that you asked. We keep only prose this server generated and signed — text sent to us by anything else is refused. Guest readings are processed without an account journal, but this does not mean nothing is stored: Gift and Bond invites, service logs and measurement records can remain. Signed-in mirror text can also be cached with its saved reading.
Your chat history is not kept forever. We store the most recent 200 messages on your account and remove older ones as new ones arrive, and any single message longer than 6000 characters is stored clipped to that length. This is a limit, not a promise of permanence — if a conversation matters to you, save it to your journal. Journal entries are never evicted to make room and are never silently shortened: a single entry is limited to 4000 characters, and if you exceed it we say so and decline to save rather than quietly cutting your words.
Field encryption (AES-GCM) protects saved birth date/time, reading-row name and occupation, chart summaries, questions, reading text, chats and journal entries when the encryption key is configured. It does not cover every database field: email, profile name, phone, location coordinates, timezone and gender are not field-encrypted. Gift names/messages are also not field-encrypted. Bond invite names and birth data use field encryption when configured. Journal and saved-text access is checked against your signed-in account.
Readings are written with large-language-model providers (Google Gemini and, as a fallback, an OpenRouter model). Chart text sent to them is scoped to your chart. Payments, when you choose to upgrade, are handled by Shopify; we never see your full card details. Other service providers include Resend for email, Klaviyo for profile, event and email-preference synchronization, and hosting and backup storage providers. Processing a reading can send chart details and supplied question/context to the model provider.
We also use a judgment service, TypeSafe, as a safety check. When it is enabled, the words you write in chat or as your question are sent to it and it returns only a number indicating whether you may need human support rather than a reading. It writes no part of your reading, and it is never sent your birth details, your saved readings or your journal.
TypeSafe also checks each 奇门 reading before you see it. Your question and the versions of the reading we wrote are sent to it, and it returns only numbers saying whether a version predicts an outcome, names a time, tells you which way to decide or guesses at what someone else is hiding, and which version reads most clearly. If a version does any of those, we rewrite it or show you a simpler reading. TypeSafe does not write or change the reading itself.
Before a 奇门 board is read, TypeSafe also reads your question to say which parts of the board it is about: work, love, money, a decision, a move, or none of these. It returns only that choice.
On the 奇门 page, your own browser keeps the words of your recent questions (up to 60) so your list of past readings can show them. They are not sent to us for that list, and clearing this site's data in your browser removes them.
A follow-up you ask under a 奇门 reading is handled like your question: its words are sent to our AI model provider to write the reply and to TypeSafe for the same checks. We keep the reply, encrypted, with that reading; the words of your follow-up are kept only in your own browser.
We advertise on Meta (Facebook and Instagram). To know which ads actually bring people here, this site loads the Meta pixel, which records that a page was viewed, that a reading was shown, that the upgrade screen was opened, and that a checkout was started. When you buy, our server also tells Meta the purchase happened, with your email address hashed one-way so it cannot be read back.
Your birth details, your question and your reading text are never sent to Meta or to any advertising network. We also pass the campaign tags from the link you arrived on (utm_source and friends) to our checkout, so a sale can be matched to the ad that led to it.
You can block this with any tracker-blocking extension, or by using a browser that blocks third-party requests — nothing about the reading changes if you do.
To delete account-linked records from the active database, open your journal and choose “Delete my account data”. That removes your readings, your chats, your journal entries, your founding seat, account row and queued transactional emails together. An email already being sent may still arrive. If the database erase cannot complete we tell you so and remove nothing, rather than reporting success on a partial delete.
If you have bought a reading, the order record stays — the order number, the amount, the currency and the campaign tag of the link you arrived on — because that is how a refund is reconciled and how we account for revenue. Your email address is removed from it; transaction identifiers and campaign information remain.
Account deletion does not automatically remove token-linked Gift/Bond invites, service logs, or records already held by service providers. Existing backups can still contain earlier data and remain subject to backup retention; deleting the active account does not immediately rewrite those copies. Contact us about records outside the active account database.
Questions about your data: love@jadeoracle.co.
Ask your first question →
First question free, no sign-up.