Access control
Owners, managers, waiters, kitchen and delivery each get a different login. You can revoke a device without resetting the whole restaurant.
Security
Security
Role-based access, encrypted payments and least-privilege staff logins — designed for a busy floor, not a compliance slide deck.
DinePOS separates guest, staff, rider and admin sessions. Payment card data stays with certified processors. Restaurant data is scoped to the outlet that owns it.
Payments
UPI, cards and wallets go through Stripe, Razorpay and similar processors. We never store full card numbers on restaurant servers.
Data handling
Menus, tickets and guest profiles live in isolated restaurant records. Exports and backups are available to the owner account.
Operations
Session cookies are HttpOnly. CSRF tokens sit on every form. Demo accounts are clearly labelled so live kitchens are not mixed with sample data.
- TLS on every public page
- Password hashing for staff and guests
- Per-restaurant media folders
- Activity-aware staff sessions
- Optional Google login for guests
- Printer and KDS traffic stays on your LAN when configured
Talk to the DinePOS team
Call +91 9211-764-655 or write to sales@dinepos.com. We can walk a menu import, a table QR pack, or a partner pilot.