What stays with your birth profile.

Birth details and the fixed result

Your chart stores your birth date and local time, whether the time is known, required sex at birth (male or female), and an optional nickname. Use a nickname instead of your real name.

The calculation also stores the selected time-zone city and country, time zone, calculated instant, and UTC offset. The selected city is a representative time-zone lookup location, not a record of your actual birthplace. Historical profiles may retain birthplace and gender fields collected by the earlier form.

The server stores the chart calculation, every card appearance and its context, and the versions used to create the fixed result. Submitting birth details creates a new temporary preview. Correcting details preserves the original result and does not replace an account profile.

If birth time is unknown, the calculation assumes 6:00 AM local time and marks the entire result as provisional.

Public previews and private account profiles

Temporary previews at /p/ and historical chart links at /r/ are public to anyone with the link. This includes the birth details shown with the result. Do not share a link unless you want others to see those details.

A creator cookie identifies the browser that made the preview. It controls saving reading positions, submitting feedback and creating a first account profile after sign-in. The server stores a hash of its token. Losing the cookie removes those permissions; it does not remove public access to the preview.

When you complete sign-in for a preview you created, an account without a profile can receive a separate private copy of that result. An existing account profile stays unchanged. Merely opening a preview, even while signed in, never creates or replaces the account profile.

Your account profile at /profile requires the owner’s account. Historical private profile and deck links also retain their authorization checks. Sign-in stores account and session records, including your email address. Personal responses are marked no-store.

The framework library contains only general readings. It does not display personal birth details or the context of your individual card appearances.

Returning to a reading

The server separately stores the last card appearance opened and its opening time. This helps you continue reading without changing the fixed result and does not indicate that you finished a card. Personal reading positions and feedback are not shown to other public-link visitors.

Browser local storage keeps the latest public preview identifier together with its matching birth input and saved time. A separate draft keeps valid edited birth input so the form can restore it. It does not store card results, artwork, authentication tokens or generated interpretations. After the server confirms that a preview was linked to your account, this browser removes that preview shortcut and its matching draft. Newer or different input is kept. If local cleanup fails, you can retry it without saving the profile again. “Clear results” removes this browser’s temporary shortcut and draft and resets open input forms. Neither action deletes the public original, its server records, or the creator cookie. Opening a public link does not remember it as your result again. A stored identifier does not grant account or creator permissions.

Activity and feedback

Activity records creation, account saving, card openings, return visits, and feedback submission. Records can include result and card-appearance identifiers, a visit identifier, and a timestamp. An opening is not treated as a completed reading.

These activity events do not contain birth details, interpretation text, email, nickname, or raw IP addresses. Where an arrival category is recorded, it is a broad category such as direct, search, social, referral or campaign rather than the original URL or query text.

Feedback ratings and any comment you submit are stored separately and are available to authorized operators. Avoid including information you do not want an operator to read.

Operator access and current limits

Only authorized operators can use the activity dashboard, and access is logged. It shows result summaries, account identifiers or guest status, activity totals, arrival categories, and feedback. It does not add email addresses or raw birth details to that dashboard.

The current interface does not provide server-side profile deletion, bulk export, or an automatic retention schedule. This page does not promise a deletion or retention timeframe.