Subprocessor List.

Current provider categories, selection status and data boundaries for Limvero restaurant data processing.

Provider categories

This list avoids naming vendors that have not been selected for production. It documents the processing boundary Limvero will maintain until a customer-specific provider list is approved.

Category

Core hosting and infrastructure

Status
Contract-specific
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 deployment
Data 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 build
Data 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 build
Data 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-specific
Data 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.

Category

Support tooling

Status
Limvero support-session workflow by default
Data 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.

Change notice

Material subprocessor additions or replacements are communicated through legal, account or security-review channels before the affected processing starts when the customer contract requires notice.

Data transfer boundary

Guest exports, restaurant operational exports and deletion requests stay inside authenticated tenant or platform workflows. They should not be sent through public contact forms.

Customer-specific review

If a restaurant needs a named provider list before go-live, Limvero confirms the production hosting, email, monitoring and integration choices during procurement.

Subprocessor details are reviewed with the Data Processing Agreement, Privacy Policy and customer security review before production launch.

Plan a clean restaurant rollout.

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

Contact Limvero