Legal_Framework_v1.0

Privacy Policy

Effective Date[Insert Date]
Last Updated[Insert Date]
StatusActive Protocol

This Privacy Policy explains how DineStack (“DineStack”, “we”, “us”, “our”) collects, uses, stores, shares, and protects information when you use our websites, desktop software, admin panels, customer ordering pages, QR ordering experience, and related services.

DineStack is a restaurant software platform that may include a website, a restaurant management software application, a super admin panel, QR-based customer ordering, subscription billing, activation/licensing, reporting, and support tools.

By using DineStack, you agree to the practices described in this Privacy Policy.

01. Who We Are

DineStack is operated by:

Entity: DineStackEmail: official.dinestack@gmail.comWebsite: https://dinestack.in/

If you have any questions about this Privacy Policy, you can contact us using the details above.

02. What This Policy Covers

This Privacy Policy applies to:

  • the DineStack website and landing pages
  • restaurant onboarding and activation flows
  • restaurant desktop software
  • super admin panel
  • QR menu and customer ordering pages
  • subscription and billing flows
  • support, diagnostics, logs, and update systems
  • any related online or offline DineStack service

This policy does not apply to third-party websites or services that may be linked from DineStack, such as payment gateways or external support tools. Those services have their own privacy policies.

03. Information We Collect

We may collect the following types of information depending on how you use DineStack.

A. Account and Business Information

When a restaurant is activated or managed through DineStack, we may collect:

-> restaurant name
-> business name
-> owner or authorized contact name
-> email address
-> phone number
-> restaurant address or location
-> plan/subscription details
-> activation key or license information
-> restaurant status and configuration
-> staff roles and permissions

B. Staff and Internal User Information

For restaurant staff, admins, managers, or internal team access, we may collect:

-> name
-> email address
-> login credentials or password hashes
-> role and permission level
-> access logs
-> session and authentication data
-> device or browser information

C. Customer Ordering Information

When a customer scans a QR code or uses the ordering page, we may collect:

-> table identifier
-> restaurant identifier
-> ordered items
-> order notes or custom instructions
-> order status
-> basic interaction data
-> payment status, if applicable

We generally do not intend to collect unnecessary personal information from restaurant customers unless it is required for order placement, payment, support, or legal compliance.

D. Billing and Subscription Information

For subscription management and autopay-related flows, we may collect and store:

-> plan selected
-> subscription status
-> renewal date
-> payment attempt history
-> coupon usage
-> invoice or transaction reference numbers
-> Razorpay or other payment processor identifiers
-> payment method metadata provided by the payment provider

We do not store your full payment card details directly on our servers. Payment processing is handled by third-party payment providers.

E. Technical and Device Information

We may collect technical data such as:

-> IP address
-> browser type
-> device type
-> operating system
-> app version
-> installation version
-> error logs
-> crash reports
-> update status
-> network and connectivity status
-> device pairing or installation identifiers

F. Usage and Analytics Information

We may collect information about how you use DineStack, including:

-> pages visited
-> features used
-> login activity
-> activation attempts
-> update checks
-> subscription events
-> QR scan events
-> menu loads
-> table lookup events
-> administrative actions
-> audit logs

04. How We Use Information

We use the information we collect to:

  • provide and operate DineStack services
  • activate restaurants and manage licenses
  • create and manage subscriptions
  • process payments and renewal flows
  • support QR-based ordering
  • sync restaurant data across devices
  • provide menu, table, order, kitchen, billing, and reporting features
  • manage staff roles and permissions
  • show update availability and install software updates
  • respond to support requests
  • detect fraud, misuse, or unauthorized access
  • maintain security and audit logs
  • improve the product, performance, and reliability
  • comply with legal and contractual obligations

05. Activation, Licensing & Device Linking

DineStack may use activation keys, device pairing, and license verification to control access to the software.

We may store:

  • -> activation code status
  • -> restaurant activation state
  • -> license status
  • -> linked device identifiers
  • -> installation records
  • -> session validity
  • -> synchronization metadata

This information is used to ensure that only authorized restaurants can access the software and that licensing conditions are enforced.

06. QR Ordering and Restaurant Data

When customers scan a DineStack QR code, the system may use table identifiers and restaurant identifiers to show the correct menu or place an order.

We may store:

  • -> QR/table mappings
  • -> table IDs
  • -> restaurant IDs
  • -> customer session tokens
  • -> ordering events
  • -> order timestamps
  • -> menu access logs

This data helps the restaurant operate the ordering flow correctly and helps prevent unauthorized or invalid access.

07. Payments, Autopay & Subscriptions

DineStack may support subscriptions, recurring billing, coupons, and payment-related automation through third-party payment providers such as Razorpay.

Payment processing may involve:

  • -> subscription creation
  • -> payment attempts
  • -> renewal status
  • -> autopay setup status
  • -> payment success or failure
  • -> invoice and receipt details
  • -> coupon application data

We may receive transaction confirmations and billing metadata from the payment provider in order to manage your subscription and service access.

08. Software Updates

We may collect update-related information such as installed version, latest version check, update status, update download progress, installation completion or failure, and device compatibility data. This is used to provide in-app update notifications and ensure the restaurant software stays secure and functional.

09. Support & Logs

We may collect support and diagnostic information to help debug issues such as activation errors, session expiry, pairing failures, table lookup issues, API errors, sync failures, and update failures. Logs may contain technical details necessary for troubleshooting.

10. How We Share Information

We may share information only when necessary, including with:

  • payment processors and billing providers
  • hosting and infrastructure providers
  • database and storage providers
  • email or notification service providers
  • analytics or monitoring tools
  • support and maintenance tools
  • legal or regulatory authorities, if required
We do not sell your personal information to advertisers.

11. Third-Party Services

DineStack may rely on third-party services for hosting, database storage, payments, and deployment. These may include cloud infrastructure, payment gateways, and software update delivery services. Those third parties may process information according to their own privacy policies and terms.

12. Data Storage and Security

We use reasonable technical and organizational safeguards designed to protect your information from unauthorized access, loss, misuse, or disclosure.

Security measures may include:

[OK] authentication and role-based access control
[OK] encrypted connections where applicable
[OK] access logs and audit trails
[OK] secure token/session management
[OK] restricted internal access
[OK] monitoring and alerting
[OK] software update verification

No system is fully secure, and we cannot guarantee absolute security.

13. Data Retention

We retain information for as long as necessary to provide the service, maintain restaurant records, comply with legal obligations, resolve disputes, enforce agreements, support subscriptions and licensing, and preserve audit and security logs. Retention periods may vary depending on the type of data and operational needs.

14. Restaurant Data vs. Customer Data

DineStack primarily serves restaurants. In many cases, the restaurant is the controller of the customer data it collects through orders and operations, and DineStack acts as a service provider or processor for that data.

The restaurant is responsible for informing its own customers, obtaining any required consents, providing notices at the point of collection, and complying with applicable laws.

If you are a restaurant customer and have questions about how your order data is used, please contact the restaurant directly.

15. Choices & Rights

Depending on your location and applicable law, you may have rights to access your information, correct inaccurate information, request deletion in certain circumstances, object to or restrict certain processing, withdraw consent where applicable, and request a copy of your data, where available. If you are a restaurant or an authorized user, you may contact us to discuss these requests.

16. Children’s Privacy

DineStack is intended for business and restaurant use and is not directed to children. We do not knowingly collect personal information from children for business services.

17. International Transfers

Your data may be processed and stored in countries other than your own, depending on the hosting and service providers we use. By using DineStack, you understand that your information may be transferred across borders as part of service operation.

18. Changes

We may update this Privacy Policy from time to time. When we do, we will revise the “Last Updated” date at the top of this page. Continued use of DineStack after changes means you accept the updated policy.

19. Contact Us

If you have questions, concerns, or requests regarding this Privacy Policy, contact us at: