Privacy overview
Restaurant data should be useful without becoming uncontrolled.
RestoVector processes account details and the restaurant records needed to operate service, kitchen, inventory, purchasing, waste, analytics, workforce tools and support.
Pilot contact: Eduard Pàmpols at eduard@restovector.com. Final controller/processor roles and regional rights are defined in the signed customer documents.
Reviewed: 28 August 2026
Information processed
This can include account and sign-in records; locations, menus, recipes, suppliers, stock, bookings, orders, waste and financial summaries; device and reliability records; and payment status or provider references. Full card numbers and biometric templates are not stored by RestoVector.
Why it is used
Data is used to provide the restaurant service, keep organizations separated, secure accounts, calculate inventory and costs, support users, recover from failures and meet contractual or legal obligations. RestoVector does not sell restaurant data for advertising.
Service providers and retention
Hosting, database, authentication, email, monitoring, optional AI and payment providers may process limited data. The final provider list, data locations, safeguards and retention periods must be documented for each production agreement.
Marketing website analytics and requests
The public website can use optional Google Analytics only when a measurement ID is configured and the visitor accepts analytics. Until consent, the Google script is not loaded. When a person submits a demo, diagnostic or pilot form, RestoVector stores the supplied details to answer the request. Campaign attribution is collected only with analytics consent, retained in this browser for up to 30 days and removed when consent is withdrawn. URL query strings are not stored in page or referrer paths.
Choices and requests
Depending on applicable law and the restaurant's role as controller, people may request access, correction, export, restriction or deletion. Pilot questions can be sent to eduard@restovector.com.
Next step
Review the workflow with your restaurant's data and roles.
A demonstration should show the real product, its limits and how it fits your operation.