Skip to content

Privacy Policy

What personal data we hold, why, who processes it for us, how long it is kept, and how to see, correct or delete it.

Effective 10 September 2026. LandSahi is operated by Legacy Technologies Private Limited. This document is written in plain English and is not legal advice; where it changes materially, the new date appears here.

1. Who is responsible

LandSahi is operated by Legacy Technologies Private Limited, which is the data fiduciary for the personal data described here under India's Digital Personal Data Protection Act, 2023. We collect the minimum the service needs, we say exactly what that is, and we do not sell personal data to anyone. Questions and requests go to legacytechnology.india@gmail.com or the grievance desk.

2. What we collect

  • Account: your email address and, where that channel is offered, your mobile number, whichever you sign in with. If you sign in with Google, the email address is the verified address of the Google account you pick, and it opens the same account a code sent to that address would. They are used to send you a one-time code, order emails and the reports you asked for. No passwords are stored. You may add the second channel so either opens your account and remove either as long as one remains.
  • Orders and payments: the parcel you ordered a report or document for, the package, the amount, the payment gateway's order and payment references, and the date the payment was confirmed; for an order on our earlier manual UPI rail, the UPI bank reference (UTR) you submitted. We never see or hold your card, UPI or bank credentials; you enter them in the payment gateway's own window.
  • Reports and documents: the generated report content and any government documents fetched for you, stored under your account.
  • Uploads: a record you upload for checking (a 7/12 photo or PDF, for example) is processed to produce your result and stored with it.
  • Messages: what you send through the contact form or by email, with the address you sent it from.
  • Technical data: your IP address and browser type are seen by the network edge and appear in short-lived server logs, as they do for every website.
  • Usage measurement: we record how the site is used on our own servers: which pages are opened, which buttons are pressed and which places people search for. It uses no cookie: a random identifier is held in your browser's session storage, discarded when the tab closes, and never sent to any other website. Page addresses are recorded with identifiers removed (a report reads as /report/[id], never its own address). We do not record report contents, names from land records, payment references or uploads. Where a search finds nothing we do record what was typed, because that is how we learn which areas to add next; those entries are deleted after 90 days, and entries that look like an email address or a phone number are discarded rather than stored. If you are signed in, this measurement is linked to your account so we can answer support questions about your own visit.

3. Why we use it

  • to sign you in and keep your reports attached to you (with your consent, given when you request a code);
  • to take your order, confirm your payment and deliver what you bought (performance of the contract you asked for);
  • to answer your messages and grievances;
  • to keep the accounts and tax records the law requires of a company;
  • to keep the site secure and detect abuse;
  • to understand how the site is used, through the measurement described above.

We do not use your data for advertising, do not build profiles for anyone else, and do not send marketing email. You can withdraw the consent you gave at sign-in by asking us to delete your account (section 8).

4. Public records about other people

Reports reproduce information from public government records: land records, the registration index, court cause lists, gazette notices. Those records name the people who hold, transfer or contest land. We reproduce them with their sources for due diligence, which is the purpose the records are published for; we do not build profiles of the people named, and corrections to a record must be made with the issuing authority. A person named in a record who believes we have misrepresented it can write to the grievance desk.

5. Who processes data for us

We run the service on our own server, and we use these providers for the parts we cannot do ourselves. Each sees only what its job needs.

  • Hosting (Hostinger, Mumbai, India): the server that runs the site and holds the database, reports and documents.
  • Network edge (Cloudflare, worldwide): every request to this site reaches our server through Cloudflare, which terminates the HTTPS connection and therefore sees your IP address, the address you requested and your browser type. There is no version of the site that does not pass through it.
  • Payments (Razorpay, India, through our IDFC FIRST Bank payment gateway account): takes the payment in its own window. It sees the amount, the order reference, the email address and mobile number on your account (we fill them in for you), and the payment details you enter. We keep only whether the payment succeeded and its references.
  • Email (Brevo, European Union): sends sign-in codes, order emails and grievance replies. It sees your email address and the message.
  • Sign-in codes on WhatsApp (MSG91, India, and Meta, worldwide): only where WhatsApp sign-in is offered and you choose it. MSG91 passes your one-time code to WhatsApp, which delivers it; both see your mobile number and the message, which holds only the code.
  • Sign in with Google (Google, worldwide): only if you choose it, and only where the button is offered. Google tells us the verified email address of the account you picked and nothing else; we tell Google nothing about you beyond the fact that you chose to sign in here. The page loads no Google script for this; you are sent to Google and back.
  • Machine reading (OpenRouter and the model providers it routes to, mostly in the United States; Google, for a tie-breaking read): images and text of land records, including records you upload, are sent to these providers to be read, summarised or answered about. They receive the record and your question, never your name, email address or account. Captcha images from government portals go the same way.
  • Government portals (Maharashtra): our server queries the official portals with the parcel identifiers you chose. Paid documents are bought in our own portal account on your behalf; the portal does not learn who you are.

Some of these providers process data outside India. We send them only what the task needs, under their published terms, and nothing in this list is used by them for advertising.

6. Third parties your browser talks to directly

  • Esri (satellite map imagery): tiles are fetched directly from Esri's servers, so it sees which map areas you view. Cadastral plot outlines are served through us, not by Esri.
  • Razorpay (only on the checkout page of an order you are paying): the payment window loads from Razorpay, and inside it Razorpay runs fraud checks that load from Stripe, Sardine and hCaptcha. They see your device and browser details and what you enter in that window, under Razorpay's terms.
  • Google Translate (only if you press EN on a Marathi report): the widget reads that page's text, including owner names and deed parties, and sends it to Google to translate. It is off unless you press EN and is never loaded for the PDF export.
  • MahaBhunaksha (older reports only): reports generated before we began proxying the government cadastral overlay load it from mahabhunakasha.mahabhumi.gov.in directly.
  • Google Analytics (only where configured, and only after you allow it on the cookie notice): described in the cookie policy. Where it is not configured, nothing from Google Analytics loads.

7. Cookies and browser storage

The complete list, with what each item is for and how long it lasts, is the cookie policy. In short: one cookie for your sign-in session, one for your language, a ten-minute one while you sign in with Google, the theme and your cookie-notice choice in local storage, the items Razorpay's payment window sets while you pay, and no advertising cookies of any kind.

8. How long we keep data

  • Sign-in codes: 15 minutes. Sign-in links: 7 days, single use. A Google sign-in in progress: 10 minutes. Sessions: 30 days, or until you sign out.
  • Account, reports, documents and uploads: for as long as your account exists, then deleted on request (section 9).
  • Order and payment records: for as long as tax and company law require, currently eight years, even after an account is deleted.
  • Zero-result search text: 90 days. Other usage measurement: kept in aggregate; linked to an account only while the account exists.
  • Server request logs: rotated within days.
  • Backups: nightly copies of the database and the evidence files, kept for seven days on a rolling basis, so a deletion reaches the last backup within a week.

9. Your rights and how to use them

You can ask for a summary of the personal data we hold on you, ask us to correct it, ask us to delete your account and its data, withdraw the consent you gave at sign-in, and nominate a person to exercise these rights for you if you are unable to. Write from your registered email address to legacytechnology.india@gmail.com; writing from the registered address is how we confirm the request is yours, and we will not act on an account request from any other address. If your account has no email address on it, add one under Sign-in methods on your orders page first. We acknowledge within 1 business day (IST) and resolve within 30 days, and where a request depends on a government portal or a bank reconciliation we tell you why and when. Deletion removes your account, your reports, documents and uploads; order and payment records stay for the period the law requires, detached from any account. Unresolved data complaints may go to the Data Protection Board of India after you have raised them with us.

10. Security

The site is served only over HTTPS. Session cookies are HttpOnly and Secure. There are no passwords to leak. The application runs in isolated containers with the least privilege each needs, secrets live outside the code, and access to the server and the operator console is limited to the operators named for it. Public records are stored, as they must be, but your account identifiers, payment references and uploads are never shown to anyone but you and the operators. If a breach affecting your personal data ever occurs, we will tell you and the Data Protection Board of India as the law requires.

11. Children

The service is for adults. We do not knowingly collect personal data from anyone under 18, and an account found to belong to a minor is deleted.

12. Changes

When this policy changes materially, the effective date above moves and account holders are emailed before the change takes effect. The version at this address is always the current one.

13. Governing law

This policy is governed by the laws of India, with courts in Maharashtra having exclusive jurisdiction, subject to any forum the law gives you. Your use of the service is also governed by the Terms of Use.