Purpose
Data is used to operate the stay—booking, front desk, hotel register / ID, folios, ops tickets, and reports—not sold as advertising profiles.
agamnosPrivacy
Guest data stays operational—and contained.
agamnos processes hotel and guest data to run stays: reservations, rooms, rates, folios, housekeeping, events, and Direct booking. GDPR-aligned principles guide what we collect, who can see it, and how long it is kept. This page is a product overview, not legal advice.
Tenant scopedRole limitedPurpose limited
We process
- Guest name, contact, stay details, and hotel-register identity (government ID type, last 4 of the number, optional encrypted ID photos). ID is for the stay register, encrypted at rest, role-limited, and not used for marketing.
- Staff accounts, roles, and shift or ticket assignments
- Operational events—check-in, folio charges, room service, housekeeping
- Payment references from processors—not full card numbers in the PMS
- Property config—taxes, rates, venues, and payment keys you save
Hotel control
- Each hotel is a tenant; data is property-scoped
- Staff see only what their role allows on the console and APIs
- The hotel remains controller of guest relationships; agamnos is the platform processor
- Direct booking and desk capture use the hotel’s chosen payment path
- Export and erasure tooling expands with the compliance roadmap
Access
Front desk agents see till and stays. Finance needs finance access. Guests never see planned room numbers until check-in.
Processors
Card capture goes to Razorpay or Stripe (or Agamnos Pay / Connect where configured). Webhooks mark folios paid without storing the card.
Demo data
Hotel Agni demo accounts are for training. Do not put real guest cards into demo properties.
Customer DPAs and retention schedules publish with enterprise packaging. Related: Security · Help: security & privacy · All help topics.