Product-aligned
Legal pages describe the current Limvero product boundaries and avoid unsupported provider or certification claims.
Public legal materials for restaurants evaluating Limvero: privacy, terms, cookies and data processing in one place.
How Limvero handles account, restaurant operation, guest, loyalty, security and support data.
Commercial service scope, customer responsibilities, acceptable use and provider boundaries.
Rules for lawful use, account access, API behavior, integrations, privacy and enforcement.
Availability, incident priority, maintenance and custom SLA boundaries.
Support channels, support sessions, safe troubleshooting and incident routing.
Subscription plans, add-ons, taxes, provider fees, overdue invoices and billing operations.
Cancellation requests, subscription refund review, provider fees and data offboarding.
Essential storage, public site tracking boundaries and user control expectations.
Processor commitments, security measures, subprocessors, data requests and deletion flow.
Provider categories, selection status, data categories and customer notice boundaries.
Responsible security reporting rules, safe testing boundaries and response process.
Legal pages describe the current Limvero product boundaries and avoid unsupported provider or certification claims.
Restaurant guest and loyalty data are treated as tenant-controlled operational data processed by Limvero.
Legal pages connect back to tenant isolation, access control, backup, export and deletion workflows.
These public materials are drafted for commercial review and prepared for qualified counsel before paid rollout.
The legal center is informational and product-aligned. Final contract language, local law requirements and customer-specific terms are reviewed during procurement.
Open Trust CenterTalk through locations, POS devices, kitchen workflow, menu migration, API needs and security review before launch.