Your data, and who can see it
Restaurant data security built into the database
Your sales, your staff and your guests’ details are kept apart from every other restaurant, and every look at them leaves a record.
- 1Your own drawerWalled off in the database, with row-level security forced
- 2Guest details encryptedPhone numbers and names, stored encrypted
- 3Support only with a reasonA written reason before a support session opens
- 4Every look recordedEach action taken in the session is recorded
- Forcedrow-level security, so one restaurant cannot read another
- Encryptedguests’ phone numbers and names
- A written reasonbefore CountStand support can look at your data
- HTTPS onlywith HSTS and a strict content security policy
01At a glance
How your data is kept.
- Walled off in the databaseRow-level security is declared on the tables and forced, so the rule applies to every query, the app’s own connection included.
- Guest details encryptedPhone numbers and names are stored encrypted, so a copy of the database is not a list of your guests.
- Support access with a reasonA CountStand support session needs a written reason to open, and each action taken in it is recorded.
- Told before we change anythingWe tell you before we change anything of yours, and if it could not wait, straight afterwards, naming what changed.
- An audit log you can readEvery governed change, with who made it and when, under Administration.
- Yours to takeExport everything you have put in, any time, including on the way out.
02In detail
What stops one restaurant from seeing another’s data?
The database does. Many systems keep customers apart with a filter the application has to remember on every query; miss it once, in a new report or a background job, and one restaurant’s numbers appear on another’s screen. CountStand declares the rule on the tables themselves, with row-level security, and forces it, so it applies to every query that touches them.
The practical result is a boundary that does not depend on anyone remembering it. A screen with a bug can show you the wrong row of your own data; it cannot pull up another restaurant’s rows, because the database refuses them to a request made for yours.
Who at CountStand can see my data?
Support, when you need help, and only with a reason. A support session has to carry a written reason before it opens, and every action taken in it is recorded against that session.
We also tell you before we change anything of yours. If a change could not wait, we tell you straight afterwards, naming exactly what changed. And the data stays yours: you can export everything you have put in, at any time.
03Questions
Questions about data security.
By the database. Row-level security is declared on the tables and forced, so a request made for your restaurant cannot return another restaurant’s rows.
Yes. Guests’ phone numbers and names are stored encrypted, and they are erased two years after the guest’s last order.
Only to help you, and only with a written reason given first. The session, and what is done in it, is recorded.
Yes. You can export everything you have put in, at any time, including when you leave.
No. It is the same in every plan, from ₹2,999 a month per outlet.
04Read next
- DPDP and personal dataEncryption, erasure after two years, and the eight-year tax record.
- Roles and PINsWho on your team can do what, and the record each approval leaves.
- Offline POSWhen the line drops, billing carries on, and every action is sent in order, exactly once, when it returns.
- Security at CountStandHow the product and the company handle security.
Keep your data walled off
The same protection in every plan, from ₹2,999 a month.
From ₹2,999 a month per outlet, plus GST