Unlawful or harmful activity
Do not use Limvero to process illegal activity, deceptive orders, fraud, sanctions violations, harassment or content that creates safety risk for guests, staff or operators.
Acceptable Use Policy.
Rules that protect restaurants, guests, staff, integrations and Limvero platform availability.
Prohibited use
These activities are not allowed on Limvero or through connected API, webhook, POS, KDS, support or integration workflows.
Credential and access abuse
Do not share staff credentials, bypass role controls, reuse POS PINs across people, sell access, impersonate another user or attempt to access another tenant.
Unauthorized security testing
Do not run scanners, load tests, brute force, destructive payloads, social engineering or vulnerability tests outside the Vulnerability Disclosure Policy.
API, webhook and integration misuse
Do not scrape, overload, replay, forge signatures, call endpoints outside granted scopes or route webhooks to destinations you do not control.
Service disruption
Do not interfere with platform availability, abuse offline sync, flood print or kitchen queues, exhaust rate limits or bypass production safeguards.
Privacy misuse
Do not import guest data without a lawful basis, export data to public channels, use loyalty data for unrelated purposes or avoid deletion/export obligations.
Customer responsibilities
Restaurants control their local operation, staff access, connected providers and lawful use of guest and business data.
Restaurant and local compliance
Customers are responsible for local restaurant, tax, fiscal, labor, alcohol, delivery, consumer-protection and privacy obligations that apply to their operation.
Provider compliance
Payment, fiscal, delivery, hardware and marketplace providers remain governed by their own contracts and certification requirements when connected.
Staff and device controls
Customers must assign least-privilege roles, revoke departed staff, protect POS devices, rotate API keys and review audit records for unusual activity.
Data handling
Customer exports, guest lists, reports and support data should be transferred only through authenticated workflows and approved business channels.
Incident reporting
Suspected account compromise, exposed API keys, unauthorized support access or risky integrations should be reported quickly to Limvero support.
Accurate configuration
Menus, prices, taxes, stock, service points, kitchen routing, loyalty rules and public API usage must reflect the restaurant workflow and local requirements.
Enforcement
Limvero uses proportionate technical and account controls to protect the platform and other tenants.
Technical controls
Limvero may apply rate limits, revoke sessions, rotate or disable API keys, block webhook destinations, disable integrations or require credential resets.
Account action
Material misuse can lead to feature restriction, tenant suspension, support-session revocation, delayed deletion handling or contract termination.
Investigation boundary
Limvero may preserve relevant audit, security and diagnostic records needed to investigate misuse, protect tenants or meet legal obligations.
Security research is handled under the Vulnerability Disclosure Policy. Commercial terms, provider boundaries and billing rules remain governed by the signed agreement.
Plan a clean restaurant rollout.
Talk through locations, POS devices, kitchen workflow, menu migration, API needs and security review before launch.