Privacy

Last updated 7 September 2026

This page describes exactly what we collect and what happens to it. It is written to be read, not to be survived.

What we collect

• Two sets of birth details — date, time and place of birth, and a first name for each person. We do not ask for a surname and we do not store one.
• What you were told — the verdict you received and who gave it, in your own words. This shapes the report.
• An email address, to deliver the report and answer you if you reply.
• Your phone number — used to take the payment and to reach you if your email bounces. Never used for marketing calls or messages, and never shared with anyone but the payment provider.
• Payment confirmation from our payment processor. We never see or store your card or UPI details.
• Basic site analytics — Google Analytics starts when a page loads so we can understand traffic, content use and the report funnel. It receives a finite public page or tool identifier; the kind of information a tool needs; a closed category saying what information a visitor tells the tool finder they possess (never the values themselves); bounded codes for validation or calculation failures; whether a result rendered; and which public article, related tool, sample-report link or start-report link was used. We count a public content view. We count a report-invitation exposure only when its marked link is actually at least half visible. An engagement guardrail is recorded only after the page has been open in a visible tab for at least 30 seconds after analytics starts and you have reached halfway down it. These events contain a finite content identifier, content type and language, a bounded CTA placement and destination, and the footer_sample_v1 experiment arm (control or sample_first). Tool starts and completed results carry that same bounded experiment arm and language. A completed-result event is sent only when the same tool and language first captured a start in this page load, and one start can produce at most one measured completion. A sample or report-start click is counted only after its exact visible CTA exposure has been successfully counted. The assignment lasts only in this tab’s JavaScript memory: it is not put in a cookie, local storage or session storage and is not a device identifier. We also measure the report funnel using bounded events: opening the start page, completing a numbered intake step, the name of a field with a validation error, opening or leaving checkout, requesting the sample, and payment confirmation. A checkout or purchase event may carry the order reference and price, but never a name, email, phone number, birth detail, form value, report text or finding. For public pages we may also send LCP, INP and CLS—the three Core Web Vitals—with a finite page identifier, bounded rating and rounded measurement. We never send the metric’s browser-generated unique ID, a raw URL, referrer or performance entry. If a page finishes measuring before Google Analytics is ready, at most those three finite values wait in this tab’s volatile memory; they are never written to browser storage and are sent when the analytics destination is ready. Public-page events use a finite page identifier and a page location without its query string. Google Analytics may assign browser and session identifiers; its first-party identifier is set to expire after 90 days and is not extended on every visit. Google signals and advertising personalisation are disabled. Google Analytics receives manual public-page views and only the bounded events described here; it does not receive names, contact details, birth details, form values, report text or findings.
• Optional product analytics — if PostHog is configured, it loads only after you choose additional product analytics. It receives the same bounded event types. We disable its automatic page views, click capture, heatmaps, session recordings and person profiles.
• Advertising measurement — for the India-only launch, Meta Pixel and bounded campaign attribution operate when you visit unless you turn analytics off below. This includes the landing path and referring page; campaign labels (utm_source, utm_medium, utm_campaign, utm_content and utm_term); advertising click identifiers (gclid, gbraid, wbraid, fbclid and msclkid); Meta browser identifiers (_fbp and _fbc) when those Pixel cookies exist; and the checkout request’s IP address, browser user-agent and source URL. We keep these fields with the order to attribute a completed purchase, avoid counting the same conversion twice, and help Meta match the purchase to the advertising interaction. If you turn analytics off, our server drops both the browser-supplied attribution and that request context instead of storing them.

Your analytics choice

You can stop Google Analytics, Meta Pixel and advertising attribution on this browser without interrupting your visit or your ability to buy a report. The setting lasts for one year on this browser and can be reversed here.

Turn off analytics on this browser

The second person

One of the two people in a matching report is usually not the customer. We treat their birth details as belonging to them: they are used to produce the report and for nothing else, they are never used for marketing, and they are erased on request from either person.

What we do not do

• We never sell or rent your data, and we never give it to anyone who wants it for their own purposes. Preparing and delivering the report involves the service providers below and our outsourced astrologer review arrangement.
• We do not put names, birth dates, birth times, places, birth stars, form values or calculated findings into analytics. The organic events use only the bounded identifiers and error categories listed above.
• We do not add you to a marketing list.
• We do not build a profile of you across other websites.

Who else touches it, and what they get

The technology providers are named below. An astrologer through our outsourced review arrangement also checks your report before delivery and therefore has access to the report and the birth details it contains. The assigned reviewer may vary. Contact us before ordering if you have questions about this review arrangement.

• Razorpay — takes the payment. Gets your name, email, phone number and the amount. Card and UPI details go to them directly and never reach our servers.
• Resend — sends the emails. Gets your email address and the text of what we send you. Never any birth detail.
• Supabase — the database and file storage. Holds everything we store, including both sets of birth details and the report.
• Vercel — runs the website. Gets the usual request records: IP address, browser, which page.
• Cloudflare — tells people apart from bots at the checkout. Gets the same request records, on that page only.
• PostHog (EU-hosted) — if configured and you permit additional product analytics, measures the bounded tool, reading and page-performance events listed above. Gets those event identifiers plus anonymous device and session identifiers; never birth details or form values.
• Google Analytics — measures manual public-page views and the bounded product and purchase-funnel events described above. Gets those event parameters plus Google’s browser, device and session identifiers; never names, contact details, birth details, report text or findings.
• Google Ads and Meta — provide advertising measurement for the India-only launch unless you turn analytics off. For a completed purchase, they may receive the applicable click and browser identifiers listed above, IP address, user-agent, source URL, order reference and purchase value. Meta may also receive a one-way hash of the buyer’s email for purchase matching. Neither receives names, birth details, report text or findings. These providers process the conversion under their own advertising and measurement terms; we do not sell the data to them or permit unrelated use through our site.

Parts of the written explanation may be drafted with the assistance of a third-party AI service; where that happens it is disclosed in the report itself. If you agreed to advertising measurement, Meta may also receive a record that a purchase happened, with the matching identifiers described above — but never birth details, report text or calculated findings. Turning analytics off prevents future browser and server events.

How long we keep it, and what erasure actually erases

Your report and the birth details behind it are retained so you can retrieve the report later. Ask us and we will erase them. Write to hello@doosrirai.in and it is done within seven days, with an email to confirm.

Site or product analytics already sent to Google Analytics or PostHog may be retained under those providers’ retention settings and deletion processes. Marketing attribution is retained with the live order only for the attribution and conversion-measurement purposes described above. An erasure request removes that stored attribution, including its click identifiers and request context, within the same seven-day process. Google Analytics, Google Ads and Meta may retain event or conversion data already sent to them under their own retention rules; ask us and we will help identify the relevant provider request route.

Four things do not go, and you should know what they are before you ask:

• The record that you bought something. The date, the amount and the reference. Indian tax and accounting law requires us to keep transaction records, and we cannot delete them on request. They contain no birth detail.
• Razorpay’s own copy of the payment. They are a regulated payment aggregator with their own retention obligations, and it is not ours to delete.
• Backups. Deleting from the live database does not reach into a backup taken last week. Those expire on their own schedule and are not searched or used for anything in the meantime.
• Emails already delivered. A report link we sent to your inbox is in your inbox. We stop the link working; we cannot unsend the message.

Everything else — both people’s birth details, the report itself, the stored file and any stored marketing attribution — is deleted, and your email address is masked in the transaction record so it can still be reconciled without identifying you.

If the second person asks for erasure, we do it on the same terms, and we do not tell the buyer who asked.

Your rights

You may ask what we hold, ask for a copy, ask for a correction, or ask for deletion. One person reads that address and answers it.

You may withdraw your consent for report processing at any time, and it is as easy to withdraw as it was to give — one email, no form and no reason required. Withdrawing it stops any further processing and we delete what we hold, subject only to the tax record described above. If you withdraw before the report is written, that is a full refund.

You may nominate someone to exercise these rights on your behalf if you die or become unable to act. Tell us who, and we will record it against your order.

These apply to both people in the report. Your partner did not fill in the form and may never have visited this site, and they may still ask us for a copy, a correction or deletion of their own details directly.

If we get it wrong

Complaints about how your data has been handled go to hello@doosrirai.in, addressed to our Grievance Officer, named below. We acknowledge within 48 hours and resolve within one month — those are the timelines the Consumer Protection (E-Commerce) Rules, 2020 set, and we are stating them rather than leaving you to look them up.

If we do not resolve it, or you are not satisfied with how we did, you may complain to the Data Protection Board of India. You do not need our permission and you do not need to tell us first.

Who operates this

Amol Pomane, Grievance Officer
Vmobify Solutions, a sole proprietorship firm, Hinjewadi Phase 3, Pune, Maharashtra 411057, India
GSTIN 27BELPP3493Q1ZG
hello@doosrirai.in
+91 89834 62134

Complaints are acknowledged within 48 hours and answered within 7 working days. That covers anything about your personal data — how it was collected, what we did with it, or a request to erase it — and anything about the report itself.