Cookies and device storage

1. Cookies and device storage

Cookies are small pieces of data stored for a website. The game also uses localStorage, sessionStorage and WebView storage in PC/Android clients. Article 399 of Poland’s Electronic Communications Law covers storing/accessing information on a device, not just items called cookies. Image/script caching is separate; disabling cache does not delete login data.

2. Categories and consent

Storage strictly necessary for transmission or a service expressly requested by the user falls within the statutory consent exception. Other storage, such as analytics/advertising, requires prior choice and cannot be enabled by default. Dismissing a notice, browsing and accepting game terms are not consent. This game notice is informational, not a pretend consent panel for services that are not connected. External integrations, particularly reCAPTCHA and old widgets, need a separate audit and, where necessary, pre-consent blocking.

3. Sessions and login — inventory

PHPSESSID: server session, configured for 24 hours. login, haslo and userKey: authentication mechanisms; the historical “haslo” cookie is a password-hash-based token, not an advertising preference. Older login code sets 24 hours without “remember me”, but uses an excessive time() × 10 expiry for that option; this must be replaced with an approved duration and secure token before publication. CPU_ID: legacy login identifier requiring an audit and retention definition. Logout removes the main login cookies. Never share their values.

4. Language, payments and notice

websiteLang: chosen PL/EN/JP language, up to one year. dimenshon_payment_device: payment-request identifier to reduce duplicate requests/abuse, up to 180 days, set in the payment context. dimenshon_cookie_notice: remembers dismissal of the informational notice for up to 180 days; it is not proof of tracking consent. The new notice removes the old invitationcookie, historically set for 9999 days and not a valid consent record.

5. Local and session storage

localStorage may contain map_click_move, gamepad_enabled, sound_music, sound_sfx, screen_w, screen_h, screen_fps, expanded_ui and quest_tracker_* for controls, sound, display and quest-list settings. These persist until deleted/overwritten unless the particular client clears them earlier. sessionStorage entries such as ddt_logged and ddt_flagged prevent repeated security reporting during a session and normally disappear when the browser/WebView session ends. Necessity must be assessed against the user-requested function, not just the entry name.

6. Third-party services

Google reCAPTCHA on registration/recovery forms and the selected payment provider may access/store their own data. Exact names and durations depend on the integration/provider settings and require measurement in the actual client. See policies.google.com/privacy and policies.google.com/technologies/cookies; the payment provider’s policy is also available on its checkout site. Not all provider storage automatically qualifies for the necessity exception. Unverified names/durations are not presented as a complete inventory.

7. Managing and deleting data

Remove cookies/site data through browser or app/WebView settings; accepting them can be blocked. This may log you out, interrupt payment or erase preferences. Change language/game preferences in the relevant settings. Server-data requests go to dimenshon@nekotec.pl; deleting cookies does not delete the account or server logs. Any future optional integrations must allow equally easy rejection and withdrawal; this informational notice does not authorise their activation.

8. Payments through PayU, PayPal and Przelewy24 — cookies

In the current integration, the provider’s website opens only after payment is selected. Displaying links in these documents does not load its scripts. After redirection, PayU, PayPal or Przelewy24 and the selected bank may use their own cookies and similar technologies for sessions, authentication, security or other purposes described by the provider. PayU provides information through its privacy portal; PayPal and Przelewy24 also publish separate cookie information. Not every provider technology is automatically necessary for payment. Optional functions are subject to applicable consent rules; preferences on the provider’s website are managed using its own mechanism. Dismissing the Dimenshon cookie notice does not consent to provider marketing or analytics. Any future embedded payment forms or scripts require a separate audit and an update to this notice before deployment.

• PayU privacy information
• PayPal cookie information
• Przelewy24 Cookie Policy

9. Contact through Support

Questions about cookies and device storage can be sent through Support, a private message to an administration account listed in Support, or dimenshon@nekotec.pl. The tab uses the existing login session and form protection; it introduces no additional advertising or analytics cookies. Users without account access can contact us by email.