Privacy Policy
The short version. To read your chart we need your date, time and place of birth, and we send those — together with your question — to Google's Gemini API, which writes the reading. We store your readings so you can return to them. You can delete any reading, or your entire account, at any time, and deletion is immediate and permanent.
This policy explains what Verdictly collects, why, who else sees it, and what you can do about it. Verdictly is operated by NexaCore Consultancy Services, a sole proprietorship registered in India ("we", "us"). It applies to verdictly.co.in and every page under it.
1. What we collect
When you sign in
We use Google Sign-In. Google sends us, and we store, only:
- your name
- your email address, and whether Google has verified it
- your Google profile picture (the link, not a copy)
- a Google account identifier, used to recognise you on return
We never receive your Google password, and we do not ask for or store one of our own. We request no access to your Gmail, Drive, contacts or any other Google service.
When you ask for a reading
- Date of birth, time of birth and place of birth. These are required to compute a chart; there is no reading without them.
- A name, if you enter one. Optional, and used only for display.
- Your question, and any follow-up questions you ask.
- The completed reading, so it is there when you come back.
Your place of birth is converted to coordinates and a time zone. Most Indian cities resolve from a list held on our own server. An unrecognised place name is looked up with OpenStreetMap's Nominatim service, which means that place name — and nothing else about you — is sent to them.
When you buy tokens
Payments are handled entirely by Razorpay. Your card, UPI or netbanking details are entered on Razorpay's own checkout and never reach our servers. We store only a record that a payment succeeded, its Razorpay payment identifier, and how many tokens it credited.
Automatically
Our web server and Cloudflare keep standard request logs — IP address, browser type, pages requested, timestamps — used to keep the service running and to investigate abuse. We do not run analytics, advertising pixels or third-party trackers, and we do not use cookies for advertising.
2. Cookies
We set exactly one cookie, vd_session, which keeps you signed in. It
holds a random token and nothing about you. Only a one-way hash of that token is stored
on our side, so our database cannot be used to impersonate you. It expires after 30 days
and is deleted when you sign out.
3. Who else sees your data
| Who | What they receive | Why |
|---|---|---|
| Google (Gemini API) | Your computed chart — planetary positions, periods and the like — and your question. Your name, email and account are not sent. | This is what writes the reading. |
| Google (Sign-In) | Handles the sign-in itself. | So we never handle a password. |
| Razorpay | Your name and email, plus the payment details you give them directly. | To take payment. They are an RBI-authorised payment aggregator. |
| MongoDB Atlas | Stores your account and readings. | Our database. |
| OpenStreetMap (Nominatim) | A place name, only when it is not in our own list. | To turn a place into coordinates. |
| Cloudflare and Hetzner | Network traffic and hosting. | To serve the site. |
We do not sell your data. We do not share it for advertising. We do not disclose it to anyone else except where the law requires it.
4. Where your data is held
Our server is located in Germany and our database is hosted with MongoDB Atlas. Using Verdictly therefore involves transferring your information outside India. We rely on the contractual protections offered by these providers. If you would rather your birth details were not processed this way, please do not use the service.
5. How long we keep it
- Sign-in sessions — deleted automatically 30 days after they are created, or immediately when you sign out.
- Readings — kept until you delete them or close your account.
- Payment records — retained as long as tax and accounting law requires, even after account closure. These contain no card details.
- Server logs — a short rolling window, then overwritten.
6. Your rights
Under the Digital Personal Data Protection Act, 2023 you may access, correct, or erase your personal data, and withdraw consent. Two of these are built into the product and take effect immediately:
- Delete one reading — open Saved readings and delete it.
- Delete your entire account — this permanently removes your readings, your sessions and your account record. It cannot be undone, and unused tokens are forfeited.
For anything else, including a copy of your data, write to us at the address in section 9 and we will respond within 30 days.
7. Security
The site is served only over HTTPS. Session tokens are stored as one-way hashes, not as the tokens themselves. Card details never touch our servers. Access to the database is restricted to our application server by IP.
No system is perfectly secure, and we do not claim otherwise. If you believe you have found a vulnerability, please write to us before disclosing it publicly.
8. Children
Verdictly is not intended for anyone under 18, and we do not knowingly collect data from children. If you believe a child has given us data, contact us and we will delete it.
9. Contact and grievances
For any privacy question, or to exercise a right above, contact our Grievance Officer:
Abhinash Anand
NexaCore Consultancy Services
Rajeev Nagar, Patna, Bihar 800011, India
Email: [email protected]
We acknowledge complaints within 48 hours and resolve them within 30 days, as required by the Consumer Protection (E-Commerce) Rules, 2020.
10. Changes
If we change this policy we will update the date at the top. Material changes affecting how we use your birth details will be announced in the app before they take effect.