Privacy policy

Dineso is a platform that restaurants use to publish menus, take lunch orders from companies and issue monthly invoices. For your user account and for enquiries sent through the marketing site, the operator named above is the data controller.

Orders, delivery details and invoices belong to the business relationship between a restaurant and its customer company. For that data the restaurant is the controller and Dineso processes it on the restaurant's behalf under the service agreement. Questions about an order or an invoice are best directed to the restaurant; we will help it answer.

Account data: email address, name, a hash of your password (never the password itself), preferred language, your role (restaurant manager, diner or platform administrator) and which restaurant or company you belong to. Social sign-in, when enabled, adds the identifier the provider gives us.

Restaurant and company data: the business names, addresses, company and VAT identification numbers, bank accounts and contact details that restaurants and their customers enter for invoicing.

Orders and billing: which meals were ordered for which day, variants and notes, the resulting monthly summaries, invoice numbers and PDF invoices.

Demo requests: company name, your name, email, optional phone number and message, and the language you wrote in.

Technical data: IP address, browser and request details in server logs, error reports when something breaks, and the identifiers of your signed-in sessions.

To provide the service you signed up for: creating and securing your account, letting you order or manage orders, generating prep sheets and invoices. Legal basis: performance of a contract (Art. 6(1)(b) GDPR).

To keep accounting and tax records: confirmed monthly invoices must be retained as the law requires. Legal basis: legal obligation (Art. 6(1)(c) GDPR).

To keep the service secure and working: rate limiting, protection against automated abuse, logging and error monitoring. Legal basis: our legitimate interest in a reliable and secure service (Art. 6(1)(f) GDPR).

To answer a demo request you sent us. Legal basis: taking steps at your request before entering into a contract (Art. 6(1)(b) GDPR).

We do not use your data for advertising, we do not build profiles, and we do not sell it.

The application sets one strictly necessary cookie that keeps you signed in (an opaque refresh token, readable only by the server) and one that remembers your chosen language. Your theme preference and an unsent lunch selection are kept in your browser's local storage and never leave it.

We use no analytics, advertising or tracking cookies, so no consent banner is shown. The demo-request form on the marketing site is protected by Cloudflare Turnstile, which inspects the browser to tell people from bots and may set its own cookie; see Cloudflare's privacy policy for details.

Your restaurant or company sees the data needed to serve you: a restaurant sees its customers' orders and contacts; a company's diner account is linked to the company's invoices.

Service providers who process data on our behalf: hosting and the database (INTERNET CZ, a.s., Czech Republic, EU); storage and delivery of uploaded images, database backups stored in the EU, and bot protection on the contact form (Cloudflare, Inc.); transactional email (Resend); error monitoring (Sentry, when enabled). Providers outside the EU are bound by standard contractual clauses.

Public authorities, when the law requires it. Nobody else.

Account data for as long as your account exists. Signed-in sessions and password-reset links are deleted thirty days after they expire.

Orders and invoices for as long as Czech accounting and tax law requires, which is up to ten years for tax documents. If you erase your account, your personal details in that history are replaced by an anonymous reference; the business records themselves stay.

Demo requests until your enquiry is closed. You can ask us to delete one at any time.

You can access, correct, export or erase your personal data, restrict or object to its processing, and withdraw any consent you have given. Export and erasure are available directly under Profile → Privacy & data; everything else by email to the address above. We answer within one month.

Erasure keeps the data we are legally required to retain (see above) in anonymized form. An account that owns a restaurant must be handed over or the restaurant closed first.

If you believe we handle your data unlawfully, you may lodge a complaint with the Czech Office for Personal Data Protection (Úřad pro ochranu osobních údajů, uoou.gov.cz) or the supervisory authority of your residence.

All traffic is encrypted in transit. Passwords are stored only as salted argon2id hashes. Each restaurant's data is isolated at the database level, so one tenant can never read another's. Access to production systems is limited to the people who operate them, and administrative actions are logged.

No system is perfectly secure. If a breach affects your data, we will notify you and the supervisory authority as the GDPR requires.

Dineso is a business tool. It is not directed at children, and we do not knowingly process data of anyone under sixteen.

When this policy changes, the new wording is published here with a new effective date. For changes that matter to you, signed-in users are told in the application.

This policy is written in Czech. The English version is a translation for convenience; if the two differ, the Czech version prevails.