Skip to content

Privacy policy

Last updated: October 22, 2026

This text is a draft. It will be reviewed before the service’s public launch.

Who we are

This service helps people find events in Uzbekistan, register for them and check in at the door. Organizers publish events; everyone else finds them and comes along. It works through our Telegram bot, this website, and the same website opened inside Telegram as a Mini App. In this policy, “we” means the team that runs the service.

This policy explains what personal data we collect, why we collect it and what you can do about it. The rules for using the service are in the Terms of use.

While the service is being tested there is no support inbox yet; we’ll add one before public launch. Meanwhile, in our Telegram bot, @newbot565324_bot, /privacy shows what you have agreed to, and /delete_me deletes your account.

What we collect and why

We collect only what the service needs to work.

  • Your Telegram account: your Telegram ID, first and last name, username and language. Telegram shares them when you use the bot, open the Mini App or log in on the website. They identify your account, let the bot write to you and set the service’s language. Organizers see your name when you register for their events.
  • Your phone number, only if you choose to share it when you log in with Telegram.
  • Your age: the year you were born, or your confirmation that you are 16 or older. We ask once, before your first registration, to check the age limit.
  • Your registrations: the events you register for, their status (for example “Going”, “Waiting for approval” or “Checked in”), your ticket, and whose shared link brought you, if any. They get you in and let the organizer run the event.
  • Your choices: the calendars you follow, your language, whether the bot may write to you, your reminder and weekly digest settings, and who sees you on guest lists.
  • Your consents: what you agreed to, when, under which version of this policy, and how (for example, which button you pressed).
  • Reports you send about events or calendars, with their reason and any details you add.
  • Sign-ins: for each login on the website or in the Mini App, a session record with the browser you used and when you were last active, so you stay logged in and your sessions can be ended.
  • Usage records: actions such as registering for an event or following a calendar, linked to your account but holding no other personal details. They show us how the service is used.

If you organize events, we also keep your calendars and team roles, the events you publish, and the posts and messages you give us to create events: posts from channels you connect, messages and forwards you send to the bot, and text you paste into the dashboard.

Like any website, our servers receive your IP address and browser details with each request. We use them to run the service and to limit how often logins and some other actions can be tried.

How we use AI

Organizers can add events by connecting a Telegram channel or group, sending a post to our bot, or pasting it into the dashboard. To turn that text into an event draft, we send it to Claude, an AI model made by Anthropic in the United States.

  • Before sending a post, we hide the phone numbers, @usernames and email addresses in its text, and put them back into the draft afterwards.
  • We don’t hide names written in the text, or anything in images that come with a post. Organizers are told this before they connect a channel.
  • We send only the post. We never send attendees’ data, guest lists or profiles.

Claude only proposes a draft. Our code checks it, and the organizer decides whether to publish it. Claude’s text never reaches attendees: event pages show the organizer’s own words, and our messages to attendees use fixed templates.

Before we read posts from a channel or group, the organizer who connects it agrees to this processing, including processing outside Uzbekistan. We record that consent, and disconnecting withdraws it. Posts you send or paste yourself are processed the same way to draft your event.

Where your data is stored

Your data is stored outside Uzbekistan, in the European Union. The service and its database run on a server we rent from Hostinger, in an EU country on Uzbekistan’s official list of countries for personal data transfers. The database is not open to the internet.

Every night we make an encrypted backup of the database and keep it with a separate storage provider, also in the EU. Only we hold the key that decrypts it.

We also rely on these services:

  • Anthropic (United States) runs Claude, which drafts events from organizers’ posts, as described above.
  • Telegram carries the bot’s messages, which can include your name and event details. Telegram’s own privacy policy covers its service.
  • Sentry (EU region) receives error reports with personal data removed, so we can fix problems.

How long we keep data

  • Your account and everything in it: until you delete your account.
  • Messages and taps the bot receives, stored as Telegram delivered them: 30 days, then deleted automatically.
  • The text of posts and messages we read to create events: 30 days. If an organizer disconnects a channel or group, its text is deleted at once. Drafts and events made from it keep the event details, and drafts also keep short quotes that show where each detail came from.
  • Published events: until the organizer removes them. Once their date has passed, they leave Discover.
  • Server logs, which hold no names or message text: 30 days.
  • Backups: 35 days, then they expire.

When you delete your account, we delete the link to your Telegram account, your sessions, settings and follows, and erase your name, username, phone number and age. The text of posts you sent us is deleted, and unpublished drafts made from them lose their text. Usage records are no longer linked to you. Your registrations stay without your name, so organizers’ counts stay right, and reports you sent stay without your name. Records of your consents, and of when your details were shared, stay as evidence, linked to the anonymized account. Events you published stay with their calendar. If you own a calendar, hand it over to another team member first.

Deleted data can remain in our backups for up to 35 days, until they expire. If we ever restore a backup, we delete again everything that was deleted after it was made, before the service goes back online.

Who sees your data

  • The event’s team. When you register, the organizer’s team (owners, admins and ticket checkers) sees your name, your status, and when you registered and checked in, so they can approve guests and let people in. They never see your phone number, Telegram username or ticket code. We record each time your details are shared this way, and your My data page shows how many times it has happened.
  • Other people. Everyone can see how many people are going. Your name appears on an event’s public page only if you choose “Everyone” on your ticket and the organizer shows the guest list. Until you change it, your choice is “Other guests”.
  • Organizers. Members of a calendar’s team see each other’s names and roles. A calendar’s name, description and events are public.
  • Our staff. They can see reports and the events, calendars and accounts the reports concern, and can act on them. Every staff action is recorded.
  • Service providers. The services listed under “Where your data is stored”, only for the work described there.

We don’t sell personal data, and we don’t use it for advertising.

Your rights and choices

  • See your data. The My data page, or /privacy in the bot, shows what you have agreed to, under which version of this policy, and how many times your details were shared with organizers.
  • Delete your account. Do it in Settings, or by sending /delete_me to the bot. It takes effect at once and can’t be undone.
  • Change your choices. Change your language, reminders and weekly digest in Settings, or your language and digest with /settings in the bot. Every reminder and digest message has a button that stops them. On each ticket, you choose who sees you on the guest list.
  • Withdraw consent. You can turn off the weekly digest at any time. An organizer can disconnect a channel or group at any time: we stop reading it at once and delete its stored posts.
  • Ask us. A contact for questions about your data will be added before public launch.

Age limits

The service is for people aged 16 and over. Before your first registration, we ask the year you were born. If you turn 16 this year, we also ask you to confirm that you are already 16. We keep only the year, not your full date of birth.

We don’t accept registrations from anyone under 16. If you are under 16, please don’t use the service.

Cookies

The website uses only the cookies it needs to work. It has no advertising or tracking cookies.

  • __Host-sid keeps you logged in. It lasts 30 days and renews while you use the site. Scripts on the page can’t read it.
  • __Host-login holds a Telegram login while it is in progress, so we can check that it is really yours and bring you back to the page you came from. It lasts 10 minutes.
  • __Host-poll, when you log in through the bot, makes sure that only the browser that asked can receive the login. It lasts 10 minutes.
  • NEXT_LOCALE remembers your language when it differs from your browser’s. It is deleted when you close the browser.

The website also keeps two things in your browser’s own storage, never sent to us: your last few searches, and which events on Following you have already seen, so new ones can be marked. Clearing your browser’s site data removes them.

In the Mini App inside Telegram, signing in uses no cookie: the sign-in lasts 24 hours and is kept only in memory.

Changes to this policy

We will update this policy as the service changes. The date at the top shows when it last changed. Each consent you give is stored with the version of the policy in force at that moment, and your My data page shows the current version. If a change needs your consent again, we will ask for it.