Skip to content

Personal data, held carefully

DPDP-compliant restaurant software, built around guest data

India’s Digital Personal Data Protection Act asks you to protect the personal data you hold, and not to keep it once its purpose is over. This is what CountStand does with it.

The short answer DPDP-compliant restaurant software has to protect guests’ personal data and not keep it longer than it needs to. CountStand stores guests’ phone numbers and names encrypted, and erases them two years after the guest’s last order; the orders stay, anonymised, because a hole in the sales record is illegal. Bills, tax records and the audit trail are kept for eight years, as the law requires, and the audit log shows who changed what, and when. In every plan, from ₹2,999 a month.
DPDPGSTBills8 years2 years1Encrypted2Erased3Bills kept
  1. 1EncryptedA guest’s phone number and name, never kept as plain text
  2. 2Erased2 years after the guest’s last order, automatically
  3. 3Bills keptBills and tax records stay 8 years, without the person on them
Fig. 0One guest’s record at a sample restaurant: from the locked box to the archive shelf.
  • Encryptedguests’ phone numbers and names, as stored
  • 2 yearsafter a guest’s last order, their details are erased
  • 8 yearsfor bills, tax records and the audit trail
  • Audit logwho changed what, and when

01At a glance

What CountStand does with personal data.

  • Encrypted when storedA guest’s phone number and name are encrypted in the database, not kept as plain text.
  • Erased on a clockTwo years after a guest’s last order, their personal details are erased automatically. Nobody has to remember to do it.
  • Orders kept, anonymisedThe bills stay, without the person on them, because a hole in the sales record is illegal.
  • The tax record kept eight yearsBills, payments, GST records and the audit log are kept for eight years, and marked when their period ends rather than deleted.
  • An audit logAdministration, then Audit log: every governed change, who made it and when.
  • Support access on the recordIf CountStand support looks at your data, it gives a written reason first, and the session is recorded.

02In detail

What does the DPDP Act ask of a restaurant?

The Digital Personal Data Protection Act treats the phone numbers and names a restaurant collects as personal data held in trust. It asks for that data to be protected, used for the purpose it was given, and not kept once that purpose is over.

CountStand builds the parts a till can carry into how it stores data. Guests’ details are encrypted when they are written. They are erased on a clock rather than on somebody’s memory. And what happened to them is kept in an audit log you can read.

Why erase personal data but keep the bills?

Because two laws ask for two different things. Personal data should not be kept longer than it is needed, so a guest’s phone number and name are erased two years after their last order. The clock runs from the last order, not the first, so a regular is not erased while they are still coming in.

Tax law asks for the opposite: bills and tax records kept for eight years, with no gaps. So the orders stay, anonymised, and the eight-year records are marked when their period ends rather than deleted. The person leaves the record; the record stays whole.

03Questions

Questions about DPDP and personal data.

Keep what the law needs, and no more

Encryption, the erasure clock and the audit log, in every plan from ₹2,999 a month.

From ₹2,999 a month per outlet, plus GST