Sign in
What this stores about you, and what it does not
Stated here because it is true of the database, not because it is policy prose: these are properties the schema enforces, and there is a test for each one that tries the violation and is refused.
- Your password is stored as a scrypt hash with its parameters, never in plain text. The session is a cookie holding a random token; only the token's sha256 is kept, so the database holds nothing that can be replayed. Sessions expire absolutely and also time out when idle.
- Each account sees its own charts. Asking for someone else's gets the same answer as asking for one that does not exist. That holds for everyone, including the people who run this: there is no account that can open your saved reading.
-
An operator can see what has been entered. The people
who run this can list every birth that has been entered here —
the date, the time and the place — because they have to be able
to see what the instrument is collecting. They cannot open your
reading, only the entry.
Every time they do, the application records who looked, when, and how many entries came back, in a log that cannot be edited or deleted and that outlives the account that made it. We would rather tell you that than have it be true and unmentioned. -
This software makes no outbound request. No analytics,
no font service, no geocoding, no telemetry; the place lookup is a
file held on the server. What you type reaches our server in Mumbai
and stops there — it is not passed on to anyone.
This used to read “nothing leaves this machine”, which was written when this ran on one laptop. It is now a hosted service, and on a hosted service that sentence would read as a promise about your machine, which it never was. - The terms and conditions are linked from the birth form and have to be agreed to before a chart is computed. They are written but not yet reviewed by a lawyer, which is said on the page itself rather than left to be discovered.