Privacy, explained without the fog.

Who we are

DineUp is a product of DwarkaLabs, a sole proprietorship operated by Kartik Dixit. In this policy, “DineUp”, “DwarkaLabs”, “we”, “us” and “our” refer to Kartik Dixit carrying on business as DwarkaLabs.

DineUp provides QR menus, table ordering, restaurant dashboards, operational analytics and related support services.

Scope and roles

This policy applies to the DineUp website, restaurant dashboard, guest ordering pages, support interactions and related services.

We decide how account, security, billing, product-usage and support information is handled. For guest order information, the restaurant decides to use DineUp to receive and fulfil orders. The restaurant is therefore responsible for its use of that information, while DineUp stores and processes it to provide the service. If you are a guest with a question about a specific order, the restaurant may be the best first contact; we will still help route privacy requests.

Information we collect

Restaurant and team information

We collect account details such as name, work email address, login method, restaurant name, location, menu and table information, team permissions, settings, and messages sent to support. If you sign in with Google, we receive the basic account information needed to create and secure your DineUp account.

Guest and order information

When a guest scans a table QR code and places an order, we store the selected items, quantities, table reference, instructions, prices, timestamps, order status and related operational details. A guest account is not required. Restaurants should avoid asking guests to include sensitive or unnecessary personal information in order notes.

Technical and usage information

We may collect device and browser details, IP address, diagnostic events, security records, pages or features used, approximate location inferred from IP, and cookie or similar identifiers needed for authentication, reliability and fraud prevention.

Requests and exports

We retain the details of support, privacy and restaurant data-export requests, including the requested date range and the information needed to verify that the requester is authorised.

How we use information

We use information to:

• create, authenticate and protect restaurant accounts;
• publish menus and route table orders to the correct restaurant;
• show order history, operational analytics and dashboard insights;
• produce authorised exports for a restaurant;
• provide support and communicate important service changes;
• monitor reliability, prevent misuse and investigate incidents;
• improve DineUp using aggregated or de-identified patterns; and
• meet legal, tax, accounting and regulatory obligations.

Depending on the context, we process information to perform our agreement with a restaurant, with consent, for legitimate business and security needs, or to comply with law. We do not sell personal information.

Sharing and service providers

Restaurant owners and their authorised team members can see the restaurant’s menus, orders, analytics and related activity according to their permissions. We also use carefully selected providers to operate DineUp, including hosting, database, authentication, email, monitoring and map or address services. These currently include Vercel, Supabase, Google sign-in, Resend, and OpenStreetMap-based services such as Nominatim where applicable.

Providers receive only the information needed for their function and process it under their own terms and safeguards. Information may be processed outside your state or country depending on provider infrastructure. We may also disclose information when required by law, to protect people or the service, in a business reorganisation, or with your direction or consent.

Retention and deletion

We keep information for as long as needed to operate the account, provide order history, analytics and exports, resolve disputes, maintain security, and meet legal or accounting duties. Retention depends on the type of record, the restaurant’s account status and the reason it is held; we do not promise that every record is kept indefinitely.

A restaurant may request an authorised export for an available date range by emailing support. It may also request account closure or deletion. We will verify authority, explain any information that must be retained, remove eligible data from active systems, and allow routine backup copies to expire under our operational schedules. Security and system logs may be retained where required by applicable law, including lawful cybersecurity obligations.

Security

We use reasonable technical and organisational safeguards designed to protect information, including access controls, authentication, encrypted network connections, backups, monitoring and restricted administrative access. No online service can guarantee absolute security. Restaurants must protect their credentials, grant only the permissions each team member needs and tell us promptly about suspected unauthorised access.

Your choices and rights

Subject to applicable law, you may ask us to confirm whether we hold your personal information, obtain a summary, correct inaccurate or incomplete information, request deletion, withdraw consent where consent is the basis of processing, or raise a grievance. You may also nominate another person to exercise relevant rights where the law permits.

Email support@dineup.sitewith enough detail for us to understand the request. We may need to verify identity, restaurant authority or account ownership before acting. We will respond within the period required by applicable law. If a request concerns a restaurant’s guest records, we may coordinate with that restaurant.

Children and team members

The person creating or accepting a restaurant account must be at least 18 years old and legally able to bind the restaurant. A younger family member may use DineUp as an authorised team member only under the responsibility and supervision of the adult proprietor, guardian or other authorised account holder.

Guests do not need an account to view a menu or place an order. The service is not designed to collect children’s personal information, and restaurants should not request it through order notes. Contact us if you believe a child has provided unnecessary personal information.

Changes and contact

We may update this policy as DineUp develops or legal requirements change. We will post the revised version here, change the “Last updated” date and provide additional notice when a change materially affects how information is used.

Privacy questions and grievances can be sent to support@dineup.site. Proprietor-level escalations can be sent to kartik@dineup.site.