Cookies and Browser Data
Technical cookies, localStorage, sessionStorage and external resources.
Edition No. 3 dated 2 September 2026
1. Cookies
| Name | Purpose | Period |
|---|---|---|
token | Main user session | up to 24 hours |
__Host-rustpp_guest | One free player search and restoration of its result. The server stores a hashed browser identifier; a network protection hash limits repeat attempts for 24 hours. The raw IP is not stored in these records. | up to 365 days; the result and browser quota are retained for up to 365 days |
The payment partner may use its own technical cookies on its secure payment page. Their contents and duration are determined by the partner’s documents shown to the User before payment.
2. Local storage
Data in localStorage may include the selected section, navigation and map state, read notifications, interface preferences, device identifiers, CCTV camera names and codes, and the Steam ID needed to separate users’ settings. This information remains until the site’s browser data is cleared.
Data in sessionStorage is stored temporarily for the current tab, for example to record onboarding dialog state. It is deleted when the tab is closed.
3. Browser extension
When connecting Rust+, the extension may temporarily store the Facepunch token in local browser storage until it has been successfully sent to Rust++. After successful transfer, the token is removed from the extension. If the operation is incomplete, the User can retry the connection or clear the extension’s data.
4. External resources
When loading avatars or game media and using connected integrations, the browser or Rust++ server may contact the relevant provider. The provider may receive standard technical request information under its own policy.
5. Managing browser data
Users can delete cookies and site data in their browser settings. Blocking necessary cookies may make sign-in, payment and certain features unavailable. Further information about data processing is provided in the Personal Data Processing Policy.