Політика конфіденційності
Last updated: 21 November 2026
This Privacy Policy explains what personal data YR Menu processes through its website, the restaurant dashboard, the staff app and the digital menus that restaurants show their guests, how we collect it, where it goes, how long we keep it and what rights you have.
1. Who is responsible
For restaurant customers, the entity that bills the restaurant is responsible ("controller") for the personal data of the restaurant's owners and staff:
| Customers billed in | Entity | Contact |
|---|---|---|
| Türkiye | İLHAN FIRAT KOÇAK (sole trader), tax No. 5710380690, Fatih Mah. 3351 Sk. No:29 İç Kapı No:3, Kepez / Antalya, Türkiye. | info@yrmenu.com |
| Uzbekistan and all other countries | TESLA KAFA LLC (OOO "TESLA KAFA" Xorijiy korxona), registration No. 2963992, tax ID (STIR) 312477429, Konstitutsiya MFY, Tafakkur ko'chasi, 43-uy, Yakkasaroy tumani, Toshkent, O'zbekiston. | info@teslakafa.com |
If you are not a customer (a website visitor, someone who contacts us, a guest account holder or a sales partner), the controller is İLHAN FIRAT KOÇAK if you are in Türkiye and TESLA KAFA LLC everywhere else.
The representative of TESLA KAFA LLC in the European Union under Article 27 GDPR is Prighter EU Rep GmbH, Schellinggasse 3/10, 1010 Vienna, Austria. You and the supervisory authorities may contact the representative on any data-protection matter: https://app.prighter.com/portal/yrmenu
TESLA KAFA LLC develops and operates the software for both entities. Its staff, in Uzbekistan and in Türkiye, can access the data of every restaurant to run, support and secure the service.
Restaurant guests. When a guest orders, books a table, leaves feedback or sends a hotel room request, the restaurant is the controller of that data and we process it on the restaurant's behalf and instructions (see the Data Processing Terms in our Terms of Service). Guests should send requests about that data to the restaurant first; we will help the restaurant answer them. A guest account (name, e-mail, phone, password or Google sign-in) works at every restaurant on YR Menu, so for the guest account itself we are the controller.
2. Data we process, why, and on what legal basis
| Whose data and what | Why | Legal basis |
|---|---|---|
| Restaurant owners and staff: name, e-mail, phone, business name and address, legal name and tax or VAT number, login details, role, panel language; sign-in through Google, and through Telegram where it is switched on. | Opening and running the account, support. | Contract |
| Restaurant content: menu items, prices, photos, descriptions, allergens, promotions, the Wi-Fi details the restaurant chooses to show. | Publishing the restaurant's digital menu. | Contract |
| Payments: plan, amount, payment status and reference, invoice and fiscal receipt details. Customers in Türkiye pay by card through iyzico, customers in Uzbekistan through Atmos or Octo, and customers in all other countries pay by card or wallet through Dodo Payments or by bank transfer in USD or EUR to TESLA KAFA LLC; for a bank transfer, the banks involved see the payer's name, account and the amount. For card payments we send iyzico or Octo your name, e-mail, phone and billing address and, for iyzico, your IP address, as their rules require. For payments through Dodo Payments we send Dodo your name, e-mail, phone, billing country and address, your business name and VAT number if that number has been verified, the plan and our payment reference; you enter card details on Dodo's own page. For card payments in Uzbek soum through Atmos, the card number, expiry date and SMS code pass through our server to Atmos; we do not store them. | Taking payments, invoicing, accounting and tax. | Contract; legal obligation (invoices, fiscal receipts, accounting records) |
| How you found us: referring website, landing page, campaign tags (UTM), and your approximate country and city, which our network provider (Cloudflare) derives from your IP address. We record them ourselves only (first party, no third-party service). They are kept only for the visit (the 2-hour session) unless you sign up; if you do, the referring website, landing page, campaign tags and city are deleted 13 months after you sign up. | Knowing which channels bring us customers, showing prices in the right currency. | Legitimate interest |
| Advertising click identifiers (gclid, gbraid, wbraid, yclid, fbclid): stored only if you accepted advertising cookies, and kept for 90 days from the click. If you then became a customer, we may send the click identifier and the fact that you signed up or paid to Google Ads or Yandex Direct. | Measuring our ads. | Consent; if you withdraw it, we stop storing and sending these identifiers from then on. |
| Guests of a restaurant (processed for the restaurant): language, table or room number, waiter calls and bill requests; and, only when the guest provides them: name, phone and e-mail for reservations, orders or feedback, the text of special requests, feedback comments and hotel room requests, and questions typed into the AI menu assistant. | Providing the restaurant's menu, ordering, reservation, feedback and hotel services. | Decided by the restaurant as controller |
| Guest accounts: name, e-mail, phone, password (stored only as a hash) or Google sign-in, order history. | Letting a guest sign in and see their orders at any restaurant on YR Menu. | Contract (the guest account terms, section 18 of our Terms of Service) |
| People who contact us: name, business name, phone, e-mail, city and message from our contact and demo forms (a copy goes to our sales team's Telegram chat), and messages sent to our Telegram bot. | Answering you and following up on your enquiry. | Legitimate interest; steps before a contract at your request |
| Sales partners and venue contacts: partner name, contact details, market and commission data; the venue name and contact name that our sales partners note about restaurants they visit, or that come from public business listings. | Running our partner programme and our sales follow-up. | Contract (partners); legitimate interest (venue contacts) |
| Everyone: IP address (our database keeps it only as a one-way hash; our hosting provider's server logs, Cloudflare and our card payment provider see the full address), browser and device type, session data, error and security logs; notification addresses of staff devices that turn on alerts. | Security, preventing abuse, fixing errors, sending staff alerts. | Legitimate interest |
| Website visitors who accept cookies: analytics and advertising data described in our Cookie Policy. | Understanding how our website is used and measuring our ads. | Consent |
| People who report content on a menu: the reason, the description, the e-mail address if they give one, the menu page they came from, and a one-way hash of the IP address with the browser and device type (the hash and the browser and device type are deleted within 24 hours). | Handling reports of illegal or infringing content and preventing abuse of the report form. | Legitimate interest |
| Restaurant dashboard activity: which owner, staff member or YR Menu administrator submitted which change in the dashboard or staff app, when, and the names of the form fields sent with it (not their content). | Security, support and investigating misuse of an account. | Legitimate interest |
For people in Türkiye, "contract" corresponds to Article 5(2)(c), "legal obligation" to Article 5(2)(ç), "legitimate interest" to Article 5(2)(f) of Law No. 6698, and "consent" to explicit consent. For people in Uzbekistan, the basis for this processing is providing the service or performing the contract you ask for when you register, book or send a form. We ask for your consent separately only for optional processing, such as analytics and advertising cookies, and you can withdraw that consent at any time.
Menu views are counted per restaurant and per day without any personal data. Detailed menu analytics for a restaurant (which items guests open, QR scans) are recorded only after the guest accepts analytics cookies.
How we collect data. Electronically: from the forms you fill in, from your use of the dashboard, staff app and menus, from cookies with your consent, from our Telegram bot, from what your browser sends automatically, from Cloudflare's country estimate, and from our sales partners and public business listings for venue contacts.
What you must give us. To open an account you must give us your name, e-mail and business details; without them we cannot provide the service. Everything else is optional.
3. Where your data is stored and who processes it
| Provider | What it does | Country |
|---|---|---|
| Hetzner Online GmbH | Servers and database since 28 October 2026: all data listed above. Outgoing e-mail, including account e-mails and reservation e-mails to restaurants and guests. Since 30 October 2026, also our mailboxes: e-mail sent to our addresses. Nightly backup copies, which are encrypted before they leave our server; Hetzner does not have the key. | Germany (backups: Finland) |
| Cloudflare, Inc. | Network delivery and security for yrmenu.com (every request passes through it), bot protection on forms (Turnstile), and your approximate country. | United States (global network) |
| Google LLC | AI services (Gemini): translating and writing menu texts, reading the menu photos and files restaurants upload, and answering guests' questions in the AI menu assistant. Also: Google sign-in, notifications to the staff app on Android, and, with your consent, Google Analytics and Google Ads. If you arrived from one of our Google ads, we may later send that ad's click identifier and the fact that you signed up or paid to Google Ads, so it can measure our ads. | United States |
| Apple Inc., Mozilla Corporation | Notifications to the staff app on those devices. Their content is encrypted end to end and contains at most a table or room number, never a guest's name or phone. | United States |
| Telegram | Our sales and support bot, copies of website enquiries to our sales team's chat, alerts to restaurant staff who turn them on (no guest name or phone), and sign-in with Telegram where it is switched on. | United Arab Emirates |
| Meta Platforms, Inc. | Advertising measurement on our website, only with your consent. | United States |
| Yandex | Website analytics (Metrica), only with your consent, and never for visitors in Türkiye, the European Economic Area or the United Kingdom. If you arrived from one of our Yandex ads, we may later send that ad's click identifier and the fact that you signed up or paid to Yandex Direct. | Russia |
| iyzico Ödeme ve Elektronik Para Hizmetleri A.Ş. | Card payments of customers in Türkiye. You enter card details on iyzico's own page. | Türkiye |
| Dodo Payments (Dodope Payments Limited, United Kingdom, and the other companies of the Dodo Payments group, including Dodo Payments Inc.) | Card and wallet payments of customers outside Türkiye and Uzbekistan. Dodo sells the subscription to you as reseller and merchant of record: it charges any VAT or sales tax, issues the invoice and processes the payment data as controller under its own privacy policy. | United Kingdom (seller), United States and India |
| JSCB "Aloqabank" | Receiving bank transfers to TESLA KAFA LLC. | Uzbekistan |
| ATMOS (AO "NATIONAL INNOVATIVE PAYMENT TECHNOLOGIES") and the fiscal data operator (OFD); Octo | Card payments in Uzbek soum and the fiscal receipts Uzbek tax law requires. | Uzbekistan |
| European Commission (VIES) | Checking the VAT number of customers billed in the European Union. | European Union |
After you consent, the analytics and advertising tools (Google Analytics, Google Ads, Meta, Yandex) run on our website, sign-up pages and restaurant dashboard. They never run on menus, ordering, booking, game or guest-account pages.
We also disclose data where the law requires it, for example to tax authorities or courts. We do not sell personal data.
4. International transfers
Because of the providers above, your data is stored in, or can be accessed from: Germany, Finland, the United Kingdom, the United States, India, Uzbekistan, Türkiye, the United Arab Emirates and, for consented website analytics outside Türkiye, the EEA and the UK, Russia.
- For people in Türkiye: no country has an adequacy decision under Law No. 6698, so every one of these destinations is a transfer abroad. The transfer between İLHAN FIRAT KOÇAK and TESLA KAFA LLC is not yet covered by the Personal Data Protection Board's standard contract; the two will sign it and notify it to the Personal Data Protection Authority within five business days of signing, and we will update this section then. Our other providers have not signed the Board's standard contract.
- For people in Uzbekistan: Germany, Finland and the United Kingdom are on the Cabinet of Ministers' list of countries with adequate protection (Resolution No. 415); the United States is on it only for companies certified under the EU-US Data Privacy Framework.
- For people in the EEA: our servers and backups are inside the EEA (Germany, Finland); Google, Cloudflare and Meta are certified under the EU-US Data Privacy Framework. For Uzbekistan, Türkiye and the United Arab Emirates there is no adequacy decision, and we do not yet have an Article 46 safeguard in place for them. When you pay through Dodo Payments, we pass your payment data to the seller, Dodope Payments Limited, in the United Kingdom, which has an EU adequacy decision; Dodo group companies in the United States and India may also process it, which is necessary to carry out the purchase you ask for (Article 49(1)(b) GDPR). Dodo processes it as an independent controller under its own privacy policy.
What protects your data today: connections are encrypted (HTTPS), backups are encrypted with a key that only we hold, and Hetzner has signed a data processing agreement with us. Our other providers process data under their own published terms. When this changes, we will update this section.
5. How long we keep data
| Data | Kept |
|---|---|
| Restaurant account and menu content | While the restaurant's account exists. After an account is closed, we delete it when the restaurant asks us to, apart from records the law requires us to keep. |
| Guests' reservations, orders and feedback at a restaurant | Guest name, contact details and note on an order: 13 months after the order (the order amounts are kept for the restaurant). Reservations: anonymised 12 months after the visit. Contact details left with feedback: 13 months, or 24 months if the guest asked to be contacted; the feedback text is kept while the restaurant's account exists. In any case, everything is deleted automatically no later than 90 days after the restaurant's account is closed, or earlier if the restaurant asks; a recovery copy is kept for 30 more days, and copies in encrypted backups are deleted at the latest after 13 months. |
| Guest accounts | Until you close the account. |
| Hotel room requests | 13 months, then deleted automatically. For a closed account: no later than 90 days after closure. |
| Invoices and payment records | At least 5 years from the end of the year in which they were issued, as tax law requires, or longer where the billing entity's law requires it. |
| Login and form rate-limit records | 30 days. |
| Questions and answers in the chat on our website | 30 days. |
| AI translation usage log | 400 days. |
| Backups | Daily copies for 30 days and one copy per month, deleted at the latest after 13 months. |
| Your cookie choice | 1 year. |
| Dashboard activity records (who submitted which change, and when) | 90 days, then deleted automatically. |
| Administrator and security activity records (two-factor sign-ins, password changes, actions taken by YR Menu staff) | 12 months, then deleted automatically. |
| Content reports | The IP hash and the browser and device type are deleted within 24 hours. Open reports are kept until they are dealt with; reports that have been dealt with are deleted 12 months after that. |
| Records of content we have hidden from a menu, including ones since lifted | As long as the restaurant's account exists. |
| Enquiries and leads from our contact and demo forms | 24 months; an advertising click identifier stored with an enquiry is deleted 90 days after the click. |
| Messages sent to our Telegram bot | 12 months; Telegram update identifiers 30 days. |
| Support messages | 12 months. |
| Analytics and QR-scan records (IP hash, browser and device type) | 13 months. |
| Waiter calls and bill requests | 90 days. |
| The remaining record of a closed guest account | 12 months after closure. |
| E-mail address given with a content report | Removed 90 days after the report, even if the report is still open. |
| Contact details of venues our sales partners visit | 12 months, unless the venue became a customer. |
| Records of accepting our Terms and policies | For the term of the contract and 10 years after it ends. |
| Server security and error logs | As long as we need them to secure the service and fix errors; we delete them earlier on request. |
Deletion runs automatically every day.
6. Security
We use encrypted connections, hashed passwords, IP addresses stored in our database only as one-way hashes, separation of each restaurant's data, encrypted backups with an offline key, access limited to the people who run the service, optional two-factor sign-in for our administrators, rate limits on logins and forms, and an audit log of administrative actions. No system is completely secure. If a breach affects your data, we will inform you and the competent authority as the law requires.
7. Your rights
You can ask us for a copy of your personal data, to correct it, delete it, export it, restrict or object to how we use it, and to withdraw any consent you gave. Withdrawing consent does not affect what we did before. Write to the contact of the responsible entity in section 1; we answer within one month.
People in Türkiye also have the rights in Article 11 of Law No. 6698: to learn whether your data is processed, to request information about it, to learn the purpose and whether it is used accordingly, to know the third parties it is transferred to in Türkiye or abroad, to have it corrected if incomplete or wrong, to have it deleted or destroyed under Article 7, to have those third parties informed of a correction or deletion, to object to a result against you that comes only from automated analysis, and to claim compensation for damage caused by unlawful processing. Send your request to İLHAN FIRAT KOÇAK in writing to the address in section 1, by registered e-mail (KEP), with a secure electronic signature, or from the e-mail address registered in your account to info@yrmenu.com. We answer within 30 days. If we refuse or do not answer, you can complain to the Personal Data Protection Board (Kişisel Verileri Koruma Kurulu, KVKK) within 30 days of our answer, or within 60 days of your application.
People in Uzbekistan can send requests to TESLA KAFA LLC at info@teslakafa.com and can complain to the authorised state body for personal data, currently the Migration and Personalisation Department of the Ministry of Internal Affairs of the Republic of Uzbekistan.
People in the European Economic Area or the United Kingdom can complain to the data protection authority where they live or work, or where they believe the problem arose. We would prefer you to contact us first, but you do not have to.
8. AI features
When a restaurant uses translation, content writing or menu import, the menu text, photos or files go to Google's Gemini service. When a guest asks the AI menu assistant a question, the question and the restaurant's menu go to Gemini; no name, table number or contact detail is added to it, so please do not type personal details into the question. The assistant's answers are produced by AI and can be wrong; allergen information must always be checked with the restaurant.
The chat on our website (the "Ask YR Menu" button) works the same way: your question, up to three earlier questions and answers of the same chat and our public pricing information go to Gemini. We keep each question and answer for 30 days, with e-mail addresses and phone numbers masked, to see what visitors ask and improve our answers; only the page path, the page language and an approximate country are stored with them, and the chat log never holds your name, account or IP address. Please do not type personal details into the chat. Its answers are produced by AI and can be wrong; the prices and plans on our pricing page are what count.
9. Automated decisions
We do not make decisions about you with legal or similarly significant effects by automated means, and we do not profile you for that purpose.
10. Children
YR Menu is a business service. We do not knowingly collect personal data directly from children. Menus, ordering, booking, game and guest-account pages carry no third-party advertising or analytics tags.
11. Cookies
Our Cookie Policy explains the cookies and similar technologies we use and how to change your choice.
12. Changes
We update this policy when our providers, our features or the law change. The date of the last change is at the top; we announce important changes in the dashboard or by e-mail.
13. Language
For customers and people in Türkiye, the Turkish version of this policy is the binding text. For everyone else, the English version is binding; other translations are provided for convenience.
14. Contact
For any privacy question or request, write to the contact of the responsible entity in section 1.