Privacy Policy

What Qrambl collects about restaurant owners, their staff and the guests who order from them, why we need it, and what you can ask us to do with it.

Draft awaiting legal reviewThis text describes how Qrambl works today but has not been reviewed by a lawyer yet. Details in [brackets] are still to be filled in.

Qrambl is a QR code ordering service for restaurants, cafés and food trucks. This policy covers qrambl.com, the restaurant pages and menus we host, and the Qrambl apps and API.

Who is responsible

Qrambl is operated by [Legal entity name], [Registered address].

For the accounts of restaurant owners and their staff, Qrambl decides why and how the data is used (it is the controller).

For the orders, reservations and reviews of a restaurant's guests, the restaurant decides, and Qrambl processes the data on its behalf (as its processor). If you are a guest, the restaurant is your first contact about your data, and we help it answer you.

What we collect

Restaurant owners and staff

  • Your account: first and last name, email address, password (stored only as a one-way bcrypt hash), language, role and when you last used the app.
  • Your restaurant: name, address, country, city, time zone, currency, logo, opening hours, menu and photos, tables, Wi-Fi details, the ways guests can pay you and the address that receives order emails.
  • Your subscription: its status, trial and renewal dates, and whether you pay through Stripe or in cash. Card details are entered on Stripe's pages and never reach Qrambl.
  • Staff invitations: the email address and role of each person you invite.
  • Security records: for each sign-in attempt, the email address used, whether it worked, the IP address and the browser's description (user agent), plus a log of the actions taken by Qrambl's administrators.
  • Notifications: if you turn them on, the push address your browser or the Qrambl app gives us, so we can alert you to new orders and waiter calls.

Guests of a restaurant

  • Guests don't create an account. An order holds the first name you give, any notes for the kitchen, the items and prices, the table or pickup number and the times its status changed.
  • A reservation holds your name, phone number, party size, date and time, and any notes.
  • A review holds your rating and comment. The restaurant's public page may show the comment with your first name.
  • If you allow notifications, we keep your browser's push address and language with your order, only to tell you when it is ready.
  • If you pay for a takeaway order by card, you pay on a Stripe page, into the restaurant's own Stripe account. We receive the payment's status and Stripe's references, never your card number. To prevent abuse, we keep your IP address with the checkout (for IPv6, only its network part).

Everyone who visits

  • Our servers see your IP address and browser details with each request. We use them to deliver pages, limit abuse and fix errors, and we don't build profiles from them.
  • We count visits with Cloudflare Web Analytics, which does not use cookies or follow you across websites.
  • The sign-up form is protected by Cloudflare Turnstile, which checks your browser for signs of automated sign-ups.
  • Fonts and scripts come from our own servers, with one exception: the image editor in the restaurant dashboard loads from the unpkg.com CDN.

Cookies

We only use the cookies the service needs to work. There are no advertising or tracking cookies.

  • auth_token — Keeps you signed in, for up to 24 hours.
  • qrambl_session — Holds a guest's cart, table and recent orders, for up to 7 days. It is signed, so it can't be altered.
  • lang — Remembers the language you chose, for up to a year.
  • Cloudflare, which delivers and protects the site, may also set its own strictly necessary security cookies.

How we use it

  • To run the service: show menus, send orders to the kitchen and keep guests and staff updated.
  • To manage your account and subscription, including billing through Stripe and trial reminders.
  • To send service emails: address confirmation, password resets, security notices, the order emails you turn on, and a short series of tips in your first four weeks, which you can stop with one click.
  • To keep Qrambl secure: rate limits, bot checks, sign-in records and abuse prevention.
  • To improve Qrambl from aggregated figures, such as how many orders are placed.

We don't sell personal data, show ads or use your data for advertising.

Where the GDPR or a similar law applies, we rely on our contract with you, our legitimate interest in a secure, working service, your consent where we ask for it (such as for notifications), and our legal duties (such as keeping accounting records).

Who we share it with

A few providers help us run Qrambl. They handle data only for us, under their own security and privacy terms:

  • Hosting: [Hosting provider and data center location] stores the database and runs our servers.
  • Cloudflare delivers and protects the website and provides Turnstile and Web Analytics.
  • Stripe bills Qrambl subscriptions. For takeaway card payments, Stripe processes the payment in the restaurant's own Stripe account (a direct charge): the money goes to the restaurant, and Qrambl never holds it or takes a fee.
  • Email: [Email delivery provider] delivers our emails.
  • Push notifications travel through the push service of your browser or phone maker, such as Google, Apple or Mozilla.

Restaurants see the orders, reservations and reviews of their own guests, and their staff see what their role allows.

We may also disclose data when the law requires it, or to a buyer if Qrambl's business is sold, who would remain bound by this policy.

International transfers

These providers may process data outside your country, including in the United States. Where the law requires it, these transfers rely on safeguards such as the European Commission's standard contractual clauses.

How long we keep it

  • Account and restaurant data: for as long as the account exists. Deleting a restaurant deletes its menu, tables, orders, reservations and reviews.
  • Guest orders, reservations and reviews: for as long as the restaurant's account exists.
  • Records of card payments: kept even after a restaurant is deleted, for accounting and to settle refunds and disputes.
  • Sign-in and security records: kept to protect accounts, for [retention period to be decided].
  • Billing records: for as long as tax and accounting law requires.

Your rights

Depending on where you live, you can ask to see, correct, delete or receive a copy of your data, object to or limit how we use it, and withdraw any consent you gave. You can change most account details in your profile. To delete your account or get a copy of your data, email us: we answer within one month.

Guests: please contact the restaurant first. If it doesn't answer, write to us and we will help.

You can also complain to the data protection authority where you live.

Security

Connections use HTTPS, passwords are stored as bcrypt hashes, sessions use HTTP-only cookies, and staff only see what their role allows. No system is perfectly secure: if a breach affects your data, we will tell you as the law requires.

Children

Qrambl accounts are for businesses and adults. We don't knowingly collect data about children, beyond the first name any guest gives when ordering.

Changes to this policy

We will post any change on this page with a new date. If a change affects how we use your data, we will also email account owners before it applies.

Contact

Questions about this page, or a request about your data? Write to us: [email protected]

Terms of Service