Summary. This page explains how Sign In With Uvio works on company websites and apps.
Key points:
- When you sign in through Uvio, the company receives only your Uvio ID, email address, first name, and last name if it is present in your account.
- Passwords, subscription history, location data, push tokens, and similar data are not transferred by default.
- Before you enter the code, check what data the company says it will receive and why. That should be disclosed in the company's interface.
- If you do not agree with the company's terms or disclosures, do not complete the code-entry flow.
This short summary is for convenience only. The full text below is legally controlling.
1. What Sign In With Uvio Is
1.1. This page explains the scenario in which a user confirms sign-in or registration on a company's external site or app by entering a one-time code sent through Uvio.
1.2. The purpose of this page is to let the user understand in advance what data may be transferred to the company after successful code verification and what documents should be reviewed before continuing.
1.3. This page supplements the Uvio Consumer Terms of Service, the Uvio Consumer Privacy Policy, and the Uvio Business Sign In With Uvio Rules. It does not replace the notice that the company must present in its own interface before the code is entered.
2. When This Scenario Applies
2.1. This scenario applies when a user voluntarily chooses sign-in or registration through Uvio on a company's external site or app and confirms that action with a one-time code.
2.2. After successful verification of the one-time code, Uvio may transfer to the company a limited set of user data needed to create, link, or confirm the user's account on the company's side and to create a user session there.
3. What Data May Be Transferred to the Company
3.1. As of the version date of this page, after successful one-time-code verification the following data may be transferred to the company:
- the user's unique Uvio identifier;
- the user's email address;
- the user's first name;
- the user's last name, if it is provided in the Uvio account.
3.2. The exact set of transferred data should be disclosed to the user in the company's interface before the code is entered.
4. What Data Is Not Transferred by Default
4.1. By default, Sign In With Uvio does not transfer:
- the user's Uvio sign-in name;
- the user's password or other authentication secrets;
- Uvio session tokens;
- subscription history, location data, push tokens, or advertising preferences;
- other data that is not necessary for sign-in, registration, or session creation on the company's side.
5. For What Purposes the Company May Use This Data
5.1. Unless the company separately discloses another use and has its own lawful basis for it, data received through Sign In With Uvio should be used only for sign-in, registration, creation or linking of the user's account, and creation of a user session on the company's side.
5.2. If the company wants to use the data for additional purposes not directly connected to sign-in, registration, session creation, or account maintenance, the company must have its own lawful basis for that further processing under applicable law.
5.3. Where that additional use requires user consent under applicable law, the consent must be requested separately from the general Sign In With Uvio notice, separately from the company's terms, and separately from other documents accepted by the user.
6. Automatic Subscription to the Company
6.1. In some Sign In With Uvio scenarios, the product logic may provide for automatic creation or reactivation of the user's subscription to the relevant company after successful one-time-code verification.
6.2. If that logic applies, the company must disclose it clearly in advance in its own interface before the code is entered.
6.3. After a subscription is created or reactivated, the user may manage it through Uvio, including unsubscribing where that function is available.
7. What to Check Before Entering the Code
7.1. Before entering the one-time code, the user should review:
- the company's privacy policy or privacy notice;
- the company's user terms, if they apply to the relevant site or app;
- the Uvio Consumer Terms of Service and Uvio Consumer Privacy Policy.
7.2. If the user does not agree with the transfer of data to the company, the company's documents, or the disclosed subscription logic, the user should not complete the Sign In With Uvio flow.
8. Who Is Responsible for the Processing
8.1. Uvio is responsible for processing data within its own interfaces, infrastructure, and one-time-code verification mechanism.
8.2. After the company receives the data on its own side, the company independently determines the conditions of its further processing for the company's own purposes and bears its own responsibility under applicable law.
9. Controller Information and Contacts
The personal data controller and the person providing services under the name "Uvio" is an individual entrepreneur Sultanbekov Artur Timerhanovich.
INN (Tax ID): 021101196690.
OGRNIP (Registration No.): 318028000111955.
Privacy inquiries: privacy@uvio.chat.
Legal inquiries: legal@uvio.chat.