SECURITY / PRODUCT STATUS
Clear controls.
Clear status.
The first venue pilot, a client deployment and the planned shared CRM have different security scopes. Here is what exists now and what we define before launch.
01 IN THE FIRST PILOT
The controls in use today.
The single-venue pilot has an HTTPS demo with table ordering, stay-linked room access and a protected staff workspace. It is in final readiness checks before live venue use.
- Connections
- Guest and staff pages use HTTPS to encrypt data while it travels between browser and server.
- Staff workspace
- The operations queue requires authentication. Individual staff roles are a separate production deployment decision.
- Guest context
- Table and stay-linked flows carry the relevant service point into a request.
- Website preview
- The interactive samples on this website send no real order or payment.
02 PER DEPLOYMENT
Agreed before a venue goes live.
A production proposal sets out the controls for that property and its workflow. The scope is written down before we describe a control as active.
- Access rules
- Named accounts, password and session rules, and permissions for each staff role.
- Stored data
- Hosting location, storage encryption, and who can access guest and order records.
- Recovery
- Backups, restore checks, retention periods and deletion arrangements.
- Integrations
- Payment-provider responsibilities, audit needs and any external messaging service.
03 SHARED CRM RELEASE GATE
Multi-business separation must be tested.
The shared CRM is in development. We will treat tenant isolation and access checks as release requirements before multiple businesses use one platform.
- Venue boundaries
- Each business must be limited to its own menus, staff, requests and reporting.
- Permission checks
- Cross-venue access and staff permissions must pass testing before launch.
- Client handoff
- The final security, support and data-handling scope belongs in the product agreement.
FOR YOUR VENUE