Cookie policy

Types of storage

Cookies are records sent by the browser to the website with requests. Local and session storage are accessible to the page but are not automatically sent with every request.

Sessions and sign-in

The session cookie keeps you signed in between pages and is renewed when you use the website. The server session has no automatic expiry; signing out ends it. Clearing browser data may require signing in again. Temporary authentication values last up to ten minutes.

Blocking required records may prevent sign-in or a correct return from the authentication service.

Referral links

After following a link, its code may remain in the browser for up to 30 days to establish the referral relationship on subsequent sign-in. Deleting cookies does not undo a relationship already recorded.

Returning after payment

The order number may be saved in session storage so the relevant deposit can be checked after returning. Clearing data or using a different browser may prevent automatic lookup.

Server payment history is not deleted and remains available in the account.

External websites

Sign-in services, Steam and payment pages may use their own cookies. Their storage rules apply separately.

Adding analytics or advertising tools requires updating the description of technologies and available settings.

Controls

You can delete cookies and website data in browser settings. You may need to sign in again afterward. Private browsing may also limit storage.

Clearing browser data does not cancel payments or delete the server account.

Support

If storage causes sign-in or payment-checking problems, tell Telegram support your browser, device and steps. Do not send session cookies: they may grant access to the account.

Cookies and browser storage compared

Cookies belong to a website and may be sent with requests, allowing the server to recognize an active session. Do not forward cookie contents to anyone, even for troubleshooting.

Local storage retains records between visits, while session storage is used within a tab's browser session. Restoring tabs behaves differently across browsers. These mechanisms are not the game balance or the server account database.

Why sign-in can persist

After authentication, a session record allows navigation without signing in again. Ending a session, its expiry or deleting the record may require authentication again.

Short-lived records used when visiting a sign-in provider help complete the procedure you started. If storage is blocked or you return much later, you may need to restart sign-in from the website.

Referral visits

A browser-stored invitation code connects a link visit with later sign-in. It may be absent on another device or browser, or after clearing data.

If the referral relationship is already stored on the server, deleting browser data does not transfer the user to another author. The local visit record and existing account relationship serve different purposes.

Checking a payment after return

A stored order number helps the result page request information about a particular deposit. It is not proof of payment: crediting uses verified server information.

Opening payment in another browser, closing a tab or deleting session data may prevent automatic order lookup. This does not cancel payment. Check your account history and contact support with the invoice number if needed.

Changing browser settings

Browser settings let you remove data only for 555Drop or for all websites. Removing only this website's data usually preserves sign-in elsewhere. The names of settings vary by browser and device.

Blocking all cookies may prevent sign-in and some account actions. Private browsing and protection tools may limit retention or access. The browser deletes some data when a private window closes.

What clearing data does not do

Clearing browser data does not cancel completed openings, debits, payments, withdrawals or code redemptions. These are linked to the server account. Do not use clearing data to try to undo a confirmed action.

Deleting cookies is not a request to delete personal data. For account and server-record questions, contact support and refer to the privacy policy.

Payment and sign-in pages

After visiting Steam, Telegram, Google or a payment service, your browser interacts with an external website. It may create its own records under its own settings and policies.

Storage settings for 555Drop do not necessarily apply to external services. If an error occurs there, check the page address, browser messages and that service's rules.

If a feature fails

Before clearing data, save any pending payment or request number. Then reopen the page and check whether required website data is allowed. Do not send a payment again merely because a local record is missing.

Tell support the browser, device and step where the problem occurred. Do not copy entire storage contents: they may contain information granting access to your account.