Security & Trust
Operator-Grade by Construction.
Tenant isolation enforced in code, not policy. An EU database for customer records where a property needs one. Export and erase tooling for customer data. The posture a luxury GM's IT lead needs to see before recommending a vendor — at a glance first, then in full.
Posture at a glance
Eight Questions a Procurement Review Asks, and Where Each Stands Today.
| Area | Where it stands today |
|---|---|
| Tenant isolation | Enforced in Firestore security rules and in server middleware; a cross-tenant request is refused at the auth boundary, before the body is read. |
| EU data residency | Property OS customer records can be kept in our Frankfurt (EU) database; sign-in, audit logs, photos and the application servers run in the US. Other products are set up per product when an EU property needs it. |
| Right of access and erasure | Export and tenant-erase tooling for all six products, behind a typed-confirmation gate; the steps not yet scripted are done by hand and listed in the deletion confirmation. |
| Tested defences | Cross-tenant regression tests in every product suite with floors that only grow; prompt-injection detection on guest routes; Helmet, a content-security policy and HSTS on every service; secrets only in Secret Manager. |
| Subprocessors | A short, published list (v1.2); at least 15 days’ notice before a new one processes personal data. |
| Encryption and transport | TLS in transit on Google-managed certificates; AES-256 at rest in Firestore and Cloud Storage with Google-managed keys. |
| Breach response | A written plan with severity classes and escalation paths; authority notification within 72 hours under GDPR; affected customers notified within 72 hours of HARIOS becoming aware. |
| SOC 2 | Not held. A Type I readiness assessment is scheduled before 10 paying customers and the Type II audit follows its six-month window; contracts sign today against the engineering controls on this page plus the MSA and DPA. |
01 · Tenant isolation
A Guest Record from One Property Cannot Be Read from Another.
Every customer-owned document in every HARIOS product lives under a tenant-scoped path — hotels/{hotelId} or locations/{locationId}. Tenant membership travels in the signed authentication token and is enforced at two layers: Firestore security rules, which refuse a read or write outside the caller's own tenant, and a server middleware (requireMemberOf) that refuses to load any document outside the authenticated user's tenant set. Cross-tenant attempts return 403 at the auth boundary before the request body is read. Server-only collections are closed to every client by rule, not by convention.
Privileged account deactivation triggers revokeRefreshTokens(uid) — existing sessions return 401 within seconds, not at next refresh.
Enforcement
Firestore rules + server middleware (defense in depth)
Cross-tenant probe
403 at auth boundary, before body parse
Deactivation
Revokes refresh tokens; sessions 401 within seconds
02 · EU data residency
Customer Records for EU Properties Can Be Kept in Our Frankfurt (EU) Database.
Customer records for EU properties can be kept in our Frankfurt (EU) database; sign-in, audit logs and photos are processed in the US. Property OS keeps two separate Firestore databases — the default one in the US (nam5) and eu-west in Frankfurt (europe-west3). A hotel's residency is recorded per tenant and read on every request, so its records are read from and written to the database it was assigned. The application servers run in the US (us-central1).
The same pattern can be applied to the other product backends; we set it up per product when an EU property needs it.
EU database today
Property OS customer records (Frankfurt, europe-west3)
Processed in the US
Sign-in, audit logs, photos, and the application servers
Other products
Set up per product when an EU property needs it
03 · Right of access & right of erasure (GDPR Articles 15, 17, 20)
Real DSAR Tooling. Typed-Confirmation Erase Gate.
Concierge OS, Property OS, Roster OS, Training OS, Operations OS and Menu OS each ship two CLI tools that run against live Firestore: an export script (Article 15 right of access + Article 20 portability) and a tenant erase script for Article 17 erasure requests; a third erases the people's HARIOS ID sign-in accounts. The erase scripts refuse to run without the operator typing the exact phrase ERASE TENANT <id> — no flag combination shortcut, no --yes override. Child collections drain before parent documents to prevent orphan references, and each erase leaves a record that it ran (Property marks its tenant registry with erasedAt).
The scripts do not yet cover everything: the sign-in accounts in Property OS, Training OS and Operations OS, a few Concierge OS platform records (hotel-group membership, partner links, support tickets, health scores) and the harios.ai property record are removed by hand, and each of those steps is listed in the deletion confirmation the customer receives.
A written GDPR posture document sits in the internal legal library, with a 10-item operational checklist that tracks the work remaining before the first EU customer signs; counsel review of it is scheduled before the first EU customer signs.
Export
Article 15 + Article 20 (one archive per tenant; dry-run default, the archive on --export; Menu OS writes its archive directly)
Erase
Article 17 tenant erase (typed-confirmation gate, no flag shortcut), HARIOS ID accounts included; the remaining accounts and records by hand, listed in the confirmation
Audit
Each erase leaves a record that it ran
04 · Tested defences
The Controls on This Page Are Tests in the Codebase, Not Sentences in a Policy.
Every product ships with a test suite that includes tenant-isolation regression cases — a request signed for one property asking for another property's document must fail, and the build fails if that test is ever removed. Test counts in every repository are enforced by a floor that only grows; lowering it is a leadership decision, never a commit.
Guest-facing and public AI routes in Concierge OS run a prompt-injection detector on every message before the model sees it. It flags and records rather than silently refusing, so a guest asking an unusual question is never treated as an attacker — and an actual attempt is visible in the audit trail. Error monitoring redacts email, name and phone fields before an event leaves the service. Every product service and harios.ai run behind Helmet with a content-security policy and HSTS; the administrative war room adds a brute-force throttle on sign-in and a flood limiter on mutations.
Application secrets exist only in Google Secret Manager and are bound to a service by reference at deploy time — no secret value lives in source, in a build, or in an engineer's notes. The GCP organisation policy forbids service-account key files outright.
Isolation
Cross-tenant regression tests in every product suite; floors only grow
AI input
Prompt-injection detection on guest + public routes (flag, record, never silently refuse)
Telemetry
Sentry events scrubbed of email / name / phone before send
Transport hardening
Helmet + CSP + HSTS on every product service and harios.ai; sign-in throttle + mutation flood limiter on the war room
Secrets
Secret Manager by reference only; no service-account key files (org policy)
Change gate
Type-check + full test suite green before any production deploy
05 · Subprocessors
A Short List. Each on the Platform for a Load-Bearing Reason.
HARIOS uses a deliberately short subprocessor list. Each provider is on the platform because no in-house alternative carries the same track record at the same operational cost; each integration is scoped to a specific capability, not “everything by default.” The main providers are below. The full, versioned list — every provider, with data locations and the change-notification procedure — is published at harios.ai/subprocessors (v1.2, effective 2026-10-19).
Compute & data
Google Cloud (Cloud Run + Firestore)
Authentication
Firebase Authentication
AI (conversation, content, scheduling)
Anthropic Claude (routed by task); OpenAI (knowledge-base search embeddings)
Transactional email
Brevo
Billing
Stripe (invoicing and payment processing)
Voice (where enabled)
ElevenLabs (Concierge OS live voice; Training OS lesson narration)
06 · Encryption and transport
Encrypted in Transit and at Rest. Google-Managed Keys.
All HARIOS traffic is encrypted in transit with TLS on Google-managed certificates, terminating at Cloud Run; no path serves HTTP. Firestore encrypts every document at rest with Google-managed keys; the encryption boundary is at the storage layer and is not opt-in. Cloud Storage objects (uploaded photos for Lost & Found, generated certificates) use the same posture.
In transit
TLS on Google-managed certificates (Cloud Run)
At rest
AES-256 (Firestore + Cloud Storage Google-managed keys)
Application secrets
Google Secret Manager (bound at deploy)
07 · Customer-side controls
The Data Is Yours. The Export Is Yours.
Customer data ownership is invariant. On contract termination, HARIOS produces a data export within 30 days (scripted for all six products; stored files are collected by hand on request); the customer chooses retention vs. erase. Audit logs are exposed to the GM through the in-product audit-log surface (not a CSV download appended after the fact — the audit log is part of the product). Data-subject requests are handled directly by the HARIOS team through the same tenant export/erase tooling, never a black-box ticket queue.
Termination export
30-day window; customer chooses retention vs. erase
In-product audit log
Real-time, scoped to GM-level role
Data-subject requests
Handled by the HARIOS team against the tenant export/erase tooling (all six products have export scripts; per-subject filtering on request)
08 · Breach response
A Written Plan. Notification Within Statutory Windows.
HARIOS maintains a written breach-response plan with defined severity classifications, escalation paths, and notification timelines per applicable jurisdiction (GDPR 72-hour authority notification; affected customers notified without undue delay and within 72 hours of HARIOS becoming aware). Customer-facing notification follows the same posture as our standing operational discipline: short, factual, no excuses, with a clear remediation timeline.
GDPR
Authority notification within 72 hours
Customers
Notified without undue delay, within 72 hours of HARIOS becoming aware
Operator notification
Direct, no marketing buffer
09 · SOC 2
SOC 2 Type I Readiness Assessment, Then Type II.
HARIOS's SOC 2 trajectory follows the customer-count gate, not a roadmap date. The Type I readiness assessment is scheduled against that gate; the Type II audit follows the standard 6-month observation window after Type I. Until the report exists, contracts sign against the engineering controls described on this page plus the standard MSA + Data Processing Agreement.
Type I trigger
Before 10+ paying customers
Type II trigger
6-month observation after Type I
Today
Engineering controls described on this page; customer DPA available
10 · Contact
security@harios.ai · sales@harios.ai · Response Within 24 Hours During US Business Hours.
Security-specific concerns route to security@harios.ai; commercial diligence routes to sales@harios.ai. Both are read by a person at HARIOS. Acknowledgment within 24 hours during US business hours; substantive response within 72.
Diligence
Bring Your IT Lead. We Walk the Posture Together.
The DPA and its SCCs annex are available under NDA for procurement teams; the subprocessor list is public. Thirty minutes covers the questions above and the ones specific to your property.
Or write to sales@harios.ai with your property name.