Privacy policy
Updated November 8, 2026
Version of 8 November 2026.
This policy explains what personal data the EVENTIS service — the eventis.uz website, the Eventis iOS app and the venue dashboard (the "Service") — processes, why, who receives it, how long it is kept and what rights you have. It is based on the Law of the Republic of Uzbekistan "On Personal Data".
1. Who processes the data
The owner and operator of the Service's personal data database is Eventis LLC ("EVENTIS", "we").
For personal data matters: phone +998 50 088 77 88, email itsakbarov@gmail.com. The person responsible for organising personal data processing is Sardor Akbarov, co-founder of EVENTIS.
2. What data we process
Guests — on registration and in the profile:
- name;
- phone number — required: the venue uses it to contact you, and you use it to sign in;
- email address — optional;
- password — we store only its irreversible transformation (a hash); nobody, including us, knows the password itself;
- interface language.
Guests — in a request: the venue, hall, date and time of day, type of event, number of guests, budget, additional wishes and comment, and — if you add one — the name, phone number and role of an additional contact (for example, a parent).
Venue representatives: the name, phone number, email and role of each dashboard user; details of the venue — name, address, contacts, legal name, taxpayer ID and documents the venue uploads to the dashboard.
Technical data: IP address, browser and device details (user agent), time of sign-ins and actions in the Service.
We do not collect passport or payment details: there are no payments in the Service. We do not ask for health data, beliefs or other special categories of data — please do not include them in a request comment.
3. Why we process data
- to register you, let you sign in and restore access to your account;
- to pass your request to the chosen venue so that it can contact you, and to show you its status;
- to tell you when the status of a request changes — in "My requests" and, when these notifications are switched on, by SMS or email;
- to let venues manage their calendar, requests and clients in the dashboard;
- to protect the Service and accounts from abuse and to handle enquiries and disputes;
- to comply with the laws of the Republic of Uzbekistan.
We do not send marketing messages. If we start, we will ask for separate consent.
4. Legal grounds
We process data with your consent, which you give when you register and when you send a request, to perform the Terms of use, and in cases provided for by law. You can withdraw your consent — see section 8.
5. Who receives the data
- The venue you sent a request to receives your name, phone number and the request details, and the additional contact if you added one. The venue uses them to contact you and agree on the event and is itself responsible for any further processing.
- Contractors that keep the Service running (hosting and data storage, SMS delivery, Telegram notifications for venues) receive only what their task requires, under contracts that oblige them to keep it confidential: Amazon Web Services and Cloudflare (hosting and data storage), Eskiz (SMS), Resend (email), Telegram (venue notifications).
- Public authorities receive data only when required by law.
We do not sell personal data or share it for advertising.
Data that a venue enters into the dashboard itself (its clients, staff, estimates) is processed on the venue's instructions and only to run the dashboard.
6. How long we keep data
- account data — while the account exists; when the account is deleted, the name, phone number, email and shortlist are deleted at once;
- requests and their history — for 3 years after the event date: you and the venue need them for your records and to resolve disputes;
- technical sign-in data and the activity log — for 1 year;
- a request draft is saved only in your browser — when you press "Send request" without being signed in — and is not sent to our servers. It is deleted when the request is sent or when you open the same venue's form after 24 hours; otherwise it stays in your browser until you clear the site's data.
After the period ends, data is deleted or anonymised unless the law requires it to be kept longer.
7. How we protect data
- the connection to the Service is encrypted (HTTPS);
- passwords are stored only as hashes;
- EVENTIS and venue staff see only the data their role needs, and their actions are recorded in a log;
- access keys to external services are stored encrypted.
8. Your rights
Under the Law "On Personal Data" you have the right to:
- know whether we process your data and receive information about its processing;
- have inaccurate data corrected — you can change your name, email and language in your profile yourself;
- have your data blocked or deleted and your account deleted;
- withdraw your consent to processing — after that we cannot pass your requests to venues;
- appeal against our actions to the authorised state body for personal data or to a court.
To exercise a right, send a request to the operator using the details in section 1. We review the request and tell you the outcome within 10 days. You can also delete your account yourself: in the app, Profile → Privacy and security → Delete account. Your name, phone number, email, shortlist and sessions are deleted at once. Requests you have already sent, and the contact details a venue received with them, stay with that venue as its records; to have those deleted too, write to us and we will pass the request to the venue.
9. Cookies and browser storage
- the
eventis_rtcookie keeps you signed in: page scripts cannot read it, and it lasts up to 90 days for guests and up to 14 days for venue dashboard users; - your browser storage (localStorage) keeps a request draft so that a filled-in form is not lost while you sign in; how long it stays is described in section 6.
The website has no advertising or analytics cookies or trackers.
10. Children
The Service is intended for adults. We do not knowingly collect data of persons under 18.
11. Changes to this policy
A new version is published on this page with its date. The date of the current version is shown at the top of the page.