This page lists the privacy and tax features Butterchop's software provides for restaurants in India, what it does not provide, and what restaurants remain responsible for. It is not a certificate of compliance and is not legal or tax advice. Using Butterchop does not by itself satisfy the Digital Personal Data Protection Act, 2023, its Rules or GST law.
Review status
Prepared: , from an engineering review of Butterchop's source code. Checked again against the source code on .
Owner: Butterchop product team.
Legal review: pending. Counsel has not yet reviewed how these laws apply to Butterchop or to restaurants.
Which provisions apply, and from when, depends on the business and its activities. Confirm them with qualified counsel or a tax adviser.
How to read the tables
Available
The software provides this control today.
Partial
The software provides part of it; the limitation is stated.
Unavailable
The software does not provide it.
Not determined
We have not yet reviewed it well enough to say.
Evidence names the part of Butterchop's source code that implements a control. A passing test shows that the control works as built, not that a law is satisfied.
Privacy and the DPDP Act
Requests to access, correct or erase personal data
Status
Available
What the software does
Restaurants record one case per request with a task for each data area (guest profile, orders, waitlist, loyalty, marketing, CRM, consent, external processors). Fulfilment waits until the requester is verified, and a case closes as fulfilled only when every task is complete.
The restaurant decides how to answer each request and completes tasks Butterchop cannot perform itself, such as requests to outside processors.
Response deadlines for India
Status
Unavailable
What the software does
Deadline rules exist only for California (US) and the EU, and their deadlines count as unverified until an administrator approves the rule. Requests cannot be filed under an India rule.
The restaurant decides when a hold is needed and when it ends.
Erasure that survives a database restore
Status
Partial
What the software does
Erasure first requires a current preview. Each erasure is written to an independent journal, and erasure is refused if that journal is missing, unsafe or turned off. Before a restaurant's database serves a request or a background job, Butterchop checks it against the journal: a database restored from an older copy gets every later erasure applied again first, and a database whose journal is missing or does not match is refused instead of served. A restore from an in-app backup runs the same check.
The check works only where the journal is set up for the deployment; where it is turned off, erasure is not available. Copies kept outside the database, such as backup files in the restaurant's own storage and exports, keep erased data until their retention removes them.
Consent and notice records
Status
Available
What the software does
Grants are recorded by purpose and channel together with the notice version shown. Withdrawals are recorded by purpose and channel; they record a notice version only when one is given. Promotional text messages need a confirmed double opt-in.
The restaurant issues any tax invoice the law requires.
Seller GST registration (GSTIN) settings
Status
Partial
What the software does
Each location can record the seller's legal name, registered address and GSTIN as dated revisions. Butterchop checks the GSTIN format and check character and needs an India jurisdiction for it. It does not confirm the GSTIN with the GST portal, so a GSTIN stays unverified unless the restaurant records its own verification evidence. Each new receipt keeps a copy of the seller details in effect on the order's business day. The printed receipt shows only the seller's legal name and GSTIN from that copy; it does not print the registered address. The GSTIN prints only when the seller legal name is set.
The restaurant holds its registration, enters it correctly and confirms it with the GST portal. A well-formed GSTIN is not proof of a valid registration.
Tax invoices under CGST Rule 46
Status
Unavailable
What the software does
Butterchop does not produce tax invoices with the Rule 46 particulars.
Evidence
None: no software control exists.
Responsibility and limits
The restaurant issues tax invoices from a system that supports them.
Tax summary by rate
Status
Available
What the software does
A report groups the tax recorded on closed checks by currency, tax name, rate and the jurisdiction code saved with the sale. Older sales without a saved jurisdiction show as unidentified and are not relabeled. Refunded tax is subtracted on the refund's business day, exemptions are shown separately, and any difference from check totals shows as unresolved, never as an invented adjustment. Each row opens the checks and refunds behind it and the rate definition. It is analytics, not a filed return.
The restaurant configures rates and jurisdiction codes and decides place of supply and the split into CGST, SGST, UTGST or IGST. The report does not determine them.
E-invoicing (IRN) and e-way bills
Status
Unavailable
What the software does
The software does not generate e-invoices or e-way bills.
Evidence
None: no software control exists.
Responsibility and limits
The restaurant meets any e-invoicing or e-way bill obligation with other tools.
UPI payee settings
Status
Partial
What the software does
Each location can store a UPI ID and payee name. A second staff member reviews it before it can be activated. Butterchop does not verify the account with a payment provider, and a payee setting does not request, confirm or record a UPI payment.
The restaurant confirms the UPI ID with its bank or payment app and confirms each payment there.
UPI payment QR and staff confirmation
Status
Partial
What the software does
For an open order, staff can show a UPI payment QR. The server makes the upi://pay link from the location's verified, active payee and the exact amount owed. The QR is bound to the order revision, the payee revision and that amount, and it expires after 10 minutes. A change to the check, the payee or the balance makes it invalid. A staff member records the payment after seeing the credit in the merchant app, a bank statement or a payment soundbox, and enters its 12-digit UPI transaction reference (UTR). One UTR pays only one tender. The payment is marked as confirmed by staff, not by a provider. If the payment names an expired or changed QR, Butterchop records the payment and marks that QR invalid. UPI is available only for orders in Indian rupees, and not in training mode.
No payment provider confirms UPI payments; the staff confirmation is the only check. Butterchop has no UPI reconciliation report, so the restaurant matches each UTR against its bank or provider statement. Butterchop cannot refund to UPI; a different refund method is possible only where the tender policy allows it.
What restaurants remain responsible for
Working out, with counsel, whether you are a data fiduciary for your guests' data and what that requires.
Giving guests notice, obtaining and honoring consent, and answering their requests within the legal timelines.
Publishing your own privacy and grievance contact, and handling breaches and notices.
GST registration, classification of what you sell, current rates and place of supply.
Issuing tax invoices, e-invoices and e-way bills where required, and filing returns.
Confirming your UPI ID with your bank or payment app and confirming each payment there.
Butterchop's role
Butterchop provides software that restaurants use to run their business. Whether Butterchop acts as a data processor for a restaurant, or has other obligations, has not yet been confirmed by legal review. Our general practices are described in the Privacy Policy.
Questions
For questions about these features, use theButterchop Support contact pageor email support@butterchop.com. Do not send guest personal data, data exports, passwords, tax portal credentials or payment details. Guests with a request about their data should contact the restaurant they dealt with.