This website uses its own and third-party cookies to personalize content and ads, provide social media functions and analyze site traffic. Also, our social media, advertising and statistical analysis partners may have information about your use of the site, and they may combine it with other information you have provided or they have collected from you, when you use the services offered by them.
This information is intended to show you how cookies work on this site and how you can configure these cookies.
What is a cookie?
A cookie is a text file that web pages place on your device and stored on it, such as your personal computer, mobile phone, tablet, etc. These files are used to store information about user visits, such as language preferences, cookies used to detect attempts to log in to a site that have repeatedly failed, and other options, while helping to set the settings for subsequent visits and to make the site more useful by personalizing its content. Cookies play a very important role in improving the experience of using this site.
Other tracking technologies
Tracking pixels are used to collect information about website usage and conversion rate tracking for your marketing campaigns.
For a better understanding of this type of technology, we inform you that pixels are snippets of code that are inserted into the source code of the page and allow us to measure, optimize and create audiences for our advertising campaigns.
In this sense, by using the Facebook Pixel Code solution we have access to statistical information regarding the access to the site. This solution also allows processing that involves providing the content relevant to you. As regards the processing carried out through this solution, given the quality of associated operators, your consent is offered to both operators. As for us, you give us your consent by checking the data processing for statistical analysis purposes (thus, within our Facebook page we will have access to aggregate and statistical information on the source of the accesses). Displaying relevant content, including Facebook and Instagram, will be a processing by them on their own behalf, which you may object to by refusing to receive ads (Hide this ad).
The purpose of Game World's use of the data provided by Facebook Pixel Code is to analyze the marketing campaigns carried out by the company, through the ads promoted on Facebook.
Types of data that Facebook gets access to via Pixel Code: IP addresses, information about the web browser, the location of the page, the document, the source and the person using the website, the buttons that the site visitors clicked, the labels of the respective buttons and all the pages visited as a result of the button presses, the date and time the minute the ad is accessed.
As for the Hotjar solution, you should keep in mind that this partner provides users with an opt-out button, which can be accessed here.
The express consent of the processing purposes, allows the installation of cookies on your device to transmit the following information:
- Accessing the website, viewing the content and registering for the campaign.
- Statistical information regarding the use of the website.
- Preferred web format for access to mobile devices.
- The latest searches from web services as well as personalized details of these services.
- Providing personalized content considering the activity on the site.
Types of cookies used
This website uses session cookies and permanent cookies. Session cookies retain data only for as long as the user is in the open browser, while permanent cookies are stored on the user's device so that they can be accessed and used in more than one session.
Depending on the purpose and the data obtained through cookies, we can use:
- Cookies strictly necessary or functional
These cookies are necessary for the operation of our site. They allow you to use the main features of our site (example: viewing the content of the pages, recording the preference to display the results) and usually appear as a result of a user's express request (for example, filling in the form, choosing a language for use). Without these cookies, you will not be able to use our site normally. These are cookies placed by Game World Romania, or on our behalf of third parties and refer only to the operation of our site.
|Mygameworld. Used to store the user's option regarding cookies that he wants placed on his device, when accessing the site.
|Mygameworld. Used to store confirmation regarding age over 18 years. In the field of gambling, operators have an obligation to ensure that users are over the age of 18
- Performance cookies
These cookies allow a site to remember information that changes the way the site behaves or looks, such as your preferred language or region.
- Advertising cookies
These cookies can be set on our site by our advertising partners. These can be used by the respective companies to create a profile based on the user's interests and to display relevant advertisements for it on other sites. They do not directly store personal information, but are based on the unique identification of the browser and device used to access the site. If you do not allow these cookies to be placed, it does not mean that you will no longer receive ads, but that the advertisements that will be provided to you will be less personalized.
You should know that accessing our partners' pages will lead to the processing of your data by them, on their own behalf, and they should inform you. To remove any doubt, accepting marketing cookies does not mean that you give Game World access to data that identifies the person who has a Facebook account and who accessed the page following a Facebook ad.
Regarding the use of the data provided by Facebook, given the impossibility of reducing the storage time on users' devices, Game World will take into account the recently collected data, considered necessary and sufficient for the smooth running of the marketing campaigns.
|Google Analytics. Contains information about user interaction with a campaign.
|Facebook. Used to remember if the user chose to stay logged in to Facebook. It serves the purpose set by Facebook.
|xs and c_user
|Used for user authentication. It serves the purpose set by Facebook.
|Facebook. Used for user authentication on Facebook in the mobile version. It serves the purpose set by Facebook.
|Facebook. Used to remember that a device or browser was logged into the Facebook platform. It serves the purpose set by Facebook.
|Facebook. Used to enable device-based connections. It serves the purpose set by Facebook
|Facebook. Used to determine the state of the user accessing accountkit.com. It serves the purpose set by Facebook.
|Facebook. Identify the used using the Account Kit. It serves the purpose set by Facebook.
|Facebook. Optimizes recovery flow after failed login attempts. It serves the purpose set by Facebook.
|Facebook. Stores the encryption key used to encrypt cookies. Purpose of processing stated by Facebook (ensuring the integrity of the site and its products)
|Facebook. Used to indicate the date of the last password entry. Purpose of processing stated by Facebook (ensuring the integrity of the site and its products)
|Facebook. Identifies the browser used to ensure site integrity and security, including recovering your Facebook account and identifying compromised Facebook user accounts.
|Facebook. Identifies the browser for Facebook account authentication.
|Facebook. Used to deliver, measure and improve the relevance of the advertisements.
|Facebook. Used to retain the user's choice regarding opposition to receiving advertisements. The purpose of the processing (stated by Facebook) is to provide advertisements.
|Facebook. Used to open a specific location in the ad agency application. The purpose of the processing (stated by Facebook) is to provide advertisements.
|Facebook. Used for delivery, measure and improve the relevance of the advertisements. The purpose of the processing (stated by Facebook) is to provide advertisements
|Facebook. Used to identify the browser used to provide advertising and analysis services.
|Facebook. Provides an optimal user experience for the user's screen. The purpose of processing (stated by Facebook) is to provide the Facebook experience.
|Facebook. Allows for payment, updating the shopping cart and viewing the shopping cart. The purpose of processing (stated by Facebook) is to provide the Facebook experience.
|Facebook. Used to improve the user experience for devices used by multiple people. The purpose of processing (stated by Facebook) is to provide the Facebook experience.
|Facebook. Used to identify the country and choose the language according to the last browser used to log in to Facebook.
|Facebook. Used to improve friends' suggestions on Facebook. The purpose of processing (stated by Facebook) is to provide the Facebook experience.
|Used to allow Facebook to remember the products that the user wants to buy. The purpose of processing (stated by Facebook) is to provide the Facebook experience. session
wd Facebook. Provides an optimal user experience for the user's screen.
|Facebook. Provides an optimal user experience for the user's screen.
|Facebook. Stores the age of Facebook java scripts. The purpose of the processing (declared by Facebook) is the performance of its page.
|Facebook. Used to improve site performance for advertisers. The purpose of the processing (declared by Facebook) is the performance of its page.
|Facebook. Stores the URL of the person who joined Facebook following an ad promoting Facebook. The purpose of the processing (stated by Facebook) is for statistical analysis.
- Cookies for statistical analysis
These cookies allow us to count visits and traffic sources, so that we can measure and improve the performance of our site. It helps us to know which pages are the least popular and to see how visitors move on the site. The information that these cookies collect is aggregated and therefore anonymous. However, using the Hotjar script will allow you to assign a unique user number, called ID, that will associate each page access with this ID. The statistical data obtained through the Hotjar script can be used to identify problems encountered by users (without identifying them) and to take the necessary measures to solve them.
If you do not allow these cookies to be placed, we will not know when you visited our site. Below you will find examples of such cookies.
|Google Analytics. Cookie used to distinguish between unique users by randomly assigning a customer ID
|Google Analytics. Cookie used to distinguish between users when using pages 24 hours.
|Google Analytics. Cookie used to slow down data collection in case of high traffic. If you use Google Tag Manager, this cookie will be called _dc_gtm_ <property-id>
|For Google Analytics to determine that two separate hits belong to the same user, a unique identifier is associated with that user, and each access will be associated with that customer ID. The unique identifier is a randomly generated character string.
|30 seconds – 1 year
|2 years from creation / update
|Google Analytics. Cookie used to slow down data collection in case of high traffic.
|30 minutes after placement / update
|Not used for ga.js. It was used for operability with urchin.js. Historically, this cookie was used in conjunction with _utmbcookie to determine whether the user's visit to the page was new or not.
|End of session. Close browser.
|Google Analytics. Stores the source of the traffic or campaign through which the user reached the site. It is loaded with the page code.
|6 months after placement / update
|Google Analytics. Stores the value of the variables personalized at the user level.
|Google Analytics. Used to include a user in an experiment.
|Google Analytics. Used to set an expiration of the user's inclusion in an experiment.
|Google Optimize. Used to determine the inclusion of a user in an experiment and the expiration of the experiments in which a user was included.
|Maximum 90 days
|Google Optimize. Used for campaigns mapped to Google Ads customer IDs.
|Google Optimize. Used for campaigns mapped to Google Ads campaign IDs.
|Google Optimize. Used for campaigns mapped to Google Ads group IDs.
|Google Optimize. Used for campaigns mapped to Google Ads group IDs.
|Google Optimize. Stores the last query parameter utm_campaign.
|This cookie is placed as soon as a user of the page interacts with an invitation to a poll. The purpose is for the same poll to no longer appear to a visitor who closed the window.
|Hotjar. This cookie is placed as soon as a user of the page has already completed a survey using the Feedback Poll widget. It is used to ensure that the same survey will not appear again if it has already been completed.
|Hotjar. This cookie is placed as soon as a user minimizes the poll window. Note the minimization action when browsing the site.
|Hotjar. Cookie placed in case the user has filled in the information in the user recruitment widget for testing. It is used to ensure that the same form does not reappear to the user who has already completed it.
|Hotjar. Cookie placed to users who minimize the participation form. It is used to stop maximizing the form while browsing the site.
|Hotjar. This cookie allows Hotjar to determine if the user has been included in the sample for generating statistical analysis.
|Hotjar. Cookie placed when the user minimizes / completes the feedback form. This cookie allows the display of the feedback window to be minimized on the other pages.
|Cookie Hotjar. This cookie is placed when the user first accesses the page that has the Hotjar script. It is used for the unique identification of the user by randomly assigning an ID. The purpose is to ensure that subsequent behavior, from the same ID through a subsequent visit, will appear for that ID.
|Hotjar. This cookie is placed when the user visits a Hotjar page that allows the selection of a language, in order to store this option and to display the page in the language selected by the user.
|Hotjar. Cookie that allows access to the page.
|New Relic. Session monitoring cookie.
|New Relic. Cookie that is placed only for browsers that do not support Navigation Timing API.
|New Relic. A cookie that is placed when a token is assigned to a user.
How cookies are managed on your browser
The user has the possibility to allow, block or delete the cookies installed in his system by changing the options settings of the browser installed in his device:
- To change cookie settings on Google Chrome:
- Click on the menu in the toolbar.
- Select Settings.
- Click Show advanced settings.
- In the privacy section, click on the content settings.
- Under Cookies there are a number of settings options.
More information about Google Chrome https://support.google.com/chrome/answer/95647?hl=en
- To change cookie settings on Mozilla Firefox:
- At the top of the window, click on the Firefox button.
- Select the options.
- Select the privacy panel.
- In the Firefox option select use custom settings for history and you can choose from different options.
You can find more information about Mozilla Firefox at: https://support.mozilla.org/en/kb/cookies
- To change the cookie settings on Microsoft Edge:
- At the top of the Microsoft Edge window, click the Tools menu.
- Select Settings, then Security and then the Cookies option and choose the cookie placement option (out of the three available).
IAB has built the following website to provide specific information on privacy issues related to Internet advertising: http://www.youronlinechoices.com/en/.
If you have any questions or questions regarding the Cookies policy, please write to firstname.lastname@example.org.