Cookie Notice

Project creators and owner, hosting, and contact

Plaryn.com is the brand and project created, built and owned by the creators acting as Plaryn Team. Plaryn Team is a creative team designation, not a separately registered legal person. Hosting the website on Bomega infrastructure does not give Bomega ownership of the project or brand.

Technical hosting and support for Plaryn.com are provided by BOMEGA spółka z ograniczoną odpowiedzialnością (BOMEGA Sp. z o.o.), Długa 2B, 56-416 Twardogóra, Poland, KRS 0000841054, NIP 9112034523, REGON 386056613. Bomega hosts the service on its servers and performs related technical data operations. Hosting alone does not make it the project owner, the contractual service provider to users or the personal data controller.

Contact for hosting and technical assistance: [email protected]. Plaryn Team creates and owns the project, while Bomega provides hosting and technical operations.

Plaryn Team is the creative team designated by the owner as the creator and owner of the project and brand. Economic rights to particular works, software and games follow actual authorship, contracts and licences; users who submit games retain their lawful rights. Bomega does not acquire any rights to Plaryn.com, its brand, code or games merely by hosting them.

Detailed rules for the functions and rights covered by this document. The provisions distinguish currently available features from options not yet enabled for paid orders.

Cookies and browser-local storage

Cookies are small records stored by the browser and can be sent with later requests to the relevant website. localStorage and sessionStorage are separate browser mechanisms that can remember interface choices or device-related information without automatically attaching those values to every Cookie header. These technologies can support sessions, security and selected player preferences.

Not every page sets every technology described here. The actual records depend on the authentication state, selected language and functions used. Each technology should be described according to its real purpose. Local browser storage should not be confused with records stored separately on the server in association with an Account.

The __Host-gp_csrf security cookie

Plaryn uses a first-party cookie named `__Host-gp_csrf` to protect selected authenticated operations against unauthorised cross-site requests. Its purpose is request security, not advertising. Relevant protections can check the consistency of an action with the current session and reject attempts to perform protected operations without the required security context.

Blocking essential cookies can prevent sign-in or secure Account updates. Authentication and security cookies must not be shared. The platform may adapt its technical protections to maintain security, subject to the relevant duty to inform Users about material changes.

Language preference with plaryn_locale

The `plaryn_locale` cookie remembers a selected language. The inspected mechanism uses a maximum age of 365 days with Path=/, Secure and SameSite=Lax. It preserves language selection between visits without acting as an advertising identifier. Members can select a different language through the available interface.

Polish and English versions of certain features have different page paths. Removing the cookie can restore the default language but does not change statutory rights or delete published content. Selecting a language does not, by itself, require transferring the user's complete Account profile to a third party.

Account sessions and authentication

Sign-in and operations protected by access controls can involve additional session and authentication mechanisms. Their implementation can vary by release and workflow. They help check whether a User is authorised and whether the requested action can safely be performed.

Deleting session cookies can require re-authentication or repeating an unsaved action. Signing out does not delete an Account or Creator projects. A cookie's existence must never be treated as the sole permission to access another person's files, because protected resources require separate authorisation.

Registered devices and player updates

Some player features can store a device-registration state, confirmation of an update or settings needed to restore a supported player environment. Such records are not identical to a public Creator profile, a purchase or unlimited access to Game Releases. They help recall a specific interface or device state.

Clearing site data, changing browser profiles or using a different device can require registering that device again or confirming an update. Users must follow the entitlement rules of the relevant Game. A local record is not proof that it has been synchronised to the server or that a Cloud Save backup exists.

Cloud Save and Account records are different

Game saves stored against an Account, publication history, followed titles and moderation reports can exist in server systems linked to their respective features. They are not merely cookies and generally are not deleted by clearing browser storage. Cookies can support access to those functions without being the complete data records themselves.

Access, correction and erasure of Account data are governed by the actual privacy controls and the Privacy Notice. Changing language or blocking localStorage does not automatically delete public Game Cards. Users should distinguish deleting device preferences from requesting closure of an Account.

Third-party resources and Game content

A Game Card may display Creator-supplied graphics or links to other services. Opening an external site can expose the visitor to that independent provider's cookies and storage practices. Those practices should not automatically be attributed to plaryn.com unless the relevant connection and integration genuinely occur.

A provider's role depends on whether the browser contacts it directly or the Service uses a server-side intermediary. Integrations can change with particular Game Releases. Any newly enabled non-essential browser technology must comply with the applicable information and consent obligations.

Necessary and optional technologies

Electronic-communications law distinguishes technologies necessary to transmit information or provide a specifically requested function from other uses of device storage. Certain session and request-security mechanisms may fall within statutory exceptions. Optional advertising, marketing or analytics uses can require valid prior consent.

The current login workflow does not require agreeing to unrelated advertising identifiers. If additional optional tools are introduced, their purposes, providers and consent controls should be disclosed. Refusing an unrelated tracker must not unnecessarily prevent access to independent public Service features.

Deleting and blocking site data

Browsers provide settings for inspecting, clearing and limiting cookies and local website data. Changes can affect language preference, signing in, form-security checks and registered-device state. The exact controls depend on the browser and device.

Deleting cookies does not constitute a server-side personal-data erasure request. Account information should be handled through the relevant privacy channels. On shared devices, members should also sign out and protect their browser profiles.

Updates and technical contact

Cookie and storage practices can change as authentication, Studio, Game features and security measures evolve. This Notice should be updated when material purposes, retention settings or providers change. The existence of planned commerce functionality is not evidence of active advertising cookies.

Questions about browser storage and technical settings can be sent to [email protected] for infrastructure support and forwarding to the appropriate team. The separate Privacy Notice explains Account data, retention criteria and individual rights in greater detail.