Terms of Service
Version 2026-08-27
These terms govern the use of Piattar by a restaurant. The annex at the end sets out how Piattar processes data on the restaurant’s behalf, as required by Article 28 of the GDPR.
1. What the service is
Piattar provides an AR menu for guests and floor-management tools for the restaurant: menu and category management, 3D and AR views of dishes, QR codes, a point of sale with modifiers, a kitchen display, shifts and a Z-report, bill splitting, guest receipts and analytics. The restaurant is responsible for the content of its menu, its prices and its tax settings.
2. The account
One account belongs to one restaurant. The owner is responsible for keeping access credentials and the owner PIN confidential, and for the staff accounts and permissions they create. Staff work under the owner’s session on shared devices; the PIN separates people at the application level, not at the database level, and the Z-report says so on its face.
3. Availability
Piattar is provided as-is, without a guaranteed uptime level. Deployments briefly interrupt service. The restaurant should not rely on Piattar as the only record of its sales: exports are provided for that purpose and should be taken regularly.
4. Ending the service
The restaurant may stop using Piattar at any time and request deletion of its data. Before deletion the restaurant should export what it is legally required to keep — in most EU countries accounting source documents must be retained for several years, and deletion here does not satisfy that duty.
Annex: data processing
This annex forms part of these terms and applies whenever Piattar processes personal data on behalf of the restaurant.
Roles
For guest, order and staff data the restaurant is the controller and Piattar is the processor: Piattar acts on the restaurant’s instructions and does not use this data for its own purposes. For the owner’s own account data — email, plan and payment details — Piattar is the controller, because the product determines what is collected.
Purpose and duration
Data is processed solely to provide the service described above, for as long as the restaurant uses Piattar, plus the retention described below.
Categories of data and of people
Guests: menu-usage events (a QR code was scanned, a dish was opened, a 3D or AR view was started) with the dish, the table and the time. No IP address, browser string, device fingerprint or advertising identifier is stored, and nothing is written to the guest’s device beyond the language cookie and, where the restaurant has enabled ordering from the phone, the table-session cookie and the basket described in the privacy notice. Staff: names, permission flags and PIN codes stored as hashes. Orders: items, amounts, taxes, payments and the table, as the restaurant’s own business records.
Security measures
Access is protected by row-level security in the database, by column-level privileges on sensitive fields, and by revoking direct write access to permission flags and PIN material. Staff PINs are stored hashed. Signed links used by kitchen displays and guest receipts carry an expiry and can be revoked. Traffic is served over HTTPS only.
Retention
Menu-usage events are deleted automatically after 25 months. Orders, shifts and bills are kept for as long as the restaurant uses the service, because they are the restaurant’s accounting records; on termination they are deleted or exported at the restaurant’s choice.
Assisting the restaurant
Piattar assists the restaurant in answering requests from individuals and in demonstrating compliance, and makes the information needed for that available on request.
Personal data breaches
If Piattar becomes aware of a personal data breach affecting a restaurant’s data, it notifies that restaurant without undue delay, with the information the restaurant needs in order to decide whether to notify its supervisory authority.
Sub-processors
Piattar uses the following providers to deliver the service. The restaurant is informed of changes to this list in advance and may object.
| Provider | Purpose | Data involved |
|---|---|---|
| Supabase | Database, authentication and file storage | All service data: menus, orders, staff accounts, analytics events |
| Render | Application hosting | Requests passing through the application |
| Stripe | Subscription billing | Owner billing details; no guest or order data |
| Sentry | Error reporting | Technical error reports; may include the address of the page that failed |
| Upstash | Request rate limiting | Short-lived counters keyed by request origin |
| Meshy | Generating 3D models from dish photos | Dish photographs supplied by the restaurant; no personal data |
| Hitem3D | Generating 3D models from dish photos | Dish photographs supplied by the restaurant; no personal data |
| Translating menu text on request (Gemini API) | Menu text only: names and descriptions of dishes and categories; no personal data |
Questions about these terms: contact Piattar at the address published on our site.