77RP cookie policy

The Service uses cookies and other browser mechanisms: • cookies - small records the browser may send when connecting to the relevant domain; • localStorage - local browser storage, used among other things to remember settings; • sessionStorage - storage tied to the session of a given browser tab; • service workers and push mechanisms - used for selected features, including notifications.

localStorage entries have no built-in expiry. Unless the application removes them earlier, they may stay in the browser until the user, the browser or the application deletes them. Changing a setting may overwrite the previously stored value.

Session cookies and sessionStorage are tied to the browser or tab session. When they are actually deleted may also depend on browser settings, in particular restoring the previous session.

We use strictly necessary technologies to carry out transmission or provide features the user requests, such as signing in, keeping a session and securing forms. To the extent they are genuinely necessary for these purposes, they do not require consent to store or read information on the device.

Optional technologies that require consent may run only after consent is given. Refusing does not block the basic features of the Service or purchases, although the optional feature may stay disabled.

Calling a record “functional” or saying it remembers preferences does not by itself exempt it from the consent requirement. What matters is the purpose, necessity and way the feature works.

The banner on 77roleplay.pl stores your choice in the browser. Your settings are also used in the Google Consent Mode configuration. Optional consent parameters are set to denied by default.

Google Tag Manager loads only after you consent in the banner. In the configuration described in this version of the policy, the published container contains no active analytics or advertising tags. We do not run Google Analytics, Google Ads or TikTok Pixel through it.

Loading Google Tag Manager by itself connects to Google infrastructure, even when the container has no active tags. This does not mean the Service uses Google Analytics cookies.

You can change or withdraw consent by opening “Cookie settings” in the page footer and saving a new choice. Withdrawing consent stops further use of the technologies covered by it, to the extent the Service controls them. It does not affect the lawfulness of earlier processing based on consent.

Making no choice, closing the banner or scrolling the page does not count as consent. A choice made in the banner does not automatically cover new purposes or new technologies that need separate consent.

You can also block or delete cookies and other site data in your browser settings. Deleting session data may sign you out, and deleting preferences may restore default settings. Deleting the stored banner decision may make the request for a choice appear again.

You turn on push notifications voluntarily, using the relevant feature of the Service and granting permission in the browser. You can turn them off in the settings of the feature or the browser. Turning on queue or ticket notifications is not consent to a newsletter or advertising.

The consent management features described here apply to 77roleplay.pl. The technologies of individual services and subdomains are described below. Banner choices do not replace browser permission settings or the settings of separate external services.

The Operator provides the following first-party records.

77rp_cookie_consent_v1 - localStorage on 77roleplay.pl; remembers your banner choice. Period: set after you choose; no automatic expiry, kept until deleted or replaced by a new choice.

77rp:selected-server - localStorage; remembers the selected server. Period: no automatic expiry; kept until deleted or changed.

77rp-ui-sounds-muted - localStorage; remembers the sound mute setting. Period: no automatic expiry; kept until deleted or changed.

77:auth-return - sessionStorage; returns you to the right page after signing in. Period: stored at sign-in; for the tab session.

portal_session - API cookie; keeps the signed-in player session. Period: 30 days; set after signing in.

portal_oauth_state - API cookie; secures sign-in through Discord. Period: 10 minutes; set when sign-in starts.

portal_fivem_auth - API cookie; secures Cfx.re authentication. Period: 15 minutes; set during authentication.

portal_sso - API cookie; carries authentication over to the queue. Period: 10 minutes; set when this feature is used.

discord_admin_session - cookie; keeps the admin session. Period: 4 hours; applies to administration, not regular player sessions.

The stored banner decision is not used for advertising. Its lack of an automatic expiry does not mean consent to unlimited future purposes.

__Host-Queue.Session - cookie; keeps the queue session. Period: session cookie, set after signing in; server-side session data lasts 12 hours.

__Host-Queue.XSRF - cookie; secures forms. Period: session cookie, set when entering the queue.

__Secure-Queue.LoginState - cookie; secures the sign-in process. Period: 10 minutes; set at sign-in.

77rp:selected-api-server - localStorage; remembers the selected server. Period: no automatic expiry; kept until deleted or changed.

77rp-ui-sounds-muted - localStorage; remembers the sound setting. Period: no automatic expiry; kept until deleted or changed.

Remembering preferences follows the rules in section 1. It is not by itself consent to analytics or advertising.

The service worker and push subscription deliver queue notifications after the user turns this feature on and grants browser permission.

A queue push subscription lasts 90 days. This is not the retention period of each notification shown.

The provider that delivers a notification depends on the browser and operating system. The privacy policy explains how notification-related data is processed.

The panel does not use analytics or advertising tags and does not show a separate consent banner for such tags. No banner does not mean there are no cookies or other technical records.

The following cookies are set for the panel domain and path /: • auth - keeps the sign-in session. Period: 7 days; after staff two-factor verification a new token valid for 72 hours is set. The cookie is deleted on sign-out and account deletion. • oauth_state - secures sign-in through Discord. Period: 5 minutes; set when sign-in starts and removed on return from that process. • oauth_return_to - returns you to the right page after signing in. Period: 5 minutes; set when sign-in starts. • lang - remembers Polish or English. Period: 1 year; set after choosing a language or signing in to a profile with a saved choice.

The auth, oauth_state and oauth_return_to cookies have the HttpOnly, Secure and SameSite=Lax attributes. The lang cookie has the Secure and SameSite=Lax attributes.

localStorage entries prefixed with 77panel: remember theme, animation, sound, chat, sidebar and layout settings, recently used commands (up to 10 items) and choices about push and snoozing reminders. For staff they also include filters, sorting and views.

Settings records are created when you change them and stay until deleted or replaced. Snoozing a reminder for 7 days sets when it appears again, not when all localStorage data is deleted.

Local storage also holds drafts of unsent messages and forms, plus the account identifier needed to link drafts to the user. These records are created while you use these features and are deleted on sign-out. Saving a draft does not send its content to external recipients. You can also delete these records by clearing site data in your browser.

sessionStorage may hold a technical marker that prevents a reload loop after an update. It is created when such an error occurs and is tied to the tab session.

The /sw.js service worker is registered after signing in and handles push notifications without caching panel content. A push subscription is created after you turn this feature on and grant browser permission. The panel does not use IndexedDB or Cache Storage.

Panel fonts and scripts are served from the Operator’s infrastructure. Discord avatars may be loaded directly from cdn.discordapp.com. Such a connection sends the provider your IP address and technical request information, among other things.

Going to sign in through Discord means using a separate service and the technologies it uses.

We use Cloudflare to route network traffic for the website, API and ticket panel. When handling connections, Cloudflare processes IP addresses and technical request information. The privacy policy explains how this data is processed.

The main website loads images from the external 7more7.com service and Discord avatars. Such requests may send recipients your IP address, browser information and other technical connection data, whether or not a cookie is involved.

Loading an external image does not by itself send the provider your drafts, your whole account history or all data stored in your browser.

Tebex checkout and the FiveM/Cfx.re, Steam and Discord services have their own privacy and browser technology rules. Your choice in the 77RP banner is not automatically consent to the technologies these providers use on their own services.

The 77RP privacy policy has details on data recipients, transfers outside the European Economic Area and user rights.

We update this policy when the technologies we use, their purposes, retention periods or the way settings are managed change.

If a new technology or purpose requires consent, we obtain it before it starts. Updating the policy does not replace consent.

Earlier consent given for an empty Google Tag Manager container does not authorise running any future analytics or advertising tags.

The current version of the policy is available in the Service.