1. Who this policy covers
Atithi Pro is used by two kinds of people, and their data is treated differently:
- Hotel users — owners, admins and staff who create an account and operate the app. For this data, we are the data fiduciary under the Digital Personal Data Protection Act, 2023 (“DPDP Act”).
- Hotel guests — people whose details a hotel records during check-in. Here the hotel is the data fiduciary (it decides to collect the data to meet its legal obligations), and Atithi Pro processes that data on the hotel's behalf. Guests should direct requests about their data to the hotel they stayed at; we assist hotels in fulfilling them.
2. Data we collect
From hotel users
- Name, mobile number and role, verified via SMS OTP at login.
- When you open the app. We keep a simple record of when your account opens Atithi Pro and which app version it is running. It helps us fix problems faster, check that updates have reached your phones, and see how many people use the app each day. It never includes your guests' details, your location or your contacts. We never sell it or use it for advertising, we don't use it to rate or monitor individual staff, and it is deleted automatically after about 13 months.
- Property details you configure: hotel name, address, GSTIN, logo, rooms, pricing, invoice settings, staff list and permissions.
- Your hotel's location — only if you ask for it. If you tap “Use my current location” while setting up the property, the app reads your device's location once, converts it into a street address to fill the form for you, and saves that address (with its coordinates) to your property profile. You can always skip it and type the address yourself. See section 3.
- Subscription and payment status. Purchases made in the Android app are processed by Google Play; payments on our website or desktop app and payment links are processed by Razorpay. We never see or store your card, UPI or bank credentials.
- A record of your consent: when you agreed to these terms and this policy, and which version (see section 12).
- Crash reports and basic diagnostic data needed to keep the app working reliably: what went wrong, the phone model, Android and app version, and anonymous account and hotel IDs. Never guest data.
About hotel guests (entered by the hotel)
- Guest register details: name, address, date of birth, mobile number, ID document type and number, travel details, room, stay dates and payment records.
- Images of identity documents (such as Aadhaar, PAN, Driving Licence, Voter ID or Passport) captured by hotel staff during check-in.
3. Device permissions
The app asks for a device permission only when a feature actually needs it, at the moment you use that feature. You can refuse any of them, or withdraw them later in your phone's settings — only the feature that needs the permission stops working, not the rest of the app.
- Camera — to scan and photograph guest ID documents at check-in. The camera opens only when staff start a scan.
- Photos — the app does not ask for access to your whole photo gallery. To use an existing ID photo instead of scanning, it opens Android's built-in photo picker, where you choose the one image to share. Saving the documents the app produces (guest register PDFs, GST invoices, reports) to the device needs no permission on recent Android versions; older versions ask for storage access the first time. A hotel can also switch on Auto-Save ID Images (off by default, set per device), which keeps a copy of each scanned ID in that phone's own photo gallery. Those copies belong to the hotel and never leave its device — so the hotel decides how long to keep them and is responsible for securing and deleting them.
- Location — used once, during property setup, and only if you tap “Use my current location”. It fills in your hotel's address so you don't have to type it. The address — and the coordinates it came from — are then saved to your property profile; the address is what prints on your invoices and reports. We do not track your location in the background, do not collect location from guests, and never use location for advertising or profiling.
- Notifications — to send operational reminders only: a govt guest report still pending, the monthly guest-register download before older ID images are cleared, offline entries finishing sync, and subscription or service notices. We never send marketing pushes.
- Microphone — the app does not use the microphone and does not ask for access to it.
4. How we use data
- To operate the guest register, room board, daybook and invoicing.
- To auto-fill your state's official guest-reporting portal (for example, Gujarat's Pathik system) at the hotel's explicit direction — this is the hotel submitting its own legally required record, with typing automated.
- To extract text from ID images using AI (see section 5).
- To provide support, process subscriptions and send service messages (OTP, billing, critical notices).
We do not sell personal data. We do not use guest data for advertising or marketing. Ever.
5. AI processing of ID images
When staff scan an ID, the image is sent to Google's Gemini API solely to extract the text fields (name, address, document number) for the entry form. This happens under Google's paid API terms, under which submitted content is not used to train Google's models. The extracted text is shown to staff for review before anything is saved.
6. Storage & security
- Data is stored in a managed cloud database (Supabase) with encryption in transit and at rest.
- Every hotel's data is isolated by row-level security — one property can never read another's records.
- Staff access is limited by per-screen permissions set by the hotel admin.
- Aadhaar numbers are kept so the hotel can file its official guest report and recognise a returning guest, and are masked to the last four digits wherever they are printed or exported (registers, reports).
- If a personal data breach affects you, we will inform you and the Data Protection Board of India as the DPDP Act requires, and report it to CERT-In as Indian law requires. Where it concerns guest records, we inform the affected hotel without delay.
7. Retention & automatic deletion
Retention follows the principle of the DPDP Act: keep data only as long as its purpose requires.
- App-open records (which account opened the app, when, and the app version) are deleted automatically after about 13 months.
- Guest register text (name, address, document number, dates) is kept for the period state lodging and guest-reporting rules require hotels to keep guest records (typically 3–5 years). Invoice records are kept for the 6 years Indian GST law requires. We are adding automatic deletion once those periods end; until then, a hotel can ask us to delete records it no longer needs to keep.
- ID images are deleted automatically, every night, once a stay is 90 days past checkout (the default window), because long-term storage of Aadhaar copies is a risk, not a feature. The written guest record (name, address, document number, dates) is kept, and hotels download a monthly Guest Register PDF so their legal record stays complete. A few images are held longer, and only as long as needed: a guest who stays again keeps theirs until 90 days after the latest stay; a month whose Guest Register the hotel has not downloaded yet gets 30 more days; and where a hotel files guests with a police portal (such as Pathik), a guest not yet filed is kept up to 90 more days so the filing can still include their ID, then deleted regardless. A hotel can ask us to delete ID images sooner at any time. This covers the copies we hold; if a hotel has switched on Auto-Save ID Images (section 3), the copies in its own device gallery are the hotel's to keep or delete.
- Hotel user accounts are kept until deleted — see Delete your account.
8. Sharing
We share data only with the services needed to run Atithi Pro:
- Official state guest-reporting portals (such as Gujarat's Pathik system) — at the hotel's direction, for its legally required guest reports.
- Google Play — subscription purchases made in the Android app.
- RevenueCat — keeps the record of Google Play subscription purchases (a purchase receipt and an anonymous hotel ID; no guest data).
- Razorpay — payments on our website, desktop app and payment links.
- Google (Gemini API) — ID text extraction, as described above.
- Google Firebase — OTP delivery for login, and crash reports (Firebase Crashlytics; no guest data).
- Supabase — database and file storage infrastructure.
- Resend — sends payment receipts and account emails to the hotel's email address (the hotel name, plan and amount; no guest data).
- Expo — delivers the app's push notifications (a device notification token only).
Each provider receives only what its function requires. We may disclose data if required by law or a valid government request, and we will tell the affected hotel unless legally barred from doing so.
9. Your rights
Under the DPDP Act you may:
- Access a summary of your personal data we hold;
- Correct inaccurate or incomplete data (most of it is editable in-app);
- Request erasure, subject to the legal retention duties above;
- Nominate a person to exercise these rights on your behalf;
- Raise a grievance and, if unresolved, complain to the Data Protection Board of India;
- Withdraw your consent at any time by deleting your account (Settings → Account → Delete my account, or this page). Withdrawing doesn't undo processing already done, or remove records the law requires us or the hotel to keep.
Guests should contact the hotel they stayed at first (it controls the record); we support hotels in responding.
10. Children
Atithi Pro accounts are for adults (18 and over) operating a lodging business. Guest records may include details of children, or of persons who have a lawful guardian, where the law requires a hotel to record every guest — these are entered by the hotel, usually with the parent or guardian present, and used for its legal compliance only.
11. Grievance officer
Vishal Patel · support@atithipro.in · +91 95582 86341 · India. We acknowledge grievances within 72 hours and aim to resolve them within 7 working days.
12. Your consent and changes to this policy
You agree to this policy and our Terms of Service by ticking the “I agree” box when you sign up; staff and existing users are asked once in the app. We record the date and the version you agreed to. We will update this policy as the product and the law evolve: when a change is material, the app shows it and asks you to agree again before you continue, and the “last updated” date is revised.