Privacy policy
This is a draft. It describes what the app actually does, which is the hard half — but it has not been read by a lawyer, and the organisation named in it does not exist until you set LEGAL_ENTITY and the grievance officer settings. Do both before listing on Google Play.
Last updated: 15 October 2026
Who this is about
MyHampi is a guide to Hampi and a directory of the people who work there — guides, drivers, guesthouses and restaurants. It introduces two people and then steps back. No money passes through it and no prices are set by it.
What is collected, and why
Your account. A phone number or an email address, whichever you sign in with, the photograph your Google account shows if it has one, and a name if you give one. This exists so your trips and favourites are still there on your next phone, and so the people who run MyHampi can find your account when you ask them for help. Sign-in is handled by Supabase; the password is never seen by this app.
Where you are, while the app is open. Used to show what is near you, to work out how far away things are by road, and to give directions. It is sent to the server when you search for something nearby, ask how far a place is, or ask for a ride, and it is not stored against your account — except that a trip plan you save, if it starts from "My location", keeps that starting point until you delete the plan. The server passes the start and end points of a route to a routing service (listed below) without your account or your phone's address. Refusing the permission turns off "what is near me" and leaves everything else working.
If you switch on nearby-monument alerts, the app keeps watching your position while it is in the background so it can tell you when a monument is close. That position stays on your phone; it is compared there against the list of places and is not sent to us.
A driver's position, while on duty. A driver who goes on duty sends the phone's position regularly, including while the app is in the background, for as long as they stay on duty. It is used to offer them rides near where they are. During a trip it is shown to one person — the visitor on that trip — and only until the trip ends. Only the latest position is kept, not a trail, and it is deleted when the driver goes off duty or when the phone stops reporting for fifteen minutes.
The emergency button. Pressing it dials 112 first. The app then records that the button was pressed: when, where the phone was if it could tell, whether somebody was signed in, and which trip it happened on, if any. This is kept so that afterwards the question of who was on that trip and where can be answered — for the person who pressed it, their family, or the police. It is not deleted when a trip ends or an account is closed, and no fixed deletion date has been set for it yet. Closing your account takes your account off it; the record of the press stays.
What you ask for. Searches, the itineraries you build, the places you favourite. Searches that found nothing are recorded without your account attached, so that missing places can be added.
What you write. A review of a monument or a partner is published under your name. A report you make about a partner is read by the people who run MyHampi. The messages the app sends you — booking confirmations, reminders — are kept in your inbox in the app.
A booking. When you ask a guide or a guesthouse for a date, they are given your name and phone number so they can ring you back — that is the whole point of the request, and it is the only time your number is shown to anyone. A ride also records where to pick you up and where you are going. If you cancel, the reason you give is shown to the partner. Your name, number, message and reason are removed from settled bookings after six months, or the moment you close your account.
Which days you used the apps. When you are signed in, the server notes that you used the visitor app or the partner app on a given day — that you did, not what you did. It is how we count how many people use MyHampi, and it is only ever added up. Downloading an app from our website is counted the same way, with nothing about who downloaded it.
Your phone, for notifications. A push token, so a confirmation reaches you. Turning notifications off removes it.
Photographs, if you are a partner and upload them. Location and camera metadata are stripped from every image before it is stored.
Your passport photos, if you add them. When you mark a place as visited in the Hampi Passport you may keep up to two of your own photographs of it. They are stored on our own server, not in a public folder: only you, signed in, can see them. There is no screen anywhere, ours included, that shows them to anybody else. Location and camera metadata are removed before a photo is stored, as a fresh copy up to 2048 pixels across. Collages and pages you export from them are made on your phone and go only where you choose to share or save them; they are never sent to us. Which places you have stamped stays on your phone, except that a place you add a photo to is, by having that photo, known to the server too. Delete a photo and it is gone; close your account and all of them go with it.
Identity documents, if you register as a partner. A licence or ID is read by a person to check you are who you say, is never shown to a visitor, and is deleted ninety days after the check.
What is not collected
No advertising identifiers. No third-party analytics or advertising SDKs. No contacts, no photo library beyond the images you choose, no microphone except while you are using the voice guide. No background location except the two described above, each of which you switch on yourself.
Who else sees it
- Supabase — sign-in and file storage. A sign-in code reaches your phone through the text-message service Supabase is set up to use.
- Google Firebase — push notifications only.
- Map and photograph servers — the map is drawn from pictures fetched by your phone from CARTO, Esri (the satellite view) and Mapbox, and monument photographs come from Wikimedia Commons. Each of these sees your phone's internet address and which part of the map or which photograph was asked for, the way any website does. Nothing else is sent to them.
- Routing and place-search services — the OpenStreetMap community servers (Valhalla and OSRM), Komoot's Photon, and Google Maps when it is switched on receive the start and end points of a route, or the name of a place being looked up. They are asked by our server, so they see neither your account nor your phone.
- A text-message service (MSG91 or Twilio) — a partner's new contact number, to send the code that proves it.
- Anthropic — the text of what you ask the AI guide, so it can answer, and the interests you choose when it plans a trip. Your account is not sent with it.
- Sarvam AI — the sound of your voice while you use the AI guide's voice mode, to turn it into text and to read the answer aloud. Your account is not sent with it, and we do not keep the recording.
- Sentry — reports of crashes and errors in the apps and on our server, so they can be fixed. Phone numbers, email addresses, sign-in tokens, precise locations and file paths are taken out before a report leaves the phone or the server, what you type is never attached, and no report is tied to your account.
- A guide, driver or guesthouse — your name and number, only on a booking you made, only for that booking. A driver also sees the pickup and drop-off points of the ride.
Nothing is sold, and nothing is shared for advertising.
How long it is kept
| What | How long |
|---|---|
| Account, favourites, itineraries | Until you close your account |
| Your passport photos | Until you delete them or close your account |
| A booking's dates and status | Kept as the partner's record of their work |
| Your name and number on a booking | Six months, or until you close your account |
| Partner identity documents | Ninety days after the check |
| Push token | Until you turn notifications off |
| The days you used the apps | Until you close your account |
| A driver's position | Until they go off duty |
| An emergency-button record | No fixed date yet; not deleted with the account |
Your rights
Under the Digital Personal Data Protection Act, 2023 you may ask what is held about you, have it corrected, and have it erased.
The first and third are in the app: Account → Your data, which lists what is held, and Close account, which erases it — your sign-in included, so the phone number or email address you signed in with is deleted too. In the MyHampi Partner app it is Account → Delete my account, and it does the same. A partner registration is closed with the account: listings come down, and documents, photographs, number and business details are deleted. Closing is refused while a booking is still being arranged, because erasing your number then would leave a guesthouse holding a room for somebody they cannot ring. Cancel it first. Any phone still signed in to the account is signed out within a minute.
Without the app, the same erasure is at the account deletion page. It sends a code to the phone number or email address you sign in with, to check the account is yours.
Settled bookings are not deleted — they are the partner's record of work they did — but your name, number and message are removed from them.
Children
Not intended for children under 18. No account is knowingly created for one.
Grievances
A named officer is required by law to answer complaints about your data within thirty days. No grievance officer has been named yet. This app is not ready to be listed. Set GRIEVANCE_OFFICER_NAME, GRIEVANCE_OFFICER_EMAIL and LEGAL_ENTITY in the API's environment.
Changes
The date at the top changes when this does, and a notice appears in the app.