
Your trust matters
Your details, explained.
Unified Reading uses birth details to calculate a profile and generate a reflective reading. This page explains session storage, AI processing, temporary caching, analytics and payments.
Last updated October 30, 2026.
Why we ask for your birth name
Pythagorean numerology assigns numbers to letters. Your full birth name supplies the expression, soul urge, and personality calculations. This app treats Y as a consonant and normalizes supported Latin accents. These are interpretive conventions, not scientifically validated personality measures.
What stays in your browser
Your form answers are kept in this browser’s local storage to support back, edit, refresh, and reopening a paid reading for 30 days; clearing site data removes them. There is no account or database of saved profiles. A reading you choose to download stays wherever you save it; it may contain personal information, so share it deliberately.
What leaves your browser
When you reveal a reading, your name, birth date, optional time and place, life stage, optional personal context and gender, and calculated profile go to our Vercel-hosted API. The API sends a prompt containing your profile to OpenRouter to generate the interpretation. City searches may go directly to OpenStreetMap Nominatim, which receives the search text and network information. The public API and the MCP server receive only a birth date; it is used for that request and not stored or logged.
The dedicated rising, Moon, Venus and Mars calculators send the entered date, time and selected coordinates to a separate Unified Reading endpoint. It calculates the placement without storing the inputs and returns a no-store response. Place suggestions use OpenStreetMap.
Who generates your interpretation
We use OpenRouter, which routes requests to an available model provider. The configured fallback order is:
- openai/gpt-6-luna
- openai/gpt-5.6-luna
- anthropic/claude-sonnet-5.5
Model providers and inference hosts can have different logging and retention rules. We do not promise zero retention or a specific deletion deadline at those vendors. See OpenRouter’s privacy policy and its provider data policies.
What our server retains
To avoid generating the same reading repeatedly, the API temporarily caches generated text in server memory for up to 24 hours, under a keyed hash of the request. That text may contain personal details. Raw input values are not kept as cache keys. The cache is bounded and can disappear earlier when the server restarts. Application error logs omit request bodies and provider response text. Vercel and upstream services may retain operational or security logs under their own policies.
Rate limiting keeps recent request timestamps associated with network addresses in server memory.
Product analytics
We use PostHog to count page views and clicks so we can see how the app is used. It stores an anonymous identifier in your browser. Page text is masked before it is sent, so your name, birth details, and reading are not included. Sessions may be recorded for product improvement, to show layout, scrolling, and clicks. Our own page text stays readable in the recording, but every form field is masked, input values are never recorded, anything showing what you entered (your name, birth details, calculated results, and reading) is masked, and chart wheels are blocked out. Your form answers are never sent to PostHog. When a page or our server hits an error, PostHog receives the error type, message, and page path. Each AI reading records which model wrote it, how many tokens it used, and what it cost, but not the prompt or the reading itself. If you arrived through a campaign link, the link’s source tags (such as utm_source) and the referring site are kept in your browser’s local storage so we can tell which channels people come from. When a purchase completes, our server records the amount, currency, any promotion code, and those source tags in PostHog against the same anonymous identifier.
Payments
The full reading is a one-time purchase handled by Stripe Checkout. Stripe collects your payment details and receipt email under its own privacy policy; we never see your card. The only reading data sent to Stripe is an anonymous keyed hash of your inputs, used to confirm that a payment belongs to this reading. Stripe also receives the anonymous PostHog identifier and campaign source tags described above, so a purchase can be attributed to a channel. Your name and birth details are not shared with Stripe. The checkout reference is kept in this browser’s local storage, and our server checks it with Stripe each time the paid reading is requested. Access lasts 30 days from checkout, in this browser only, and clearing site data ends it sooner, so download your reading to keep it. Payments are not linked to an account.
Limits of the chart
The chart is calculated for reflection, not a professional ephemeris report. Unknown birth time hides Moon and rising and gives a solar chart. With a birth time and place, whole sign houses (each house is one sign, counted from the rising sign) and the chart ruler are calculated; without a birth time the app shows a solar chart counted from the Sun sign. Planetary aspects and transits to your chart are not calculated; the astrology calendar lists each year’s computed retrogrades, eclipses and Moon phases. To calculate houses, your birth place is geocoded on our server; the coordinates and time zone are used only for that request and are not stored or logged. Sample narratives are illustrative editorial examples; sample numbers and signs are calculated from the displayed fictional birth details.