Restaurant operational data
Menu, order, payment metadata, cash shift, inventory, loyalty, report and audit records are retained while the tenant account is active and needed for restaurant operations.
Data Retention.
How Limvero describes retention boundaries for restaurant operation data, exports, diagnostics and deletion workflows.
Retention categories
Retention is tied to implemented product workflows and customer-controlled tenant lifecycle actions.
Tenant exports
Stored tenant export snapshots include checksum, byte size, storage metadata, retention metadata and truncation flags when capped collections are exported.
Report exports
Async CSV report exports include expiration handling, blocked expired downloads, expired content cleanup and retained metadata for auditability.
Support sessions
Support-session metadata, approvals and revocations are retained as security and troubleshooting records for controlled account access.
Public demo requests
Public contact requests store business lead details, consent, source metadata and hashed IP metadata instead of raw IP addresses.
Security and diagnostics
Security, request, webhook, deployment and worker diagnostics are retained as needed to investigate abuse, recover jobs and operate the service.
Lifecycle controls
Export, deletion and support workflows are designed to avoid accidental data loss or unsafe public transfer.
Export before deletion
Tenant deletion requires a valid export snapshot, reason, delay window, confirmation phrase and platform audit before irreversible deletion is applied.
Retention depends on contract and law
Specific retention periods can vary by signed agreement, local legal requirements, accounting needs, security investigation or provider obligations.
No public-form data exports
Guest lists, tenant exports and operational data should be transferred only through authenticated workflows and approved business channels.
Data retention works together with the Privacy Policy, DPA, tenant export snapshots and delayed deletion process.
Plan a clean restaurant rollout.
Talk through locations, POS devices, kitchen workflow, menu migration, API needs and security review before launch.