Privacy Policy — Navaniit Creation

Last updated: 2018-10-20

1. Who we are

Navaniit Calc is a numerology and Ramal calculator product of Navaniit Creation, operated by SG Tech, a proprietorship. We are based in India and the product is offered first to Indian users, with global expansion later. This Privacy Policy describes how we handle your personal data under India's Digital Personal Data Protection Act, 2023 (DPDPA). SG Tech is the Data Fiduciary for the personal data described here: it determines the purpose and the means of processing it.

2. What we collect

For your Numerology Report, we collect:

  • Name — used to compute the Chaldean numerology values from your letters.
  • Date of birth — used to compute Moolank, Bhagyank, Lo Shu Grid, Kua, Personal Year, and Sun Signs.
  • Gender — used to apply the gender-specific Kua and remedy rules in the calculation method.
  • Language preference — English or Hindi.
  • Email address — collected at account creation (sign-in identity), not on the report form. Generating a Numerology Report requires you to be signed in; we associate your saved reports with your account.
  • Mobile number at checkout — when you pay through the payment gateway we ask for a 10-digit Indian mobile number, which the gateway requires; we store it on your account so you are not asked again, and you can change or remove it through the Grievance Officer.
  • GST details for your tax invoice — at checkout every buyer chooses the State the purchase is supplied to, and a buyer who wants the tax invoice in a business's name may give that business's GSTIN, its registered name and its address. These are used for one purpose only: they are printed on the GST tax invoice for that order and decide which tax split it shows (CGST + SGST within our State, IGST outside it). They are stored on the order as a snapshot of what you declared at purchase, so a reprint matches the original. The State is also remembered on your account to pre-fill your next checkout.
  • IP address — used for rate-limiting and grievance traceability. We do not store the raw IP; we store only a HMAC-SHA256 hash.
  • Consent record — timestamp + HMAC hashes of your IP, the consent copy you agreed to, the privacy policy version, your browser user-agent string. NO raw name.
  • What you type into a calculator — the numerology tools (Lo Shu and Vastu grids, Personal Year, Maha Dasha, Complete Chart, Name Numerology, Mobile Number and the rest) compute on our servers, not in your browser. The name, date of birth or phone number you enter is sent to us to be calculated and the result is sent back. It is used for that calculation and is not stored: no database row is written, and the response is marked private and never cached. Tools were computed in the browser until August 2026; this section describes what happens now.
  • Saved Ramal readings (Ramal Calculator, subscribers only) — when you cast a reading, we save it to your account automatically so your history survives a reinstall or a second device. What is saved is the cast itself (the sixteen dice values and the method), the name you entered for the reading if any, and — where you asked a question — its house, its direction, and the question in your own words. The verdict, the timing and the answering figure are NOT saved; they are recomputed from the saved cast each time you open the reading, so later corrections to the method reach your history. The field that collects the question tells you it is saved.
  • Optional voice input (Ramal Calculator) — if you tap the microphone button, your spoken question is transcribed in your browser via the Web Speech API. On Chrome / Edge the audio is sent to Google for transcription; on Safari it is sent to Apple. We never receive your raw audio — only the resulting text, which is then sanitised and processed the same way as a typed question. You can use the tool without voice; typing is always available.

3. How we use it

  • To generate your Numerology Report.
  • To enforce the abuse-prevention rate limits that cap how many reports may be generated from one connection in a given period.
  • To respond to grievances and erasure requests under DPDPA §12 and §17.
  • To meet our compliance obligations.

Because generating a Numerology Report requires you to be signed in, it relies on the consent you gave when you created your account (the cross-border transfer, retention, and generation purposes in the sign-up consent). You can withdraw that consent at any time via the Grievance Officer (section 7).

We do NOT use your data for advertising, profiling, fine-tuning AI models, or sharing with third parties beyond what is described in section 4.

4. Who we share it with

To generate your Numerology Report, your name + date of birth + gender + language preference are sent to Anthropic, PBC in the United States, our AI provider. This is a cross-border transfer.

  • Anthropic operates under their published Commercial-tier terms, which contractually exclude your data from model training ("no-training tier").
  • Anthropic retains your data for up to 30 days under their default retention policy, after which it is deleted.
  • We have a signed Data Processing Agreement (DPA) with Anthropic. A copy is held on file at .claude/memory/legal/anthropic-dpa-signed.pdf and can be requested through the Grievance Officer.

Our payment gateway (a licensed Indian payment aggregator) receives your name, email, mobile number and the order amount to process a card / UPI / net-banking payment. It also receives an opaque customer reference — our internal user id, which is not your name and not your email — so that its record of the payment can be matched to your order. It does not receive your date of birth, your report or anything you typed into a calculator.

We do NOT share your data with any third party other than those named above. We do NOT sell your data. We do NOT use your data to train any AI model, including our own.

5. How long we keep it

  • The share link for a freshly generated Numerology Report: maximum 1 hour. While a report is being generated and for one hour afterwards, a copy sits in a temporary cache (Vercel KV) keyed by an unguessable link. After 1 hour that cache entry expires and is deleted automatically. This is a delivery buffer, not the record — the record is the account copy below.
  • Your saved Numerology Reports: generating a report requires you to be signed in, so a copy — your name, date of birth, the computed numerology data, and the report content — is stored durably against your account so you can revisit it under "My Reports". This account-linked data is protected by row-level security so only you can read it. To have it deleted, contact our Grievance Officer (see sections 6 and 7); we process erasure requests manually.
  • Your saved Ramal readings: kept for 2 years from the date of the reading, then deleted. They are protected by row-level security so only you can read them, and they are erased along with your account: deleting your account deletes every saved reading, including the question text, in the same operation.
  • Consent audit log: indefinitely, as a HMAC-hashed record (no raw PII). This is retained for DPDPA grievance defense. You may request erasure of the linkable hash via our Grievance Officer.
  • IP-hash for rate limiting: until UTC midnight on the day of the request (typically <24 hours).
  • Mobile number given at checkout: kept on your account until you ask the Grievance Officer to delete it or you delete your account.
  • GST details given for a tax invoice (GSTIN, registered name, address, State): kept with that order's tax invoice as a tax record for the period the law requires — 8 years, the same window as the invoice itself (GST Rules 56). Because the invoice is a record we are obliged to keep, these details are retained even after you ask for erasure or delete your account (DPDPA §8(7)): the order and its invoice stay, unlinked from the deleted account. The copy of your State kept on your account for pre-filling is deleted with the account.
  • UPI transaction reference (UTR) and tax invoice records: retained for 8 years as required by GST Rules 56 and RBI Master Direction on Digital Payments §6. After the retention window, UTRs are HMAC-hashed and the linkable record is deleted; the hash remains for compliance defence only. UTR values are not written to application logs.
  • Anthropic-side: up to 30 days, then deleted (their policy).

6. Your rights under DPDPA

You have the right to:

  • Access — request a copy of the data we hold about you.
  • Correction — request correction of inaccurate data.
  • Erasure (DPDPA §12) — request deletion of your data. Your saved Numerology Reports (name, date of birth, numerology data, and report content stored against your account) and your saved Ramal readings (including the question in your own words) are deleted on request: contact the Grievance Officer (see section 7) and we process the erasure manually within the timeline in section 7. For our consent and rate-limit logs we store only HMAC hashes (no raw PII), so erasure there means we redact your hash. Anthropic's 30-day retention on their side decays independently.
  • Grievance redressal (DPDPA §17) — file a grievance through the Grievance Officer (see section 7).
  • Withdraw consent — at any time, by contacting the Grievance Officer.

To exercise any of these rights, use the Grievance page and select the appropriate category.

7. Grievance Officer

Name: Navaniit Mandhaani Role: Grievance Officer (DPDPA §17) Contact: Through the Grievance page (preferred) or by email to the address listed there.

We aim to acknowledge your grievance within 7 days and resolve it within 30 days.

8. Cookies and local storage

We use:

  • A language preference cookie (lang=en|hi) — first-party, 30-day, non-tracking.
  • A consent-variant cookie (cb-variant=a|b) — first-party, 30-day, non-tracking. A/B-testing on consent-block layout only.
  • An authentication session cookie (__Host-navaniit_session, plus a _data companion) — first-party, HTTP-only, Secure, SameSite=Strict, 30-day maximum lifetime. Set when you sign in and required for every signed-in page; it identifies your session so we can show you your own reports and readings, and it carries no name, date of birth or reading content. Signing out clears it. It is strictly necessary for the service and is not used for tracking or advertising.

We do NOT use third-party tracking cookies. We do NOT use Google Analytics. We do NOT use Meta Pixel.

9. Security

  • All data in transit is encrypted (HTTPS/TLS).
  • API keys and secrets are stored encrypted and flagged Sensitive at our hosting provider (Vercel), never in our source code, and are rotated on a documented internal schedule that sets a separate interval for each secret. The runbook is an internal operations document rather than a published page; you may request a summary of it through the Grievance Officer.
  • All HMAC hashing uses a server-side pepper (AUDIT_LOG_PEPPER) that is never exposed client-side.
  • We do NOT log raw names, dates of birth, phone numbers, or generated report content. Our application code is written not to place them in logs, and this is enforced by review rather than by an automatic filter.

10. Children

Our service is for users 18 years of age or older, and the form has an explicit age-attestation checkbox. An adult may make a report for a child in their care, such as a parent for a son or daughter: the child's name and date of birth are then used only to make that report, and the report asks the child to read it with a parent or guardian. If you believe a minor has used our service on their own, please contact the Grievance Officer.

11. Changes to this policy

If we make a material change to this policy, we will update the version number and the "Last updated" date at the top, and post a notice on the home page for 30 days.

12. Contact

For any privacy concern, use the Grievance page.