Security & Data Protection
Grove is engineered around multi-tenant isolation, role-based access control, and database-level security policies. Here is an honest, technical explanation of how our architecture protects your hotel's data.
PostgreSQL Row-Level Security
Every database query is automatically filtered by tenant ID at the database layer, preventing cross-property data leaks.
Encrypted Authentication
Authentication and password hashing are managed through Supabase with secure, time-bounded JWT session tokens.
Granular Role-Based Access
Explicit permissions per role (Owner, Manager, Reception, Housekeeping) ensure staff only access authorized workflows.
Staff Identity Resolution
Staff accounts are tied to verified hotel entities and can only be provisioned by authenticated Hotel Owners.
1. Multi-Tenant Architecture & Data Flow
In Grove, security is not enforced purely through frontend checks. Our core data isolation is enforced at the PostgreSQL database layer using Row-Level Security (RLS) policies.
This guarantees that staff from Hotel Alpha can never read, modify, or delete bookings, folios, or guest records belonging to Hotel Beta.
2. Role-Based Permissions Hierarchy
Grove recognizes four distinct operational roles with strict principle-of-least-privilege boundaries:
- Owner: Sole administrative authority for property settings, tax configuration, staff account creation, financial exports, and billing folios.
- Manager: Operational oversight, daily reporting, room allocations, booking modifications, and front desk supervision.
- Reception: Front desk check-ins, guest verification, keycards, room tariff posting, and express check-out.
- Housekeeping: Room status updates (dirty, cleaning, inspected, out-of-order) without access to financial ledgers or owner settings.
3. Encryption & Communications
All traffic between your browser and Grove is encrypted in transit using industry-standard TLS (Transport Layer Security) over HTTPS. Session tokens are digitally signed with cryptographic keys and transmitted over secure HTTP-only cookie headers.
4. Responsible Vulnerability Reporting
We welcome responsible disclosure of potential security vulnerabilities. If you discover a security concern, please email our engineering team directly at security@grovepms.com. We review and respond to legitimate security reports promptly.