How NUMEON uses data

Your name, birth date, selected language, calculated numerology profile, and generated narrative are stored so the same result can be revisited and shared consistently.

NUMEON calculates deterministic numerology values first. Only the structured context required to create the personal narrative is sent to the AI provider; the provider does not calculate or override numerology values.

A randomly generated visitor ID is held in a 90-day HttpOnly cookie. The raw ID is not stored in the database; a SHA-256 hash is used for reading rate limiting.

A separate 30-day HttpOnly cookie may hold opaque referral attribution. It is cleared after a successfully referred reading is created.

Referral URLs contain opaque codes. Successful invitations may create conversion records; when a person explicitly chooses to compare two stored profiles, NUMEON stores one canonical comparison record.

Recipient reaction choices are browser-session interface state only. They are not stored in the database or reported to the sender.

When analytics configuration is enabled, NUMEON sends limited product-interaction events to PostHog. Names, birth dates, reading text, referral tokens, and personal result links are intentionally excluded. Automatic click/page capture and session recording are disabled.

The PostHog browser identifier is held in sessionStorage only for the current tab session. It is not merged with NUMEON's rate-limit identity, and no user profile is created. NUMEON does not use browser fingerprinting. GeoIP enrichment is disabled; however, PostHog is a third-party network service, and NUMEON does not claim that network infrastructure never processes an IP address or guarantee absolute anonymity.

Anyone with a result link can view that result; do not enter sensitive personal information beyond the requested name and birth date.