What we collect
When you cast a reading, you give us your full birth name, date of birth, optionally your time and place of birth, and an optional commonly-used name. If you purchase a reading on the web, our payment processor (Stripe) handles your card information; we never see or store your full card number. If you purchase inside the iOS app, Apple handles the entire transaction · see the section below.
How we use it
Your birth data is used solely to compute and compose your reading. We do not sell, share, or rent your birth data to anyone. We do not use it for marketing or training. We do not advertise to you based on it.
Sign in with Apple
If you sign in to the iOS app with Apple, we receive two things from Apple: a stable identifier for you (Apple calls this the “sub”) and an email address. The email may be your real one, or it may be a private relay address Apple generates on your behalf · a string like abc123@privaterelay.appleid.com that forwards to your real address. When Apple gives us a relay address, that is the only email we ever see. We do not, and cannot, see your real address behind it.
We use the Apple sub to recognize you on return visits and to link your iOS purchases to your account. We use the email to send you the link to your reading and any refund or redo correspondence. We do not pass either to anyone else.
If you delete your Numen account (in the app or on the web), we tell Apple to revoke your sign-in so Apple stops emitting tokens for you and stops sending you the “your app is still using Sign in with Apple” reminders for our app.
In-app purchases (iOS)
When you buy a reading inside the iOS app, Apple processes the entire transaction. We do not see your card number, your Apple ID, or your device identifiers. What Apple gives us is a signed transaction record containing: the transaction ID, the product ID (which reading you bought), the purchase date, and whether the purchase occurred in Apple’s sandbox or production environment. We verify that record against Apple’s servers and use it to authorize composing your reading. Nothing else from your Apple account reaches us.
Refunds via Apple
If Apple grants you a refund for an iOS purchase, Apple notifies us through App Store Server Notifications V2. When that notification arrives, we mark the affected reading as revoked · the permanent URL for that reading begins returning a 410 (the page-gone status) and the reading is no longer readable. We keep the cache row internally as an audit trail of what was composed and when, but read access is closed. The posture matches a Stripe-side refund on the web: refund granted, URL revoked, audit row retained.
Palm photos
If you upload a palm photograph, we use it for one purpose only: to compose your palm reading. The image is sent to our composer, which extracts a written description of the visible lines and mounts. As soon as the reading composes, the image is deleted from our storage immediately · within the same request, not on a delayed schedule. The iOS permission strings that ask for camera and photo access make this promise; the code that runs after composition keeps it. As a safety net, any palm photo that somehow escapes the immediate-delete path (for example, a composition that errors before the delete fires) is auto-purged within 24 hours by a separate cleanup job.
How the reading is composed
Numen readings are composed by Anthropic’s Claude under a hand-authored Master Prompt that we wrote. For a numerology or astrology reading, we send Anthropic your name, your date of birth, and your target date. For a palm reading, we send Anthropic our composer’s written description of your palm photo, alongside your name and date of birth. We do not send the photograph itself to Anthropic. Anthropic processes this data under their API terms: it is ephemeral, not used for model training, and not subject to human review.
The reading is a contemplative instrument · for reflection, for self-knowledge, for the steadiness an old map can give. It is not medical, legal, or financial advice.
Where it lives
Your reading data is stored on our infrastructure (Vercel hosting, Supabase database). We retain your reading so you can return to it via your unique URL. You may request deletion at any time · in the iOS app via the in-app account-deletion control, on the web via your account page, or by emailing the address below.
Third parties involved
- • Apple processes iOS in-app purchases (StoreKit), provides Sign in with Apple, and sends us refund notifications (App Store Server Notifications V2). Apple handles card data; we never see it.
- • Stripe processes payments on the web. We never see or store full card numbers.
- • Anthropic (Claude) composes your reading from your computed chart data (and, for palm readings, our composer’s written description of your palm). Anthropic processes the data ephemerally per their API terms and does not retain it for model training or human review.
- • Supabase stores your reading record and (if you have one) your account.
- • Resend delivers the email containing your reading link and any refund or redo correspondence.
- • Vercel hosts the application and may log standard request metadata.
Cookies
We use only essential cookies needed for the site to function. We do not use tracking, advertising, or analytics cookies.
Your rights
You may request a copy of your stored data, correction of any inaccuracies, or deletion of your data at any time. We will honor all such requests within 30 days. iOS users can delete their account from inside the app at any time · no email or human ticket required.
Contact
Questions about this policy or your data: support@numenist.com