Terms of Service.

Commercial service boundaries for restaurants using Limvero, written to separate Limvero software from third-party provider obligations.

Service and customer responsibilities

These terms explain what Limvero provides and what restaurant teams control.

Limvero provides restaurant operations software for POS, kitchen, menu, inventory, loyalty, reports, API keys and webhooks.

Customers manage authorized users, staff PIN access, device assignment, API keys, restaurant data accuracy and local compliance.

Fiscalization, acquiring, delivery marketplaces, hardware and third-party integrations require separate provider terms when connected.

Customers keep credentials private, assign least-privilege roles, rotate API keys and report suspected compromise quickly.

The service cannot be used for unlawful processing, abuse, credential sharing, unauthorized security testing or platform misuse.

Support sessions are controlled, time-bounded and designed to avoid credential sharing during troubleshooting.

Plan, billing, availability and offboarding terms match the signed commercial agreement.

Plans are organized by restaurant scope, locations, workflow modules, API usage and onboarding/support requirements.

Renewal, suspension, cancellation, refunds and add-on rules are confirmed in the order form or subscription agreement.

Public status and incident communication are separate from any customer-specific SLA agreed in writing.

Tenant export snapshots and deletion request workflows support commercial offboarding and data-return expectations.

Material service, security or legal updates are communicated through appropriate product, legal or account channels.

Final paid contracts are reviewed with counsel and aligned with the customer jurisdiction and rollout scope.

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