Guest feedback is intended for the restaurant.
GuestRecovery is not built to publish private guest feedback publicly. The system is designed to help restaurants respond and improve.
GuestRecovery Privacy Policy
Privacy matters when guest feedback is meant to stay private.
GuestRecovery is built for private hospitality feedback, live recovery workflows, manager response, and restaurant operating insight. This Privacy Policy explains what information may be collected, how it may be used, and how we approach guest, restaurant, and pilot data.
Last updated: May 2026
Privacy approach
GuestRecovery is designed around private hospitality communication.
Restaurants use GuestRecovery to collect guest signals, respond to service moments, recognize team members, and improve operations. That means the data should be treated as operationally useful and handled with care.
Data supports recovery and improvement.
Feedback, alerts, notes, and outcomes may be used to support manager response, training, reporting, and Experience Gap analysis.
Pilot and demo access should be handled carefully.
Private walkthroughs, pilot access, and internal dashboards are intended for authorized restaurant, owner, manager, or GuestRecovery users.
Information We Collect
GuestRecovery may collect information provided through demo requests, pilot access requests, restaurant onboarding, guest feedback flows, manager dashboards, support messages, and related product workflows.
This may include contact information such as name, email address, phone number, restaurant or company name, job role, location details, and information submitted through a request form.
Guest Feedback and Recovery Data
When GuestRecovery is used by a restaurant, guests may submit private feedback such as ratings, comments, praise, suggestions, menu ideas, service notes, issue categories, or other experience-related details.
Depending on how a restaurant configures the system, a guest signal may also be associated with a table, section, QR source, prompt type, visit context, optional contact information, or recovery follow-up information.
Less-than-4-star feedback may be routed to management so the restaurant can respond, acknowledge the signal, check on the guest, record a recovery action, and document an outcome.
Restaurant, Manager, and Team Data
GuestRecovery may collect or process restaurant operating information, including tenant or location information, staff or manager names, assigned roles, QR source names, prompt locations, response activity, recovery notes, resolution status, and reporting data.
This information is used to support the restaurant’s internal hospitality workflow, including manager alerts, recovery tracking, praise capture, Experience Gap reporting, setup support, and pilot evaluation.
How We Use Information
GuestRecovery may use collected information to provide and improve the service, respond to demo and pilot requests, configure restaurant accounts, route guest signals, support manager workflows, generate reports, provide support, improve product features, and communicate with restaurants or authorized users.
Information may also be used to understand product performance, improve QR prompt workflows, refine manager alert rules, analyze recovery patterns, and develop better hospitality intelligence features.
Demo, Sandbox, and Pilot Data
GuestRecovery may use demo or sandbox data for product walkthroughs. Controlled demos should not expose live restaurant guest signals, live tenant data, billing records, or private operational records.
Pilot restaurants may provide real operating feedback to help evaluate QR placement, manager alerts, escalation timing, recovery tracking, source tracking, staff praise, and Experience Gap reporting. Pilot feedback may be used to improve the product and prioritize future features.
Security
We use reasonable administrative, technical, and organizational measures intended to protect information handled through GuestRecovery. No system can be guaranteed completely secure, but the service is built with the expectation that private guest feedback and restaurant operating data should not be treated casually.
Restaurants and authorized users are responsible for maintaining the security of their own accounts, devices, internal permissions, and access practices.
Data Retention
GuestRecovery may retain information for as long as needed to provide the service, support restaurants, maintain records, analyze product performance, comply with legal obligations, resolve disputes, and improve the product.
Retention periods may vary depending on the type of data, restaurant configuration, pilot status, legal requirements, or operational need.
Choices and Requests
Restaurants, authorized users, and guests may contact GuestRecovery about privacy questions or data-related requests. Depending on the nature of the request, we may need to verify identity, confirm the restaurant relationship, or coordinate with the restaurant that collected the feedback.
Because GuestRecovery may operate as a tool used by restaurants, some guest feedback requests may need to be handled by or coordinated with the restaurant that received the feedback.
Children’s Privacy
GuestRecovery is not intended for use by children. The service is designed for restaurants, managers, owners, authorized staff, and guests who are providing feedback about a restaurant experience.
Changes to This Privacy Policy
We may update this Privacy Policy as GuestRecovery develops, as new features are added, or as legal, operational, or product needs change. The updated version will be posted on this page with a revised update date.
Contact
For privacy questions, pilot inquiries, or data-related requests, contact GuestRecovery at:
Email: contact@guestrecovery.app
Important note:
This Privacy Policy is provided for website and product transparency.
It should be reviewed by qualified legal counsel before GuestRecovery
is used commercially at scale, especially if additional integrations,
payment processing, SMS messaging, or jurisdiction-specific privacy
obligations are added.