Security, privacy and data handling
How RestCall handles payments, guest data, staff authority and devices — described as mechanisms you can check, not badges you have to take our word for.
Charges run through your own merchant account.
A guest can ask to be forgotten, on the call.
Consequential actions carry a name, not a shared PIN.
Payments
Card data never reaches RestCall servers. Charges run through your restaurant’s own merchant account — Stripe or Stax — and settle directly to your bank on your own payout schedule. There is no platform balance in between, and no week where your revenue is sitting with us.
How payments workThe rest of the surface
Each area below is handled by something that ships today. Where a capability is still in pilot, it says so.
The guest can leave, and take their record with them, without waiting on a support ticket.
Every text a guest receives is one they agreed to, and one they can stop.
Authority is attached to a person. Refunds, voids and drawer opens are attributable after the shift ends.
A tablet on an open counter is a risk. It is treated like one.
Recordings exist to fix the call, and they do not sit around after they have stopped being useful.
A group with several addresses should not hand every manager every location.
What this page is not
Everything above describes how the software behaves, because that is what we can show you. We do not publish certification logos, audit seals or uptime numbers on a marketing page.
If your group runs a security review, send us the questionnaire. We will answer it against the product as it ships, and say plainly where something is roadmap rather than live.
Before you sign
Send the questionnaire your group uses. We answer it against the product as it ships today — and tell you where something is still roadmap.
