Політика файлів cookie

1. Introduction

1.1. This Cookie Policy describes how Skagry, the operator of the Skagry Universe game (the “Operator”), uses cookies and similar technologies on the website and in the game. Capitalized terms not defined in this Cookie Policy, including “Applicable Law”, have the meanings given to them in the Terms of Service.

1.2. Cookies are small text files stored by a website in the User’s browser. Local storage (localStorage), session storage (sessionStorage) and IndexedDB are comparable browser storage facilities in which a website may store data on the User’s device.

1.3. The Operator uses only cookies and storage that are strictly necessary to provide the Service requested by the User or to remember choices made by the User. The Operator does not use analytics, advertising or tracking cookies and does not permit third parties to place advertising cookies through its website. Strictly necessary cookies and storage are exempt from consent under Applicable Law; the cookie notice informs the User of their use. The Operator measures the audience of the website without cookies and without storing anything in the User’s browser, as described in clause 4.5.

2. Cookies Set by the Operator

2.1. refresh_token: maintains the User’s signed-in session. It is set by the Operator’s server upon sign-in, is inaccessible to page scripts and is sent only to the Operator’s website. Duration: seven (7) days or, where the User signs in without choosing to remain signed in, until the browser is closed. It is deleted upon sign-out.

2.2. locale: stores the language of the website. It is set when a page is opened in a given language. Duration: until the browser is closed.

2.3. cookie_consent: records that the cookie notice has been displayed and the version of this Cookie Policy to which it referred, so that the notice is not displayed again. Duration: one (1) year.

2.4. skagry_stand_gate: set only on environments closed with a password, such as test environments and the game before its public launch, and never on an open environment; it confirms that the browser has passed the access check of that environment and is inaccessible to page scripts. Duration: thirty (30) days.

2.5. scalar_sid: used exclusively by the Operator’s staff in the administration tools to maintain an administrator’s session in the API reference. Duration: until the browser is closed.

3. Local Storage and Similar Technologies

3.1. _sh (local storage): indicates that a sign-in has taken place on the device, so that the session can be restored promptly. It is deleted upon sign-out.

3.2. _uc (local storage): a copy of basic Account details (Account identifier, user name, roles and language) that enables the page to display them before the server responds. It is deleted upon sign-out.

3.3. Map cache (local storage; entries named after the map data they contain, such as worldgetsectors_…): copies of public game map data that accelerate the loading of the map. It contains no personal data and is kept until the User clears the browser storage.

3.4. Journal cache (IndexedDB): copies of the User’s battle and espionage reports from the in-game journal that enable the journal to open promptly. It is refreshed from the Operator’s servers.

3.5. skagry.account.saved (session storage): records, for a single page reload, that the Account settings have been saved, so that a confirmation can be displayed after a change of language. It is deleted immediately after it is read.

3.6. skagry.gameUi (local storage): records that the game opens with the new version of its interface on the device. It is set when the User selects that version and, in the Operator’s desktop and Android applications, once at the first launch, and it is removed when the User selects the previous version. It is not sent to the Operator’s servers or to any third party and is kept until the User clears the browser or application storage.

3.7. skagry.shell.gameUiDefault (local storage): set only by the Operator’s desktop and Android applications, once for each profile, to record that the default version of the interface has been applied, so that it is not applied again after the User has selected another version. It is not sent to the Operator’s servers or to any third party and is kept until the User clears the application storage.

3.8. skagry.chatDock.ui (local storage): the state of the chat window in the game: whether it is collapsed, which of its lists are open, and its position and size. It is not sent to the Operator’s servers or to any third party and is kept until the User clears the browser storage.

3.9. skagry.notificationsPinned.N (local storage; one entry for each Account used on the device, where N is the Account identifier): whether the User has pinned the list of notifications open in the game, stored as true or false. It is not sent to the Operator’s servers or to any third party and is kept until the User clears the browser storage.

3.10. skagry.recentEstates.N (local storage; one entry for each Account used on the device, where N is the Account identifier): the identifiers of up to three of the User’s planets that the game showed last, so that the menu of the User’s planets can offer them again. It is not sent to the Operator’s servers or to any third party and is kept until the User clears the browser storage.

4. Third-Party Services

4.1. Google sign-in: on the sign-in and registration pages, where sign-in with Google is offered, the browser loads Google’s sign-in library from accounts.google.com. Google may set or read its own cookies in accordance with its privacy policy, available at https://policies.google.com/privacy (відкриється в новій вкладці)

4.2. External links: the footer of the website links to the game’s channel on YouTube and to a profile on GitHub. The website loads no video, image or script from those services and they set no cookies through it; once the User follows a link, the cookies of the linked site are governed by its own policy.

4.3. Payments: payments are completed on the Payment Provider’s own page, which uses its own cookies in accordance with the Payment Provider’s policy.

4.4. The Operator has no control over third-party cookies, which are governed by the policies of the respective providers.

4.5. Audience measurement: the Operator measures the audience of the website, of the sandbox and of the game with software that it runs itself, on a subdomain of its own domain. The browser loads one script from that subdomain; the measurement sets no cookie, writes nothing to local storage, session storage or IndexedDB, and shares no identifier with any other website, and no third party receives its data. The sandbox additionally carries the audience measurement of Vercel, which hosts it; that measurement sets no cookie either. What each of them records is described in the Privacy Policy.

5. Management of Cookies

5.1. The User may view, block and delete cookies and clear local storage in the browser settings. Blocking or deleting strictly necessary cookies ends the signed-in session and may prevent parts of the Service from functioning. Clearing local storage, session storage or IndexedDB does not delete the Account or game data, which are stored on the Operator’s servers.

6. Amendments and Contact

6.1. Should the Operator introduce cookies that are not strictly necessary, such as analytics cookies, this Cookie Policy will be amended beforehand, and the User’s consent will be requested before such cookies are set. Each version of this Cookie Policy bears its own number, and the cookie notice is displayed again upon publication of a new version.

6.2. Questions concerning cookies may be sent to info@skagry.com.