06  ·  Terms of useA plain-English overview of acceptable use

Fair use.
Plainly stated.

The service01

What DineSights
is — and isn’t.

A QR-based menu and lightweight CRM for independent restaurants. We do not take orders, process payment, or replace any part of your existing POS.

DineSights provides:

  • QR codes that open a web-based menu for diners.
  • A menu editor and dashboard for restaurant owners to manage that menu and review visit information.
  • Lightweight communication tools, including SMS one-time codes for identity verification and optional outbound messages from a restaurant to its own diners.
  • Subscription billing via Stripe for restaurants using the platform.

DineSights does not handle food orders, kitchen tickets, payment processing, or any part of a restaurant’s service flow that touches the kitchen or the bill.

Text messagesBy providing your phone number and selecting Send Code, you consent to receive a one-time transactional security code on your mobile device. Standard message and data rates may apply. For assistance, reply HELP to the number from which you received the message, or contact us at contact@dinesights.com. To stop receiving messages, reply STOP at any time. Carriers are not liable for delayed or undelivered messages.
If you run a restaurant02

What we ask of
restaurants.

A short set of expectations that keep the platform usable for diners and the network of restaurants alongside you.

i.

Use accurate menu information.

Prices, dishes, and dietary information should match what you actually serve. Don’t use the menu surface to advertise things you don’t offer.

ii.

Be honest with diners.

Diners who share a phone number are doing so to be recognized. Use that information the way they’d expect — not for spam, not for resale.

iii.

Honor opt-outs and deletion requests.

When a diner asks to be removed or replies STOP to a text, the relationship ends. We’ll help you process the request if you’re unsure.

iv.

Keep your account secure.

Don’t share your owner phone number or OTP. Treat the DineSights dashboard as you would your POS — only trusted people get access.

v.

Don’t use the platform to harass or deceive.

The product exists to help good restaurants run a real relationship with their diners. We reserve the right to remove accounts that misuse it.

vi.

Keep your subscription current.

Billing is managed by Stripe. If a payment fails repeatedly, the menu may be paused until billing is resolved. We’ll always reach out first.

If you're a diner03

What we ask of
diners.

Almost nothing — but a couple of common-sense expectations help keep things working for everyone.

  • Use your own phone number when signing in. Don’t enter someone else’s number to receive an OTP.
  • Don’t try to abuse rewards — e.g., re-signing under fake numbers to stack rewards. We may revoke clearly fraudulent reward progress.
  • Don’t use the platform to send abusive messages or report fake issues. Real reports get a real response.
Billing04

How billing
works.

Restaurant subscriptions are handled by Stripe. The bullets below are how DineSights handles the practical edges of subscription life.

  • Your subscription begins when you complete checkout and continues until you cancel.
  • You can cancel at any time. You’ll continue to have access through the end of the period you’ve already paid for.
  • If a payment fails, Stripe will retry on its standard schedule. We’ll also reach out so you have a chance to fix it before any service interruption.
  • Refund policy is judged case-by-case. Reach out and we’ll talk it through.
Pricing

Current pricing is communicated during your demo and shown in checkout before you confirm. Pricing may change with notice; existing customers are given a fair window before any change applies to their plan.

Availability05

Honest limits
on uptime.

DineSights is a real piece of software running on real infrastructure. We do everything reasonable to keep it up — but we don't promise the impossible.

We work to provide a reliable service, but we can’t guarantee uninterrupted access. Outages, planned maintenance, or third-party provider issues (Stripe, Twilio, Supabase, our cloud host) may occasionally affect availability. When something significant happens, we’ll communicate it directly to affected restaurants.

To the extent allowed by law, DineSights is provided as-is, without warranties beyond what’s explicitly agreed in writing for your account. Our liability for any issue is limited to what you’ve paid us in the recent past, in line with standard SaaS terms.

Ready when you are

Question on the terms?

If something here doesn't fit your situation — a multi-location group, an unusual setup, a question about a specific clause — write in and we'll talk it through.

Email support