Privacy Policy

Scope

This policy applies to information handled by Live Technologies through LiVE. A restaurant may use LiVE with its own website, customer channels, workforce systems, or other services. Those separate services and the restaurant's own activities may be covered by the restaurant's privacy notice or another provider's policy.

Restaurant operators and Live Technologies

For employee, customer, reservation, order, and restaurant operating information, the restaurant operator generally decides why the information is collected and how LiVE is used. The restaurant operator is normally the business or controller, and Live Technologies processes that information to provide LiVE under the operator's instructions.

Live Technologies is responsible for information used to operate and secure the LiVE platform itself, including LiVE administrator accounts, company licensing, device authorization, service security, support, and direct communications with Live Technologies. Payment processors and some other providers may act under their own legal responsibilities for information they receive.

Information LiVE processes

The information processed depends on the modules a restaurant enables and how its authorized users operate them. It may include:

• Restaurant employee and administrator information: names, business email addresses, telephone numbers, user and employee identifiers, authentication information, roles, permissions, restaurant and location assignments, employment and scheduling records, time-clock records, training or checklist activity, and other workforce information entered by the restaurant.
• Customer and reservation information: guest names, email addresses, telephone numbers, reservation and event details, party size, seating and table information, preferences, notes, menu selections, requests, rewards or customer-service records, and communications with the restaurant.
• Orders, transactions, and payments: ordered items, prices, taxes, discounts, tips, order source, dining or table details, transaction amount and status, processor and transaction references, payment method, card brand and last four digits when returned by the processor, refunds, and reconciliation records.
• Device, printer, and authorization information: assigned device name and platform identifier, authorized company, restaurant, location and screen, authorization and session events, application or browser information, device and print-agent versions, printer assignments and local-network addresses, connection and print status, IP address or a one-way hash of it, and security or diagnostic events.
• Precise location: coordinates, accuracy, capture time, and related verification results when an authorized user starts a protected workflow that requires physical-presence or geofence verification, such as certain time-clock or manager-authorized actions. LiVE does not request continuous background location.
• Camera, photos, and documents: camera frames used to scan a device-authorization QR code, and photos or files an authorized user deliberately captures or selects for an enabled operational workflow, such as a checklist-completion photo or a receiving or invoice document.
• Communications and notifications: email, SMS, voice, push or in-app message content; contact choices and consent records; sender and recipient details; replies; delivery, opt-out, and failure records; and support communications.
• Operational and security records: tickets, table and kitchen events, inventory and receiving activity, changes made by authorized users, timestamps, audit history, login and authorization attempts, error details, rate-limit events, and other records needed to operate, reconcile, secure, and support the service.
• Website information: ordinary request data such as IP address, browser type, requested pages, timestamps, and security logs. When a platform administrator signs in, LiVE uses a secure, essential session cookie. The public website also loads font assets from Google.

LiVE receives information from restaurant operators and their authorized personnel, from customers who interact with restaurant workflows, automatically from authorized devices and web requests, and from configured service providers and restaurant integrations.

Android permissions and device access

Camera

Camera access is requested only after an operator chooses a camera-based feature. For device authorization, LiVE processes QR video frames on the device and does not upload or retain the camera video; the authorization code decoded from the QR image is sent securely to LiVE for validation. A code may also be entered manually. If an authorized user chooses to capture an operational photo or document, that selected file is uploaded and retained with the related restaurant record.

Location

The Android application declares approximate and precise location permissions. LiVE requests location in the foreground when a protected action requires physical-presence verification. Precise coordinates may be sent to the LiVE backend and recorded with the related time-clock, authorization, or audit record. Denying location prevents that protected action but does not cause continuous background collection.

Internet, network state, and local printing

LiVE uses internet and network-state access to communicate with its services and determine whether an operation can be completed. When printing is enabled, LiVE may send a requested print job to the printer assigned to that authorized device on the restaurant's local network. Printer addresses and assignments are restricted to the restaurant and location configured by an authorized administrator.

Payment processing

LiVE supports processor-hosted and customer-present payment workflows. NMI/Network Merchants is currently used for enabled card-present and tokenized payment workflows, and Stripe is configured for certain enabled online event or ticket workflows. The restaurant's assigned processor collects or tokenizes payment-card credentials. LiVE sends transaction amounts and restaurant order references to the processor and receives limited results needed to complete and reconcile the transaction.

LiVE is designed to reject full card numbers, CVV/CVC, expiration data, PIN, and raw card-track data submitted to its own application endpoints. LiVE may retain processor references, authorization codes, transaction status, card brand, and last four digits for receipts, reconciliation, refunds, fraud prevention, accounting, and support.

How information is used

• Provide restaurant operations, point-of-sale, reservations, workforce, inventory, communications, printing, reporting, and support features selected by the restaurant.
• Authenticate administrators and operators; authorize devices; and enforce company, restaurant, location, role, and screen boundaries.
• Process, reconcile, document, and support orders, payments, refunds, and other requested transactions.
• Send operational communications and notifications requested by a restaurant or user, and honor applicable consent and opt-out choices.
• Maintain service availability, diagnose errors, support local printing, investigate incidents, prevent fraud and misuse, and preserve audit history.
• Comply with law, enforce agreements, resolve disputes, and protect restaurants, users, customers, Live Technologies, and others.

How information is disclosed

LiVE discloses information only as needed for the purposes described above, including to:

• The relevant restaurant operator and its authorized users. The operator controls access to its employee, customer, reservation, order, and operating records.
• Hosting and infrastructure providers. The audited production service uses Vercel for web applications and Hostinger-hosted infrastructure for the API, database, and stored operational files.
• Payment providers. NMI/Network Merchants and, for enabled online workflows, Stripe process payment requests and return transaction results.
• Communications providers. Twilio supports configured SMS and voice workflows, OneSignal supports configured push notifications, and Google services support configured email delivery and website font assets.
• Restaurant-directed integrations and local devices. Information may be exchanged with a restaurant system the operator enables or sent to an assigned printer on that restaurant's local network.
• Professional advisers, authorities, and transaction participants. Information may be disclosed when reasonably necessary to comply with law, protect rights and security, investigate misuse, obtain professional advice, or complete a merger, financing, reorganization, or sale subject to appropriate protections.

The LiVE Android application does not contain an advertising SDK and is not used to serve third-party ads. Service providers process information to provide their contracted functions and may maintain their own policies for information they process.

Data retention and deletion

LiVE does not apply one fixed retention period to every type of record. Short-lived authorization codes, reset links, and sessions expire on configured schedules. Other information is retained for the period reasonably needed to provide the restaurant's service, follow the restaurant's documented instructions, maintain operational continuity, reconcile transactions, meet accounting or legal obligations, resolve disputes, prevent fraud, and preserve required security and audit history.

When information is no longer required for those purposes, Live Technologies will delete, de-identify, or securely isolate it as appropriate. Deletion may be limited when a record must be kept for legal, tax, payment, employment, security, fraud-prevention, dispute, or audit reasons. Information retained for one of those reasons will remain restricted to that purpose.

Account and data requests

The LiVE Android application does not currently offer self-service account creation. Restaurant user access and authorized devices are provisioned by the restaurant operator or Live Technologies. An authorized user may ask the restaurant operator to remove access and may submit a request concerning the associated personal information.

To request access, correction, or deletion, email info@liveapp.food with the subject "LiVE Privacy Request." Identify the restaurant, location, your relationship to the restaurant, and the account or record involved. Do not send passwords, payment-card numbers, or sensitive documents by email. Live Technologies may need to verify your identity and coordinate with the restaurant operator before acting. Restaurant employees and customers may also submit a request directly to the restaurant that collected their information.

Your privacy rights and choices

Depending on where you live and your relationship with a restaurant, you may have rights to request access to, correction of, deletion of, or a copy of personal information; to object to or restrict certain processing; or to appeal a decision. You may also withdraw a consent where processing depends on consent. These rights may be subject to identity verification and legal exceptions.

Communication choices can also be managed through the controls supplied for the applicable restaurant program. Where offered, SMS recipients may reply STOP to the sending number. Device permissions can be changed in Android settings, although camera- or location-dependent functions will not work without the required permission.

Security

LiVE uses administrative, technical, and physical safeguards designed to protect information. The audited platform includes encrypted HTTPS connections, secure and expiring sessions, hashed credentials and authorization codes, encryption for sensitive processor and device configuration, rate limits, audit logging, access and role controls, and company and location boundaries. No service can guarantee absolute security.

Children

LiVE is a business and restaurant-operations service and is not directed to children under 13. The Android application is intended for authorized restaurant personnel and devices, not for children to create accounts. A restaurant may record ordinary reservation or party information involving families; the restaurant is responsible for using that information lawfully.

Processing locations

LiVE and its providers may process information in the United States and other places where they operate. Where required, Live Technologies uses appropriate contractual or legal safeguards for cross-border processing.

Changes to this policy

This policy may be updated as LiVE's services, providers, or legal obligations change. The effective date above identifies the current version. Material changes will be communicated through the website, application, restaurant operator, or another appropriate channel.