Osobné dáta


Rovas is run by a NeoFund s.r.o.. In this document, this organization will be referred to as we.

Personal data

Data we collect

Rovas can be used by anonymous and registered users. Anonymous users have only limited and read-only access to the project pages. To gain access to all Rovas functions, users must register in the application by choosing their user name and supplying a valid email address and country of residence. Users may also select their preferred language for the Rovas interface in their user profile.

If the user plans to use the forex functionality, they must also provide their bank account number or PayPal email address.

How the data is used

The user data we collect is used exclusively to allow users to use the application. In particular, user names are used to identify user-generated content, email addresses are used to send messages to users, the country of residence is used to filter relevant content, and the language setting allows us to display the interface in the selected language. The optional bank account and PayPal email addresses are used only for sending payments to the users.

With the exception of the user name, all collected personal information is private. We do not use any information provided by users for any purposes other than those explicitly stated here or in the Rovas rules.

Deleting user data

Users can permanently delete their account and all associated personal data at any time by logging into their user profile at:

https://rovas.app/user/

After logging in, the user can initiate account deletion from the Edit profile tab. Once the deletion is confirmed, the user account and all related personal data (including email address, country, language settings, and payment identifiers) are permanently removed from our systems without undue delay. All user public user content is assigned to the Anonymous user. This action is irreversible.

Cookies

This portal uses cookies to support the following functionality:

  1. To enhance user experience, including the ability to store login information, which allows users to repeatedly visit the portal without the need to authenticate every time.
  2. To keep track of what content a user visited, in order to avoid showing the same information repeatedly.