Category
Core hosting and infrastructure
Data categories
Application runtime, encrypted traffic metadata, deployment artifacts and backups if hosted there.
Boundary
The final VPS or cloud provider is listed in the customer order form or security review before production processing starts.
Category
Database and cache infrastructure
Status
Self-managed in Limvero deploymentData categories
PostgreSQL, Redis and operational service data processed inside the selected Limvero environment.
Boundary
Limvero does not claim an external managed database vendor by default. Any managed provider is disclosed before use.
Category
Email and transactional communications
Status
Provider not selected in public buildData categories
Business contacts, onboarding messages, support communications and security notifications.
Boundary
A mail provider is added only when configured for production and is disclosed before customer communications are routed through it.
Category
Monitoring and incident communications
Status
Provider not selected in public buildData categories
Service health metadata, incident communication contacts and limited diagnostics needed to operate the service.
Boundary
The public status page is manual until production monitoring automation is connected and provider details are approved.
Category
Payment, fiscal and delivery providers
Status
Customer/provider-specificData categories
Only the integration data needed for a contracted payment, fiscal or delivery workflow.
Boundary
These providers are not included by default. Restaurant-selected or region-specific provider terms apply when integrations are enabled.
Status
Limvero support-session workflow by defaultData categories
Support session metadata, scoped account diagnostics and audit records for customer-approved troubleshooting.
Boundary
No third-party help desk vendor is publicly claimed by default. Any added support vendor is disclosed before production use.