Privacy Policy
Last updated: 24 October 2026. Applies to users in the Republic of Serbia. The Serbian version is the binding one; this is a translation.
Draft. This text is being prepared and awaits legal review; it may change before it takes effect.
1. Introduction
This policy explains what personal data the Edim service processes, why, for how long and what rights you have, in accordance with the Law on Personal Data Protection of the Republic of Serbia ("Official Gazette of RS", No. 87/2018, the "LPDP").
Edim is a service for restaurants and cafés: a QR code menu for guests, orders and waiter calls, and team tasks. The policy applies to:
- owners — people who register an account and venues;
- staff — administrators and waiters added to the account by the owner;
- guests — people who open a venue's menu by scanning a QR code or following a link.
Services: the web app edim.app, the Edim mobile apps (Android, iOS), the guest menu edim.menu and in-app support.
2. Controller and contact
The controller for Edim is a sole proprietor registered in Serbia:
| Name | Dmitrii Smirnov PR Beograd |
| Address | Čika-Ljubina 12, 11000 Belgrade (Stari Grad), Serbia |
| Registration number / Tax ID | [TO BE ADDED] / [TO BE ADDED] |
| D-U-N-S | 754167199 |
| Email for data questions | support@edim.online |
Send any questions about your data to this email address or through support in the app.
3. Edim's role: controller and processor
Edim has two roles, depending on whose data it is:
| Data | Controller | Edim's role |
|---|---|---|
| Owner account, support, service security | Edim | controller |
| Staff data entered by the owner | the venue (employer) | processor |
| Guest orders and waiter calls | the venue | processor |
As a processor, Edim processes data only on the venue's instructions, under the data processing agreement that is part of the Terms of Use for venues. Guests and staff may send requests about such data to the venue; Edim helps the venue fulfil them.
4. Data we process and its sources
| Category | Data | Source |
|---|---|---|
| Owner account | name, email, password (stored only as a hash by Google Firebase Authentication), country, language, time zone; with Google sign-in — name, email and profile photo from the Google account | owner, Google |
| Business and venues | venue name and address, logo, images, invoicing details (company name, address, tax ID, registration number, phone, email), menu, tables, events | owner |
| Staff | name, email, phone, role, workplace, "on vacation" status; optionally — date of birth, photo, tips goal | owner or administrator, the staff member |
| Work in the app | tasks and comments, accepted orders and calls, notifications | account users |
| Notification channels | device token for push notifications, Telegram ID (if the user links it) | device, Telegram |
| Guests | a random guest identifier in the browser, table, order contents and time, waiter call and its reason ("waiter", "bill", "help"), menu language | guest's device |
| Support | messages and screenshots the user sends, app version, account details the operator needs | user, app |
| Technical data | IP address and request details in server logs, device and browser type, error reports, app integrity check (Firebase App Check) | device |
Guests do not create an account. Edim does not ask for a guest's name, phone or email and does not track guests across venues. Guests should not enter health data or other special categories of data in order notes.
We do not use behavioural analytics, advertising cookies or profiling, and we do not make decisions based solely on automated processing.
5. Purposes and legal basis
Each processing activity relies on one of the bases in Article 12 of the LPDP:
| Purpose | Legal basis (Art. 12 LPDP) |
|---|---|
| Creating and running the account, venues and menu; sign-in and email confirmation | performance of a contract (Terms of Use) |
| Receiving guest orders and calls, assigning a waiter, notifying staff | performance of the contract with the venue; Edim as processor |
| Staff invitations, password reset and other system emails | performance of a contract |
| User support | performance of a contract; legitimate interest in solving the problem |
| Security: abuse prevention, rate limiting, logging of support staff access | legitimate interest |
| Finding and fixing errors in the app | legitimate interest |
| Notifications via Telegram | consent (the user links the account and can unlink it) |
| Keeping accounting and tax records of payments, once payments are introduced | legal obligation |
You may withdraw consent at any time without affecting the lawfulness of earlier processing.
6. Recipients
We do not sell data or share it for advertising. Only processors working for Edim and the venue whose account holds the data have access:
| Recipient | What it does | Data |
|---|---|---|
| Google (Firebase: Authentication, Firestore, Storage, Cloud Functions, Hosting, Cloud Messaging, Crashlytics, App Check) | sign-in, database and files, server processing, push notifications, error reports | all service data |
| Postmark (ActiveCampaign) | sending system emails | email, name, email content (link, venue name) |
| TryDesk | in-app support chat | messages, screenshots, account context |
| Sentry (Functional Software, Inc.) | error reports of the web app | user identifier, device, error description |
| Telegram | notifications, only if the user links an account | Telegram ID, notification text |
| The venue (owner and staff) | working with orders, tasks and the team | data of their account |
| Public authorities | only when required by law | as requested |
Edim support staff may view account data only to help, and every such access is logged.
7. Transfers outside Serbia
The database and files are stored in the European Union (Google Cloud, region eur3). Part of the server processing and the Postmark and Sentry services run in the USA, so data for those operations is transferred outside Serbia.
Transfers comply with Articles 63–65 of the LPDP: to countries with an adequate level of protection according to the list of the Government of the Republic of Serbia, and to other countries with standard contractual clauses or other appropriate safeguards offered by the processors.
8. Retention
| Data | Retention |
|---|---|
| Account, venues, menu, staff, tasks, orders | while the account exists; after a deletion request — deleted within 30 days |
| Database backups | up to 7 days (point-in-time recovery), daily backups 7 days, weekly backups 14 weeks |
| Support chat history | while the user's account exists; deleted with the account or the staff member |
| System email delivery records | 7 days (without the links and codes from the email) |
| Rate-limiting data | 1 day, as a hash only (no email or IP address) |
| Log of support staff access | 2 years |
| Guest identifier | in the guest's browser until the guest clears it |
| Accounting records of payments | as required by the Law on Accounting |
When the period ends, we delete the data or anonymise it permanently.
9. Your rights and complaints to the Commissioner
Under Articles 26–38 of the LPDP you have the right to:
- get information about and a copy of the data we process;
- ask for correction or completion of your data;
- ask for deletion of your data and account;
- ask for restriction of processing;
- receive your data in a structured, readable form (portability);
- object to processing based on legitimate interest;
- withdraw consent (for example, unlink Telegram in your profile).
You can change most data yourself in your profile and settings. For anything else write to support@edim.online. We reply without delay and within 30 days at the latest; this may be extended by 60 days with notice. We may ask you to confirm your identity.
If you believe the processing is unlawful, you have the right to lodge a complaint with the Commissioner for Information of Public Importance and Personal Data Protection, Bulevar kralja Aleksandra 15, 11120 Belgrade, www.poverenik.rs.
10. Cookies, children, security and changes
Cookies and local storage. We do not use advertising or analytics cookies. The browser stores only what the service needs: the sign-in session, the guest and table identifiers, language, theme and selected filters. You can clear them in your browser settings; the basket is then lost and you need to sign in again.
Children. Owner and staff accounts are for adults. Guests can use the menu without an account and without entering personal data.
Security. Data is transmitted encrypted (HTTPS). Access is limited by roles and database rules, support staff sign in with a second factor, and the database is backed up regularly. We notify the Commissioner and you of a data breach within the periods set in Articles 52–53 of the LPDP.
Changes. We announce significant changes to this policy in the app or by email at least 15 days in advance. The date of the last change is at the top of this page.
11. Data from your Google account
When you sign in with Google, Edim receives only basic profile data from Google: your name, email address, profile photo and Google account identifier. We do not request access to your contacts, calendar, Google Drive or any other Google services.
- Use. Only to sign you in to Edim, to show your name and photo in your profile and to send system emails (email confirmation, invitations, password reset, support).
- Sharing. We do not sell this data, do not use it for advertising, profiling or creditworthiness assessments, and do not transfer it to third parties, except the processors listed in section 6 that store and process it for us (Google Firebase) and the venue whose account you work in (your name and photo are visible to the team).
- Protection. The data is transmitted encrypted (HTTPS) and stored with Google Cloud; access is limited by database rules and account roles.
- Retention and deletion. We keep it while your account exists; after a deletion request we delete it within the period in section 8. Request deletion at support@edim.online or through in-app support. You can revoke Edim's access to your Google account at any time at myaccount.google.com/permissions.
Edim's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.