Privacy Policy.

How Limvero handles restaurant account, operation, guest, loyalty, security and public website request data.

Data categories

Limvero processes data needed to operate the restaurant platform and support commercial onboarding.

Tenant, restaurant, location, staff, role, device, billing contact and support metadata.

Menu, orders, payments metadata, cash shifts, stock movements, reports, print jobs and audit events.

Customer profiles, contact details, order history, loyalty balance, promo usage and preferences when provided by the restaurant.

Sessions, token metadata, API key metadata, support sessions, request logs, webhook delivery state and system diagnostics.

Demo-request business contact details, consent record, source path, UTM values and hashed IP metadata.

Sales, onboarding, support and security-review communications related to the restaurant account.

The policy is written to align with implemented product behavior and procurement review.

Data is used to provide Limvero, secure accounts, support restaurants, improve reliability and handle lawful business requests.

Restaurant guest and loyalty records belong to the restaurant tenant and are processed according to tenant workflows.

Public forms collect business request details only and avoid uploads or guest/customer exports.

Platform workflows support tenant export snapshots, guest CRM anonymization and deletion request processing for offboarding and privacy operations.

Hosting, database, email, analytics and support vendors are listed when selected for production use.

Access control, tenant isolation, token rotation, production checks, backup/restore and audit records support privacy protection.

Privacy questions, data-processing requests and DPA review should go through the dedicated privacy mailbox.

Talk through locations, POS devices, kitchen workflow, menu migration, API needs and security review before launch.