Legal
Cookie Notice
Cookies are small files a site asks your browser to keep so it can recognise a visitor on the next request. Here is exactly what hack.sale uses, why, and why different scripts follow different rules.
1. Two modes, not one
The Site deliberately runs a split regime, which is worth explaining, because the web usually offers one of two extremes: everything behind a consent wall, or no banner at all.
| What | When it loads | Why |
|---|---|---|
| Traffic counter (Yandex.Metrica) | always, no prompt | anonymised measurement, processing localised in Russia |
| Support chat (Jivo) | only after explicit consent | third-party widget carrying a conversation, i.e. substantive data |
| Record of your choice | after you answer the banner | so you are not asked on every visit |
The reasoning is simple. Counting how many people opened a page is measurement. Attaching a third-party widget that a person will type into, possibly leaving contact details, is something else entirely. We chose not to flatten that difference for the sake of a tidy rule.
2. What the Site stores itself
The Site sets no cookies of its own. The only thing it keeps in your browser is your answer to the consent banner, and it lives in local storage (localStorage, key hs-consent) rather than in a cookie.
The difference is practical, not terminological: unlike a cookie, that record is never sent to the server on any request. Its only job is to stop the banner reappearing.
No advertising, affiliate or tracking cookies are set.
3. Analytics cookies
Yandex.Metrica (counter 96930918) sets its own cookies — _ym_uid, _ym_d and relatives. Their purpose is to tell a returning visit apart from a new one, so that one person is not counted as ten.
The data is anonymised: the counter sees a device, a referrer and a path through the pages, not an identity. Yandex LLC is the controller of that data.
You can stop the collection in any of these ways:
- block cookies in your browser, globally or for this domain;
- turn on Do Not Track, which the counter honours;
- use a blocker — the Site is fully functional with the counter absent.
4. Support chat cookies
The Jivo widget sets the cookies it needs to hold a conversation: a session identifier, window state, and the binding to your message history.
None of them appear until you press “Accept” on the banner — until then the widget script is never attached to the page. Declining means there is no chat on the Site; email, Telegram and Discord remain available for reaching support.
5. Withdrawing consent
There is no separate “withdraw” button. Withdrawal is done by clearing this site’s data in your browser:
- open your browser settings, privacy section;
- clear cookies and site data (local storage) for hack.sale — the consent record lives in the latter;
- reload the page: the banner returns and you can answer “Decline”.
After withdrawal the support chat will not load. Everything else — catalog, knowledge base, search, product pages — carries on unchanged, since none of it needs cookies at all.
6. Cookies on external platforms
Visiting Digiseller, Telegram, Discord, YouTube or any other external resource is governed by their own rules. The Site has no influence over the cookies they set on their own domains.
Checkout happens on the payment service’s side, so its cookies appear there rather than here.
7. Changes
If the set of cookies changes, this page is updated before the change takes effect. The revision date is in the header. Related documents: Privacy Policy and Legal Information.