Hamkosa Privacy Policy
In short
- Hamkosa is a service that helps office colleagues order lunch together. The operator is Muxamedjanov Ruslan Olegovich, email [email protected].
- We process only what is needed to put an order together and split the bill: your Telegram profile, the dishes you choose, amounts and payment marks.
- We do not sell data, show ads, or share names, Telegram IDs or card numbers with food delivery services.
- Data is stored with our hosting provider Railway in the USA and in Telegram in the Netherlands.
- You can delete your data with a button in the mini app; to find out what we store about you, write to [email protected]. We reply within 10 days.
1. Who we are
The operator and owner of the personal data database, responsible for processing personal data, is Muxamedjanov Ruslan Olegovich, an individual, Republic of Uzbekistan. Email: [email protected]. We will provide a postal address on request.
This policy covers the whole Hamkosa service: the Telegram bot, the mini app, the browser extension and the website. It describes how the service works now. Personal data is processed under the Law of the Republic of Uzbekistan "On Personal Data".
2. What data we process
- Telegram profile — Telegram ID, name and username. Telegram provides them when you use the bot.
- Orders and payments — the dishes chosen, their quantity and prices, amounts due, marks of payment and of receiving the order, the delivery status of the order from the food delivery service. The organizer's bank card number, if the organizer entered it.
- Opinions and feedback — votes for a restaurant, lunch ratings, ideas and bug reports; for bug reports — the screen, app version and device; screenshots you yourself attach to an idea or bug report.
- Company data — the name of the work group, the office address and its location on the map, who is the admin and who is the organizer.
- Technical data — a log of actions in the service, a log of the bot's private messages (to whom and when, without the text), mini app sessions and connected extension devices.
Apart from the Telegram profile, all data is entered by you or your colleagues, or appears as you use the service. We do not process special categories of data such as biometrics. We do not receive passwords to food delivery accounts or payment data, other than the organizer's card number.
Data is processed automatically: collected, recorded, stored, used and deleted.
3. Why and on what basis
| Purpose | Basis |
|---|---|
| Put a shared order together, split the bill, remind about transfers, choose a restaurant | performance of the user agreement |
| Show the organizer's card number to participants | the organizer's consent; the setting can be turned off and the card deleted |
| Send you private messages | your consent; withdrawn by stopping the bot |
| Review ideas and bug reports, understand where to order next time | the operator's legitimate interest |
| Find failures and protect the service | the operator's legitimate interest |
We will ask for separate consent for any new purpose.
4. Who sees your data
- Participants of the same order — your choice and your share. Only overall totals are posted in the group, without amounts or ratings by name.
- The organizer — amounts, payment marks and ratings for their own orders.
- The organizer's card number — participants of their orders, and only if the organizer has turned this on.
- Company admins — their own company's data.
- The operator — screenshots you attached to an idea or bug report, in the operator's own chat with the bot in Telegram. Only the operator sees them; organizers and company admins do not.
- Food delivery services Uzum Tezkor and Yandex Eats — the cart contents and the office delivery location. Names, Telegram IDs and card numbers are not shared with them. The organizer places the order with their own account under the service's rules.
- Our providers: Railway — server and database hosting (USA); Telegram — bot messages and an encrypted database backup (the Netherlands); Cloudflare — the website only.
- Public authorities — only when required by law.
We do not sell personal data or use it for advertising.
5. Where and how long we store data
Data is stored in the USA and the Netherlands. These countries are on the list of countries ensuring adequate protection of personal data subjects' rights (Resolution of the Cabinet of Ministers of the Republic of Uzbekistan No. 415 of 29.07.2026); the USA is listed for companies participating in the EU-U.S. Data Privacy Framework, which includes Railway.
- Data is kept while the company uses Hamkosa.
- At the request of a person or a company admin — made with a button in the mini app or by email — we delete data from the database within 10 days and from backups within 30 days.
- Server logs are kept for no longer than 30 days.
- Screenshots attached to ideas and bug reports are stored in Telegram, in the operator's chat with the bot. Our database keeps only the Telegram file identifier; the images themselves are not stored on our server. Before sending, the mini app makes the image smaller and does not send data about where it was taken.
6. Browser extension
The extension is needed only by the organizer.
- It works only on uzumtezkor.uz and eats.yandex.com and exchanges data only with the Hamkosa server. It does not see browsing history or other websites.
- It puts the collected order into the website's cart and reports to the server what ended up in the cart: dishes, quantities, total.
- To check the transfer and investigate failures, after a transfer and when the button is pressed it sends a cart summary: the restaurant, dishes, quantities and total in the cart on the website, the food delivery service's response about the order cart, and on an error its code and the beginning of the response. The summary also includes the extension version, the time, which page of the website is open, whether you are signed in (yes or no) and the names of the website's service records without their contents. The extension does not send the page text, the delivery address or the phone number. The summary is kept in server logs for no longer than 30 days.
- After transferring the cart to Uzum Tezkor, on the order page it reads the order status and sends it to the server: the stage (being prepared, courier on the way, delivered and so on), whether the order is late, the promised delivery time, the time the order was created and whether the tab is visible. Instead of the order number it sends a hash of it, which lets the server tell one order from another. The extension does not send the courier's name, phone number or location, the delivery address, the page text or your other orders. Participants of the collection see the status in the lunch message in the group and in the mini app; it is stored together with the order.
- After transferring the cart to Yandex Eats, on the orders page it reads the order status and sends it to the server: the stage (being prepared, courier assigned, courier on the way, delivered and so on), the order step (for example, 2 of 4), whether a courier is assigned and whether they are delivering another order first (yes or no), the approximate time until arrival — only once a courier is assigned, the time the status was read and whether the tab is visible. Instead of the order number it sends a hash of it. The extension checks the order's restaurant against the transferred cart in the browser and does not send it to the server. The extension does not send the courier's name, phone number or location, the delivery address, the page text, the payment status or your other orders. The website updates the Yandex Eats orders page itself. If no status arrives for 5 minutes and the tab is in the background, the extension refreshes it, no more than once every 5 minutes; it does not refresh a tab you are looking at. Refreshing stops when the order is delivered, the tab is closed or 3 hours have passed. You can stop sending the status and refreshing the tab with the «Не следить и не обновлять» ("Stop tracking and refreshing") button in the extension's window. Participants of the collection see the status in the lunch message in the group and in the mini app; it is stored together with the order.
- While an Uzum Tezkor order is not delivered and the order page is open in a background tab, the extension refreshes that tab no more than once every 3 minutes, because the website updates the status only in a visible tab. It does not refresh a visible tab where the website updates the status itself. Refreshing stops when the order is delivered, the tab is closed or 3 hours have passed. You can turn it off with the «Не обновлять эту вкладку» ("Do not refresh this tab") button in the extension's window.
- It checks only whether you are signed in to the food delivery account. It does not store or transmit sign-in data.
- It does not place or pay for orders and does not see payment data.
- It stores its device key, its own settings and the state of order tracking in the browser.
7. Your rights
You can:
- find out which of your data we process, why and with whom we share it;
- have inaccurate data corrected — we correct it within 3 days;
- request deletion of your data or that we stop processing it;
- withdraw your consent;
- appeal our actions to the authorized state body or to a court.
You can delete your data yourself: in the mini app, open "Profile" → "Delete my data". Your card, settings and roles are deleted immediately. Records of your screenshots are deleted from the database immediately, and the operator deletes the screenshots themselves from their chat with the bot manually within 10 days. In the order history your name is replaced with "Deleted participant"; the amounts stay so that your colleagues' calculations still add up. A company admin first hands the role over to someone else; an organizer first closes or cancels their open collection.
An admin can delete the company: "Company" → "Danger zone" → "Delete company". The bot leaves the company's groups immediately, open collections are cancelled, and the company's data is deleted after 10 days.
For your other rights, write to [email protected] and include your Telegram username. We reply within 10 days. To stop the bot from messaging you privately, simply stop or block it in Telegram.
8. Security
Connections to the server use HTTPS only. Sign-in to the mini app is verified by Telegram's signature, and access keys are stored only as hashes. The backup is encrypted. Only the operator has access to the database. In case of a data breach, we will notify the authorized state body within the time limits set by law and inform affected people through the bot.
9. Website
The website does not use cookies, visitor counters or third-party services.
10. Age
Hamkosa is intended for office employees aged 18 and over.
11. Changes and language
The current version is always available at the address of this page; previous versions are available at addresses with the version number. The bot will announce significant changes in the groups where it works.
This policy is drawn up in Russian; the Uzbek and English texts are translations, and in case of any discrepancy the Russian text prevails.