Tenant isolation
Organization and property boundaries on operational APIs. Staff and guests only see the hotel they belong to.
agamnosTrust
Protect guest data, hotel systems, and AI workflows.
agamnos is built for multi-tenant hospitality: each hotel’s inventory, folios, and staff stay inside clear boundaries. Controls are aligned with SOC 2, GDPR, and ISO 27001. Formal certifications follow the enterprise readiness program.
SOC 2GDPRISO 27001
Role-based access
Front desk, housekeeping, technicians, schedulers, accountants, and owners each get the permissions their job needs—not a shared admin password.
Audit trails
Sensitive changes—reservations, payments, night audit, room service charges—are written for review.
Payments
Card data stays with Razorpay or Stripe. agamnos stores payment references and folio lines, not PANs.
Desk money vs Finance
Hotel-today till is visible to front desk. Insights stays behind report access, and Finance stays behind finance access, so agents see shift money without the full ledger.
AI workflows
When enabled, AI stays property-scoped, redacts sensitive fields, and requires human confirm for irreversible actions.
What we protect
- Guest PII and stay history—scoped to each hotel tenant
- Inventory, rates, folios, events, and channel credentials
- Staff accounts and role assignments
- Processor keys and webhook secrets stored as hotel config
How operators benefit
- Fewer access surprises—sidebar and APIs follow the same roles
- Clearer reconciliation—folio and payment history on the stay
- Safer Direct and desk capture—processor hosts the card form
- Honest posture—controls first; certifications on the roadmap
Customer DPAs and formal SOC 2 / ISO reports ship with enterprise packaging. For day-to-day operator guidance, see Security and privacy in Help · Privacy overview.