Security & data protection

Your guests’ data, your books, kept in India and kept apart.

AtithiSetu holds guest records, folios, payroll and GST returns for your business. This page sets out how that data is stored, who can see it, and how every change to your books is recorded.

Accounting · Audit trail

Who changed what, and when

Read-only
  • Discount applied21:42

    Folio · Room 204 · Priya S., Cashier

    ₹0₹245 (10%)

  • Payment voided21:47

    Folio · Room 204 · Rahul M., Manager

    ₹2,450 UPIVoid — duplicate

  • Room moved10:15

    Booking · Mehra · Anita K., Front desk

    Room 204Room 206

  • Rates updated11:02

    Tariff · Deluxe · Vikram M., Owner

    ₹6,200₹6,500

Illustrative example — the actions and fields are the ones AtithiSetu records.

Hosted in India, one database schema per property

  • Your data is stored on servers in Mumbai, India.
  • Every property gets its own PostgreSQL schema, so one customer’s records are never stored alongside another’s.
  • Every request is checked against the property its login belongs to — a login for one property is refused at another.

Role-based access, set per property

  • Built-in roles for owners, managers, front desk, housekeeping, maintenance, chefs, waiters, cashiers, therapists and event managers — plus custom roles you define.
  • Each role gets None, View, Edit or Full access, page by page.
  • One person can hold a different role at each property in a group.
  • Clinical records in the Ayurveda module are limited to clinical roles, and every opening of a record is logged. Access to staff identity and bank details is logged too.

An audit trail of every change to your books

  • Every entry, edit or deletion in the ledger, folios, payments, cash drawers, GST output register, supplier invoices and payroll is recorded with who made it, their role, when, and the values before and after.
  • Business actions are recorded the same way — discounts, voided payments, reversed folio lines, cancelled invoices, room moves, rate changes and payroll approvals.
  • A deleted invoice is kept as a full snapshot with the reason and the person who deleted it. Changes to role permissions are logged too.
  • The audit trail is read-only and visible to the owner.

Sign-in and sessions

  • Passwords are hashed with bcrypt and never stored in readable form.
  • Repeated failed sign-ins from the same address are blocked, and one-time login codes are rate-limited.
  • Sessions use a secure, HTTP-only cookie in production.

Encryption

  • All traffic to the app is served over HTTPS, and browsers are told to use HTTPS only (HSTS).
  • Staff PAN, Aadhaar and bank account numbers, staff documents, and your payment-gateway and email credentials are additionally encrypted with AES-256-GCM.

Payments without holding card data

  • AtithiSetu never stores card numbers, CVVs or UPI PINs.
  • Online payments go through your own Razorpay, PhonePe or Paytm merchant account — the money settles to you, not to us.
  • Payment confirmations from the gateway are checked against its signature before a bill is marked paid.

Compliance built into daily work

  • DPDP 2023: consent is recorded with the policy version the guest agreed to, and each property names its own data protection contact.
  • Form-C is generated from the guest record for foreign nationals, with a log of submissions.
  • GST: sequential invoice numbers, GSTR-1 and GSTR-3B working sheets, GSTR-2B reconciliation, and e-invoice data prepared for your GSP.

Security review or questionnaire?

Send your IT or procurement team’s questions and we will answer them in writing, along with our data-processing terms.

[email protected]Privacy Policy