Private by design. Every change on the record.
How SmartPOSWizard protects restaurants, employees and guests. Last updated October 22, 2026.
1. Tenant isolation
Each restaurant has its own tenant. Every read and write is scoped to that tenant and the locations a user is allowed to see, and cross-tenant access is blocked and tested.
2. Roles and permissions
Cashier, kitchen, juice bar, manager, owner, HR / payroll and platform admin roles each see only their own screens. Permissions are enforced on the server as well as in the app.
3. Employee PINs
Every employee has their own PIN, verified by the server and never stored in plain text. Five failed attempts lock the account, stations lock after inactivity, and switching employees clears the previous session.
4. Enrolled stations
Each Windows station is enrolled to one restaurant, location and station, and can be revoked remotely. Auto-start opens a locked screen; it never signs anyone in.
5. Payments
Card data is handled by a certified payment provider and terminal. SmartPOSWizard never stores card numbers or security codes. Failed payments never mark an order paid, and retries never charge twice.
6. Guest privacy
Pickup boards, kiosks and customer displays show only what guests need. Kiosk sessions reset between guests.
7. Audit trail
Sign-ins, orders, voids, refunds, time-clock changes, menu and settings changes are recorded with who, what and when.
8. Encryption and hosting
Traffic is encrypted with TLS. Data is encrypted at rest and backed up regularly, and restores are tested.
9. Platform access
Platform administrators sign in separately with strong authentication. Support access to a restaurant’s data requires approval and is logged.
10. Responsible disclosure
Found a security issue? Email security@smartposwizard.com with the details. Please give us reasonable time to fix it before sharing it publicly, and don’t access other customers’ data.
SmartPOSWizard is onboarding pilot restaurants. Some controls above describe how the production service is being built and are validated during the pilot. The public demo runs in your browser with sample data only.