Privacy
What we hold, and who can see it
A birth date, a birth time and a birth place together identify a person more precisely than most of what a company holds. EnteAstro holds those for you and for the people you save, so this page says plainly what happens to them.
What we hold
- · Your account: email, a bcrypt hash of your password, your display name and your calculation preferences.
- · Birth profiles: for you and for anyone you add — name, date, time, place, coordinates and the resolved time zone.
- · Calculated charts and daily readings, cached against those profiles.
- · Numerology and palm readings you have generated.
- · A security log of sign-ins, sign-outs and password changes.
Who can see it
You. Birth profiles, saved charts, daily readings and palm readings carry no staff read policy in the database at any role — not support, not admin, not the owner. That is enforced by the database rather than by an internal rule somebody could be persuaded to make an exception to.
What an operator can see is the operational minimum: your email, your account status and your subscription state, for answering a billing or access question.
Palm photographs
A palm photograph is biometric. When photo-assisted readings ship, the default offer will be to keep the structured reading and discard the image; where an image is kept it is private, served only through short-lived signed links, and deletable on its own without losing the reading. It is never used to train anything.
What we do not do
- · We do not sell your data, and there is nobody we share it with for marketing.
- · We do not send birth details, chart data or palm images to any analytics service.
- · We do not store card numbers. Payment is handled entirely by Stripe.
- · We do not make your charts public, and nothing you save is indexed by a search engine.
Getting rid of it
From your account you can export everything as a file, or delete your account — which removes every profile, chart, reading and image, cannot be undone, and leaves us no copy. You do not have to ask anybody, and you do not have to be a subscriber to do it.
Where it lives
In a PostgreSQL database in the EU (eu-west-1), inside a schema used by no other Techvora product, reached by a least-privileged database role that cannot read any other application's data. Sessions are stored as a keyed hash rather than as tokens, so a copy of the database yields no usable session.