Two-step sign-in
- Staff can turn on a code from an authenticator app as a second step at every sign-in.
- Recovery codes cover a lost phone.
- If a person loses both, you can reset their authenticator. They are signed out everywhere and set it up again.
Restaurant POS security and cash control means no one person can move money alone. In Zentaro Serve a void or a refund needs a reason and a second person. Staff permissions limit what each role can do, and void control and discount limits are set by you.
Many people hear "secure" and think of encryption. The question an owner often has is smaller and sharper: at eleven at night, when you are not there, who can make a sale disappear?
Three actions can quietly remove value from a restaurant: voiding a sale, refunding a payment, and writing off stock. In Zentaro Serve these can need a second person to approve. You choose who can void or refund, and the limit above which a second person is needed.
And the rule doesn't get weaker offline. A void that needs approval captures that approval on the terminal itself, even offline, and carries it to the server when the line returns. The manager needs to have signed in on that terminal while it was online. Going offline does not skip the approval.
Looking for who can see and do what? See Staff access control.
The same app, signed in by different people. Each one sees only the screens their role allows.
A waiter sees tables, orders and bills. Not your reports, costs or settings.
A manager runs their outlet. Not your company settings.
You decide what each role can do.
A region manager sees only their region.
An approval to void or refund must come from a signed-in person, never from a terminal that happens to be logged in. Kitchen roles have no permission to take payment.
Servers and bartenders handle orders, not settlements. Touching an order has never implied authority over the money on it, and nobody has to remember to switch that off.
Hiding a menu entry is not security. Access is checked on the screen, again if someone types the URL directly, and again at the API — so a hand-built client gets the same answer as the app.
The audit trail is evidence, not a diary. Restaurant users, including the owner, have no screen to edit it. That is why it helps in a dispute.
Each restaurant's information is kept separate from every other restaurant's. A manager given one outlet is set up to see that outlet, not a sister outlet. You choose who gets which outlet.
Everything you hold about one person can be exported as a bundle, and erased when retention says it must be. India's DPDP Act gives your guests that right; answering it should not mean a developer writing a query.
One-time codes are stored so that reading the database cannot recover a live one, and a service refuses to start on a publicly-known secret rather than accepting attacker-signed tokens quietly.
Sessions expire, and a revoked login stops working everywhere rather than in the one place somebody remembered. When a person leaves your team, their access leaves with them.
We count visits without cookies. When a page opens, the counter records which page it was and the date, and adds one to a daily total. For a few actions, such as using a calculator or printing a template, it also records the name of the action. It never records what you type. The counter gives you no ID, so it cannot link one visit to the next. The counter does not save your IP address, your browser or device details, or the page you came from. The one exception is a calculator shown on another website, described below. The counts only help us see which pages and tools are useful. To block abuse, your IP address is held in the memory of the server to limit repeat requests. It is not written to disk, and it is lost when the server restarts.
To ask what we hold about you, or to ask us to delete it, use our contact page.
Privacy and grievance contact: [email protected], Zentaro LLP, Moshi, Pune 412105, Maharashtra, India.
Write to this address to see, correct or erase your details, to take back your permission, or to complain about how we handle your data. If you are not happy with our reply, you may complain to the Data Protection Board of India.
The problem you know
What it is not
Who it is for
Talk to us and we will show the controls on your own roles. Talk to us
Set limits by role, ask for a reason on every void and refund, and ask a second person to approve refunds. Count each drawer at close, so a gap shows with the shift it came from.
That depends on the permissions you set. You choose who can refund, and a refund can need a second person to approve it.
A void cancels an item or a bill that was already entered. Because it can hide a sale, each void needs a reason, and a manager PIN above your limit.
Yes. You set a discount limit for each role. Above it, a manager decides. You can also set a lowest price that nobody sells under.
Lost-device recovery lets you switch the device off, so it does not stay signed in. Every till is paired to your outlet with a code.
Can one person void a settled bill alone? Does that change when the internet is down? Can a kitchen screen approve anything? And can anyone in the building edit the audit log? You are entitled to specific answers, from us as much as from anyone else.
Last updated: