Privacy policy

The short version: rent pins carry no identity, we never store your raw IP address, content pages (not the map) carry Google ads that set advertising cookies, and we never sell your data. The longer version is below.

What we collect

• IP address. Read from your request and immediately turned into a salted hash for anti-abuse (rate limits, and de-duplicating reports and ratings). The raw IP is never stored and the hash is never shown or linked to your identity.
• Location. The point you tap is rounded to about 100m before it is saved. The precise location is never stored. The optional “show my location”control asks your browser for your device’s current location to centre the map on you — it is used in your browser only, never sent to us, and never stored. Your device or browser may use its own location service to work out where you are.
• Rent and listing details. BHK, rent, furnishing, water source, an optional one-liner, and the like. Shown publicly (except contact fields). On the map feed the timestamp is coarsened to a date.
• Email. Required when you post a listing (so we can send you your private manage link and callback notices) or when you watch an area (so we can send alerts). Kept server-side only, never shown on the map, never in a public API, never sold. Every email has an unsubscribe link.
• Contact you volunteer in a callback. If you request a callback on a listing, the phone or email you type is stored and shown only to that one listing’s owner. Sharing it is your choice.
• Owner phone (optional).A poster may add a phone number and choose to show it directly. It is kept server-side and revealed only to a signed-in seeker who unlocks it on that listing — never on the map or in a public API. If the box is left off, the number is never exposed.
• Ratings and reports. A 1–5 locality or build score, or an abuse report, de-duplicated by your IP hash.

Rent pins themselves carry no name, email, or phone. Nothing on the map traces to a person.

How contact sharing works

There is no automatic matchingand no bulk contact exchange. The rent map carries no contact at all, so there is nothing to share. In the marketplace, a poster’s contact is private by default: a seeker leaves their ownphone or email through “request a callback”, that contact goes only to that one listing’s owner (read from a private manage link, and by email if they opted in), and the owner calls back.

A poster may instead choose to show their own number directly. When they opt in, that number is revealed only to a signed-inseeker who taps “show number” on that listing — never on the map, never in a public API, and never in bulk. Each reveal is rate-limited and logged, and it is the poster’s decision, per listing.

We never cc these to ourselves, and we never share contact with brokers, advertisers, or any third party outside this flow.

Third-party services

• Protomaps.The map draws from a basemap file we host ourselves; its fonts and icons load from Protomaps — the only third-party host your browser contacts for the map’s tiles and labels. No Google Maps, no API key, no per-request tracking. (If you tap “show my location”, your device may separately use its own location service to find you — that is your browser or operating system, not us.)
• Email delivery. When email is enabled, we hand the recipient address and message to an email provider (Resend) solely to deliver mail you asked for.
• Hosting, and where your data lives. The app and its database run on a server we control, hosted with Railway. That server is located in the United States, so data you submit is stored and processed outside India. It is not held in a third-party cloud database, and it is not shared with anyone beyond the providers named here.

We keep one lightweight first-party metric: a daily visitor count that records the anti-abuse hashed IP once per day — no cookies, no raw IP, aggregate counts only, nothing about an individual stored or exposed. The only third-party code we load is Google AdSense, on content pages (see Cookies below). We use no separate analytics service, and no Supabase or IP-lookup services.

Cookies

The rent map needs no login and sets no cookie. If you sign in with Google to post a listing or request a callback, we set one essential cookie - a session token that keeps you signed in; nothing more. (The moderation tool stores its access token in the moderator’s own browser; this never applies to public visitors.)

Advertising.Some content pages (not the map) carry a few sponsored ads served by Google AdSense, which helps keep the site free. Google sets cookies to show and measure these ads. Where the law requires it - the EEA, the UK, and California - you’ll see a consent prompt (Google’s own) before personalised ads run, and can decline. Wherever you are, you can control or turn off ad personalisation at myadcenter.google.com, and clearing this site’s data removes its cookies. Apart from the cookieless daily visitor count described above, we run no other analytics, and we never sell your data.

How long we keep it

• Rent pins: until you delete them, or until 3 distinct reports auto-hide them.
• Listings: until you mark them rented or delete them from your manage link.
• Emails (area watch, listing notifications): until you unsubscribe, or the listing is removed.
• Callback contact: with the listing, removed when the listing is deleted. Once the owner has seen it, we cannot recall what they noted down.
• IP hashes: retained for abuse prevention. As salted hashes with no stored raw IP, they cannot be traced back to you.
• Account (if you sign in to the marketplace): your Google email, name, and account id, kept while the account exists - write to us to delete it. Sign-in sessions expire after 30 days or when you sign out.

Your rights

• Access. Ask what data we hold that relates to you, and what we have done with it.
• Correction. Edit a listing any time from its manage link. A rent pin cannot be edited - it is a record of what someone paid, not a profile - so correct one by deleting it and pinning again, or ask us and we will fix it.
• Deletion.Delete your own pins any time: open the pin and choose delete. Because a pin carries no account and no email, the only proof it is yours is a secret your browser saved when you posted it, so this works from the device you pinned from. Clear that browser's storage, or pin from a different device, and we can no longer tell it was you - write to us and we will remove it. Listings are deleted from their manage link. Deleting a pin erases the row outright; we do not keep a hidden copy. Because pins carry no identity and IPs are only ever stored hashed, there may be nothing else that identifies you to erase.
• Withdraw consent. Unsubscribe from any email through the link it carries. Withdrawing is as easy as giving consent was.
• Complain. Write to us first (below) and we will respond within 30 days. If you are in India and are not satisfied, you may escalate to the Data Protection Board of India.
• We never sell, rent, or trade personal data.

Security

Everything is served over HTTPS. Coordinates are rounded before storage, IPs are stored only as a salted hash, and the server refuses to start in production without a secret salt. Rate limits, a daily read budget, and low-zoom aggregation resist bulk scraping. Sign-in is delegated to Google, so we never see or store a password; sign-in sessions are kept only as a hashed token. There is no password store to breach.

No system is perfect. If a breach ever affects your personal data, we will notify you and the relevant authority without undue delay, and say plainly what happened and what we are doing about it.

Children

This service is meant for adults renting homes and is not directed at children. Please do not submit a pin, a listing, or an email address if you are under 18. We do not knowingly collect data from children, and we will delete it if we learn we have.

Contact, grievances, and changes

For any question about how your data is handled, to exercise any right above, or to raise a grievance, write to [email protected]. That address reaches the person responsible for data protection on this project, and we aim to reply within 30 days.

We may update this policy. If a change materially affects how we handle your data, we will say so at the top of this page rather than quietly revise it.