Venue data separation
Users, menus, orders, reports, settings and assigned devices are handled with the current venue context.
Platform
Security and trust
Practical controls for the people, venues and devices using QRelia.
Security is part of the venue account, the order flow and the connected device setup. This page describes controls that are implemented today without claiming certifications QRelia does not hold.
Account and venue controls
The important boundaries are carried through the application.
Individual staff access
Venue teams can use named accounts and roles instead of one shared password.
Two factor authentication
Eligible accounts can add an authenticator step and receive recovery codes.
Recorded activity
Administrative actions can be reviewed to support accountability and investigation.
Responsible access
The venue remains responsible for who can enter the account.
Use a separate account for each member of staff, remove access when a role changes, protect recovery codes and enable two factor authentication wherever practical.
- Email confirmation for new accounts
- Role based access within the venue
- Anti forgery protection on state changing forms
- HTTPS for public application traffic
- Security and diagnostic logging
Connected device controls
A device is paired to the intended venue before it enters live service.
The setup uses pairing values from the venue account. QRelia then records the assigned identity, connection state and recent contact for the device.
- Guided setup from the venue account
- Venue controlled pairing values
- Assigned device identity
- Online status and heartbeat information
- Profile and animation controls from the venue account
Payments and processors
Subscription card details are handled by Stripe rather than stored directly by QRelia.
Email delivery and optional analytics involve separate providers described in the Privacy Policy. Public analytics loads only after the visitor gives permission through the cookie choice.
Report a security concern
Send enough detail for the issue to be investigated safely.
Do not include passwords, full payment card details or live pairing secrets in the first message.