Privacy Policy

Overview

LoopdUp is operated by ASTRONAUT KIDS COMPANY LIMITED (CÔNG TY TNHH DU HÀNH GIA NHÍ), enterprise registration number 0109657770. Registered office: 11th floor, Viet A Building, 9 Duy Tan, Cau Giay Ward, Hanoi, Vietnam.

LoopdUp helps hospitality venues manage guest conversations, service requests, feedback, reviews, loyalty activity, staffing, stock, operational follow-up, and performance snapshots. This policy explains the types of information LoopdUp may process when a venue uses the native Loop app, the web workspace, connected Meta channels, Google Business Profile, supported POS and Canva workflows, AI features, Business Health Scan flows, reports, and related support workflows. Processing depends on the features enabled for the venue.

Information we may process

When you request early access, we use your name, email, business type, employee range, city, country, and any role or business name you provide to respond to your request. The website form is processed through AWS and delivered to our contact inbox.

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.
• Account email, username, verified identity, password hashes, session and account-recovery records. Google account login and Google Business Profile authorization are separate connections.
• 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 authorized live review workflow when it 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.
• Authorized POS sales, bill, product, menu, voucher and customer information made available by the connected provider or a supported export.
• Staff availability, planned shifts, stock counts, operational tasks and approval records supplied or created for enabled venue workflows.
• Campaign briefs, brand information, selected images or documents, Canva design and export identifiers, and generated creative assets.
• Text, relevant conversation context, selected audio or images, and business context processed by the AI feature you use.

Account access and credential protection

Loop account passwords are stored as salted, one-way scrypt hashes rather than recoverable passwords. Native session credentials use Expo SecureStore. HTTPS web sessions use HttpOnly cookies with Secure and SameSite controls. Creating an account does not grant access to a venue without an authorized access relationship.

External connection credentials are different from Loop login passwords: authorized workflows may need to retrieve them to contact the connected service. Integration credential storage uses encrypted AWS SSM Parameter Store SecureString, with server-side access controls. Raw connection credentials are kept out of the normal assistant context. See Security & AI for the account and workflow controls.

Google Business Profile integration

Google Business Profile API access has been approved for LoopdUp. Enabled workflows are confirmed for each connected venue. 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 review and reply content is fetched for the exact authorized location and used within a bounded review operation. Raw review content, reviewer identity and intermediate or derived review state are not retained as permanent records, reusable AI memory, stored summaries or review-history analytics.
• The active Reviews view may keep required pages only in process memory, for at most 15 minutes from each fetch. Cache reads do not extend that limit. Sign-out, venue changes, refresh, connection changes, disconnect and expiry clear the applicable cache. Outside the bounded operation or active session cache, review content and derived state are discarded. Later views use a fresh read from Google.
• 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 Loop or contact hello@loopdup.com . They can also revoke LoopdUp from their Google Account third-party connections. See the data deletion instructions .

POS, staffing and stock information

Supported POS connections process the sales, bill, product, menu, voucher or customer fields needed by the authorized venue workflow. Access may use an API, export or a controlled browser task, including selected iPOS workflows through AWS Bedrock AgentCore Browser. Some supported exports arrive by email and are checked before import.

Staffing, stock and operational information is used to prepare schedules, maintain venue records, support analysis and carry out authorized tasks where those features are enabled. Approval records and resulting provider status may be kept for accountability. Connecting a POS does not authorize every possible change; supported external changes require the permissions and approval for that workflow.

Canva and creative assets

Enabled Canva Connect or MCP workflows may send a campaign brief, text, brand information and authorized assets to Canva. Loop may receive design identifiers, previews, editable-design links and export information. Private-image uploads depend on the available workflow and the rights confirmed for the asset.

Creative inputs, generated assets and workflow records may be stored to let the team review, edit and reuse authorized campaign material. A design saved in the venue’s Canva account is also governed by Canva’s own retention and deletion controls. Generating a design does not by itself authorize publishing a campaign.

AI processing

Loop uses external AI services, including the OpenAI API, for request interpretation, response drafts, business recommendations and creative or operational assistance. The relevant context may include the request, conversation history, venue information, selected sales or operational records, and text, audio, images or files supplied for the feature. Context is subject to the source’s permission and data rules, including the live Google review boundary described above.

Submitted context is processed by the selected AI provider under its applicable terms, data policy and service settings. Provider-side retention differs by feature and endpoint. OpenAI’s API handling is described in its data controls documentation. This is separate from the conversation, creative and operational records Loop keeps to provide the venue’s service.

Loop’s central AI usage monitoring keeps operational metadata such as provider, model, token usage, timing, status and hashed request references, rather than raw prompts and responses in that log. AI output is subject to manager review and the workflow’s approval rules. More detail is available on Security & AI.

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 Loop.
• 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.
• Importing supported business data, preparing staffing or stock work, and recording permissions, approvals and outcomes for enabled operations.
• Preparing, previewing and revising authorized campaign material through supported creative and AI workflows.

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, Google, Canva and supported POS platform services for the connections enabled by the venue; AWS for hosting, infrastructure, protected credential storage and selected email, file or browser workflows; OpenAI and other AI services used by the selected feature; database, analytics, 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.

Infrastructure and international processing

LoopdUp is operated from Vietnam. Its current core AWS environment uses the Singapore region. Information may also be processed in other countries by the connected platform or AI service used for a task. A connected service’s location and processing rules are separate from the region used by LoopdUp’s core AWS environment.

For a specific venue or feature, contact us to clarify the applicable connection, information categories and processors. The Integrations overview links to the individual services and the native app.

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.

Disconnecting a service removes or disables its connection and stops future authorized access. It does not automatically delete all conversation, imported POS or creative records already held by Loop. Those records, connection credentials, transient Google review content and provider-held copies have different deletion rules. Deletion requests can specify the account, venue, connection or records concerned; we will explain any applicable retention limits.

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 .