Privacy Policy

There are two different relationships here, and they matter, because they decide who you ask when you want something changed or erased.

We do not collect more than the above, we do not buy personal data from anyone, and we do not run advertising or advertising trackers.

Hotels are required to record a guest’s identity. The Service is built to store the type of document and its last four digits only — never the full number, and never a scan or photograph of it. That is a deliberate design decision: the full number is a liability nobody needs to carry.

If a property records a full identity number somewhere it does not belong — in a notes field, for instance — that is the property’s doing and its responsibility. We advise strongly against it.

• To perform the contract with you — running the account you asked for.
• For the legitimate uses the DPDP Act allows, including keeping the Service secure and preventing fraud.
• To meet a legal obligation — tax and company law require certain records to be kept for a set number of years.
• With your consent, where consent is what the law requires. You may withdraw it, and withdrawing it is as easy as giving it.

We share personal data only with the processors that make the Service work, and only as far as each needs:

We may also disclose data where the law requires it, to a court or an authority acting within its powers, or to a buyer of our business — in which case this policy continues to apply until you are told otherwise.

We do not sell personal data, and we never will.

The Service can show a property anonymous, aggregated figures from other properties nearby — what ingredients are costing, where there is surplus stock, how busy the area is. This is off unless a property switches it on, each kind of sharing is a separate switch, and what leaves an account is a number, never a guest, a customer, an order or a staff record. No property can see another’s rows.

• Data is stored in India, in Supabase's Mumbai region.
• We keep operational records for as long as the account is live, and then for 60 days so you can export them.
• Tax and financial records — invoices, bills, GST data — are kept for 8 years, because the Income-tax Act and the GST law require it.
• Security and access logs are kept for 180 days.
• When a retention period ends, data is deleted or irreversibly anonymised.

• Every connection is encrypted in transit (TLS), and data is encrypted at rest by our hosting provider.
• Passwords are stored as one-way hashes. Nobody at DineFlow can read your password.
• Every property's rows are separated at the database itself by row-level security, not merely by application code — so a bug in a screen cannot expose another property's data. This is tested.
• Staff access inside a property is limited by role; an owner decides what each person can open.
• Our own access to customer data is limited to the people who need it to support you, and administrative access to a property is recorded and shown in the app while it is happening.

No system is perfectly secure. If a breach occurs that is likely to affect you, we will notify you and the Data Protection Board of India as the DPDP Act requires, without undue delay.

Under the DPDP Act, 2023 you may ask us to:

• Tell you what personal data we hold about you and who it has been shared with.
• Correct anything inaccurate, complete anything incomplete, or update anything out of date.
• Erase personal data where it is no longer needed for the purpose it was collected for and no law requires us to keep it.
• Nominate someone to exercise these rights on your behalf if you die or become incapable.
• Withdraw a consent you gave.
• Raise a grievance — and if you are not satisfied with our answer, complain to the Data Protection Board of India.

Write to privacy@dineflow.in. We answer within 30 days. We may need to confirm who you are first, so that we do not hand somebody’s data to the wrong person.

If a property recorded you as a guest, customer or staff member, ask that property first — they decide what happens to their records. Tell us and we will pass the request on and make sure it is acted on.

We use no advertising or tracking cookies. What the Service stores on your device is only what it needs to work:

• A session cookie that keeps you signed in.
• Small preferences — the theme you chose, the kitchen station a screen is set to.
• An offline queue holding orders taken while the internet was down, so they can be sent when it returns.

Clearing your browser data removes all of it, and will sign you out and discard anything still queued.

The Service is for businesses and is not directed at children. We do not knowingly collect the personal data of anyone under 18 as a user. A property that records a child in a booking must have the consent of a parent or guardian, as the DPDP Act requires.

We will post any change here and update the date at the top. If a change materially affects your rights we will tell you by email and in the app at least 30 days beforehand.

For anything about privacy, write to privacy@dineflow.in.

The Grievance Officer is [grievance officer name — not set], at grievance@dineflow.in. We acknowledge within 48 hours and resolve within 15 days.

Postal address: [registered address — not set]

See also the Terms of Service and the contact page.