Privacy policy

Last updated: 14 October 2026 (product renamed from RasoiFlow to DineDost)

This policy explains how DineDost, a product of SoftOps Technology LLP ("DineDost", "we", "us"), handles information. DineDost is restaurant billing and management software that a restaurant installs on its own Windows computer and uses over its own local network.

1. Data stays on the restaurant's computer

All business data entered in DineDost (menu, orders, bills, payments, customers, staff, stock and reports) is stored in a database on the restaurant's own computer. It is not sent to us or to any server we operate. We cannot see the restaurant's sales, customers or bills.

2. Information DineDost handles

• Restaurant and staff details entered by the owner, such as restaurant name, address, GSTIN, staff names and login usernames. Staff passwords are stored only as secure hashes.
• Customer details the restaurant chooses to record, such as a customer's name and mobile number for credit (due) or delivery.
• Licence information. To activate a licence, the owner sends us an activation code that identifies the installation and computer. It contains no sales or customer data.

3. Optional Google Drive backup

The restaurant owner may choose to connect their own Google account so DineDost can copy its daily backup file to the owner's Google Drive. This is optional and can be turned off at any time.

• DineDost requests only the drive.file permission. With it, DineDost can see and manage only the files it creates itself (the backup files in a "DineDost Backups" folder). It cannot see, read or change any other file in the owner's Google Drive.
• DineDost uses this access only to upload backup files, list and download those backup files for restore, and delete old backup files it created.
• The Google access token is stored, encrypted, only on the restaurant's computer. It is not sent to us. We never see the owner's Google password or the backup files.
• The owner can disconnect at any time from Settings in DineDost, or from their Google Account at myaccount.google.com/permissions.

DineDost's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Data received from Google APIs is not used for advertising, is not sold, is not transferred to anyone else, and is not used to train any AI or machine learning model.

4. Sharing

We do not sell, rent or share any restaurant or customer data. Because the data stays on the restaurant's computer, we do not hold it. If the restaurant asks us for support, we may look at the screen with the owner's permission to help fix a problem.

5. Security

DineDost works on the restaurant's local network only and is not reachable from the internet. New phones must be approved by the owner before they can log in. The restaurant is responsible for keeping its computer and Wi-Fi secure.

6. Data retention and deletion

The restaurant controls its data and can delete it at any time. Daily backups on the computer are kept for 30 days by default. Backups in Google Drive are kept for 30 days by default and can be deleted by the owner from their Drive at any time.

7. Changes

We may update this policy. The date at the top shows the latest version.

8. Contact

SoftOps Technology LLP (DineDost)
Contact: Sumit Mhetre
Ichalkaranji, Maharashtra, India
Email: mhetresumit53@gmail.com
Phone / WhatsApp: +91 95795 71061