Trust centre
Clear controls, clear limits and no invented certifications.
This public summary explains how RestoVector currently approaches account security, restaurant separation, access, monitoring, backups and responsible product operation.
This page is a product and pilot-stage transparency summary. It does not replace a signed customer agreement, data-processing agreement or independent legal review.
Reviewed: 28 August 2026
Restaurant and role separation
Every restaurant record is scoped to an organization. Staff accounts receive explicit roles and location access. Waiters, cooks, managers, owners and company operators do not share the same permissions.
- ✓ Organization-scoped data access
- ✓ Role and location permissions
- ✓ Owner-governed manager assistant access
- ✓ Separate private company operations console
Operational safeguards
Sensitive changes are validated on the server. Restaurant activity uses audit histories where appropriate, payment-provider references do not contain full card data, and offline access is prepared per device with a temporary credential.
- ✓ Server-side authorization
- ✓ Signed payment-provider workflows when connected
- ✓ Error monitoring and health checks
- ✓ Controlled device and offline preparation
Data and AI boundaries
Restaurant data is used to provide the service, calculations, security and support. The management assistant is read-only and location-scoped; access metadata can be audited while conversation text is not kept in the restaurant database.
What remains customer-specific
Final retention periods, subprocessors, service levels, support targets, workforce notices, payment providers and regional legal terms belong in the executed customer agreement and deployment plan.
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.