Privacy Policy

1. Who we are

DinerGrid is operated by DWILS PTE. LTD., a company incorporated in Singapore under UEN 202606134E, with its registered office at 160 Robinson Road, #14-04, Singapore Business Federation Center, Singapore 068914. We are the organisation responsible for the personal data described here.

We handle personal data in line with the Singapore Personal Data Protection Act 2012. Where we handle data about diners in Malaysia on behalf of a Malaysian restaurant, the Malaysian Personal Data Protection Act 2010 applies to that restaurant as the data user, and we act on its instructions.

2. Two different roles

This distinction decides who is answerable for what, so we state it plainly.

• Your account data. We are the controller. This is the data you give us to open and run a DinerGrid subscription.
• Your diners' data. We are the processor and you are the controller. Orders, names, phone numbers and addresses your diners give you belong to you. We hold them to run the service for you and act only on your instructions.

You are responsible for having a lawful basis to collect your diners' data and for the notices you give them. We do not sell diner data, do not share it with other restaurants, and do not use it to market anything to your diners.

3. What we collect

• From you: name, work email, phone number, business name, outlet addresses, business registration or tax identifiers where you supply them, and your login credentials, which are stored only as a salted hash.
• Billing: plan, invoices and payment history. Card numbers are held by our payment provider, never by us; we keep only the last four digits and the expiry so you can recognise the card.
• From your diners, on your behalf: order contents, table or outlet, and where the order is a delivery, the contact name, phone number and delivery address.
• How you found us: when you sign up, the campaign tags on the link that first brought you to dinergrid.com (such as utm_source), the click id an advertising platform added to that link (Google's gclid, Meta's fbclid), the site that sent you and the page you first landed on.
• How our own site is used: on dinergrid.com, which pages are opened, how far down they are scrolled, which sections come into view, which links and buttons are tapped, how long a page stays open, and which sign-up steps are reached. Each record carries a random id kept in your browser, your country as our network provider reports it, and whether the device is a phone. It does not include your IP address, your browser's details, your name or your account, and it is not shared with anyone. Browsers set to "Do Not Track" or Global Privacy Control send none of it.
• How fast the service is: in your dashboard, on the kitchen screen and on your diners' ordering pages, how long a page took to appear and how long each request to us took to answer, with the kind of page or request, the connection type and whether the device is a phone. On a diner's page, which restaurant it was. It does not include an IP address, browser details, a name, an account, or any order or diner.
• Technical: IP address, browser and device type, and timestamped records of requests and sign-ins, which we need for security, rate limiting and fault diagnosis.

We do not knowingly collect data from children, and we do not collect special categories of personal data such as health or biometric data.

4. Why we use it

• To provide the service you have subscribed to, which is the performance of our contract with you.
• To bill you, and to chase an unpaid invoice.
• To verify a phone number or email address at sign-in, using a one-time code.
• To keep the service secure: detecting abuse, rate limiting, and investigating incidents. This is our legitimate interest in running a safe platform.
• To provide support when you ask for it.
• To learn which of our own advertisements and posts bring restaurants that go on to use DinerGrid, so we spend less on the ones that don't.
• To see where our own pages lose people, so we can make them clearer.
• To send service notices such as an outage, a security matter or a change to these terms. You cannot opt out of these while you hold an account, because they are part of the service.

We do not use your data or your diners' data to train models that serve anyone else, and we do not sell personal data to anybody.

5. How long we keep it

• Account and business data: for as long as your account is open. When you close your account, from Settings in your dashboard, we stop your subscription that day and delete your data 30 days later — your menu, orders, diner records, staff accounts, inventory, saved card reference and settings. You can stop the closure at any point in those 30 days, and you can download everything in one file before it runs. Once it runs it cannot be undone.
• Invoices and payment records: retained after closure for as long as tax and company law require us to keep accounting records. An invoice has to say who it was raised against, so your business name and tax number stay on it.
• A record that a free trial was used: kept after closure, so the trial cannot be taken repeatedly by closing and reopening an account.
• Message logs, meaning the record of a verification code, invoice notice or other message we sent: the recipient address is automatically redacted 90 days after the message, and the message queues are trimmed on the same 90-day schedule. This runs daily and is not a manual process.
• Security and request logs: kept for a short operating window and then rotated out.
• Records of how our site is used: deleted automatically after 120 days.
• Speed records: request timings are deleted automatically after 30 days, page-load timings after 120 days.

6. Who else processes it

We use a small number of providers to run the service. Each one only receives what it needs.

• DigitalOcean, hosting for the application and database, in their Singapore region.
• Cloudflare, content delivery, TLS and protection against attack. Traffic passes through Cloudflare before reaching us.
• Resend, delivery of transactional email such as verification codes and invoices.
• Cloudinary, storage and delivery of images you upload, such as menu photos and your logo.
• Sentry, error and performance monitoring. When a fault occurs, diagnostic data is sent to Sentry so we can find and fix it: the error, where in our code it happened, and the method and path of the request. It is configured not to receive request or response bodies, cookies, query strings, IP addresses or account identifiers. An error message can occasionally include a detail from the request that caused it. Sentry is operated in the United States.
• Stripe, processing of your subscription payments. Your card details go to Stripe, never to us; we hold only the brand, last four digits and expiry. Stripe receives your billing email and name. Stripe is operated in the United States and Ireland.
• Stripe also processes the payments your diners make online, where your restaurant has set up its own Stripe account through DinerGrid. Those payments are made to your restaurant's Stripe account, not to us. We send Stripe the amount and which order or table it is for; your diner gives their payment details to Stripe directly.
• Anthropic (Claude) and Google (Gemini), the AI features in the dashboard, such as reading a menu photo, menu translation and description drafting. Only the text or photo you submit for that feature is sent; Gemini is used when Claude is unavailable.
• Google Workspace, our own business email, which is where a message you send us arrives.
• Google Ads, only if you reached us by clicking one of our Google ads. We tell Google that the click led to a sign-up and, later, that your restaurant took its first orders: the click id and the time, nothing else. Not your name, email, phone or business.

Our public pages load web fonts from Google Fonts, which means your browser contacts Google when you view them.

Encrypted backups of the database are kept with Cloudflare R2. They are encrypted before they leave our server with a key Cloudflare does not hold.

Your account data and your diners' order data are stored in Singapore. Some of the providers above operate elsewhere, so parts of your data, such as an email in transit, an image on a content network, or diagnostic data sent to our error monitoring in the United States, are handled outside Singapore. Where that happens we require, by contract, protection comparable to what Singapore law requires. We will tell you if we add a provider that materially changes this.

7. How we protect it

All traffic to DinerGrid is encrypted in transit with TLS, and our public sites enforce HTTPS. The link between our edge and our servers requires a client certificate, so our origin will not answer a request that did not come through it. Access to production is restricted, sign-ins are rate limited, and repeated failed attempts lock an account temporarily. Passwords are stored only as salted hashes. Every request carries an identifier so we can trace a fault without reading your content.

No system is perfectly secure. If a breach affects your personal data and is likely to cause significant harm, we will notify you and the Personal Data Protection Commission as the law requires, and we will tell you what happened and what we are doing about it.

8. Your rights

You may ask us to tell you what personal data we hold about you and how we have used it, to correct anything inaccurate, or to withdraw a consent you previously gave. Withdrawing consent may mean we can no longer provide part of the service, and we will tell you if that is the case.

Email service@dinergrid.com with "data request" in the subject. We acknowledge within two business days and respond substantively within 30 days. There is no charge for a reasonable request.

If your diner makes a request about their own data, it comes to you as the controller; we will help you answer it. If you are unhappy with how we have handled a request, you may complain to the Personal Data Protection Commission of Singapore.

9. Cookies and similar technology

In the product — your dashboard and the ordering pages your diners use — we use only what the service needs: a session cookie to keep you signed in, and local storage in your browser for preferences such as language and theme. No advertising cookies, and no tracking of you across other websites.

On dinergrid.com itself, your browser's local storage keeps a note of the link that first brought you there, and a random id, for up to 90 days. The note leaves your browser only if you sign up; the id goes with the records of how our site is used, both as described in section 3. No Google advertising script or third-party analytics runs on our pages.

A small number of our own campaign pages, such as dinergrid.com/jin-tarorice, carry the Meta (Facebook) pixel so we can measure how an advertisement performed. Those pages are marketing for DinerGrid, never part of the product, and the pixel is not present on your dashboard or on your diners' ordering pages. Meta may use what it collects there to build its own profile of you. You can block it with your browser's tracking protection or an ad blocker.

10. Links to other sites

Our pages may link elsewhere. We are not responsible for the privacy practices of sites we do not run.

11. Changes

We may update this policy. For a material change we will email the account owner at least 30 days beforehand and update the date at the top of this page.

12. Contact

DWILS PTE. LTD., 160 Robinson Road, #14-04, Singapore Business Federation Center, Singapore 068914. Email service@dinergrid.com. See our contact page.