Privacy Policy

This Privacy Policy (the “Policy”) explains which personal data is processed when the Mated service is used, why and on what basis, to whom it is transferred, how long it is kept, how it is protected and how it can be deleted. The Mated service (the “Service”) includes the mated.one website, the workspace, the Mated app for iOS and the chat widget that users install on their websites. By using the Service, you confirm that you have read the Policy and consent to the processing of your personal data on its terms. If you do not agree with the Policy, do not use the Service.

The Policy has been drawn up in accordance with the legislation of the Republic of Uzbekistan, including the Law of the Republic of Uzbekistan “On Personal Data” No. ZRU-547, the Law of the Republic of Uzbekistan “On Electronic Commerce” and the Civil Code of the Republic of Uzbekistan. The Policy applies together with the Public Offer under which the Service is provided.

The Policy has been drawn up in Russian. The Uzbek and English texts of the Policy are translations; in the event of any discrepancy between the texts, the Russian text prevails.

1. The Operator and its details

The owner and operator of the personal data of Users and website visitors (the “Operator”, “we”) is the individual entrepreneur who provides the Service and is the Executor under the Public Offer. The Operator determines the purposes and procedure for processing this data that are described in the Policy. The Operator processes the personal data of Customers of the User on the User’s instructions in the manner set out in Section 11.

YaTT (individual entrepreneur) XASANOV SHAXZOD RUSTAM O‘G‘LI
PINFL (STIR, taxpayer number): 52211056450050
State registration certificate No. 7402538 of 8 January 2026
Address: 18/60 Feruza Street, Feruza mahalla, Ulugbek town, Mirzo-Ulugbek district, Tashkent, Uzbekistan
Settlement account: 20218000507020046001
Bank: JSCB “Kapital bank” (АКБ «Капитал банк»)
MFO (bank code): 01158
Phone: +998 20 005 22 11
E-mail: [email protected]
Support on Telegram: @xasanov49

The following terms are used in the Policy:

“personal data” means any information relating to an identified or identifiable natural person (the personal data subject);
“processing” means any action or set of actions performed with personal data, whether or not by automated means: collection, systematization, storage, modification, supplementing, use, provision, dissemination, transfer, depersonalization and destruction;
“User” means a person who has registered an account in the Service and accepted the Public Offer;
“employees of the User” means persons to whom the User has given access to the User’s account; the provisions of the Policy on the User’s data also apply to the data of the User’s employees;
“Customers of the User” means persons who write to the User through the channels connected to the Service and the chat widget, or who submit a Facebook lead ad form on the User’s page, as well as event participants whom the User has uploaded to the Service from the Unicore integration or added manually.

2. What data we process

2.1. Account data

first name and, if you have provided it, last name;
mobile phone number — it serves as your login for signing in;
password — stored only as an irreversible hash (Section 7);
email address — if you have provided it;
profile photo — if you have uploaded one;
interface language and notification settings, including the identifiers of the Telegram chats to which you have asked for notifications to be sent;
the selected plan, its validity period, the remaining AI answers, the remaining monetary balance (if any), the history of payments and of balance changes made by the Service administrator;
information you enter to set up the AI agent: instructions, knowledge base, files and their descriptions, reply templates;
information about linked accounts, if you have linked several of your accounts in order to switch between them;
communications with support — by email, via Telegram or by phone.

2.2. Data from connected channels, the widget and integrations

When you connect an Instagram or Facebook page, a Telegram bot, your Telegram account via Telegram Business, or the chat widget on your website to the Service, the Service receives and processes the data of Customers of the User on your instructions:

incoming and outgoing messages: text, photos, videos, voice messages, files, stickers, locations and contacts, shared posts, replies to your stories and mentions of you in stories;
comments on Instagram posts;
the profile data of the other party to the conversation that the platform transmits: name, username, profile photo, identifier;
if the “gift for following” feature is enabled in Instagram — information on whether the other party follows your account, as well as the number of their followers and the verification mark, which Instagram transmits together with this information;
the name, phone number and other information that the other party has themselves provided in the conversation; the AI agent extracts this information into a lead;
leads from Facebook lead ad forms, if your Facebook page is connected to the Service: name, phone number, email address, answers to the form questions, name of the ad or campaign;
leads: name, phone number, email address, deal amount, stage, notes and brief summaries of inquiries;
message metadata: time, channel, language, the ad from which the other party came (if the platform transmits it);
for the chat widget — a random visitor identifier (Section 10.3);
access tokens for the connected channels — the keys that Meta and Telegram issue for working on behalf of your page or bot.

When you connect via Telegram Business, the Service also receives the name, username, photo and identifier of your Telegram account and processes the conversations in those private chats to which you have given the chatbot access in the Telegram settings.

The Service converts voice messages into text using OpenAI (Section 5).

If you keep a list of event participants in the Service, the Service stores information about them: name, phone number, email address, ticket type, payment status and amount, registration date. If the Unicore integration is connected, the Service receives this information from your Unicore account on your instructions, together with Unicore’s full response for the ticket. You can also add participants manually and enter information about them: Telegram, organization, position, city, country, participation status, responsible employee, comment. For the integration, the Service stores the credentials for your Unicore account (login and password or access token) in their original form, because it uses them for requests to Unicore.

With respect to the data of Customers of the User, the Operator acts on the User’s instructions (Section 11).

2.3. Payment data

Plans and additional AI answers are paid for through the Uzum Checkout service with Uzcard, Humo, Visa and Mastercard bank cards, with confirmation under the 3-D Secure protocol. You enter your card details on the Uzum payment page; the Operator neither receives nor stores them. To issue an invoice, we transmit to Uzum the internal account identifier, the invoice number, the amount and purpose of the payment, as well as information about the seller and the service for the fiscal receipt. We do not transmit the payer’s name, phone number or email address to Uzum. From Uzum, we receive and store the order number and the amount, status and date of the payment.

This data is used to activate the plan, record payments, consider refund requests, and for accounting and tax records.

2.4. Technical data

the IP address of the device — the server receives it with every request and uses it to limit the request rate and protect the Service against abuse; the IP address may be recorded in the technical logs of the server and of Cloudflare;
information about the browser and operating system (the user-agent string) — saved together with the trusted device record;
information about sign-in sessions and trusted devices: when they were created and until when they are valid;
the device token for push notifications — if you use the Mated app for iOS;
error log entries: time, type of error, account or channel identifier;
visit statistics of the mated.one website — described below.

Website visit counter. When a page is viewed, the mated.one website sends the following to the Service’s server: a random browser identifier, a random browser tab identifier, the page address without parameters, the page language and the device type (phone or computer). With the first view in a tab, it also sends the address of the website you came from (without the path and parameters), the utm_source, utm_medium and utm_campaign tags, whether this is the first visit to the website from this browser, and the page load time. When you click the links for sign-up, sign-in, prices, contacts, articles, Telegram, phone or e-mail, the same identifiers, page language and device type, the name of that action and the address of the page where it happened are sent; if the link is clicked before the first page in the tab has finished loading, the first-view details are attached to the click as well. The browser identifier is stored in localStorage under the key mated_vid until the browser is cleared and is needed to tell new visitors from returning ones; the tab identifier is stored in sessionStorage under the key mated_sid and deleted when the tab is closed. No cookies are used for this; no name, contact details or IP address are saved in the visit record, and the identifiers are not linked to an account. If Do Not Track or Global Privacy Control is enabled in the browser, the counter sends nothing.

2.5. Reviews on the website

Reviews from Mated’s clients may be published on the mated.one website: the author’s name, position and company, photo and the text of the review. Reviews are posted by the Operator. The author of a review may ask for it to be changed or removed using the contacts in Section 13.

3. Legal grounds for processing

We process personal data on the grounds provided for by the Law of the Republic of Uzbekistan “On Personal Data” No. ZRU-547:

your consent — you give it when registering in the Service (this is stated on the registration page), as well as when connecting channels and integrations;
performance of the contract with you (the Public Offer) — without processing account, channel and payment data, the Service cannot be provided; this also covers the security and anti-fraud measures provided for by Section 13 of the Public Offer;
performance of the obligations imposed on the Operator by the legislation of the Republic of Uzbekistan: tax and accounting records, personal data protection, responses to lawful requests from government authorities.

The Operator processes the data of Customers of the User on the User’s instructions; the User is responsible for ensuring a lawful basis for processing it (Section 11).

You may withdraw your consent at any time by writing to us using the contacts in Section 13. Withdrawal of consent does not affect the lawfulness of processing carried out before it. After consent is withdrawn, the Service may become fully or partially unavailable.

4. Purposes of processing

registration, sign-in and account management, including confirmation of sign-in with an SMS code;
operation of the Service: receiving and sending messages in the connected channels, AI agent answers, setting up the AI agent based on your past conversations (training mode), converting voice messages into text, extracting leads and receiving leads from lead forms, maintaining the CRM and lists of event participants, notifications about leads, conversations, AI agent answers and payments;
accepting payments, activating the plan, recording payments, considering refund requests, accounting and tax records;
responding to support requests;
security of the Service, protection against abuse and fraud;
diagnosing and fixing faults in the Service;
performance of obligations established by law, including responses to lawful requests from government authorities;
website traffic measurement and Service usage statistics in aggregated form;
publishing reviews from Mated’s clients on the website;
service messages: confirmation codes, notifications about the operation of the Service, about payments and about changes to documents.

We do not send advertising mailings. We use the data of Customers of the User only to provide services to the User.

5. To whom we transfer data

We do not sell personal data and do not transfer it for advertising purposes. Data is received only by the persons listed below and only to the extent necessary for the relevant feature to work. Each of them processes the data on the terms of its own agreements and policies.

Uzum Bank (the Uzum Checkout service) — accepting card payments: internal account identifier, invoice number, amount and purpose of the payment, information for the fiscal receipt. You enter your card details directly on the Uzum page.
Eskiz — sending SMS messages with confirmation codes: phone number and the text of the SMS with the code. For numbers outside Uzbekistan, the SMS is delivered via international telecom operators.
OpenAI — AI agent answers, lead extraction, brief summaries of inquiries, the agent’s training mode and converting voice messages into text: your instructions for the agent, the knowledge base and file descriptions, data from the setup wizard and the sandbox, the latest messages of the conversation (in training mode — up to 200 conversations together with your employees’ replies), voice messages of Customers of the User as audio files. Images are not transferred to OpenAI.
Meta Platforms (Instagram, Facebook) — operation of the connected pages: incoming and outgoing messages and comments, files that the Service sends on your behalf. From Meta, the Service receives the profile data of the other parties to conversations, leads from lead forms and access tokens for your pages.
Telegram — operation of the connected Telegram bot and of the account connected via Telegram Business (messages pass through the Telegram Bot API), and notifications: the Mated bot @helpmated_bot sends to the Telegram chats you have specified — depending on your settings — notifications about new leads, about conversations awaiting a reply from an employee, about AI agent answers and about payments. Notifications may contain the name, username, profile link and phone number of a Customer of the User, the text of their message, the agent’s answer, a summary of the inquiry, and the amount and method of payment. Communications with support at @xasanov49 also go through Telegram.
Apple — push notifications in the Mated app for iOS: the device token and the notification text, which may contain the name and phone number of a Customer of the User, the channel, a summary of the inquiry or the beginning of the message from the Customer of the User, and payment information.
Cloudflare — the network through which all requests to the Service’s server pass: from the workspace, the app and the chat widget, as well as incoming notifications from Meta, Telegram, Uzum and Eskiz (they contain the texts of messages from Customers of the User and phone numbers) and files that Meta fetches for sending. In transmitting them, Cloudflare processes the content of these requests and IP addresses.
Unicore — only if you have connected this integration: the Service transmits your credentials to Unicore in order to obtain information about participants from your account.
The provider of the email service through which the [email protected] address operates — the emails you send us and our replies.
Government authorities — in the cases and in the manner provided for by the legislation of the Republic of Uzbekistan.

Cross-border transfer. OpenAI, Meta, Telegram, Cloudflare and Apple are foreign companies. The data transferred to them is processed on their servers, including outside the Republic of Uzbekistan, i.e. it is transferred across borders. Cross-border transfer is also possible in other cases: when an SMS is sent to a number registered outside Uzbekistan (the number and the text of the SMS with the code are transferred to foreign telecom operators for delivery), and if the servers of other recipients listed in this section — Unicore and the email service provider — are located outside the Republic of Uzbekistan. Without such transfer, the core features of the Service do not work: AI answers, the Instagram, Facebook and Telegram channels, push notifications. By registering in the Service, connecting channels and using these features, you consent to such transfer. A User who connects channels is responsible for having a lawful basis for transferring the data of Customers of the User to these companies (Section 11).

6. Retention periods

We collect only the data needed for the Service to work. The following retention periods currently apply:

account data, settings, conversations, leads and the CRM, lists of event participants, AI agent settings, the knowledge base and files — for as long as the account exists. Disconnecting a channel does not delete its history: conversations and leads remain in the account and become available again if the same channel is reconnected. They are completely deleted together with the account (Section 9);
files from conversations (photos, videos, voice messages, documents) — stored on the Service’s server until the account is deleted;
SMS confirmation codes — only in the server’s RAM, for 10 minutes;
records of sign-in sessions and trusted devices — until the account is deleted; all of them are deleted when the password is reset;
push notification tokens — until you sign out of the account in the app or until Apple reports that the token is invalid, but no longer than the account exists;
the access token of a disconnected Instagram or Facebook channel — deleted when Meta confirms that notifications for this channel have been turned off; until such confirmation is received, the token is kept for a retry and is not used to send messages;
records of payments and of balance changes made by the administrator — for no less than the period established by tax and accounting legislation, including after the account is deleted (without being linked to it);
the Service’s error log — 14 days;
the log of incoming notifications from Meta (copies of notifications, including the text of messages and comments, as well as notifications that Meta sends for a channel that has already been disconnected) — kept for diagnostics; a period for its automatic cleanup has not yet been set;
the server’s system logs (may contain a phone number, fragments of incoming messages and service information about payments) — kept for diagnostics and security purposes; the Operator has not yet set a retention period for them;
website visit statistics — without a time limit; the records do not contain a name, contact details or IP address;
reviews on the website — until the Operator deletes them, including at the author’s request;
communications with support — for as long as necessary to respond to the inquiry and resolve any possible dispute;
database backups — created every night (Section 7); data deleted from the Service remains in the backups already created until those backups are deleted.

Data for which a retention period is specified is deleted or depersonalized when that period expires. If an automatic deletion period has not yet been set, you can send us a deletion request using the contacts in Section 13.

7. How we protect data

We apply legal, organizational and technical measures to protect personal data against unlawful or accidental access, modification, blocking, copying, dissemination and destruction. The following measures currently apply:

Encryption in transit. The website, the workspace, the app and the widget exchange data with the Service’s server over HTTPS. The Service exchanges data with Meta, Telegram, OpenAI, Uzum, Eskiz and Apple over HTTPS through their official application programming interfaces (APIs).
Passwords. Mated account passwords are stored only as irreversible hashes (the scrypt and bcrypt algorithms with a random “salt”). The Service does not store the Mated account password itself and has no way of learning it. The credentials for the Unicore integration are stored in their original form, because the Service uses them for requests to Unicore (Section 2.2).
Sign-in. Sign-in is performed with a phone number and password. On a new device, a six-digit SMS code is additionally required: it is valid for 10 minutes and is cancelled after 5 incorrect attempts; the number of codes and sign-in attempts is limited. After the code is entered, the browser or device is considered trusted for 180 days. Resetting the password with an SMS code ends all sessions and revokes all trusted devices of the account.
Sign-in cookies. The session and trusted device cookies are inaccessible to page scripts (HttpOnly) and are transmitted only over HTTPS. The server stores the trusted device key only as a hash.
Data separation. The data of each account is isolated: requests are executed in the context of a specific account, and one User cannot obtain another User’s data, except where you have linked your own accounts in order to switch between them.
Administrative access. The admin panel is accessible only from a private network (VPN) and requires a separate sign-in: a login, a password and a one-time TOTP code from an authenticator app. A session in the panel lasts no more than 12 hours. The Service administrator sees account data in the panel and uses this access for support, troubleshooting and security. If the administrator opens a User’s workspace for support purposes, such access is limited to 2 hours and each such instance is recorded in the server log. Only a limited number of persons authorized by the Operator have access to the server and the database.
Payment data. Card details are entered on the Uzum Checkout page and confirmed by the bank under the 3-D Secure protocol; they do not reach the Service’s servers.
Backups. Since 25 September 2026, the database has been backed up every night. The backups are encrypted with a key that is kept only by the Operator, outside the server. Restoration of the latest backup is automatically tested every week. Files from conversations (photos, videos, voice messages, documents) are not included in the backups.

No method of transmitting and storing data provides absolute protection. If you notice a sign-in to your account that you did not make, reset your password immediately (this will end all sessions) and notify us using the contacts in Section 13. Report any vulnerabilities you find in accordance with the rules in Section 12.

8. Your rights

In accordance with the Law of the Republic of Uzbekistan “On Personal Data” No. ZRU-547, you have, in particular, the right to:

know whether the Operator and third parties hold your personal data and which data exactly;
receive information about the processing of your data: the purposes, methods and sources of collection, the composition of the data, retention periods, and to whom it is transferred;
demand the correction, supplementing, blocking or destruction of your data if it is incomplete, outdated, inaccurate, unlawfully obtained or not necessary for the purpose of processing;
withdraw your consent to processing;
appeal against the Operator’s actions to the authorized government body or to a court and defend your rights, including claiming compensation for damage in court.

To exercise your rights, write or call using the contacts in Section 13 and state the phone number to which the account is linked. We may request information confirming that the request was sent by the account owner. We respond to requests within the time limits established by law.

9. Deleting your account and data

You may delete your account and the data associated with it at any time:

in the Mated app for iOS: the “Profile” section → “Delete account”. The account is deleted immediately after confirmation;
on request: write to [email protected] or to @xasanov49 on Telegram, or call +998 20 005 22 11, and state the phone number to which the account is linked. Once we have verified that the request was sent by the account owner, we will delete the data within 30 calendar days.

If you want a refund for the unused period or of the remaining monetary balance, submit a refund request before deleting the account — the procedure is set out in Section 6 of the Public Offer.

When an account is deleted, the following are deleted: account data, connected channels (for Instagram and Facebook, the Service also asks Meta to stop sending notifications), conversations and files from them, leads, AI agent settings and their files, the chat widget, information about the connected Telegram bot, notification settings, push notification tokens, sign-in sessions and trusted devices, links to other accounts, the Unicore integration settings and the list of event participants.

If you connected your own Telegram bot, it remains in your Telegram account — you can delete it via @BotFather. If you connected your account via Telegram Business, disconnect the chatbot in Telegram: Settings → Telegram Business → Chatbots. The Service does not process messages that Telegram sends after the account is deleted.

After the account is deleted, the following are retained:

records of payments and of balance changes made by the administrator — without being linked to the account, for no less than the period established by tax and accounting legislation;
error log entries — for up to 14 days, and server system log entries, including the record of the account deletion with the account identifier and phone number — for the periods specified in Section 6;
data in database backups — until those backups are deleted;
records that are not yet deleted together with the account: the log of incoming notifications from Meta — it retains copies of incoming messages and comments from Instagram and Facebook, including their text; information about message attachments (type, file name or caption, source link, coordinates of shared locations, voice message transcription text — up to 500 characters); reply templates. You can send us a request for their deletion using the contacts in Section 13;
data that had already been transferred to the recipients listed in Section 5 before the account was deleted (for example, conversations that remain in Instagram, Facebook and Telegram, payment information held by Uzum) — with those recipients, on the terms of their rules.

Account deletion is irreversible: the account and data cannot be restored, and access to the Service ends.

Disconnecting a channel in the Service, as well as removing the Mated app in the Facebook or Instagram settings, does not delete data in the Service. To delete it, delete the account in one of the ways specified above.

If the Operator has suspended or terminated access to the Service on the grounds set out in Section 12 of the Public Offer, the data is kept for the periods specified in Section 6 for as long as the account exists. You may require the deletion of the account and data by sending a request as described above.

Cookies are small files that a website saves in the browser. The browser’s local storage (localStorage — kept until you clear it) and session storage (sessionStorage — cleared when the tab is closed) work in a similar way. This section lists both.

10.1. The mated.one website

The public pages of the website do not set their own cookies and do not load third-party analytics or advertising systems or third-party fonts. Only the following is saved in the browser:

mated.lang (localStorage) — the website language (ru, en or uz), so that the sign-in pages open in the right language; kept until the browser is cleared;
mated-motion (localStorage) — your choice made with the “Pause animations” button; saved when you press this button and kept until the browser is cleared;
mated_vid (localStorage) — a random browser identifier for the visit counter, to tell new visitors from returning ones (Section 2.4); kept until the browser is cleared;
mated_sid (sessionStorage) — a random tab identifier for the visit counter (Section 2.4); deleted when the tab is closed.

10.2. The workspace and the app

The workspace uses two necessary cookies that are set by the Service’s server:

mated_session — confirms that you are signed in to your account; valid for 90 days after sign-in (for an internal sign-in by the Service administrator — from 2 to 12 hours);
mated_device — set after sign-in or registration is confirmed with an SMS code, and marks the browser as a trusted device so that the code is not requested at every sign-in; valid for 180 days.

Both cookies are inaccessible to page scripts (HttpOnly) and are transmitted only to the Service’s server and only over HTTPS. The Mated app for iOS uses the same cookies and stores them on the device. In addition, the workspace stores interface settings in your browser’s localStorage and sessionStorage: language, simplified mode, hidden tips and completed onboarding, filters in the conversations section. These records are needed only for the interface to work.

The workspace does not load third-party web analytics services or advertising counters.

10.3. The chat widget on Users’ websites

The Mated chat widget on a User’s website does not use cookies. It stores in that website’s localStorage the entry mated_wv_<widget identifier> — a random visitor identifier issued by the Service’s server in order to continue the conversation with the same visitor. The entry is kept until the browser is cleared. With each message, the widget sends the server the message text, up to the 10 most recent messages of the conversation and this identifier. The Service’s server does not save the visitor’s IP address in the database and uses it to limit the request rate; the address may be recorded in the technical logs of the server and of Cloudflare (Section 2.4).

10.4. Third-party pages

The Uzum Checkout payment page, as well as the Meta and Telegram pages that open when channels are connected, operate under their owners’ rules and may set their own cookies. We do not control them.

10.5. How to manage cookies

Necessary cookies are used for the operation and security of the Service and do not require separate consent. You can view and delete cookies and site data in your browser settings:

Google Chrome: Settings → Privacy and security → Cookies and other site data;
Mozilla Firefox: Settings → Privacy & Security → Cookies and Site Data;
Safari: Settings → Privacy → Manage Website Data;
Microsoft Edge: Settings → Cookies and site permissions.

If you block the mated_session and mated_device cookies, you will not be able to sign in to the workspace.

11. Data of Customers of the User

The owner of the personal data of Customers of the User is the User: the User determines why and on what basis this data is processed. The Operator processes this data on the User’s instructions and only to provide services to the User. The User undertakes to:

have a lawful basis for processing the data of Customers of the User, including by obtaining the Customers’ consent where it is required, in particular consent to the transfer of the data to the recipients listed in Section 5 and to its cross-border transfer;
inform Customers of the User about the processing of their data, including its transfer to the recipients listed in Section 5, and respect the Customers’ rights;
use the Service in accordance with the law and the rules of the connected platforms.

The User gives the instruction to process data by accepting the Public Offer and connecting channels and integrations. In carrying out this instruction, the Operator:

processes the data of Customers of the User only to provide services to the User and does not use it for its own purposes;
transfers it only to the recipients listed in Section 5 and only for the operation of the relevant features;
protects it with the measures set out in Section 7;
deletes it when the account is deleted, in the manner and with the exceptions set out in Section 9.

For questions about the processing of their data, a Customer of the User should first contact the User — the company with which they corresponded. It is currently not possible to delete the conversation or lead of an individual Customer of the User in the workspace (the User can remove an event participant from the list themselves). To fulfil a request from a Customer of the User to delete their data, the User sends us a request using the contacts in Section 13, specifying the channel and the other party to the conversation; we delete this data within 30 calendar days. If a Customer of the User contacts us directly, we will inform the User of their request and help the User fulfil it.

12. Reporting a vulnerability

If you have found a vulnerability in the Service, report it to [email protected] before public disclosure so that we have time to fix it. Please:

describe the problem, the steps to reproduce it and the possible consequences;
do not exploit the vulnerability to cause harm: do not obtain, modify or delete other people’s data and do not disrupt the operation of the Service;
give us reasonable time to fix it before publishing the details.

We strive to acknowledge receipt of reports and to keep you informed of the progress of the fix. We will not take legal action in respect of good-faith research carried out in accordance with these rules.

13. Changes to the Policy and contacts

We may change the Policy. The current version is always published on this page, and its date is shown at the top of the page. Changes take effect upon publication, unless otherwise specified in the new version. We may additionally notify you of material changes in the workspace or via the contacts specified in the account. Continued use of the Service after the changes take effect constitutes acceptance of the new version.

For questions about the processing of personal data, to exercise your rights and to delete data, contact the Operator:

E-mail: [email protected]
Support on Telegram: @xasanov49
Phone: +998 20 005 22 11
The Operator’s address and details are in Section 1.

Current document: mated.one/privacy/