Essential application storage
Login, session, route-guard and security state needed for Restaurant Cabinet and Platform Admin operation.
Cookie Policy.
How Limvero uses browser cookies and local storage for security, cabinet operation, POS continuity and public website requests.
Storage categories
The current public policy separates essential product storage from analytics or marketing tools.
POS offline storage
Local terminal queues and sync state used by POS/KDS workflows when offline behavior is enabled.
Preference storage
Language, tenant currency, selected location or UI state that helps staff resume work without reconfiguration.
Public demo form metadata
UTM values can be submitted with demo requests so Limvero can understand the request source without tracking guests.
Analytics
Analytics appears here only when an analytics provider is connected and consent behavior matches the policy.
Marketing pixels
Advertising or remarketing tags stay disabled unless the vendor list, consent behavior and policy are updated.
User control and transparency
Tracking stays aligned with the real website implementation and customer consent expectations.
Browser controls
Users can clear or block cookies and storage in the browser, understanding that cabinet login or POS offline behavior may be affected.
Product controls
When preference or consent controls are added to Limvero, this page describes how to use them.
Vendor transparency
Any public tracking, support widget or marketing vendor is listed with purpose and retention expectations.
Plan a clean restaurant rollout.
Talk through locations, POS devices, kitchen workflow, menu migration, API needs and security review before launch.