Privacy notice

You (the business that signs up) decide what you enter about your customers, guests and staff. INDRA, made by VritantaNextGen, stores it for you and shows it back to the people you give access to. Please enter only what you have a reason to keep, and tell your guests and staff what you keep.

• Your login: your name, email and role. Your password is never stored as text; only a salted scrypt hash is kept, which cannot be turned back into the password.
• Your business: its name, state, GSTIN and UPI ID if you add them, invoices, quotes, payments, expenses and the double-entry books.
• Customers and vendors: name, phone, email, GSTIN and address, as far as you fill them in, with leads, deals and notes.
• Guests (INDRA Stay): name, phone, email, nationality, ID type, the last four characters of an ID, passport or visa number, where they arrived from and where they go next (the Form C fields), their dates, room, notes and folio charges.
• Staff (People): name, phone, email, designation, department, join and exit dates, salary, attendance, leave and payslips, and the last four digits of a bank account.
• Website enquiries: if your INDRA website has an enquiry form, the name, email, phone and message a visitor sends are stored for you.
• Receipts: a signed log of who did what and when, for example “Priya approved invoice 117”. See below.
• Pictures: images you upload for your website are saved as files on the server, and are served at public addresses so your website can show them.

At check-in you can enter a guest’s ID number. INDRA keeps only the last four characters, for Aadhaar, passport, visa and any other ID number. The longer number is cut down while the form is read, before anything is saved or written to a receipt. The screen then shows only “ending 1234”. For staff, the same idea applies to bank accounts: the last four digits only.

This means INDRA cannot print a full ID number back to you. If you need a copy of the ID for a legal reason, keep it the way you do today, and do not type a full ID number into a free-text note.

Guest phone numbers and emails are stored on the booking so your staff can reach the guest. They are shown to people in your business who can open the front desk. INDRA does not send messages to guests by itself. When you share a bill or a reminder on WhatsApp, INDRA only opens WhatsApp on your phone with the text filled in. You press send.

On the homestay hub, a traveller’s enquiry goes to the owner. A basic (free) listing shows the owner’s phone and email only after the owner gave consent on the listing form and the listing is live. A listing on INDRA Stay does not show its owner’s phone or email on the hub.

• indra_session keeps you signed in. It is signed, readable only by the server, sent only to this site, and lasts up to 14 days. Demo visits use the same cookie for a shorter time.
• indra_prefs is set only on demo visits, to keep the look you chose. It expires after 30 days.
• Your browser’s own storage remembers whether you last chose English or Hindi in the Ask bar, that you dismissed the “install INDRA” card, and a look you picked in the explainers. None of it is personal data.
• A service worker keeps INDRA’s pictures, icons and fonts on your phone so pages load faster, and a small offline page. It is written never to keep signed-in pages, forms or personal data.

INDRA has no advertising or analytics scripts. Its fonts are served from the site itself, not from a font company’s server.

• AI, only on the plan with AI: when you ask an agent to draft something, the text it needs (for example the details of an invoice or an enquiry) is sent to Anthropic’s Claude service to write the draft. Without AI, or while AI is switched off, nothing is sent. A daily spending limit applies.
• Voice: the microphone button uses your phone browser’s own speech recognition. On many phones the browser sends the sound to its maker. INDRA receives only the text.
• Team chat (Matrix): if you connect a Matrix server, drafts and replies are posted to the server you chose. INDRA stores the access token for it in sealed (encrypted) form.
• Abuse protection: the homestay hub forms for reports and claims keep a salted hash of the sender’s network address, never the address itself, to slow down spam. Sign-in attempts are counted in memory for a short time.

Every action writes a signed receipt that is chained to the one before it, so nobody can quietly change history. The same property means a receipt cannot be edited or erased one by one without breaking the chain. Receipts hold who did what, and amounts or names where needed to understand the action. Of an ID number, only the last four characters can ever reach a receipt.

• Correcting: people with the right role can edit customers, guests and staff records in the app.
• Exporting: today you can download the day book (CSV), Tally-style vouchers, and the receipts verification bundle from the app. There is not yet one button that exports everything.
• Deleting and leaving: the app has no “delete my business” button yet, and no way to erase one guest or staff member completely. Today it is a request to us, through the contact page.

You can ask about your data on the contact page.