Levee Labs Inc. (“Levee”) operates a hospitality inspection, standard operating procedure (SOP), staff learning, and brand-standards platform for hotel and hospitality operators. This policy describes how Levee collects, uses, shares, and protects personal data across the Levee web portal, the native mobile application, this website, and the optional connectors described below.
Last updated · 11 October 2026
FIG 1.0 · Summary
The rest of this page is the detail behind these five points.
Account, authentication, and usage data needed to run the platform; the content you or your employer create in it (inspection records, SOP text, checklist answers, notes); and the photos, video, and voice audio submitted through inspection and training features.
A small, named set of subprocessors — cloud hosting and AI infrastructure, web hosting, voice AI, messaging delivery, a CRM and a meeting scheduler for demo requests made on this website, and an optional property-management-system integration. Levee gives customers at least 30 days’ notice before adding a new subprocessor that processes customer personal data.
Photos, video, audio, and written content may be processed by AI models — Levee’s and its subprocessors’ — to detect issues, score compliance against brand standards, generate training content, and support search. That processing exists to run the feature you invoked; Levee does not turn your data into an advertising product.
If your organization connects Levee to ChatGPT, Claude, GitHub Copilot, or another AI assistant, that connector receives read-only, tenant-scoped access to SOPs and brand standards, and nothing else.
Levee does not sell personal data.
FIG 2.0 · Scope
Levee is a business platform. Almost everyone who uses it does so through an employer that subscribes to Levee.
Levee’s customers — hotel owners, management companies, and hospitality brands — subscribe to the platform and decide which of their facilities and staff use it.
Inspectors, managers, general managers, and other employees the tenant authorizes. If you use Levee because your employer gave you access, your employer controls your account and most of the content you create in the platform. Questions about your employment, or about the specific policies your employer applies, should go to your employer first; Levee will still help directly with requests about your personal data where we can.
FIG 3.0 · Collection
Some of this comes from the tenant business, some from the individual user, and some from ordinary use of the applications.
| Category | Examples |
|---|---|
| Account and identity | Name, email address, phone number, employer or tenant, and role. |
| Authentication | Password (stored hashed), login and reset codes, and device identifiers used for session security. |
| Inspection and SOP content | Checklist responses, inspection notes, SOP and brand-standard text, annotations, and compliance scores. |
| Media | Photos, video, and voice audio submitted during inspections, training, or coaching features. |
| Room scans | The shape of a room captured by the mobile app’s depth sensors during an inspection: a floor plan and the positions of walls, doors, and fixtures. A room scan is geometry, not a photograph. |
| Usage and diagnostic data | App and device platform and version, timestamps, feature usage, and error logs. |
| Integration data | Room and reservation status from a property-management system, only where a customer chooses to enable that integration. |
| AI-connector data | Search terms and the specific documents fetched, when a user reaches Levee through an authorized AI assistant connector. |
FIG 4.0 · Use
Every use below exists to run the platform for the tenant business and its staff.
For the content a tenant business and its staff create in the platform — inspection records, SOP text, checklist data, and related media — Levee acts as a data processor (or “service provider,” depending on applicable law) on behalf of the tenant, who remains the controller of that data. A Data Processing Addendum governs that relationship; contact us to request it.
For account administration, security, and the limited data Levee needs to run the relationship with the tenant business itself, Levee acts as a controller.
FIG 5.0 · Subprocessors
Levee uses a small number of third-party providers to deliver the platform, in these categories.
Application hosting, storage, and AI processing of platform data, including inspection media.
Hosting and server-side rendering for the customer-facing web portal.
Conversational voice and speech-to-text for the training and roleplay features, where a customer enables them.
Transactional email and SMS, for example login codes and notifications.
Only for customers who choose to enable a PMS integration. It processes room and reservation status data, not guest personal data, unless a customer’s own PMS configuration provides it.
FIG 6.0 · Connectors
Levee offers an optional connector, built on the Model Context Protocol, that lets an authorized user query their tenant’s SOPs and brand standards from a supported AI assistant.
A user authorizes the connection through their AI assistant, and the resulting credential is bound to that one user, their tenant, and a limited, read-only permission: search and retrieve SOPs and brand standards. It cannot write, cannot delete, and cannot reach other tenants’ data or other Levee modules such as inspections, tickets, or user records.
The assistant sends the user’s search terms to Levee and receives matching document titles, the retrieved document text, and a citation link back to the source in Levee. Levee does not expose user profiles, contact details, facility data, or operational logs to the assistant.
The user or their administrator can revoke the connection at any time, which immediately ends the assistant’s access.
Levee logs connector usage — which tenant and user made which call — for security and support purposes, in the same tenant-isolated way as other platform activity.
FIG 7.0 · Controls
When you ask for a demo on levee.io, Levee collects your name, work email, company, and organization type, and uses them only to respond to your request and prepare for the meeting. They are stored in Levee’s CRM, which runs on Notion, and Levee receives an email notification of the request. If you book a time, Cal.com schedules the meeting and receives your name, email address, and chosen time. Levee does not use demo-request details for advertising or sell them. To have your demo-request details deleted from Levee’s CRM and from Cal.com, email support@levee.io.
Levee’s web applications use cookies and similar technologies to keep you signed in and to protect your session. The marketing website uses privacy-conscious, aggregate web analytics to understand traffic; it does not run third-party advertising trackers. OAuth tokens are used only for the connectors a user explicitly authorizes, not for cross-site tracking.
Levee stores and processes personal data in the United States, with the specific exceptions described under “Overseas recipients” below. The Levee API, the database, and file and media storage run in Google Cloud’s us-central1 region. The web applications are served from a United States region by Levee’s web-hosting provider. Derived analytics are held in United States locations, and Levee’s operational logs are held in a Google Cloud logging location that is not restricted to a single region or country. If you use Levee from another country, your personal data is transferred to the United States and handled there.
Levee’s subprocessors are located in the United States, with four qualifications. Some Google AI models are served from a multi-region endpoint rather than from a single country. Levee’s operational logs are kept in a Google Cloud logging location that is not restricted to a single region or country. Email and SMS delivery necessarily routes a message onward to the country of the recipient’s mail provider or mobile network. And where a customer enables the optional property-management-system integration, that system runs wherever that customer’s own vendor deployment runs, which may be outside the United States. Every subprocessor and its location is named at levee.io/legal/subprocessors. Where a subprocessor is certified under an applicable international data-transfer framework, that is noted there too. Sending data to a subprocessor does not end Levee’s responsibility for it: Levee remains answerable to its customers for how the subprocessors it chooses handle their data, and publishes the list so a customer can assess it. Customers with specific international-transfer requirements should contact us about the terms that apply under their Data Processing Addendum.
Levee retains personal data for as long as it is needed to provide the service to the tenant business, to meet legal and contractual obligations, and to resolve disputes, and then deletes or de-identifies it. How long that is depends on the type of data and on the customer’s agreement with Levee; contact us for the periods that apply to your organization. Tenant businesses can request deletion of their account and content, and individual users can request access to or deletion of their personal data, at the address below.
Depending on where you live and your relationship to a Levee tenant, you may have rights to access, correct, or delete your personal data, or to object to certain processing. Because a tenant business typically controls its staff’s account and the content they create, we may direct some requests to your employer, but we will still respond to you directly and assist as required by law.
Levee is a business tool for hospitality-company staff. It is not directed to children, and Levee does not knowingly collect personal data from children.
FIG 8.0 · Commitments
Levee uses technical and organizational measures designed to protect personal data, including encryption in transit, access controls scoped to tenant and facility boundaries, and restricted internal access to production systems. No method of transmission or storage is completely secure, and no provider can guarantee absolute security. To ask about a specific security or compliance requirement, contact us at the address below.
Levee may update this policy as the platform or its practices change. The updated version is posted at this URL with a new “Last updated” date, and material changes get additional notice consistent with Levee’s subprocessor and customer-notification commitments.