1. What this is
Jwala computes a Vedic birth chart from a date, a time and a place, and reports what a set of encoded classical rules and a published collection of planetary combinations say about it. It runs on one machine and the computation happens there.
It is not advice of any kind — not medical, financial, legal, psychological or otherwise — and nothing in it should be acted on as though it were. It makes no claim that the chart predicts anything. Where a figure in the report rests on a choice this project made because the classical sources give no formula, the report says so beside the figure rather than in a footnote, and the Advanced View opens any figure up into the part that came from a text and the part that is ours.
2. What we collect, and what it is used for
The birth date, time and place you enter, how exact you say the time is and where it came from, the charts computed from them, and your account's username and password.
They are used to compute and store your charts. A saved chart is replayed from what was stored, never recomputed, so reopening one shows you what you read before rather than what today's software would produce.
There is one other use and it is worth stating plainly. Computing a chart also writes an entry to a register of charts that have been shown. That register exists for a research study this project runs separately — the study needs to know which people have already been told what the system says about them, so that it never treats them as though they had not been. Your chart and your answers do not go into that study, and the way the data is stored makes it incapable of representing a record as study-grade; what the register holds is the fact that a chart was shown. §5 explains why that entry cannot be removed.
Please note that a birth date, time and place together identify one person almost uniquely, whatever name is attached. Removing a name does not make the record anonymous. That is why the default is that nobody but you can see yours.
3. What the classical reading is, and what it never becomes
The classical reading is never tuned on anything you enter. The rules and weights it reports are the ones the classical sources set, and they do not move because of what users do. When this service tells you what Parashara says, that is what Parashara says — not a number adjusted until users liked it.
This is not a policy we are asking you to take on trust. The part of the system that computes those readings cannot read the part that stores your data — it opens no database and imports no storage code — and an automated test asserts that it cannot, by inspecting the code rather than by checking a setting. It is one of this application's declared invariants and it is not going to be relaxed, because the moment a classical figure can be quietly tuned, nothing on the page means what it says.
A model built on top of it is a separate thing, and it asks you separately. We do intend to learn from what people tell us, and anything learnt that way lives in its own layer, is labelled as ours rather than as the tradition's, and runs only for people who agreed to it. §11 is where that agreement is described, including the part that cannot be undone. Agreement obtained afterwards does not cover what was already collected.
4. Who can see what
- Your charts are yours. A chart belonging to another account answers exactly as one that does not exist, so this page cannot even be used to find out whether someone else has entered a given birth.
- Your register entries are scoped to you. The record of which charts have been computed is whole in the database, and no page shows you anyone else's row.
- An operator account can read the charts that have no owner at all — a small number of records that predate accounts existing and cannot be attributed to anyone. It cannot read yours.
- Nothing leaves this machine. There is no network client, no outbound request and no third party. The software has no code capable of sending your data anywhere, and a test asserts that too.
- Your password is never stored. Only a one-way hash of it is, with the parameters recorded alongside. Nobody operating this system can read your password.
5. Deletion, retention and export
What erasing does. Ask us and we will erase your data. It removes, in one step and at once: every chart saved for you, the birth details you entered them from, everything derived from those charts, any answers you gave — including any rating you gave of how a past period of your life went, and any note you wrote in your own words beside one — and your account and all its sessions. It cannot be undone, your password is required again before it runs, and nothing can afterwards be written back to what it emptied. You can be shown exactly what would go, and what would not, before you decide. There is not yet a button for this on the page, so for now it is done on request — the software does the erasing, not a person with a database open. Write to the address in §10.
What erasing cannot reach. If you agreed under §11 to let your ratings train a model, erasing removes the ratings and everything else listed above, and it cannot remove what the model already learnt from them. Learning is not storage and there is no honest way to subtract one person's contribution from a trained model after the fact. That is the reason §11 asks for that agreement separately, and says this before asking rather than after.
What stays, and why. Computing a chart writes an entry to the register described in §2 — a record that a chart was shown — and that register is append-only: the database physically refuses to update or delete a row in it. The register exists because this project also runs a research study, and the study needs the record of who has already been told what the system says about them to be one nobody can falsify. A record that can be deleted does not do that job. The entry holds the birth date, time and place the chart was computed from, together with a code derived from them.
We will not describe that code as anonymous. It is a one-way hash of your birth date, time and rounded coordinates, and because there are only so many minutes and so many places, anyone holding the database could work backwards from it to the birth details in a few hours of ordinary computing. It identifies you. Calling it a hash and leaving it there would be the comfortable description rather than the true one.
Two other things survive an erasure, both for the same structural reason: an internal assignment used to keep a fair test set, which holds only that derived code; and — for anyone who has used the period-rating feature in §11 — the record of which periods were shown to you, and when.
That last one is a narrow thing and it is worth being exact about what it is not. It records that a period of your chart was displayed, which period, and at what time. It holds no birth details and no answer of yours. It survives because it is what makes "you told us how that period went before we showed you anything" a fact we can check rather than a claim we make — delete it and a later answer could be presented as having come first. Your ratings themselves are erased, and they are the part that is about you: what you said about your own life stays out of the store once you have asked for it to go.
We regard the gap as a problem rather than a term you should accept. It is recorded as an open decision, not written around, and closing it means deciding which of two interests wins: yours, or that of everyone the study will later recruit. We would rather say this than report an erasure that did less than it sounded like.
How long we keep it. Until you erase it. There is no automatic expiry and we do not promise one, because a retention period is a promise to delete at the end of it and we cannot make that promise about the register entries. Saying "kept for two years" and then keeping something for ever would be worse than saying nothing.
Export. There is still no export feature. You can see a full account of what is held about you from your account before erasing, and you can ask for a copy in the meantime.
One practical limit, stated because it is true of any database. Erasing overwrites and removes rows; it does not guarantee that the bytes are unrecoverable from the storage underneath, and it does not reach any backup an operator may hold.
6. Your account
You must be 18 or over to hold an account here. Making one is a declaration that you are. The chart itself is not an adult matter and we put no age on reading one; an account is different, because it keeps a record of you, and because §11 offers choices that nobody under 18 should be asked to make about their own life.
Keep your password to yourself; anyone who has it has your charts. Sign-in sessions expire on their own, both after a fixed period and after a spell of inactivity, and changing your password ends every session you have open.
Please do not enter someone else's birth details without their agreement. The record identifies them, not you, and §5 applies to it.
7. No warranty
The software is provided as it is, with no warranty of any kind. The astronomical calculations rest on a published ephemeris and the interpretive material on translations of classical texts whose chapter and verse numbering this project has not finished verifying — the report says where that is so. Nothing here is guaranteed to be correct, available, or fit for any purpose.
8. Changes to these terms
If these terms change in a way that affects what is done with data already collected, that is a new purpose and we will ask again rather than announce it. Changes that do not affect that will be dated on this page.
9. Governing law, and the licence
These terms are governed by the law of India, and the Digital Personal Data Protection Act, 2023 applies to the personal data described above.
The software is not open source and no licence to it is granted. All rights in it are reserved. You may use this site as it is offered to you; you may not copy, modify, redistribute or run your own instance of the software behind it. Nothing here restricts what you do with your own chart or with the classical material the report quotes — the texts are not ours and the report says where each statement came from.
We intend to publish the chart engine and the rule library as open source when the research programme behind this service publishes its results. That is a commitment about timing, not a licence granted today: until it happens, the paragraph above is what governs. When it does happen it will cover the engine and the rules — the parts the research rests on — and not this application.
10. Complaints and contact
This service is a programme administered by Avagatham Technologies Pvt. Ltd., A-2, First Floor, Vijay Court, 2 Balfour Road, Kilpauk, Chennai 600 010.
Write there with a complaint, a data-protection request, or a request for a copy of what is held about you. That includes a complaint about the part of §5 that cannot be erased — the register entry — which is the one thing here you cannot resolve yourself, and so the one most worth having a route for.
11. Features that ask for more than this
Some parts of this software collect something beyond a birth chart, and each of those asks separately rather than relying on this page. At present:
- Rating your own past periods. The report can ask how each past period of your life actually went, record your answer, and only then show what the classical texts say about that period. You may also write a note in your own words beside any rating, and a note can say far more about you than a rating does — so it is covered by the same opt-in and removed by the same erasure. That is self-reported information about your life and it has its own notice and its own opt-in. Erasing your data removes your ratings and your notes. What survives is the record of which periods were shown to you, for the reason given in §5 — not what you said about them.
- Using what you tell us to improve the model. Separate again, and separately refusable. If you agree, your ratings and notes may be used to train a model that makes this service's readings better. If you do not, nothing you enter is used for it, and the readings you get are what the classical texts say and nothing more — which is the whole service as it stands today, not a reduced version of it. A model trained on your data cannot unlearn it. Erasing your account removes your ratings, your notes and your charts; it cannot remove what a model has already learnt from them. You should decide this knowing that, which is why it is said here and not after.
These are three separate agreements and you may give one without the others. Computing and keeping your charts is the service and is covered by this page. Rating your periods is an opt-in. Letting those ratings train a model is a second, independent opt-in. Declining either one costs you nothing but that feature: the chart, the dasa and everything the classical texts say about them are yours either way.
A feature that collects something new asks for it separately, in advance, and works without it if you decline.