How Maghraut PMS protects your hotel and guest data

• All traffic between staff devices, guest browsers, and Maghraut PMS uses HTTPS/TLS 1.2+. HTTP is redirected to HTTPS.
• The managed Postgres database and object storage are encrypted at rest by the underlying cloud provider using industry-standard AES-256.
• Service-role keys, payment provider keys, and integration tokens are stored on the server side only — never bundled into the browser app and never returned to the client.
• Passwords are hashed by the managed auth provider (bcrypt-family). Maghraut PMS staff never see, store, or transmit plaintext passwords.

Every staff member belongs to a tenant (hotel / group) and is assigned one or more roles. Roles are stored in a dedicated server-side table and checked on every request — they cannot be elevated from the browser.

• Owner / PMS Manager — full access to PMS, POS, reports, and administration.
• Front Office — reservations, check-in / check-out, guest folios, payments.
• Cashier — settle bills, record payments, day-close.
• Outlet Manager — POS administration for restaurant / room-service outlets, discounts, voids, refunds, reports.
• Restaurant Staff / Room-Service Staff — POS-only access via the dedicated POS Portal. No reservations, no PMS reports, no settings.

Per-module access scopes (view / write / none) allow further fine-tuning per staff member for Dashboard, Calendar, Reservations, Events, Guests, Payments, Notes, and Setup.

Sensitive operations write append-only entries to a dedicated audit log table. Each entry records the actor (user ID + email), timestamp, tenant, entity, and relevant metadata (amount, reason, reference IDs).

• Folio charges & payments — every insert, update, delete.
• POS orders — creation, modification, settlement, void, refund.
• Reservation status changes, cancellations, no-shows.
• Role assignments and access scope changes.

Audit logs are readable only by Owners, Managers, and platform super admins — PII fields (actor email, IP) are not visible to general staff.

• The managed Postgres database is backed up daily by the cloud provider with point-in-time recovery (PITR) available on supported plans.
• Object storage (ID documents, media) is replicated for durability across availability zones.
• Operational data is retained for as long as the hotel's subscription is active. On contract termination, data can be exported and is then scheduled for deletion per the agreed retention window.
• Guest documents (passport / Aadhaar scans) are retained according to the hotel's local regulatory requirements, configurable per property.

Maghraut PMS runs on Lovable Cloud, which is built on Supabase (managed Postgres, Auth, Storage) and a major public cloud provider for the underlying compute, database, and storage — the same class of infrastructure used by many regulated SaaS products.

• Edge runtime for server functions — low-latency, globally distributed.
• Managed Postgres with automated patching and monitoring.
• Private object storage with signed-URL access.
• Provider-level network controls (DDoS protection, WAF, rate limits on public endpoints).

Maghraut PMS is multi-tenant by design. Every hotel or group is a separate tenant, and all data — reservations, guests, folios, payments, POS, events, housekeeping — is scoped by tenant_id and property_id at the database layer.

• Row-Level Security (RLS) is enabled on every operational table. A signed-in staff member can only read or modify rows belonging to a tenant they are an explicit member of.
• Cross-tenant access by platform super admins is granted explicitly per table via security-definer functions — not via a hidden bypass.
• Public surfaces (booking engine, online menu, pre check-in) call narrowly scoped server functions that only expose the fields needed for that flow.

• Daily database backups with point-in-time recovery enable restoration to a specific moment in case of accidental data loss or corruption.
• Compute and storage are managed and auto-healing — the cloud provider replaces failed instances without manual intervention.
• Object storage is replicated across availability zones so a single-zone outage does not cause data loss.
• Software releases follow a review-and-promote workflow with the ability to roll back to a previous version of the application.
• On major incidents, status and ETA are communicated to property owners via the support channel listed below.

Maghraut PMS processes guest personal data on behalf of the hotel that subscribes to it. The hotel is the data controller; Maghraut PMS is the processor. Guest data is never sold and is not used to train external AI models.

The platform handles these sensitive categories of hotel data:

• Guest profiles — name, contact, preferences, stay history. Scoped to the tenant and accessible only to authorized staff.
• Passport & Aadhaar copies — stored in private object storage, never publicly accessible, served only via short-lived signed URLs to authorized staff.
• Contact information — phone, email, address. Used only for operational communication for the booking.
• Reservation records — dates, rooms, packages, special requests. Tenant-scoped with RLS.
• Payments & invoices — amounts, methods, references. Card data is handled by PCI-compliant payment providers; Maghraut PMS stores only non-sensitive references and last-four / brand metadata as returned by the provider.

Guests submitting pre check-in details share their information only with the specific property they are checking into. Document uploads land in private buckets with column-level revokes on token / OTP fields.

• Staff sign in with email + password or Google. Passwords are hashed by the managed auth provider; leaked-password protection (HIBP check) is available.
• Session tokens (JWT) are short-lived with automatic refresh; sign-out invalidates the session locally and on the server.
• No anonymous sign-ups for the PMS — accounts are provisioned by the property owner or manager.
• Public-facing endpoints (booking engine, menu, pre check-in) use scoped server functions; they cannot enumerate other tenants' data.
• Webhooks and external callbacks verify signatures before processing.

Maghraut PMS aligns its operational practices with widely accepted security best practices and industry guidance (OWASP Top 10, principle of least privilege, defense in depth). The platform inherits the certifications maintained by its underlying cloud providers.

• Underlying infrastructure — managed by major cloud providers with their own SOC 2 / ISO 27001 programs. Customers should refer to the provider's trust portal for current attestations.
• Payment processing — handled by PCI-DSS-compliant providers (e.g. the payment gateway you configure). Maghraut PMS does not store raw card numbers.
• Privacy — Maghraut PMS supports data export and deletion workflows so the hotel can meet local privacy requirements (e.g. GDPR-style subject access / erasure requests).
• Application security — input validation, parameterized queries, RLS-by-default, signed URLs for private files, regular dependency scanning, and automated security scans of the database schema and policies.

Maghraut PMS does not claim to hold SOC 2, ISO 27001, HIPAA, or PCI-DSS certifications in its own name. For procurement reviews requiring certified attestations, please contact us — we can share the underlying provider certificates and a current security questionnaire.

For security questionnaires, DPAs, procurement reviews, or to report a vulnerability, contact sales@maghraut.com. For a broader overview of our trust posture, see our Trust & Privacy page.