Security — Aagantuk

Guest data is encrypted, access is controlled by role, and identity-document information is protected through the safeguards below. This page describes our approach at a level useful to a hotel owner deciding whether to trust us with their register — see our Privacy Policy for the full detail on data handling.

Encryption

Guest and hotel records are stored in an encrypted database on the front-desk device itself, not in a plain, readable file. Data sent between the app and our cloud infrastructure is encrypted in transit.

Role-based access

Every hotel's data is kept separate from every other hotel's. Within a hotel, staff see only the properties and app sections their owner or admin has given them — a receptionist doesn't automatically get an owner's view across every property, and one hotel's staff can never see another hotel's records.

Identity-document safeguards

A guest's consent is recorded before any scanned document detail is stored.
Where the document format supports it, the app checks the government issuer's own digital signature on the scanned code, and flags to staff when it can't be verified.
The app is designed to capture and retain as little of a document's information as the format allows — for example, reading only a masked reference from a current-format Aadhaar QR code rather than the full number.

Infrastructure

Aagantuk's cloud sync runs on Google's Firebase and Google Cloud platform, which provides the underlying data-center security, redundancy and infrastructure protection beneath our own application-level controls.

Ongoing practice

We review access controls and security practices as the product and our customer base grow, and we keep the app's dependencies and security-relevant components up to date.

Reporting a concern