Cookie Policy

1.1. This Cookie Policy regulates how we, BOHEMIA INTERACTIVE a.s., ID No: 272 18 864, having its registered office at Stříbrná Lhota 747, Mníšek pod Brdy 252 10 (“We”) use cookies, how We handle them and how you, user of our websites (“You”) can adjust Your settings regarding the cookies. It also regulates how We process Your personal data in connection with the cookies.

1.2. This Cookie policy also provides You with all necessary information according to the General Data Protection Regulation (EU) 2016/679 (“GDPR”).

1.3. We take Your privacy seriously and always ensure that Your information is protected when using Bohemia Interactive websites which are listed below. In order to improve Your experience on Our websites We use cookies to the purposes specified below.

2.1. Cookies are small data files that are transferred to your device They can be used to recognize Your computer and adapt the website to Your needs, such as remembering items You have placed in Your cart, and the last products You viewed. Via cookies We also collect some of Your personal data and then process it for the purpose of creating statistics of Our website’s traffic and the activities of visitors of Our websites.

3.1. All use of cookies by Us and processing of Your personal data associated with them is conducted based on the consent given by You to Us when You enter Our websites if the cookies are enabled in Your browser. We respect Do-not_track settings.

4.1. Our websites use cookies mainly for:

• Preventing fraudulent activities.
• Improving security.
• Keeping track of items in Your shopping cart.
• Identifying You when You return to Bohemia Interactive websites.
• Recommending products to You as You browse Our websites based on Your interests.
• Creation of statistical reports such as Google analytics.

5.1. On the domains bistudio.com and bohemia.net We use the following cookies:

• "connect.sid" which identifies user session on a page
• "_gid" - Google analytics - used to distinguish users
• "_ga"- Google analytics - used to distinguish users
• "_gat"- Google analytics - used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_
• "arma3_session" which identifies user session on a page
• "bi_auth_session" which identifies user session on a page
• "xsrf-token" which protects against cross site forgery (https://www.owasp.org/index.php/Cross-Site_Request_Forgery_(CSRF))
• "__utmz" - Google analytics - used to store the traffic source or campaign that explains how the user reached Our site. The cookie is created when the JavaScript library executes and is updated every time data is sent to Google Analytics
• "__utmc" - Google analytics - not used in ga.js. Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the __utmb cookie to determine whether the user was in a new session/visit
• "__utmb" - Google analytics - used to determine new sessions/visits. The cookie is created when the JavaScript library executes and no existing __utmb cookies exist. The cookie is updated every time data is sent to Google Analytics
• "__utma" - Google analytics - used to distinguish users and sessions. The cookie is created when the JavaScript library executes and no existing __utma cookies exist. The cookie is updated every time data is sent to Google Analytics
• "__utmt" - Google analytics - used to throttle request rate
• "ips4_hasJS" - Invision forum - This cookie is set by JavaScript and then later read to determine if JavaScript is supported in the user agent
• "ips4_ipsTimezone": "Invision forum - This cookie is set by JavaScript to detect the user's local time zone so that the software can adapt the displaying of times automatically",
• "ips4_IPSSessionFront" - Invision forum - This is a session tracking cookie, used to track the user between page clicks

5.2. On the domain bistudio.cz We use the following cookies:

• "_gid" - Google analytics - used to distinguish users
• "_ga"- Google analytics - used to distinguish users
• "_gat"- Google analytics - used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_
• "bi_auth_session" which identifies user session on a page

5.3. On the domain bistudio.lu We use the following cookies:

• "_gid" - Google analytics - used to distinguish users
• "_ga"- Google analytics - used to distinguish users
• "_gat"- Google analytics - used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_
• "bi_store_auth_session" which identifies user session on a page

5.4. On the domain bistudio.sk We use the following cookies:

• "_gid" - Google analytics - used to distinguish users
• "_ga"- Google analytics - used to distinguish users
• "_gat"- Google analytics - used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_
• "bi_auth_session" which identifies user session on a page

5.5. On the domain blackelement.net We use the following cookies:

• "_gid" - Google analytics - used to distinguish users
• "_ga"- Google analytics - used to distinguish users
• "_gat"- Google analytics - used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_
• "bi_auth_session" which identifies user session on a page

5.6. On the domain carriercommand.com We use the following cookies:

• "qtrans_cookie_test" – used for testing purposes only
• "ccgm_age_verification_cookie_check" - stores if user entered through age gate"

5.7. On the domain dayz.com We use the following cookies:

• "dayz_session" which identifies user session on a page
• "__utmz" - Google analytics - used to store the traffic source or campaign that explains how the user reached Our site. The cookie is created when the JavaScript library executes and is updated every time data is sent to Google Analytics
• "__utmc" - Google analytics - not used in ga.js. Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the __utmb cookie to determine whether the user was in a new session/visit
• "__utmb" - Google analytics - used to determine new sessions/visits. The cookie is created when the JavaScript library executes and no existing __utmb cookies exist. The cookie is updated every time data is sent to Google Analytics
• "__utma" - Google analytics - used to distinguish users and sessions. The cookie is created when the JavaScript library executes and no existing __utma cookies exist. The cookie is updated every time data is sent to Google Analytics
• "__utmt" - Google analytics - used to throttle request rate
• “dsc” – used to identify the user
• “lang” – used to store user´s language
• “mab” – used to identify the user

5.8. On the domain dayzgame.com We use the following cookies:

• "dayz_session" which identifies user session on a page
• "__utmz" - Google analytics - used to store the traffic source or campaign that explains how the user reached Our site. The cookie is created when the JavaScript library executes and is updated every time data is sent to Google Analytics
• "__utmc" - Google analytics - not used in ga.js. Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the __utmb cookie to determine whether the user was in a new session/visit
• "__utmb" - Google analytics - used to determine new sessions/visits. The cookie is created when the JavaScript library executes and no existing __utmb cookies exist. The cookie is updated every time data is sent to Google Analytics
• "__utma" - Google analytics - used to distinguish users and sessions. The cookie is created when the JavaScript library executes and no existing __utma cookies exist. The cookie is updated every time data is sent to Google Analytics
• "__utmt" - Google analytics - used to throttle request rate

5.9. On the domain minidayz.com We use the following cookies:

• "_gid" - Google analytics - used to distinguish users
• "_ga"- Google analytics - used to distinguish users
• "_gat"- Google analytics - used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_

5.10. On the domain dayzdev.com We use the following cookies:

• "__utmz" - Google analytics - used to store the traffic source or campaign that explains how the user reached Our site. The cookie is created when the JavaScript library executes and is updated every time data is sent to Google Analytics
• "__utmc" - Google analytics - not used in ga.js. Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the __utmb cookie to determine whether the user was in a new session/visit
• "__utmb" - Google analytics - used to determine new sessions/visits. The cookie is created when the JavaScript library executes and no existing __utmb cookies exist. The cookie is updated every time data is sent to Google Analytics
• "__utma" - Google analytics - used to distinguish users and sessions. The cookie is created when the JavaScript library executes and no existing __utma cookies exist. The cookie is updated every time data is sent to Google Analytics
• "__utmt" - Google analytics - used to throttle request rate
• "_gid" - Google analytics - used to distinguish users
• "_ga"- Google analytics - used to distinguish users
• "rxx" - tumblr service cookie"

5.11. On the domain arma3.com We use the following cookies:

• "_gid" - Google analytics - used to distinguish users
• "_ga"- Google analytics - used to distinguish users
• "_gat"- Google analytics - used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_
• "arma3_session" which identifies user session on a page
• "XSRF-TOKEN" which protects against cross site forgery (https://www.owasp.org/index.php/Cross-Site_Request_Forgery_(CSRF))

5.12. On the domain arma.cz We use the following cookies:

• "_gid" - Google analytics - used to distinguish users
• "_ga"- Google analytics - used to distinguish users
• "_gat"- Google analytics - used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_
• "bi_auth_session" – which identifies user session on a page

5.13. On the domain arma2.cz We use the following cookies:

• "_gid" - Google analytics - used to distinguish users
• "_ga"- Google analytics - used to distinguish users
• "_gat"- Google analytics - used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_
• "laravel_session" – which identifies user session on a page

5.14. On the domain arma2.com We use the following cookies:

• "_gid" - Google analytics - used to distinguish users
• "_ga"- Google analytics - used to distinguish users
• "_gat"- Google analytics - used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_
• "laravel_session" – which identifies user session on a page

5.15. On the domain arma3.cz We use the following cookies:

• "_gid" - Google analytics - used to distinguish users
• "_ga"- Google analytics - used to distinguish users
• "_gat"- Google analytics - used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_
• "bi_auth_session" – which identifies user session on a page

5.16. On the domain armamobileops.com We use the following cookies:

• "_gid" - Google analytics - used to distinguish users
• "_ga"- Google analytics - used to distinguish users
• "_gat"- Google analytics - used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_

5.17. On the domain armatactics.com We use the following cookies:

• "__utmz" - Google analytics - used to store the traffic source or campaign that explains how the user reached Our site. The cookie is created when the JavaScript library executes and is updated every time data is sent to Google Analytics
• "__utmc" - Google analytics - not used in ga.js. Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the __utmb cookie to determine whether the user was in a new session/visit
• "__utmb" - Google analytics - used to determine new sessions/visits. The cookie is created when the JavaScript library executes and no existing __utmb cookies exist. The cookie is updated every time data is sent to Google Analytics
• "__utma" - Google analytics - used to distinguish users and sessions. The cookie is created when the JavaScript library executes and no existing __utma cookies exist. The cookie is updated every time data is sent to Google Analytics
• "__utmt" - Google analytics - used to throttle request rate
• "csrf_cookie" which protects against cross site forgery (https://www.owasp.org/index.php/Cross-Site_Request_Forgery_(CSRF))

5.18. On the domain makearma.com We use the following cookies:

• "_gid" - Google analytics - used to distinguish users
• "_ga"- Google analytics - used to distinguish users
• "_gat"- Google analytics - used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_
• "manwar_session" – which identifies user session on a page
• "browserupdateorg" – which stores information if user dismissed notification about outdated browser

5.19. On the domain makearmanotwar.com We use the following cookies:

• "_gid" - Google analytics - used to distinguish users
• "_ga"- Google analytics - used to distinguish users
• "_gat"- Google analytics - used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_
• "manwar_session" – which identifies user session on a page
• "browserupdateorg" – which stores information if user dismissed notification about outdated browser

5.20. On the domain mec.cz We use the following cookies:

• "_gid" - Google analytics - used to distinguish users
• "_ga"- Google analytics - used to distinguish users
• "_gat"- Google analytics - used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_
• "bi_auth_session" – which identifies user session on a page

5.21. On the domain projectargo.net We use the following cookies:

• "_gid" - Google analytics - used to distinguish users
• "_ga"- Google analytics - used to distinguish users
• "_gat"- Google analytics - used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_
• "connect.sid" – which identifies user session on a page

5.22. On the domain takeonmars.com We use the following cookies:

• "__utmz" - Google analytics - used to store the traffic source or campaign that explains how the user reached Our site. The cookie is created when the JavaScript library executes and is updated every time data is sent to Google Analytics
• "__utmc" - Google analytics - not used in ga.js. Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the __utmb cookie to determine whether the user was in a new session/visit
• "__utmb" - Google analytics - used to determine new sessions/visits. The cookie is created when the JavaScript library executes and no existing __utmb cookies exist. The cookie is updated every time data is sent to Google Analytics
• "__utma" - Google analytics - used to distinguish users and sessions. The cookie is created when the JavaScript library executes and no existing __utma cookies exist. The cookie is updated every time data is sent to Google Analytics
• "__utmt" - Google analytics - used to throttle request rate
• "laravel_session" – which identifies user session on a page

5.23. On the domain takeonthegame.com We use the following cookies:

• "__utmz" - Google analytics - used to store the traffic source or campaign that explains how the user reached Our site. The cookie is created when the JavaScript library executes and is updated every time data is sent to Google Analytics
• "__utmc" - Google analytics - not used in ga.js. Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the __utmb cookie to determine whether the user was in a new session/visit
• "__utmb" - Google analytics - used to determine new sessions/visits. The cookie is created when the JavaScript library executes and no existing __utmb cookies exist. The cookie is updated every time data is sent to Google Analytics
• "__utma" - Google analytics - used to distinguish users and sessions. The cookie is created when the JavaScript library executes and no existing __utma cookies exist. The cookie is updated every time data is sent to Google Analytics
• "__utmt" - Google analytics - used to throttle request rate
• "__atuvs" - used to show You an updated share count for an article, if You Yourself share it and return to the page later, but before the sharing cache was updated. No info from this cookie is sent back to AddThis. It is created and used only on the
client
• "__atuvc" - used to show You an updated share count for an article, if You Yourself share it and return to the page later, but before the sharing cache was updated. No info from this cookie is sent back to AddThis. It is created and used only on the client.",
• "qtrans_cookie_test" – used for testing purposes only

5.24. On the domain takeonhelicopters.com We use the following cookies:

• "__utmz" - Google analytics - used to store the traffic source or campaign that explains how the user reached Our site. The cookie is created when the JavaScript library executes and is updated every time data is sent to Google Analytics
• "__utmc" - Google analytics - not used in ga.js. Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the __utmb cookie to determine whether the user was in a new session/visit
• "__utmb" - Google analytics - used to determine new sessions/visits. The cookie is created when the JavaScript library executes and no existing __utmb cookies exist. The cookie is updated every time data is sent to Google Analytics
• "__utma" - Google analytics - used to distinguish users and sessions. The cookie is created when the JavaScript library executes and no existing __utma cookies exist. The cookie is updated every time data is sent to Google Analytics
• "__utmt" - Google analytics - used to throttle request rate

5.25. On the domain ufo-afterlight.com We use the following cookies:

• "_gid" - Google analytics - used to distinguish users
• "_ga"- Google analytics - used to distinguish users
• "_gat"- Google analytics - used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_
• "bi_auth_session" – which identifies user session on a page

5.26. On the domain ufo-afterlight.cz We use the following cookies:

• "_gid" - Google analytics - used to distinguish users
• "_ga"- Google analytics - used to distinguish users
• "_gat"- Google analytics - used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_
• "bi_auth_session" – which identifies user session on a page

5.27. On the domain ufo-aftermath.com We use the following cookies:

• "_gid" - Google analytics - used to distinguish users
• "_ga"- Google analytics - used to distinguish users
• "_gat"- Google analytics - used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_
• "bi_auth_session" – which identifies user session on a page

5.28. On the domain ufo-afterraform.com We use the following cookies:

• "_gid" - Google analytics - used to distinguish users
• "_ga"- Google analytics - used to distinguish users
• "_gat"- Google analytics - used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_
• "bi_auth_session" – which identifies user session on a page

5.29. On the domain ufo-afterraform.cz We use the following cookies:

• "_gid" - Google analytics - used to distinguish users
• "_ga"- Google analytics - used to distinguish users
• "_gat"- Google analytics - used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_
• "bi_auth_session" – which identifies user session on a page

5.30. On the domain ufo-aftershock.com We use the following cookies:

• "_gid" - Google analytics - used to distinguish users
• "_ga"- Google analytics - used to distinguish users
• "_gat"- Google analytics - used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_
• "bi_auth_session" – which identifies user session on a page

5.31. On the domain ylands.com We use the following cookies:

• "_gid" - Google analytics - used to distinguish users
• "_ga"- Google analytics - used to distinguish users
• "_gat"- Google analytics - used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_
• “_hjIncludedInSample” - Hotjar.com cookie. This session cookie is set to let Hotjar know whether that visitor is included in the sample which is used to generate funnels."
• "ips4_hasJS" - Invision forum - This cookie is set by JavaScript and then later read to determine if JavaScript is supported in the user agent
• "ips4_ipsTimezone": "Invision forum - This cookie is set by JavaScript to detect the user's local time zone so that the software can adapt the displaying of times automatically",
• "ips4_IPSSessionFront" - Invision forum - This is a session tracking cookie, used to track the user between page clicks

5.32. On the domain ylands.net We use the following cookies:

• "_gid" - Google analytics - used to distinguish users
• "_ga"- Google analytics - used to distinguish users
• "_gat"- Google analytics - used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_
• "browserupdateorg" - stores if user dismissed notification about outdated browser
• "xsrf-token" which protects against cross site forgery (https://www.owasp.org/index.php/Cross-Site_Request_Forgery_(CSRF))
• "csrf-token" which protects against cross site forgery (https://www.owasp.org/index.php/Cross-Site_Request_Forgery_(CSRF))

5.33. On the domain sogpf.com We use the following cookies:

• "_gid" - Google analytics - used to distinguish users
• "_ga"- Google analytics - used to distinguish users
• "_gat"- Google analytics - used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_
• "_cf_bm" - Cloudflare - Cloudflare places the __cf_bm cookie on End User devices that access Customer sites that are protected by Bot Management or Bot Fight Mode. The cookie is necessary for the proper functioning of these bot solutions.

6.1. All Your personal data We acquire via cookies is processed automatically through Our information systems.

6.2. All Your personal data We acquire via cookies is used only in connection with particular cookies and for the purposes of carrying out the functionalities of such cookies or purposes defined in this policy.

6.3. Most browsers automatically accept cookies, but you can modify Your browser setting to decline cookies by visiting the Help portion of your browser’s toolbar. If you choose to decline cookies, some parts of Our websites may not work as intended or may not work at all.

7.1. List of personal data collected in connection with particular cookies You can find in Appendix No. 1 to this policy.

8.1. Except data acquired via cookies of Google Analytic - _gid, _ga, _gat or _utmz, _utmc, _utmb, _utma, _utmt (“Google Analytics Cookies”), via dsc, lang and mab (“Trello Cookies”), via _hjIncludedInSample (“Hotjar Cookie”) and via __atuvs, __atuvs (“AddThis Cookies”) all Your personal data We acquire via cookies is processed by Us.

8.2. Personal data collected via Google Analytics Cookies is transferred to Google LLC, 600 Amphitheatre Parkway, Mountain View, CA, 94043, United States for purposes of creating reports which are then given to Us and help Us to optimize Our websites. Such personal data will not be used for other purposes than defined in this policy. More information about Google Analytics Cookies can be found here.

8.3. Personal data collected via Trello Cookies is transferred to Trello, Inc., 55 Broadway, 25th Floor, New York, NY 10006, United States for purposes of providing better functionality of Our websites. Such personal data will not be used for other purposes than defined in this policy. More information about Trello Cookies can be found here.

8.4. Personal data collected via Hotjar Cookie is transferred to Hotjar Limited, a private limited liability company registered under the Laws of Malta with company number C 65490, having its registered address situated at Level 2, St Julian’s Business Centre, 3, Elia Zammit Street, St Julian’s STJ 1000, Malta for purposes of purposes of providing better functionality of Our websites. Such personal data will not be used for other purposes than defined in this policy. More information about Hotjar Cookie can be found here.

8.5. Personal data collected via AddThis Cookies is transferred to Oracle America, Inc., 500 Oracle Parkway, Redwood Shores, CA 94065 for purposes of providing better functionality of Our websites. Such personal data will not be used for other purposes than defined in this policy. More information about AddThis Cookies can be found here

9.1. Cookies You accepted during visiting Our websites are kept on the hard drive of Your device in the user data folder based on your operation system and browser You use for a specific time period which is specified in Appendix No. 1 to this policy.

9.2. If You have cookies enabled in Your browser after the time period specified in Sec. 9.1 lapses and You visit a particular website again the cookies will be used automatically again in Your browser once You visit such website.

9.3. Personal data We collect via cookies is kept by Us for specific period of time which is specified in Appendix No. 1 to this policy.

10.1. Right to access and rectification of personal data. You have the right to access and rectify or amend incorrect or incomplete personal data about You which We collect.

10.2. Right to erasure of personal data. You have the right to request Us to erase all Your personal data We collected via cookies based on Your consent. If You would like Us to erase Your personal data You can contact Us at [email protected]. Once We receive Your request We erase all the personal data We are obliged to according to GDPR. You can also erase at any time the cookies stored on the hard drive of Your device according to the specific functionalities of Your browser.

10.3. Right to restriction of processing of personal data. You have the right to request Us to restrict the processing of Your personal data in some cases until Your request to erase or change Your personal data or Your objection is not processed.

10.4. Right to withdraw the consent to process personal data and use cookies. Where We use cookies or process Your personal data based on Your consent You can withdraw such consent at any time by making restrictions in Your browser to use cookies (disabling cookies in Your browser).

10.5. Right to object to processing of Your personal data. If You feel Your personal data is not processed by Us in compliance with applicable laws You can object to such processing and request Us to make remedy.

10.6. Right to file a complaint. If You think that during the processing of Your personal data We breached applicable laws You are entitled to file a complaint to the official authority residing in Your state, in the state where You work or where the infringement of your rights took place. In the Czech Republic such official authority is:

The Office for Personal Data Protection
Pplk. Sochora 27
170 00 Praha 7
Czech Republic

11.1. Most browsers have a help menu which will direct You to Your cookie settings. You can choose not to accept cookies, be notified if a new cookie is requesting to be accepted, or to accept cookies.

11.2. Please note that by deleting cookies or disabling future cookies certain areas or features of Our websites may become unavailable to access and it will mean You will need to re-enter details, such as Your username and password each time You visit Bohemia Interactive websites. If You adjust Your cookie settings this will also affect the other websites You visit.

14.1. This policy is valid and effective as of 1st June 2018.

14.2. By using Our websites You declare You are familiar with this policy and You understand it.

14.3. We may from time to time change this Policy or change, modify or withdraw access to this site at any time with or without notice. However, if this Policy is changed in a material, adverse way, We will post a notice advising of such change at the beginning of this Policy and on this site's home page for 30 days. We recommend that You re-visit this Policy from time to time to learn of any such changes to this Policy.

14.4. If You have any questions regarding the cookies We use or personal data We collect via cookies You can contact Us at [email protected].

Name of cookie	Personal data collected in connection with the cookies	Time period for which the cookies are kept in Your device	Time period for which the personal data is kept by Us
connect.sid	0	2 hours	0
_gid	Data regarding Your activity on particular website	24 hours	24 hours
_ga	Data regarding Your activity on particular website	2 years	2 years
_gat	Data regarding Your activity on particular website	1 minute	1 minute
arma3_session	0	2 hours	0
bi_auth_session	0	2 hours	0
xsrf-token	0	2 hours	0
__utmz	Data regarding Your activity on particular website	6 months	6 months
__utmc	Data regarding Your activity on particular website data	End of browser session	End of browser session
__utmb	Data regarding Your activity on particular website data	30 minutes	30 minutes
__utma	Data regarding Your activity on particular website data	2 years	2 years
__utmt	Data regarding Your activity on particular website data	10 minutes	10 minutes
ips4_hasJS	0	24 hours	0
ips4_ipsTimezone	0	End of browser session	0
ips4_IPSSessionFront	0	End of browser session	0
bi_store_auth_session	0	2 hours	0
qtrans_cookie_test	0	1 hours	0
ccgm_age_verification_cookie_check	Date of birth	1 month	1 month
dayz_session	0	2 hours	0
dsc	Data regarding Your activity on particular website data	3 days	3 days
lang	0	End of browser session	0
mab	Data regarding Your activity on particular website data	1 month	1 month
rxx	Data regarding Your activity on particular website data	1 month	1 month
laravel_session	0	2 hours	0
vsid	0	2 hours	0
manwar_session	0	2 hours	0
browserupdateorg	0	1 month	0
__atuvs	Data regarding Your activity on particular website data	2 years	2 years
__atuvc	Data regarding Your activity on particular website data	2 years	2 years
_hjIncludedInSample	0	1 hour	0