Privacy
Property context deserves property discipline.
This notice explains the information handled through the official OMERVIA site and the principles applied when a one-property proof moves into onboarding and guest operations.
1. Information submitted on this site
A pilot request may include your name, business email, company or portfolio name, portfolio-size range, an optional property or portfolio URL, your consent to be contacted, and technical request metadata needed to protect the form from abuse.
2. Why we use it
We use pilot-request information to review whether a private OMERVIA proof is appropriate, contact you about that request, issue a secure property-scoped onboarding invitation when approved, protect the service, and maintain legitimate operational records.
3. Property onboarding
If a proof proceeds, onboarding may collect property facts, policies, approved operational media, documents, escalation contacts and other information needed to build a trustworthy Property Brain. Sensitive access information is treated separately from general property knowledge and is subject to disclosure rules tied to the correct property, reservation and stay phase.
4. Guest-operations data
OMERVIA is designed to resolve the exact property, reservation and conversation before using property information. Property-specific facts and media are not intended to leak across properties. Ambiguous identity, property or authorization should fail closed rather than produce an invented answer.
5. Data minimization and security
The operating model minimizes unnecessary personal information in logs, keeps provider credentials and session material out of ordinary automation data paths, uses scoped authentication for internal event flows, applies anti-replay/deduplication controls, and restricts protected information to authorized use.
6. Media and third-party data
Property media should be supplied or approved by an authorized owner/operator. OMERVIA does not treat a third-party listing gallery as automatically reusable. Provider and channel data are handled only through authorized integration paths and current permitted scopes.
7. Retention and control
Information is retained only as needed for the pilot review, onboarding, service operation, security, legitimate recordkeeping and applicable obligations. A proof is designed with pause/stop control, and operational entitlement to sensitive stay information does not continue indefinitely after the relevant stay.
Questions about privacy
Use the contact path provided during your OMERVIA pilot or return to the official pilot request and ask for privacy assistance before submitting property-sensitive information.