Privacy Policy

This policy covers renavo.net, Renavo demos, and the Renavo hotel-operations service. For guest and staff information processed for a hotel, the hotel normally decides why the information is used and Renavo processes it on the hotel's instructions. Renavo is responsible for information submitted directly through this website, such as demo requests and security reports.

The exact information depends on how Renavo is deployed.

• Website and sales details: name, work email, hotel, room count, and correspondence.
• Hotel account details: username, role, property assignment, session and security events.
• Guest-service details: name, booking reference, room, contact-channel identifier, messages, requests and ratings.
• Operational records: tasks, owners, deadlines, policy decisions, approvals, PMS receipts, incidents and Ledger events.
• Technical records: request identifiers, service health, security signals, redacted diagnostics and performance measurements.
• Configuration and credentials supplied by a hotel are stored as protected secrets. Renavo is not designed to store full payment-card numbers.

We use information to verify users, answer guest requests, operate hotel systems within configured authority, dispatch work, complete approved actions, maintain the Ledger, prevent abuse, troubleshoot incidents, provide support and improve reliability. We do not sell personal information or use hotel guest conversations for unrelated advertising.

Renavo may use language, voice and computer-use models to interpret requests and prepare or perform hotel-system actions. Hotels configure policies, permissions and whether money actions execute automatically inside policy or require approval. Low-confidence, out-of-policy, safety-sensitive and failed operations are designed to stop or become visible incidents. The Ledger records the relevant request, decision and execution evidence.

Information may be available to the hotel that serves the guest and to vendors needed to operate Renavo, such as hosting, database, observability, communications and AI infrastructure providers. Providers receive only the access needed for their service and are expected to protect it. We may disclose information when required by law, to investigate abuse or security incidents, or as part of a business transaction subject to appropriate safeguards.

Operational retention is configured for each deployment and may also be governed by the hotel's legal or contractual duties. Renavo provides owner-restricted export, deletion and retention-pruning tools. Some non-identifying receipts, security records or duplicate-prevention fingerprints may remain where needed to preserve audit integrity, prevent repeated actions or meet legal obligations. Backups and provider caches expire on their own controlled schedules.

Renavo uses tenant boundaries, role-based access, protected sessions, encrypted sensitive identifiers, secret-backed credentials, allow-listed system connections, bounded request bodies, audit events and operational monitoring. No system is perfectly secure. Report suspected vulnerabilities to security@renavo.net and do not include live guest data unless we request it through a protected channel.

Depending on your location, you may have rights to access, correct, delete, restrict or receive a copy of personal information. Hotel guests should normally contact their hotel first because the hotel controls the guest relationship. You may also contact security@renavo.net. We will verify the request and coordinate with the relevant hotel where necessary.

Renavo and its providers may process information in countries other than the one where it was collected. Contractual and technical safeguards are used where required. We may update this policy as the service changes; the date above identifies the current version. Material changes will be communicated through the service or the relevant hotel agreement.