iDonate

iDonate Platform Privacy Policy

(Personal Data Processing Policy)

  • Version: 2.0
  • Effective date: for new users and Donors — 13.10.2026; for Streamers who registered before this version was published — from the day they give the consent requested in clause 21.5
  • Amendment (20 October 2026): Section 20¹ (Instagram chat widget) and the related clauses have been added. They apply only to Streamers who enable this feature, with their separate consent (clause 21.3).
  • Amendment (21 October 2026): the procedure for re-checking (at least once every 30 days), updating and deleting stored YouTube channel identifiers and channel names obtained from YouTube has been described (item 6 of Section 7, clauses 12.2, 20.2, 20.8, 20.11 and 20.12). This amendment does not extend retention periods; it shortens them.
  • Amendment (22 October 2026): the re-checking and deletion of profile channel links of the form youtube.com/channel/… has been described (clauses 12.2, 20.2 and 20.8). This amendment does not extend retention periods; it shortens them. It has also been specified that, if the Streamer has enabled "Read the donor's name and amount" in a donation level's settings, the Donor's name and the amount are also sent to the TTS service (Section 10: clauses 10.3, 10.4 and 10.5).
  • Amendment (31 October 2026): the temporary short code derived from YouTube live chat message identifiers, used to remove deleted messages from the widget, has been described (clauses 5.6, 12.2 and 20.8). This amendment does not extend how long chat messages are held in temporary memory.
  • Amendment (1 November 2026): since 30 October 2026, uploaded and service files (except voice messages) are also copied, in encrypted form only, to the cloud backup storage provider; before that it received only the encrypted backup copy of the database. The recipient is not new, but the data it receives has expanded (the Summary, clauses 10.1, 10.3, 10.5 and 11.1). The purpose of the copy, its retention period and its deletion procedure have been added (clauses 6.2, 12.2, 16.5 and 17.4). Clause 10.4 has been corrected: password hashes, PINFLs, settlement account numbers and masked card numbers were already transferred to this provider as part of the encrypted backup copy of the database before this amendment.
  • Amendment (7 November 2026): if the Streamer's Telegram account is linked to the Platform, the voice message from a Donation may also be sent to the Streamer as an audio file via the Operator's Telegram bot. The recipient (Telegram) and the purpose (purpose 4 in clause 6.2, clause 9.4) are not new, but the data Telegram receives has expanded (clauses 5.8, 10.3, 10.4, 10.5, 11.2, 12.2, 14.1, 17.3 and 17.5). The Operator's retention period for voice messages (30 days) does not change. This amendment applies to Donations sent after its publication.
  • Amendment (15 November 2026): if the Donor uses the "Voice Selection" service (clause 7.10 of the Offer), the message text is synthesized in the voice and tone the Donor has chosen. If the Streamer's Telegram account is linked to the Platform, this audio recording may also be sent to the Streamer via the Operator's Telegram bot. The recipients (the TTS service provider and Telegram) and the purposes (purposes 4 and 5 in clause 6.2, clause 9.4) are not new. The voice and tone chosen by the Donor have been added to clause 5.2, and the data Telegram receives has expanded (clauses 5.8, 9.4, 10.3, 10.4, 10.5, 12.2 and 17.5). The Operator's retention period for synthesized voice files (30 days) does not change.
  • Permanent address: https://idonate.uz/privacy-policy
  • Previous version: the 2024 version. It ceases to have effect from the date this version enters into force.

Summary

The following summary is provided for convenience. The full and legally binding text is set out in the sections that follow it.

  • Your personal data is processed by the owner and operator of the iDonate platform — "CODO IT" LLC (Section 2).
  • Only the data necessary for the operation of the Platform, payments, security and compliance with legal requirements is collected (Sections 5–6).
  • Your data is not sold. No advertising or web analytics tracking tools (trackers) are used on the Platform (Section 13).
  • The Platform's main servers are located in the territory of Uzbekistan. For certain services, part of the data is transferred abroad. These services are: Telegram, text-to-speech conversion, bot protection, Google, Meta (Instagram), the AI assistant in the dashboard and storage of encrypted backup copies (Section 10).
  • When you make a Donation, your name (nickname), message and voice message may be shown publicly on the Streamer's live stream. Do not include personal data in your message (Section 8).
  • Payment card details are entered not on the Platform but on the Payment Organization's page (clause 5.9).
  • Your rights, the procedure for submitting requests and the procedure for deleting an account are set out in Sections 15–17. Email address for requests: info@idonate.uz (clause 2.1).

1. General Provisions

1.1. This Privacy Policy (hereinafter — the Policy) sets out how "CODO IT" LLC processes personal data on the iDonate platform. It specifies:

  • what data is processed, for what purposes and on what legal grounds;
  • to whom data is disclosed, and where and for how long it is stored;
  • how data is protected;
  • the rights of personal data subjects and the procedure for exercising them.

1.2. The Policy has been developed in accordance with the following documents:

  • Law of the Republic of Uzbekistan No. ZRU-547 "On Personal Data" dated 2 July 2019 (hereinafter — the Law);
  • the Model Procedure for Processing Personal Data, registered with the Ministry of Justice on 15 November 2023 under No. 3478 (hereinafter — the Model Procedure);
  • Resolution of the Cabinet of Ministers of the Republic of Uzbekistan No. 415 dated 29 July 2026;
  • other legislative acts.

1.3. The Policy applies to the following (hereinafter collectively — the Platform):

  • the website https://idonate.uz and its subdomains;
  • Streamers' donation pages;
  • the Streamer's Personal Dashboard;
  • widgets (overlays) for OBS and other streaming software;
  • the Operator's official Telegram bots (@idonateuzbot, @idonateuz_bot and @idonatetts_bot);
  • the Platform's application programming interfaces (API).

1.4. The Policy does not apply to third-party websites and services (for example, the payment pages of the Payment Organization and banks, YouTube, Twitch, Telegram, Google and Instagram). If you follow a link or use their services, they process your data in accordance with their own rules.

1.5. The Policy is an integral part of the iDonate platform Public Offer (https://idonate.uz/public-offer). In the event of a conflict between the Policy and the Offer on matters of personal data processing, the provisions of the Policy shall apply.

1.6. How consent is given.

  • A Streamer, when registering (on the website or in the Operator's Telegram bot), accepts the Public Offer and this Policy by ticking the corresponding box (pressing the consent button). This constitutes consent to the processing of personal data for the purposes specified in the Policy, including the cross-border transfer specified in Section 10 (Article 21 of the Law, clause 9 of the Model Procedure).
  • A Donor clicks the payment button on the donation page, next to which links to the Policy and the Public Offer are displayed. By doing so, the Donor consents to the processing necessary to make the Donation, to the public display specified in Section 8 and to the transfer specified in Section 10.
  • For a Visitor, only technical data is processed. Such processing is necessary for the operation and security of the Platform (Section 6).
  • Form and proof of consent. Consent is given in electronic form. The Operator records the date and time at which the Streamer's consent was given, the method used (website, Telegram bot or the acceptance window in the dashboard), the IP address and the version of the Policy (Article 31 of the Law).
  • Term of consent. The Streamer's consent remains valid for as long as the account exists, and the Donor's consent remains valid for the retention periods specified in Section 12. Consent may be withdrawn at any time in accordance with the procedure set out in Section 17 (clauses 10 and 11 of the Model Procedure).
  • Previously registered Streamers. From Streamers who registered before this version of the Policy entered into force, the Operator requests separate consent to this version, including to the cross-border transfer specified in Section 10 (clause 21.5).

1.7. The official text of the Policy is in the Uzbek language. Translations into other languages are provided for information purposes. In the event of any discrepancy between the texts, the Uzbek text shall prevail.


2. Information about the Operator

2.1. The owner and operator of the personal data database (hereinafter — the Operator):

  • Name: "CODO IT" Limited Liability Company
  • TIN: 311366908
  • Location (legal address): Navoiy viloyati, Navbahor tumani, Yangiqoʻrgʻon QFY, Sarbozor MFY, Davriqoʻrgʻon koʻchasi, 182-uy
  • Postal address: the same as the legal address
  • Email (including for requests concerning personal data): info@idonate.uz
  • Telegram (support): https://t.me/idonate_admin
  • Website: https://idonate.uz

2.2. The Operator has designated a person responsible for the processing and protection of personal data (Article 31 of the Law). This person may be contacted via the email address specified in clause 2.1. Write "Personal Data" in the subject line of the email.


3. Key Terms

The following terms are used in the Policy:

  • Personal data — any information relating to a specific natural person or allowing that person to be identified (Article 4 of the Law).

  • Data subject — the natural person to whom the personal data relates.

  • Processing — any action or set of actions performed with personal data: collection, systematization, storage, modification, supplementation, use, provision, dissemination, transfer, depersonalization and destruction.

  • Dissemination — disclosure of data to an indefinite range of persons. For example, displaying a donation message on a public live stream.

  • Cross-border transfer — transfer of personal data outside the territory of the Republic of Uzbekistan.

  • Depersonalization — actions that make it impossible to determine that data belongs to a specific data subject.

  • Third party (service provider) — a person who is neither the data subject nor the Operator but is involved in the processing. For example, the Payment Organization, the SMS service or the hosting provider.

  • Streamer — a person who has registered on the Platform and opened a Personal Dashboard in order to receive Donations.

  • Account holder — the natural person in whose name the account on the Platform is registered, who has passed identification and to whose settlement account payments are credited. As a rule, the account holder is the Streamer themself.

  • Channel Host — a person, other than the account holder, who actually conducts the live streams on the channel linked to the account with the account holder's consent, for example, a family member (clause 5.4).

  • Donor — a person who sends a Donation to a Streamer. The Donor does not register on the Platform.

  • Visitor — a person who opens any page of the Platform.

  • Payment Organization — a licensed organization that accepts and transfers payments. The current Payment Organization is "MULTICARD PAYMENT" Joint-Stock Company (License No. 26 of the Central Bank of the Republic of Uzbekistan dated 12.05.2021).

  • Widget — an element of the Platform that the Streamer displays on their live stream. For example, a donation notification, a goal bar, a top Donors list, a wheel or a chat.

  • Dashboard — the Streamer's Personal Dashboard on the Platform.

  • "Rahmat" service — a third-party service used by the Operator to verify, on the basis of the Streamer's PINFL and phone number, the Streamer's official surname, first name and patronymic (hereinafter — full name), self-employed status and payment details.

  • Streamer Settlement Account, Commission, Personal Dashboard, username — have the meanings given in the Public Offer. In the Policy, "service fee" means the Commission under the Offer, and "dashboard" means the Personal Dashboard.

Other terms in the Policy are used in the meanings given in the Law.


4. Processing Principles

4.1. The Operator processes personal data on the basis of the following principles:

  • lawfulness — processing is carried out only on a lawful basis;
  • purpose limitation — data is used only for the purposes announced in advance;
  • data minimization — only data in the amount necessary and sufficient for the purpose is collected;
  • accuracy — data is kept accurate and is updated where necessary;
  • storage limitation — data is stored until the purpose is achieved or for the period established by law;
  • confidentiality and security — data is protected against unauthorized access and disclosure.

4.2. The Operator does not sell personal data, does not lease it and does not provide it to third parties for advertising purposes.

4.3. If the purpose of processing changes, the Operator obtains separate consent from the data subject for the new purpose (Article 19 of the Law).


5. What Data Is Processed

5.1. All Visitors

a) Technical data. It is recorded in web server and application logs:

  • IP address;
  • browser and device type (User-Agent);
  • date and time of the request;
  • address of the page opened;
  • technical information about errors.

The logs also record notifications from the Payment Organization (which contain the payer's phone number) and login events (with the Streamer's phone number).

b) Cookies and data in browser storage (Section 13).

c) Country detection. The Operator does not determine your country by your IP address and does not send the IP address to third parties for this purpose.

d) Bot protection. A bot protection service is used on certain pages and forms of the Platform. In this case, the IP address and technical characteristics of the browser are transferred to the service provider.

5.2. Donors

a) Data you enter yourself in the donation form:

  • name or nickname. This field is optional: if it is not filled in, "Anonymous" is shown;
  • message text;
  • voice message (optional);
  • Donation amount;
  • your choice as to whether you pay the service fee yourself;
  • if the "Voice Selection" service is used, the voice and tone in which the message is read out (clause 7.10 of the Offer);
  • payment method;
  • if enabled by the Streamer, the selected meme, wheel, goal or other interactive feature.

b) Data received from the Payment Organization:

  • payment status, date and time;
  • transaction identifier;
  • payment system or method;
  • fiscal receipt link;
  • the payer's phone number. It is provided by the Payment Organization. For payments via SBP (Faster Payments System), the phone number is not received.

c) Technical data (clause 5.1) and a random code used to track the payment status. This code is used for a short period to display the payment status.

d) The payer's phone number is not shown to the Streamer. It is used only for the purposes specified in Section 6.

5.3. Streamers

a) Registration and login:

  • phone number;
  • password. It is stored only as a one-way hash; the Operator does not know the original password;
  • one-time confirmation codes (valid for a short period);
  • information about login sessions: IP address, browser type, time and the hash of the session identifier;
  • records of additional login confirmation.

b) Registration or login via Telegram. The following is obtained from the Telegram profile:

  • Telegram identifier;
  • first name, last name and username;
  • language setting.

If you share your contact with the bot, your phone number is also obtained.

c) Sign in with Google — not offered (discontinued on 18 October 2026, clause 20.2). No Google account data is obtained for logging in.

d) Data for identification and receiving payments:

  • PINFL (personal identification number of a natural person);
  • official surname, first name and patronymic;
  • status as a self-employed person;
  • number of the settlement account to which payments are credited;
  • account identifier with the Payment Organization.

This data is obtained from, or verified through, the "Rahmat" service on the basis of the PINFL and phone number (Section 7).

e) Channel and application data:

  • channel link, name, identifier and platform (YouTube, Twitch, Telegram and others);
  • channel verification code;
  • screenshots you upload;
  • public channel statistics;
  • results of the review of the application, including reasons for rejection.

f) Profile, settings and content:

  • username (nickname) and profile picture;
  • email address (if provided);
  • widget and voice settings;
  • list of banned words;
  • memes and other media files you upload;
  • wheel, lot, goal and subscription settings;
  • widget links and secret keys (tokens).

g) Financial and operational data:

  • history of Donations received: amount, date, service fee, payment method, receipt link;
  • subscription and balance top-up transactions;
  • data related to the service fee and limits.

h) Level and moderation data:

  • the Streamer's level, the history of its changes and the reasons for them;
  • identifier of the employee who made the relevant decision;
  • history of previous usernames. It is retained to prevent fake accounts from being opened in another Streamer's name;
  • account status (active, blocked, etc.).

i) YouTube widget (optional, clauses 20.11 and 20.12):

  • the links and identifiers of the YouTube channels and (if the Streamer has specified them) live streams in the widget settings;
  • YouTube access tokens are not stored.

j) Requests: messages you send to the support service and the responses given to them.

k) Instagram chat widget (optional, Section 20¹):

  • the identifiers, username, account type and follower count of the connected Instagram professional account;
  • the Instagram access token — stored only in encrypted form; it is valid for 60 days and is renewed automatically;
  • the list of granted permissions, the time of connection and of enabling the comment subscription, the time the token was last renewed and its expiry time, the time the profile was last checked, and the technical error code.

Your Instagram password is not obtained: login takes place on the Instagram page.

5.4. Channel Host (a Person Other than the Account Holder)

5.4.1. If the account holder indicates that another person (for example, a family member) uses the account to conduct live streams, the following data is processed:

  • the Channel Host's surname, first name and patronymic;
  • their kinship or other relationship with the account holder;
  • requests to change this data.

5.4.2. The account holder warrants that they obtained the Channel Host's consent before entering this data and that the Channel Host has reached 18 years of age. A minor may not be a Channel Host.

5.4.3. The Channel Host may contact the Operator directly and exercise the rights specified in Section 15.

5.5. Users of Telegram Bots

5.5.1. When you use the Operator's Telegram bots, the following is obtained:

  • Telegram identifier;
  • first name, last name and username;
  • language setting;
  • messages you send to the bot.

If you share your contact, your phone number is also obtained.

5.5.2. If the Streamer has enabled the points module, the following data of participating viewers is processed:

  • Telegram identifier;
  • name;
  • points balance;
  • materials confirming that a task has been completed.

The points module allows viewers to earn points by completing tasks set by the Streamer and to exchange them for gifts set by the Streamer. The module is not currently offered to new Streamers.

5.6. YouTube Live Chat Participants

If the Streamer has enabled the YouTube chat widget (with or without connecting a Google account), the public messages in the chat of the Streamer's current live stream are obtained through YouTube API Services:

  • the author's YouTube display name;
  • the message text (for a Super Chat or Super Sticker, also its amount);
  • the message time;
  • the author's chat badges (channel owner, moderator, member, verified);
  • if the Streamer has enabled "Profile picture", the link to the author's YouTube profile picture.

This data is used only to display the widget in the Streamer's live stream; it is not stored in the database and is not written to logs, and it is held in temporary memory (cache) for no more than 5 minutes. The author's YouTube channel identifier is not stored: it is used only to derive an irreversible short code for choosing the nickname color and for removing messages from blocked users. Messages deleted on YouTube and messages from blocked users are also removed from the widget. To remove messages deleted on YouTube from the widget and to avoid showing a message twice, an irreversible short code derived from each message's identifier is held in temporary memory for no more than 40 minutes; it contains no message text, author's name or channel identifier.

5.7. Data the Operator Does Not Collect

5.7.1. The Operator does not request and does not purposefully process the following data:

  • special categories of personal data (Article 25 of the Law): data on racial or social origin, political, religious or philosophical beliefs, membership of political parties and trade unions, physical or mental health, private life and criminal record;
  • biometric and genetic data used to identify a person;
  • copies of passports or other documents.

5.7.2. We ask that you do not include such data in a donation message or voice message.

5.8. Voice Messages

A voice message is accepted for broadcasting on the Streamer's live stream and for delivery to the Streamer (purpose 4 in clause 6.2). The Operator does not use voice messages to identify a person (biometric identification) or to create voice samples. Voice messages are stored on servers located in the territory of Uzbekistan. If the Streamer's Telegram account is linked to the Platform, the voice message may also be sent to the Streamer as an audio file via the Operator's Telegram bot (clauses 9.4 and 10.3). This copy is kept in the Streamer's Telegram chat, on Telegram's servers outside Uzbekistan, in accordance with Telegram's rules; the Operator does not control it. Voice messages are not transferred to any other foreign recipients.

If the Donor uses the "Voice Selection" service (clause 7.10 of the Offer), an audio recording of the message text is synthesized in the voice the Donor has chosen. If the Streamer's Telegram account is linked to the Platform, this audio recording may also be sent to the Streamer via the Operator's Telegram bot. This copy is likewise kept in the Streamer's Telegram chat, on Telegram's servers outside Uzbekistan, in accordance with Telegram's rules; the Operator does not control it. The audio recording on the Platform is kept for the period set in clause 12.2 for synthesized voice files (TTS).

5.9. Payment Card Data

5.9.1. Card details for a Donation or other payment are entered not on the Platform but on the page of the Payment Organization or payment system. Such details are: card number, expiry date and SMS confirmation code. They are processed by the Payment Organization in accordance with its own rules. The Operator does not store the card's CVV/CVC code.

5.9.2. The Operator does not store the full payment card number or its expiry date. The Payment Organization provides the Operator only with the payment result and the data specified in clause 5.2. Card numbers entered under the Platform's old card payment and withdrawal methods (until August 2026) are stored only in masked form (the first 6 and last 4 digits), and the card expiry dates have been deleted. CVV/CVC codes have never been stored.


5.10. AI Assistant (Support Chat)

5.10.1. In the support chat in the dashboard, the Streamer's questions are answered first by an artificial intelligence-based assistant (the AI assistant). Its use is optional: at any time, you can contact a member of the Operator's staff via the "Contact an operator" button.

5.10.2. To enable the AI assistant to prepare a response, the following is sent to the AI service provider (USA):

  • the text of the message written by the Streamer in the chat and the previous messages in the current conversation;
  • brief service data on the status of the Streamer's account: level; the amount, time and status of the last few Donations (without the Donor's name or message); whether widgets are connected; and the status of certain settings.

The phone number, PINFL, official full name, settlement account number and payment card data are not transferred to the AI assistant. Do not include your personal data in the chat.

5.10.3. The AI assistant only provides information and does not make any decisions regarding the Streamer's account (Section 19). If the Streamer writes to the Operator, the text of the request is sent to the Operator's staff via Telegram as an internal service notification.

5.10.4. Under the AI service provider's terms, data sent to it is not used to train its models and is deleted by the provider within 30 days (except where flagged as violating its usage policies). Conversations are stored on the Operator's server for the period specified in Section 12.

5.11. Instagram Live Comment Authors

If the Streamer has connected the Instagram chat widget (Section 20¹), the comments posted on the Streamer's Instagram live stream (Live) are obtained through the Meta Platforms service (Instagram API):

  • the author's Instagram username;
  • the comment text;
  • the time the comment was received;
  • the Instagram identifier of the comment.

This data is used only to display the widget in the Streamer's live stream; it is not stored in the database and is not written to logs, and it is held in temporary memory (cache) for no more than 5 minutes. Comments are retained only while the Streamer's chat widget is open in the streaming app (OBS) (that is, if it has requested data within the last 3 minutes); otherwise, an incoming comment is discarded immediately. The identifiers of the Streamer's current and last 5 live streams are held in temporary memory for as long as the widget is open, and an irreversible short fingerprint of the comment identifiers (used to skip duplicate comments) is held there for no more than 35 minutes. The author's Instagram identifier is not stored: it is used only to choose the nickname color and to determine whether the comment belongs to the Streamer themselves. The Operator does not obtain the comment author's profile picture. Meta does not send notifications about comments deleted on Instagram, so such a comment is not removed from the widget automatically; it disappears from temporary memory within 5 minutes, but it may remain on the live stream screen for the period set by the Streamer or, if no period is set (the default setting), until new comments push it out or until the widget clears the screen approximately 30 minutes after comments stop.

6.1. The Operator processes personal data on the following grounds provided for in Article 18 of the Law:

  • Contract — performance of a contract to which the data subject is a party (the Public Offer, including the Contract concluded with the Donor for each Donation), or taking steps at the data subject's request before entering into a contract.
  • Consent — the data subject's consent (Article 21 of the Law).
  • Legal obligation — performance of the Operator's obligations established by law. For example, obligations in the areas of tax, accounting, payments and information, or lawful requests from government authorities.
  • Legitimate interest — exercise of the rights and legitimate interests of the Operator or a third party, provided that the rights and legitimate interests of the data subject are not violated. For example, protection against fraud and attacks.

6.2. Purposes:

No. Purpose Data Data subjects concerned Legal ground
1 Creating an account, logging in, recovering and protecting the account Phone, password hash, confirmation codes, Telegram identifier, login sessions Streamer Contract
2 Identifying the Streamer, connecting the Streamer to payment acceptance, routing payments directly to the Streamer's account (split payment) PINFL, official full name, self-employed status, settlement account number, identifier with the Payment Organization Streamer Contract; legal obligation
3 Verifying the channel and reviewing the application, preventing fake accounts Channel data, verification code, screenshots, username history Streamer Contract; legitimate interest
4 Accepting the Donation, processing the payment and delivering it to the Streamer Name/nickname, message, voice message, amount, payment method, data received from the Payment Organization Donor Contract (the Contract concluded with the Donor)
5 Displaying the Donation on the live stream and in widgets, converting the message to speech (TTS) Name/nickname, message, voice message, amount, selected meme Donor Consent
6 Fiscal receipts, accounting and tax records Donation and payment records, the Streamer's identification data (to the extent required by law) Donor, Streamer Legal obligation
7 Calculating the Streamer's level and limits Donation statistics, number of unique payers (based on the payer's phone number) Streamer, Donor Contract; legitimate interest
8 Preventing fraud, bot attacks, abuse and unauthorized access; investigating security incidents IP address, browser data, logs, bot check result, payment data, payer's phone number All data subjects Legitimate interest; legal obligation
9 Content moderation (filtering banned words, detecting and removing unlawful content) Donation message, voice message, memes, payment monitoring data Donor, Streamer Legal obligation; legitimate interest
10 Sending service messages (confirmation codes, account status, subscription period, etc.) Phone, Telegram identifier Streamer Contract
11 Handling requests and providing support, including the AI assistant (clause 5.10) Contact details, content of the request, relevant account or payment data; conversations with the AI assistant All data subjects Contract; legal obligation; for the AI assistant — the Streamer's consent
12 Subscriptions and balance top-ups Amount, transaction identifier, account identifier Streamer Contract; legal obligation
13 Displaying YouTube widgets and channel statistics Data specified in clauses 20.11 and 20.12 Streamer, chat participants The Streamer's consent; legitimate interest (chat participants' public messages on YouTube)
14 Complying with lawful requests of government authorities and courts Data specified in the request All data subjects Legal obligation
15 Analyzing and improving service quality Only depersonalized or aggregated statistics — Article 18 of the Law (subject to depersonalization)
16 Instagram chat widget: connecting the Streamer's Instagram account and displaying live stream comments on the Streamer's live stream Data specified in clause 5.3(k) and clause 5.11 Streamer, comment authors The Streamer's separate consent (clause 20¹.2); for comment authors — legitimate interest (comments they have posted on the Streamer's public live stream)
17 Keeping backup copies to restore data if it is lost Platform data and files (voice messages are not included in the external copy) All data subjects Legitimate interest

6.3. The Operator sends advertising messages only with the data subject's separate consent. This consent may be withdrawn at any time. Service messages (row 10 of the table in clause 6.2) are not considered advertising.

6.4. The Donor may reduce the data they provide for purpose 5 (public display): leave the name field blank ("Anonymous") and not write a message text. The Platform may ask the Donor to choose one of the following: a message text, a voice message or a meme; whether they are displayed on the live stream depends on the Streamer's settings. The Donation is delivered to the Streamer in any case.


7. Sources of Data

The Operator obtains personal data from the following sources:

  1. From the data subject themself — through forms, the dashboard, bots and requests.
  2. From the "Rahmat" service (service operator — "MULTICARD PAYMENT" Joint-Stock Company). On the basis of the PINFL and phone number provided by the Streamer, the following is obtained: official full name, self-employed status, settlement account number and identifier with the Payment Organization.
  3. From the Payment Organization, "MULTICARD PAYMENT" — payment result, transaction data, the payer's phone number, fiscal receipt link.
  4. From Telegram — the data specified in clause 5.3(b) and clause 5.5 when logging in via Telegram or interacting with a bot.
  5. From Google — only when "Connect with Google" is used in the YouTube widget: the identifier and title of the YouTube channel that belongs to that Google account (clause 20.12).
  6. From the public APIs of YouTube, Twitch and Telegram — the channel's public data (name, identifier, description, statistics) for channel verification and the YouTube widget (clause 20.11), and for regularly re-checking stored YouTube channel identifiers and names (clause 20.8); for the YouTube chat widget, the public messages of the live stream chat (clause 5.6).
  7. From the account holder — data about the Channel Host (clause 5.4).
  8. From the payment service for Paid Features (once charging begins, clause 8.2 of the Offer) — the status of subscription and balance top-up transactions.
  9. From the bot protection service — the bot check result.
  10. From Meta Platforms (Instagram API) — only for the Instagram chat widget: the identifiers, username, type, follower count and access token of the Instagram professional account connected by the Streamer (clause 5.3(k)); live stream comments (clause 5.11).

8. Publicly Visible Data (Dissemination)

8.1. Donation data. Depending on the Streamer's settings, the following may be displayed or played on the Streamer's live stream and in widgets:

  • the Donor's name or nickname;
  • message text;
  • Donation amount;
  • voice message;
  • the message read out in a synthesized voice (TTS);
  • selected meme.

The live stream is broadcast to an indefinite range of viewers on YouTube, Twitch and other platforms. It may be recorded and stored by the Streamer or by those platforms.

8.2. Top Donors list and goal widgets. These may display Donors' names or nicknames and amounts.

8.3. The Streamer's public profile. The following is visible to everyone on the donation page:

  • username;
  • channel name and link;
  • profile picture;
  • goals and other information the Streamer has made public.

The Streamer's PINFL, phone number, official full name and settlement account number are not shown publicly. Where fiscal receipts are enabled, the Streamer's PINFL appears on the receipt as the principal's (komitent's) identifier in accordance with tax legislation. The receipt link is provided to the Donor and is visible in the Streamer's donation history.

8.4. Circumstances beyond the Operator's control. Once information has been displayed on a live stream, the Operator cannot control its recording and dissemination by viewers, the Streamer or other platforms. Therefore:

  • do not write personal data about yourself or other persons (phone number, address, document number, etc.) in a donation message;
  • do not record and send another person's voice without their consent.

8.5. Streamer's responsibility. The Streamer is independently responsible for displaying Donors' data on their live stream and for storing stream recordings. The Streamer must use this data only within the scope of the Platform's services.


9. Disclosure of Data to Third Parties

9.1. General rule. The Operator discloses personal data only on the following conditions:

  • for the purposes specified in this Policy;
  • only to the extent necessary for that purpose;
  • only to persons who are obliged to ensure the confidentiality of the data.

9.2. Recipients in Uzbekistan:

Recipient Purpose Data disclosed
"MULTICARD PAYMENT" — Payment Organization (License No. 26 of the Central Bank) Accepting the Donation payment, transferring the Streamer's share directly to the Streamer's account (split payment), issuing the fiscal receipt Amount, the Streamer's username, identifier with the Payment Organization and settlement account number, the Donor's name and message in the payment description; where fiscal receipts are enabled, the Streamer's PINFL (for the fiscal receipt)
Banks, payment systems and e-wallets (Uzcard, Humo, Visa, Mastercard, Payme, Click, Uzum, Paynet and others) Processing the payment The Operator does not transfer data to them. The Donor enters their data directly on their pages; they interact with the Payment Organization
"Rahmat" service ("MULTICARD PAYMENT" JSC) Identifying the Streamer, verifying self-employed status PINFL, phone number
SMS service provider (Uzbekistan) Sending confirmation codes and service SMS messages Phone number, SMS text
Data center (hosting provider) Hosting servers in the territory of Uzbekistan All data on the Platform is stored. The provider does not process it for its own purposes
Tax authorities and the fiscal data operator (via the Payment Organization) Registration of fiscal receipts Receipt details established by law

9.3. Recipients abroad are specified in Section 10.

9.4. Streamer. In their dashboard and widgets, the Streamer sees:

  • the Donor's name or nickname;
  • the Donor's message and voice message;
  • the Donation amount and date.

If the Streamer's Telegram account is linked to the Platform, this information about each Donation (together with the selected meme and, if the "Voice Selection" service is used, its audio recording) is also sent to the Streamer via the Operator's Telegram bot (clause 10.3).

The payer's phone number and payment instrument details are not provided to the Streamer.

9.5. Government authorities. The Operator discloses personal data to courts, law enforcement agencies and other competent government authorities only on the grounds and in the manner established by law. When a government authority requests data, the Operator notifies the data subject thereof (clause 18 of the Model Procedure). This does not apply where notification is prohibited or restricted by law.

9.6. Reorganization. If the Operator is reorganized or the Platform is transferred to another person, personal data passes to the legal successor in accordance with the law. The Operator notifies data subjects of this in advance. Google user data is transferred only in the manner specified in clause 20.6.

9.7. Notification. When data is disclosed to a third party, the Operator notifies the data subject within three days in writing, including in electronic form (Article 23 of the Law). With respect to the data disclosed to the recipients specified in this Policy in connection with each Donation, registration or identification, the data subject is notified in electronic form before the data is disclosed — when they are made familiar with the Policy. If data is disclosed to a third party not specified in the Policy, the Operator sends the data subject a separate notice. This does not apply where notification is not required by law (for example, when government authorities exercise their powers).


10. Cross-Border Transfer

10.1. The Platform's main database and files are stored on servers located in the territory of Uzbekistan (Section 11). Certain features work only through foreign services, and an encrypted backup copy is kept abroad for recovery purposes. For this reason, the data specified in clause 10.3 is transferred outside Uzbekistan.

10.2. Grounds for transfer (Articles 15 and 27¹ of the Law):

  • Listed states. Resolution of the Cabinet of Ministers No. 415 dated 29 July 2026 approved the list of states that ensure equivalent protection of personal data. The list includes the member states of the European Union, the United Kingdom and Switzerland. The USA is included in the list only in respect of companies operating under the EU-US Data Privacy Framework (DPF).
  • States not on the list. Transfers to such states are made only to the minimum extent necessary for a feature chosen by the data subject, and with the data subject's consent (Article 15 of the Law; clause 21 of the Model Procedure). Where the competent government authority establishes legal, organizational and technical conditions in accordance with clause 4 of Resolution No. 415, the Operator complies with them. If you do not consent to such transfer, you may use the alternatives specified in clause 10.5.
  • Data that must be stored in Uzbekistan under Article 27¹ of the Law (clause 11.2) is not transferred abroad.

10.3. Foreign recipients:

Recipient Country Purpose Data transferred Ground
Telegram Messenger Inc. (Telegram group) The Netherlands (Telegram stores the data of users registered from Uzbekistan in data centers in the Netherlands); group companies — the British Virgin Islands and the UAE 1) Login and registration via Telegram; 2) confirmation codes and service notifications to the Streamer via the Telegram bots they have connected; replies to text sent to the Telegram bot for TTS; 3) internal service notifications to the Operator's staff (monitoring of applications and payments); 4) if the Streamer's Telegram account is linked to the Platform — a notification to the Streamer about each Donation 1–2) Data you have shared on Telegram (Telegram identifier, name, username, language setting and, if you share it, phone number) and the text of the notification. 3) Internal identifiers (account, application or Donation number) and the Streamer's public username; where necessary for reviewing applications and requests — channel data, the text of the Streamer's request, the Channel Host's name and their relationship to the Streamer (clause 5.4); in payment monitoring notifications — the Donation amount, the Donor's name (nickname), message and the Streamer's channel. Phone numbers, PINFLs and settlement account numbers are sent only in masked form (the last digits); email addresses and card data are not sent. 4) The Donor's name (nickname), message, voice message, amount, selected meme and the "Voice Selection" audio recording (clause 5.8) The Netherlands is on the list; the UAE and the British Virgin Islands, where group companies are located, are not, therefore — the data subject's consent, only for the feature they have chosen (clause 10.2); for item 4 — the Donor's consent (clause 1.6). For item 3, only the minimum data necessary for review and monitoring is provided to Telegram
Speech synthesis (TTS) service provider USA Converting the donation message into a synthesized voice (TTS) Text of the donation message (after banned words have been filtered out); if the Streamer has enabled "Read the donor's name and amount" in a donation level's settings — the Donor's name (nickname) and the Donation amount; text sent to the Operator's Telegram bot for conversion to speech. The Donor's phone number and other identifiers are not transferred DPF (the provider participates in the EU-US Data Privacy Framework)
Bot protection service provider USA (global network) Protecting the Platform's forms from bots (clause 5.1(d)) IP address, technical characteristics of the browser and device DPF
Cloud backup storage provider USA Storing an encrypted backup copy of the database and of uploaded and service files (clause 11.1) Backup copy of the database, uploaded files (except voice messages) and service files (for example, copies of payment and Donation records) — in encrypted form only; the provider has no access to its contents and sees only technical attributes such as the file name, size and time DPF
Google LLC USA The YouTube widget (including "Connect with Google") and channel verification (Section 20) Data specified in Section 20; the channel's public identifier DPF
Twitch Interactive, Inc. USA Twitch channel verification The channel's public name or identifier The Streamer's consent (clause 1.6); the company does not participate in the DPF
Content delivery networks (CDN) and font services Various countries (European Union, USA) Loading the software libraries and fonts needed to display pages IP address and browser data when your browser accesses them directly Listed state / DPF
AI service provider USA AI assistant in the dashboard: preparing answers to the Streamer's questions (clause 5.10) The text of the message written by the Streamer, previous messages in the current conversation and the service data specified in clause 5.10.2. Phone number, PINFL, official full name, settlement account and card data are not transferred The Streamer's consent (clause 1.6); use of the AI assistant is optional
Meta Platforms, Inc. (Instagram) USA Instagram chat widget: "Connect with Instagram", obtaining and updating account data, receiving live stream comments (Section 20¹) Data necessary for communication with Instagram: the authorization code granted by the Streamer on the Instagram page, the access token and the identifier of the Streamer's Instagram account. Phone number, PINFL, full name, Donations and other Platform data are not transferred DPF; the Streamer's separate consent (clause 20¹.2); the feature is optional

10.4. Safeguards.

  • Only the minimum data necessary for the feature is transferred abroad. For example, the message text is sent for TTS; the Donor's phone number is not transferred. If the Streamer has enabled "Read the donor's name and amount" in a donation level's settings, the Donor's name and the amount are also sent to the TTS service for conversion to speech. The encrypted backup copy is an exception: for recovery purposes it contains the data specified in clause 11.1 in full.
  • Voice messages are transferred abroad only to deliver them to the Streamer via Telegram (clause 5.8) and are not transferred to any other foreign recipients. The "Voice Selection" audio recording (clause 5.8) is sent via Telegram only to the Telegram account of the Streamer to whom that Donation was sent. Password hashes, PINFLs, settlement account numbers and masked card numbers (clause 5.9.2) are transferred abroad only as part of the encrypted backup copy (clause 10.3). In internal service notifications sent to the Operator's staff via Telegram, phone numbers, PINFLs and settlement account numbers are shown only in masked form (the last digits).
  • Data is transferred via encrypted communication channels (HTTPS/TLS).
  • Foreign service providers process data in accordance with their own terms of use and privacy policies.

10.5. Opting out of transfer.

  • If the Donor does not want the message text to be transferred to the TTS service (abroad), the Donor may choose not to write a text, or may choose a voice message (in which case the next bullet applies) or a meme instead. In these cases, and also if the Streamer has disabled TTS, nothing is transferred to the TTS service. Exception: if the Donor has not written a text but "Read the donor's name and amount" is enabled in the donation level's settings, only the Donor's name and the amount are sent to the TTS service.
  • If the Donor does not want the voice message to be sent to the Streamer via Telegram (transferred abroad), the Donor may choose not to send a voice message.
  • If the Donor does not want an audio recording of their message to be sent to the Streamer via Telegram (transferred abroad), the Donor may choose not to use the "Voice Selection" service.
  • A Streamer may log in with a phone number and SMS code instead of logging in via Telegram, and may choose not to use the YouTube and Instagram widgets.
  • Bot protection is mandatory for the security of the Platform. The encrypted backup copy is necessary for data recovery and cannot be declined separately.

10.6. Notification of leaks. If it is discovered that data has been leaked in the course of a cross-border transfer, the Operator:

  • notifies the competent government authority thereof within 24 hours of the moment of discovery;
  • provides detailed information on the causes and the measures taken to eliminate them within 72 hours.

(Resolution of the Cabinet of Ministers No. 415 dated 29 July 2026, clause 4.)


11. Place of Storage

11.1. The Platform's database, uploaded files (voice messages, memes, screenshots, profile pictures) and logs are stored on servers located in the territory of the Republic of Uzbekistan. Synthesized voice files (TTS) are also stored on these servers. A backup copy of the database is stored on the same servers. A copy of the database, uploaded files (except voice messages) and service files encrypted using modern methods is also uploaded to a cloud backup storage provider for recovery purposes (clause 10.3).

11.2. The Operator does not process data that must be stored in Uzbekistan under Article 27¹ of the Law. Such data is biometric and genetic data and data on subscribers of telecommunications operators. Voice messages are not used for biometric identification. The Platform stores them in Uzbekistan; the copy sent to the Streamer via Telegram is kept on Telegram's servers (clause 5.8).


12. Retention Periods

12.1. General rule. Personal data is stored until the purpose of processing is achieved or until the period established by law expires (Article 10 of the Law). Once the purpose has been achieved, the data is destroyed or depersonalized within three days (clause 23 of the Model Procedure).

12.2. Periods:

Data Retention period
Account and profile data (phone, password hash, username, Telegram identifier, settings, memes) For as long as the account exists. After the account is deleted, destroyed within the period specified in Section 17
PINFL, official full name, settlement account number, identifier with the Payment Organization For as long as the account exists. Thereafter, only to the extent related to financial records, for the period established by tax and accounting legislation
Donation and payment records (amount, date, Streamer, service fee, transaction identifier, receipt link) For the period established by tax and accounting legislation (at least 5 years after the reporting year — Article 29 of the Law "On Accounting"). After the period expires, depersonalized or destroyed
Donor's name and message In the Streamer's donation history, for as long as the Streamer's account exists. At the request of the Donor or the Streamer, the name and message are depersonalized (for example, replaced with "Anonymous")
Voice messages 30 days from the date the Donation is received. After the period expires, deleted automatically. This period does not apply to the copy delivered to the Streamer via Telegram: it remains in the Streamer's Telegram chat under Telegram's rules and is not controlled by the Operator (clause 5.8)
Synthesized voice files (TTS) 30 days from the date of creation. This period does not apply to the copy of the "Voice Selection" audio recording delivered to the Streamer via Telegram: it remains in the Streamer's Telegram chat under Telegram's rules and is not controlled by the Operator (clause 5.8)
Payer's phone number and payment status tracking code 12 months. After the period expires, deleted or irreversibly hashed
Channel verification screenshots 30 days after the application has been reviewed
History of previous usernames For as long as the account exists and for 1 year after the account is deleted (the same as the period in clause 17.5 of the Offer). This is necessary to prevent another person from opening an account in the Streamer's name
PINFL and phone number of a person whose Contract was terminated under subclause "a" or "b" of clause 17.4 of the Offer One year from the date the Contract was terminated (clause 17.5 of the Offer). Used only to prevent such a person from re-registering without the Operator's consent
Confirmation codes and phone verification records Deleted automatically within 1 day after their validity expires. Deleted immediately once the account has been created
Login sessions (IP address, browser type) Deleted automatically once the session expires
Server and application logs 90 days. Web server access logs — 10 days
YouTube statistics, live stream and video data obtained through the YouTube API (except the live stream link specified by the Streamer), live chat messages Not stored in the database; held in temporary memory for no more than 5 minutes for performance (clauses 5.6 and 20.8)
Short code of YouTube live chat message identifiers (no message text, author's name or channel identifier) Not stored in the database; held in temporary memory for no more than 40 minutes (clause 5.6)
YouTube channel identifiers stored for channel verification and the YouTube widget; a profile channel link of the form youtube.com/channel/… (the channel identifier in it); a channel name obtained from YouTube that the Streamer has not changed For as long as they are needed for these features (the profile link — until the Streamer changes or removes it). Re-checked through YouTube API Services at least once every 30 days (in practice weekly) and updated; the name of a channel that has not yet been verified is not updated and is deleted or replaced no later than 30 days after it was obtained. If the channel is no longer available on YouTube, or cannot be re-checked within 30 days of the last successful check (or, if never confirmed, the first check), the identifier (and such a profile link) is deleted and a name obtained from YouTube is replaced or deleted (clause 20.8)
The live stream link and identifier specified by the Streamer in the YouTube widget (clause 20.11) Until the Streamer removes or replaces it on the widget page; deleted at the Streamer's request or when the account is deleted (clause 20.8)
Instagram connection (the data specified in clause 5.3(k), including the encrypted access token) Until the Streamer disconnects, removes the permission granted to iDonate on Instagram or requests deletion of the data. Deleted immediately upon disconnection, removal of the permission on Instagram or a request via Meta, and no later than the next business day when the account is deleted or upon a request by email. The token is valid for 60 days; if it expires or cannot be decrypted, the token is deleted, and the remaining connection data is kept for 30 days for reconnection and then deleted automatically (clause 20¹.6)
Instagram live stream comments Not stored in the database; held in temporary memory for no more than 5 minutes (clause 5.11)
Points module data Until the Streamer disables the module or until the participant so requests
Requests and responses to them 3 years after the last message
Conversations with the AI assistant (clause 5.10) The same period as for requests
Data confirming that consent was given (date, time, method, IP address, Policy version) For as long as the consent is valid and thereafter for the limitation period for disputes established by law (Article 31 of the Law)
Backup copies Database: on the server — 7 days; encrypted external copy (cloud backup storage) — 30 days. Uploaded files (except voice messages) and service files: the encrypted external copy is kept while the file is on the server and is destroyed within 30 days after the file is deleted or replaced. These periods also apply to backup copies of data deleted under clause 12.1, the other rows of this table and clause 17.3: until they expire such copies are kept for recovery purposes only, and when they expire the copies disappear

12.3. Statutory retention. Data that the law requires to be retained is retained for the period established by law even if consent is withdrawn or the account is deleted. Examples of such data are tax and accounting documents. During that period, the data is not used for any other purposes (Article 18 of the Law).


13. Cookies and Browser Storage

13.1. The Platform uses only cookies and browser storage that are necessary for its operation. Advertising, web analytics or third-party tracking cookies are not used.

13.2. Cookies:

Name Purpose Duration
Session cookie Maintaining the logged-in state Expires after a period of inactivity. For the Platform only
Security cookie Protection against cross-site request forgery (CSRF) For the duration of the session
"Remember me" cookie "Remember me" function; login via Telegram 30 days
Registration cookie Managing the registration process 90 days
Service cookie Maintaining the logged-in state of authorized users 14 days

13.3. Browser storage (localStorage, sessionStorage). For convenience, the following is stored on your device:

  • the last name, amount, payment method and service fee choice entered in the donation form (the message text is not stored);
  • the status of an incomplete payment;
  • dashboard interface settings (for example, the open tab, the state of the side panel).

This data is not sent to the Operator's server and remains only in your browser. Card data is not stored in browser storage; if pages of a previous version have saved it, it is deleted when the donation page is opened.

13.4. Third-party technical tools. The bot protection service and the external resources specified in clause 10.3 may use their own technical tools in accordance with their own rules.

13.5. Deleting cookies. You can delete cookies and browser storage in your browser settings. If necessary cookies are deleted, login and certain features will not work.


14. Security Measures

14.1. The Operator takes legal, organizational and technical measures to protect personal data against unauthorized access, modification, destruction, copying and dissemination (Article 27 of the Law). In particular:

  • Communication with the Platform is carried out via the encrypted HTTPS (TLS) protocol.
  • Passwords are stored only in the form of a one-way cryptographic hash.
  • YouTube access tokens are not stored: the token obtained through "Connect with Google" is used once and immediately revoked (clause 20.12).
  • The Instagram access token is stored in the database only in encrypted form, is used only for communication with Instagram and is not written to logs. The authenticity of messages received from Instagram (webhooks) is verified by means of Meta's signature.
  • Confirmation codes are randomly generated and valid for a short period. The number of attempts to send and enter a code is limited.
  • The number of requests is limited, and tools for protection against automated attacks are used.
  • Login via Telegram is protected by additional confirmation and other technical measures.
  • The authenticity of notifications received from the Payment Organization is verified by means of cryptographic checks and other technical measures.
  • The PINFL and official full name are protected from modification after identification. The PINFL is shown in masked form in the dashboard.
  • Access to administrative tools is granted only to authorized employees, each through a personal account and within the scope of their duties. For certain important administrative actions, it is recorded who performed them. Access to other service tools is likewise granted only to authorized persons and is protected by technical measures.
  • Voice message files on the Platform are stored with protection against unauthorized access and are deleted after 30 days (Section 12). The copy sent to the Streamer via Telegram is described in clause 5.8.
  • The Operator's employees use personal data only within the scope of their job duties and undertake not to disclose it (Article 12 of the Law).
  • Secret keys and access credentials are renewed when necessary.

14.2. No method of transmission over the Internet or of electronic storage is absolutely secure. The Operator continuously improves its protective measures.

14.3. Incident response. If the Operator discovers a breach of personal data security, it:

  • takes measures to eliminate the breach and mitigate its consequences;
  • notifies the competent government authorities in the cases provided for by law (clause 10.6);
  • where there is a serious risk to the rights and interests of data subjects, notifies them as soon as possible and gives recommendations on how to protect themselves.

14.4. Your part:

  • do not give your password or confirmation codes to anyone. The Operator's employees will never ask for a code by phone or by message;
  • keep widget links and keys secret. If they are disclosed, renew them in the dashboard;
  • log out when you finish working on shared devices;
  • if you suspect unauthorized access to your account, immediately notify us at the address specified in clause 2.1.

15. Rights of the Data Subject

15.1. In accordance with Articles 11, 17, 21, 22, 24 and 30 of the Law, every data subject has the following rights:

  1. To know whether data exists. To know whether the Operator holds personal data about them and what that data consists of.
  2. To receive information about processing (Article 22 of the Law):
    • the fact, grounds and purposes of processing;
    • the methods of processing;
    • the composition and source of the data;
    • to whom the data has been disclosed;
    • retention periods;
    • cross-border transfer.
  3. Rectification and supplementation. To demand that incomplete, outdated or inaccurate data be changed and supplemented.
  4. Temporary suspension. To demand that processing be temporarily suspended if the data is incomplete, outdated, inaccurate, unlawfully obtained or not necessary for the purpose.
  5. Destruction. To demand the destruction of data in the cases provided for by law.
  6. Withdrawal of consent (Section 17).
  7. Objection to an automated decision (Section 19).
  8. Complaint. If they consider that their rights have been violated, to apply to the competent government authority in the field of personal data (Article 8 of the Law) or to a court.

15.2. The rights of a data subject who lacks legal capacity or is a minor are exercised by their legal representative.

15.3. Where it would violate the rights and legitimate interests of other persons, the provision of information to a data subject may be restricted in accordance with the law (Article 22 of the Law).

15.4. Data subject's obligation. The data subject must provide the Operator with accurate information about themselves and update it in a timely manner when it changes.


16. Procedure for Requests and Response Times

16.1. Ways to submit a request:

  • via the email address specified in clause 2.1. Subject: "Personal Data";
  • by a written application sent to the postal address specified in clause 2.1;
  • via the support chat in the dashboard (the "Contact an operator" button).

The Operator accepts requests to stop processing and to destroy data in electronic form (Article 31 of the Law).

16.2. Content of the request. The request should include:

  • your name;
  • your contact details for receiving a response;
  • the substance of your request;
  • the details necessary to find the data about you. For a Streamer — username or phone number. For a Donor — the date of the Donation, the Streamer, the amount and the phone number used for the payment.

16.3. Identity verification. To prevent the disclosure of another person's data, the Operator may ask the applicant to verify their identity. For example, a code may be sent to the registered phone number or to Telegram. Only the minimum data necessary for this purpose is requested.

16.4. Requests are handled free of charge.

16.5. Response times:

Request Period Basis
Receiving information about processing Within 10 days. If the provision of information is refused, a reasoned written notice is also sent within 10 days Article 22 of the Law (for the notice of refusal); the rest — the Operator's own commitment
Changing or supplementing data Within 3 days from the moment the request is received. If the data is found to be untrue — immediately Article 11 of the Law; clause 15 of the Model Procedure
Withdrawal of consent Processing is stopped. The data is destroyed no later than the business day following the day the application is received (except in the cases referred to in clause 12.3) Clause 10 of the Model Procedure
Destruction of unlawfully processed data Within 1 business day Clause 24 of the Model Procedure
Destruction upon achievement of the purpose of processing Within 3 days Article 17 of the Law; clause 23 of the Model Procedure
Temporary suspension Immediately after a justified request is confirmed, and in any event within 3 days Article 30 of the Law (the period is the Operator's own commitment)
Review of an objection to an automated decision Within 10 days; the result is communicated in writing Article 24 of the Law

These periods apply to live systems; data in backup copies disappears when the period specified in clause 12.2 expires.

16.6. Notification of the outcome. When data is changed or destroyed, or its use is restricted, the Operator notifies the data subject in writing, including in electronic form. Where necessary, the Operator also notifies the other participants in the processing (Article 31 of the Law).


17.1. Withdrawal of consent. A data subject may withdraw consent at any time. To do so, they submit a written (electronic) request in the same form in which the consent was given or in the manner specified in clause 16.1 (Article 21 of the Law).

Withdrawal of consent does not affect processing lawfully carried out before the withdrawal.

17.2. Consequences. If consent to the processing of data necessary to use the Platform is withdrawn, the Operator cannot provide the relevant services. For example:

  • the Streamer's ability to receive Donations is terminated and the account is closed.

17.3. Account deletion. A Streamer may request deletion of their account. To do so, the Streamer submits a request in the manner specified in clause 16.1. After identity has been verified:

  • access to the account is blocked immediately;
  • the following data is destroyed or irreversibly depersonalized no later than the next business day:
    • phone number (except in the case specified in clause 17.4) and password hash;
    • Telegram link;
    • profile picture, email address, settings, memes and widgets;
    • Instagram connection, including the access token (Section 20¹);
    • channel verification materials;
    • identification data, except for the part specified in clause 17.4;
  • Donors' names, messages and voice messages in the donation history are deleted or depersonalized; the last paragraph of clause 17.5 applies to copies already sent to the Streamer via Telegram.

17.4. Data retained after deletion. Even after the account is deleted, the following is retained:

  • Donation and payment records that the law requires to be retained for tax and accounting purposes. They are retained only for the period established by law and only for that purpose;
  • data related to a case under consideration at the request of a court or government authority, or to an unresolved dispute. Such data is retained until the case or dispute is concluded;
  • the history of previous usernames, for the period specified in clause 12.2;
  • the PINFL and phone number of a person whose Contract was terminated under subclause "a" or "b" of clause 17.4 of the Offer — solely to prevent re-registration, for the period specified in clause 17.5 of the Offer.
  • data and files in backup copies — solely for recovery purposes, in encrypted form, until the period specified in clause 12.2 expires.

17.5. Donor's request. A Donor may request the following with respect to their Donation:

  • depersonalization of the name and message;
  • deletion of the voice message;
  • deletion of the phone number.

The financial record (amount, date, transaction) is retained in accordance with clause 17.4. The Operator cannot delete data that has already been shown on a live stream from recordings made by the Streamer or by third parties (clause 8.4). The Operator may be unable to delete copies of Donation data, of the voice message and of the "Voice Selection" audio recording already sent to the Streamer via Telegram (clauses 5.8 and 9.4) from the Streamer's Telegram chat.

17.6. Parents of a minor. A parent or legal representative of a minor may request deletion of the minor's data in the same manner.


18. Minors

18.1. Streamers and Channel Hosts. Registration on the Platform as a Streamer and acting as a Channel Host are permitted only from the age of 18. A person under 18 may not use the Platform as a Streamer or Channel Host, including through the account of a parent or legal representative.

18.2. Data collected without parental consent. The Operator does not separately verify age. If the Operator discovers that a minor's data has been collected without parental consent, the Operator stops processing it. At the request of the parent or legal representative, the data is destroyed within the periods specified in clause 16.5. This does not apply to data that the law requires to be retained.


19. Automated Processing and Decisions

19.1. Rules applied automatically. The following are applied automatically in order to perform the terms of the Public Offer (Article 24 of the Law):

  • Donation limits are determined depending on the Streamer's level and the payment method, and the service fee depending on the Streamer's level and the terms of connection with the Payment Organization. The exact values are shown on the Platform, in the dashboard and on the donation page before payment;
  • technical security restrictions (request rate limits, bot checks) are temporary and do not give rise to legal consequences;
  • the answers of the AI assistant in the dashboard (clause 5.10) are for information purposes only and do not give rise to legal consequences.

19.2. Decisions reviewed by an employee. The following decisions are not made solely by automated means. They are reviewed by an authorized employee of the Operator:

  • raising a Streamer's level (after the established conditions have been met);
  • rejecting a registration application;
  • blocking an account;
  • other decisions having legal consequences.

19.3. Objection. A data subject may object to a decision based solely on automated processing. The Operator reviews the objection and notifies the data subject of the outcome in writing within 10 days.


20. Google User Data (YouTube Widget)

20.1. Scope. This Section applies to data that the Platform receives through Google API services ("Google user data") and to public data that it receives through YouTube API Services. This data is received through the following features:

  • the YouTube widget, used without connecting a Google account (clause 20.11; no Google user data is received, only public data);
  • "Connect with Google" in the YouTube widget (clause 20.12; the token is not stored).

Both features are optional. You log in to the Platform with a phone number or via Telegram; the previously available "Sign in with Google" and "Connect with YouTube" features have been discontinued (clause 20.2). In addition, when a channel is verified and the verified channel's data is updated (clause 5.3(e)), only the channel's public data is received through YouTube API Services using an API key (item 6 of Section 7); no Google user data is received in this case. The Operator does not post, modify or delete anything on YouTube on the Streamer's behalf.

20.2. Discontinued features: "Sign in with Google" and "Connect with YouTube". These features (the Google openid, email, profile and youtube.readonly permissions; access and refresh tokens were stored in encrypted form) were discontinued on 18 October 2026. The Google account identifiers and the access and refresh tokens stored for them were deleted on the same day; before deletion, a request to revoke the tokens was sent to Google. The Operator no longer receives your Google account identifier, email address, name or profile picture. Channel links (youtube.com/channel/…) established to have been written through "Connect with YouTube" were also removed from profiles on 21 October 2026. The former Google sign-up in the mobile app (April 2024 to 28 September 2026; it also requested the youtube and yt-analytics.readonly permissions) also wrote a channel link of the form youtube.com/channel/…. Such links whose source has not been established are re-checked as described in clause 20.8.

The Operator does not receive your Google account password, contacts, emails, files or other Google data.

20.3. (Not applicable: "Sign in with Google" has been discontinued — clause 20.2.)

20.4. (Not applicable: "Connect with YouTube" in the dashboard has been discontinued — clause 20.2. For the YouTube widget, see clauses 20.11 and 20.12.)

20.5. YouTube and Google terms. By using the Platform's YouTube features, you agree to the YouTube Terms of Service: https://www.youtube.com/t/terms. Google processes data in accordance with its own Privacy Policy: http://www.google.com/policies/privacy.

20.6. Limited Use.

iDonate's use and transfer to any other app of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements.

(In other words: iDonate's use of information received from Google APIs, and its transfer of such information to any other app, will comply with the requirements of the Google API Services User Data Policy, including the Limited Use requirements.)

In particular, Google user data:

  • is used only to provide and improve user-facing features that are visible to, and used by, the user;
  • is not sold;
  • is not used for advertising, including personalized or targeted advertising;
  • is not used to determine creditworthiness or for lending purposes;
  • is not provided to data brokers or information resellers;
  • is not used to develop, improve or train generalized artificial intelligence or machine learning models;
  • is transferred to third parties only in the following cases:
    • where necessary to provide or improve a feature that you use and that is visible on the Platform, and only with your consent;
    • for security purposes;
    • to comply with applicable law;
    • in the event of a reorganization of the Operator (merger, acquisition), or a sale of its shares or assets — with your explicit prior consent.

The Operator's employees read Google user data only in the following cases:

  • with your explicit consent (for example, to review your request);
  • for security purposes (for example, to investigate abuse);
  • to comply with applicable law;
  • where the data is used in depersonalized, aggregated form for internal operations.

20.7. Place of storage. Google user data is stored on the Operator's servers in Uzbekistan. YouTube live chat messages are not stored in the database.

20.8. Retention periods:

  • Access and refresh tokens are not stored: the token obtained through "Connect with Google" is used once and immediately revoked (clause 20.12). The Google account identifier, email address and profile data are not obtained.
  • YouTube data (statistics, live stream and video data) is not stored in the database: it is retrieved through the YouTube API when a widget is opened and is held in temporary memory (cache) for no more than 5 minutes for performance. The short code of live chat message identifiers is held for no more than 40 minutes (clause 5.6).
  • YouTube channel identifiers stored for channel verification and the YouTube widget (the verified channel and the widget's channels), and a channel name obtained from YouTube, are retained only for as long as they are needed for these features. They are re-checked through YouTube API Services at least once every 30 days (in practice weekly) and updated: if the channel's name changes on YouTube, the channel name on the donation page is updated too. A channel name that the Streamer entered or changed, or that the Operator changed, is neither updated nor deleted. If the channel is no longer available on YouTube, or cannot be re-checked within 30 days of the last successful check, the channel identifier is deleted (the channel is also removed from the widget settings) and a channel name obtained from YouTube is replaced with the channel handle entered by the Streamer or, if there is none, with the Streamer's username on the Platform. This does not affect the channel's verified status. The identifier in a profile channel link of the form youtube.com/channel/… is re-checked in the same way: if the channel no longer exists on YouTube or cannot be re-checked within 30 days, the link is removed from the profile (and the donation page); the Streamer may enter it again in the profile settings. The name of a channel that has not yet been verified is not re-checked or updated: no later than 30 days after it was obtained from YouTube it is deleted (in an active account, replaced in the same way). The "Connected with Google" mark in the widget is kept for no more than 30 days (clause 20.12).
  • At your request or when the account is deleted, the YouTube channel data in the widget settings is deleted no later than the next business day; the Streamer may also delete it themselves on the widget page at any time.

20.9. Revoking permission and deleting data. The token obtained through "Connect with Google" is revoked immediately, so the Operator does not retain ongoing access to your Google account. Nevertheless, at any time you may:

20.10. Changes. If the Operator intends to change the way it uses Google user data, it will notify you in advance and ask for your consent to the new use.

20.11. YouTube widget (without connecting a Google account). The Streamer may use the "YouTube" widget in the dashboard without connecting a Google account. In this case no Google user data is requested: the Operator obtains only public data through YouTube API Services (YouTube Data API):

  • the identifiers of the YouTube channels (up to 5) verified or specified by the Streamer;
  • the identifiers of those channels' current live streams, their public like counts and the number of viewers currently watching them (the public figure shown by YouTube);
  • if the Streamer has enabled the chat widget, the public messages in that live stream's chat (clause 5.6).

The channel links and identifiers (and the live stream link and identifier, if the Streamer specified one) are stored in the widget settings; the Streamer may delete them on the widget page at any time. Channel identifiers are re-checked through YouTube API Services at least once every 30 days. If a channel is no longer available on YouTube or cannot be re-checked within 30 days, it is removed from the widget settings and its identifier is deleted (clause 20.8); the Streamer may add the channel again. Statistics are not stored in the database: they are requested only while the widget is open in the streaming app (OBS) or when the Streamer saves a link on the widget page, and are kept in temporary memory (cache) for no more than 5 minutes. Chat messages are obtained only while the chat widget is open in the streaming app (OBS) and are not stored in the database. This data is used only to display the widget enabled by the Streamer. The YouTube Terms of Service and the Google Privacy Policy referred to in clause 20.5 also apply to this feature.

20.12. YouTube widget — "Connect with Google". The Streamer may connect a channel on the YouTube widget page with the "Connect with Google" button. In this case Google requests only the youtube.readonly (read-only) permission; signing in with Google is not enabled and the Google account email address is not requested. The Operator uses the obtained token once to get the identifier and title of the YouTube channel that belongs to that Google account and then immediately revokes the token — the token is not stored. The channel identifier is stored in the widget settings; the Streamer may delete it on the widget page at any time. It is re-checked in the same way as other channel identifiers, through YouTube API Services and without a token (clause 20.8). The "Connected with Google" mark next to the channel is kept for no more than 30 days; after that the channel remains in the widget as a channel added by link. The channel title is shown only in the confirmation message and is not stored. The widget statistics are obtained as described in clause 20.11.


20¹. Meta and Instagram Data (Instagram Chat Widget)

20¹.1. Scope. This Section applies to the Instagram chat widget, which the Streamer enables on a voluntary basis. The widget displays the comments from the Streamer's Instagram live stream (Live) in the streaming app (OBS). The feature works through the "Instagram API with Instagram Login" service of Meta Platforms, Inc. Only a professional (Business or Creator) Instagram account can be connected; a Facebook Page is not required. The Operator does not post, modify or delete anything on Instagram on the Streamer's behalf (except for enabling the subscription to comment notifications for iDonate when connecting and disabling it when disconnecting), does not reply to comments and does not hide them.

20¹.2. Connection and consent. The Streamer clicks the "Connect with Instagram" button in the dashboard, logs in to their account on the Instagram page and grants permission to iDonate. The Instagram password is not provided to the Operator. A consent text and a link to the Policy are displayed next to the button; connecting constitutes the Streamer's separate consent to the processing specified in this Section and to the exchange of data with Meta (clause 10.3). This consent is recorded in accordance with clause 1.6 (method — "Connect with Instagram") and is kept for the period specified in clause 12.2; the consent record is not deleted even when the connection is removed. Consent may be withdrawn at any time by the methods specified in clause 20¹.7.

20¹.3. Permissions requested:

  • instagram_business_basic — reading the account's identifier, username, type and follower count;
  • instagram_business_manage_comments — receiving live stream comments through Meta notifications (webhooks). This permission is not used to delete or hide comments or to reply to them.

No other permissions (content publishing, direct messages, statistics) are requested.

20¹.4. Data obtained and stored.

  • About the Streamer: the data specified in clause 5.3(k). While the widget is available to the Streamer and the token is valid, the username, account type and follower count are updated from Instagram once a day. The access token is stored only in encrypted form and is used only for communication with Instagram.
  • About comment authors: the data specified in clause 5.11. It is not stored in the database and is held in temporary memory for no more than 5 minutes.
  • Instagram does not provide viewer counts or likes (hearts); the Operator does not obtain them.

20¹.5. Purpose of use and restrictions. Data obtained from Instagram is used only to display the Instagram chat widget enabled by the Streamer and to show the connection status in the dashboard. Such data:

  • is not sold and is not leased;
  • is not used for advertising or profiling and is not provided to data brokers;
  • is not used to train artificial intelligence or machine learning models;
  • is not used for surveillance, discrimination or making decisions about an individual (credit, employment, insurance, housing and the like);
  • is not provided to third parties, except for: service providers that store it on the Operator's behalf (the data center — clause 9.2; the encrypted backup copy — the cloud backup storage provider, clause 10.3), and where required by law or for security purposes — to the minimum extent necessary. The comment author's username and the comment text are displayed in the widget on the Streamer's live stream (clause 5.11).

20¹.6. Place of storage and retention periods. Instagram connection data is stored on the Operator's servers in Uzbekistan; an encrypted backup copy of the database is also held by the cloud backup storage provider (clause 11.1). It is deleted in the following cases:

  • the Streamer clicks the "Disconnect" button in the dashboard — immediately;
  • the Streamer removes the permission granted to iDonate in the Instagram settings — Meta sends a notification to the Operator and the data is deleted automatically and immediately;
  • a data deletion request is received via Meta (clause 20¹.7) — immediately;
  • Instagram revokes the access token (for example, if the Streamer changes their Instagram password) — if the widget is available to the Streamer, the Operator detects this during the daily check and deletes the connection; if the widget has been made unavailable, the token is not used and the connection is deleted as described below (after the token expires);
  • the account is deleted (clause 17.3) or deletion is requested via the email address specified in clause 2.1 — no later than the next business day.

The access token is valid for 60 days and is renewed automatically for as long as the Streamer is able to use the widget. If the widget is made unavailable to the Streamer, the token is not renewed. If the token expires or cannot be decrypted, the token is deleted during the daily check; the remaining connection data is kept for 30 days so that the Streamer can reconnect and is then deleted automatically. Deleted data disappears from backup copies within the period specified in clause 12.2.

20¹.7. Revoking permission and deleting data. At any time, the Streamer may:

  • click the "Disconnect" button on the Instagram widget page in the dashboard (https://idonate.uz/instagram-vidjet). The Operator then immediately deletes the connection data and, if the access token is still valid, sends Instagram a request to stop sending comments; after that, comments from this account are not accepted and are discarded immediately. Even if the Instagram widget has been made unavailable to the Streamer, the "Disconnect" button is shown on this page for as long as the connection remains;
  • remove the permission granted to iDonate in the Settings and activity → Website permissions → Apps and websites section of the Instagram app;
  • send a data deletion request via Meta. Once the request has been fulfilled, a confirmation code and a link to a status check page are provided (https://idonate.uz/instagram/ochirish/…). No personal data is shown on this page;
  • submit a request via the email address specified in clause 2.1.

20¹.8. Meta terms. When the Instagram chat widget is used, the Instagram Terms of Use (https://help.instagram.com/581066165581870) and the Meta Privacy Policy (https://privacycenter.instagram.com/policy) also apply. Meta processes data in accordance with its own rules.

20¹.9. Changes. If the Operator intends to change the composition of the data obtained from Instagram or the purpose for which it is used, it will notify the Streamer in advance and request their new consent (clauses 21.3 and 21.5).


21. Amendments to the Policy

21.1. The Operator may amend the Policy in the following cases:

  • when legislation changes;
  • when the Platform's features or service providers change;
  • for other justified reasons.

21.2. Publication. A new version of the Policy is published on the Platform together with its effective date and version number. Previous versions are kept in an archive on the Platform and are provided upon request.

21.3. Material changes. Streamers are notified of material changes via the Personal Dashboard and the Telegram bot or SMS at least 30 calendar days before they take effect. Material changes include:

  • new purposes or new categories of data;
  • new foreign recipients;
  • extension of retention periods.

The addition of a new optional feature that the Streamer enables themselves does not require 30 days' notice if the related processing and cross-border transfer begin only with the separate consent that the Streamer gives in accordance with clause 21.5 when enabling the feature (for example, clause 20¹.2). The description of such a feature is included in the Policy before the feature is offered and is published in accordance with clause 21.2, indicating the date of the amendment.

When the purpose of processing changes, the Operator obtains new consent from the data subject (Article 19 of the Law).

21.4. Disagreement with a new version. A data subject who does not agree to a new version may withdraw consent and delete their account in accordance with Section 17.

21.5. Separate consent. For processing for a new purpose or for transfer to a new foreign recipient, the Operator obtains separate consent; continued use of the Platform does not constitute such consent. Streamers who registered before this version entered into force are shown this version when they first log in to the dashboard, and their consent is requested. Until consent is given, the Operator processes their data only to the extent necessary to perform the Public Offer and its legal obligations (Articles 18 and 19 of the Law).


22. Final Provisions and Contact Details

22.1. The Policy is governed by and interpreted in accordance with the legislation of the Republic of Uzbekistan. Disputes relating to personal data are resolved in the manner established by law (Article 32 of the Law). This does not limit the data subject's right to apply directly to the competent government authority or to a court.

22.2. If any provision of the Policy is held to be invalid, this does not affect the validity of its remaining provisions.

22.3. Contact details:

  • "CODO IT" LLC, TIN 311366908
  • Address: Navoiy viloyati, Navbahor tumani, Yangiqoʻrgʻon QFY, Sarbozor MFY, Davriqoʻrgʻon koʻchasi, 182-uy
  • Email: info@idonate.uz
  • Telegram (support): https://t.me/idonate_admin

© "CODO IT" MChJ · idonate.uz