Privacy Policy

How LoopdUp handles business, venue, channel, and guest interaction information for hospitality workflows.

Overview

LoopdUp helps hospitality venues manage guest conversations, service requests, feedback, reviews, loyalty activity, operational follow-up, and performance snapshots. This policy explains the types of information LoopdUp may process when a venue uses LoopdUp Desk, connected Meta channels, the selected-venue Google Business Profile beta, Business Health Scan flows, reports, and related support workflows.

Information we may process

The information LoopdUp processes depends on the venue setup, connected channels, and features used. It may include:

  • Venue, business, team, and staff account details needed to provide LoopdUp.
  • Facebook Page connection data and Instagram business account connection data.
  • Google OAuth connection metadata; authorized Business Profile account and location identifiers; listing names and verification state; and review, reviewer, and reply fields needed for the direct review-management workflow when that beta is enabled.
  • Messenger and Instagram messages, attachments, conversation metadata, delivery or status metadata, and staff reply history.
  • Page, Instagram, channel, account, PSID, and Instagram-scoped user identifiers.
  • Profile and channel identity, such as names, usernames, profile images, locale, or other identity fields made available through the connected platform.
  • Page and Instagram insights metrics, performance signals, feedback, review-related signals, loyalty activity, voucher activity, and operational notes.
  • Operational logs used for security, reliability, troubleshooting, audit, and service improvement.

Google Business Profile integration

The Google Business Profile integration is in development for selected hospitality venues and depends on Google API approval. Only an owner or manager authorized by the business may connect a profile. Connection uses Google OAuth. LoopdUp never asks for or stores the user's Google password.

  • OAuth credentials are kept in encrypted credential storage and are used only to make authorized Google API requests for the connected venue.
  • Account and location metadata are used to show the connected account, map the verified location, and scope every review action to the active venue.
  • Live official review and reply content is used only for the direct Desk review workflow. LoopdUp does not retain the raw API response and does not use this live content for Manager AI analysis, Pulse summaries, or aggregated review-health reporting.
  • Live official review content receives a conservative 29-day expiry. An automated cleanup removes expired content; disconnect removes the applicable live review rows and credential mapping sooner.
  • Connected venue data is available only to authorized venue users, LoopdUp personnel who need it to support or secure the service, and processors needed to operate the integration under appropriate controls.

Managers can disconnect in LoopdUp Desk or contact hello@loopdup.com . They can also revoke LoopdUp from their Google Account third-party connections. See the data deletion instructions .

How information may be used

LoopdUp uses information to provide and improve the service configured by the venue. Depending on the setup, this may include:

  • Routing guest messages from connected channels into LoopdUp Desk.
  • Supporting staff replies, staff takeover, bot pause or resume, and handoff flows.
  • Allowing human staff to send manual support replies through connected Meta channels where Meta policy permits, including Human Agent follow-up where allowed.
  • Managing support, service, order, booking, contact, CRM, and guest history workflows.
  • Preparing reports, Pulse views, Business Health Scan outputs, performance snapshots, and operational recommendations for venue managers.
  • Securing, monitoring, debugging, and maintaining LoopdUp and connected integrations.

Sharing and processors

LoopdUp may share or make information available only as needed to provide, secure, and support the service. This can include authorized venue owners, managers, and team users; Meta and Google APIs and connected platform services; hosting, database, infrastructure, secure credential storage, analytics, AI, customer support, and other service processors; and professional or legal advisers where necessary. LoopdUp does not authorize unrelated third-party use of venue Meta conversation data outside the service configured for the venue.

Retention and deletion

Except where a shorter platform-specific limit applies, LoopdUp keeps records as needed to provide the service, maintain conversation and operational history selected by the venue, support security and reliability, troubleshoot issues, meet legal or operational obligations, and produce reports. We may delete or anonymize records when they are no longer needed for these purposes.

Guests, venue users, or authorized venue contacts can request deletion or anonymization of applicable records. See the data deletion instructions for details.

Contact

For privacy questions, deletion requests, or connected channel data requests, contact LoopdUp at hello@loopdup.com .