Last updated 18 August 2026
Privacy
Privacy is the point of INNERCODE. Your birth information is used only to calculate your chart — never stored on our servers, never sent to the AI, and never placed in a link.
This is a working draft, shared for transparency. Have it reviewed by a qualified professional before public launch.
What we don't do
We keep as little as possible.
- No account, and no password to create.
- No server-side database of your readings.
- No analytics or advertising cookies, and no tracking.
- Your birth date, time, and place are never sent to the AI, written to a log, or put in a URL.
Where your reading lives
Your completed reading exists only in the browser tab where it was created, in that tab's session storage. Close or clear the tab and it is gone. It cannot be recovered — because we never kept a copy.
City search
City search runs on our own server against a bundled offline dataset, so your query is not sent to a third party. Only if an optional fallback is enabled would a query with no local match be sent to a geocoding provider — a place name only, never your birth details.
The AI interpretation
To write the reflection, only approved facts derived from your calculated chart (elements, stems, branches, and similar) are sent to the AI provider. Your birth date, time, place, and any name are never sent. An optional “woman” or “man” context is sent only if you choose it.
Cookies
One cookie stores only your language preference (“en” or “zh-CN”). There are no analytics or advertising cookies.
Rate limiting
To prevent abuse, requests are counted per visitor using a one-way hash of your IP address combined with a secret. The raw IP address is never stored.
Third parties
The reflection is generated by an AI provider, optional fallback city search may use a geocoding provider, and the site is served by a hosting provider. Each receives only the limited data described above, handled under its own policy.