Skip to content
Piattar

Privacy

Last updated 27 August 2026

Piattar is an AR menu and floor-management system for restaurants. This page describes what the product actually does with data — it is written from the code, and the technical statements below can be checked against it.

What we keep on your phone

One technical cookie — the page language. At restaurants that let guests order from the phone, one more: a table-session cookie set when you scan a table's QR code. Nothing else: no analytics identifier, no visit counter, no advertising tag.

  • NEXT_LOCALE — the language you read the menu in, kept for a year. It remembers your choice while you browse the site. Scanning a table QR code picks the language from your phone's settings instead, so this cookie does not decide it.
  • piattar_guest — only after you scan a table's code at a restaurant that has switched on ordering from the phone. It holds a random table-session id, the restaurant and the table, for four hours, and is revoked when the table's bill is closed. It carries no name and is never used for analytics. Your basket (dish ids only) is kept in the browser's sessionStorage until the tab closes.

About cookie consent

You are not asked for consent, and here is why: the cookies on the guest side serve your own language choice and — where the restaurant lets you order from the phone — the ordering you asked for by scanning your table's code. Neither tracks you.

  • It does not link two of your visits: it holds nothing but a language code — ru, et or en.
  • The table-session cookie is strictly necessary for the ordering service (a shopping-basket session cookie); it is not used for analytics, advertising or third parties, and guest pages set no such cookies.
  • Sign-in and work-shift cookies exist only in the restaurant dashboard, which a guest never opens.

What the restaurant records

The restaurant keeps counts of how its own menu is used, on its own account. These are server-side records, not files on your phone.

  • Events such as: a QR code was scanned, a dish was opened, a 3D or AR view was started — with the dish, the table the sticker belongs to, and the time.
  • No IP address, no browser string, no device fingerprint and no advertising identifier is stored with these events.
  • The data is used by that restaurant only. It is not sold, not shared with advertising networks and not combined across restaurants.

Why we could not find your data if you asked

A guest has no account and the product does not know who you are. That is not an excuse but a consequence of the design: there is nothing to search and nothing to search by.

  • Menu events carry no name, no email, no IP address and no device fingerprint — they cannot lead back to a person.
  • Your IP address is visible to the server while the request is being served and is used only as a temporary rate-limiting key; it is not stored in the database.
  • If you gave your name to a waiter and it was typed into an order note, ask the restaurant: those records belong to them.

If you run a restaurant on Piattar

An owner account stores what the product needs to work.

  • Account and venue details you enter yourself: name, address, legal details, staff names and their PIN codes (stored hashed, never in readable form).
  • Orders, shifts and bills created in the point of sale, kept as the business records of the restaurant.

Your rights

Under the GDPR you can ask for access to your data, correction, deletion, restriction, and you can object to processing.

  • Guests: the events above contain no identifier that points back to a person, so there is normally nothing to look up for an individual guest.
  • Restaurant owners and staff: requests are handled through the restaurant that holds the account.

Questions about this page or about data: contact the restaurant you visited, or Piattar at the address published on our site.