Cookies and local storage

Sessions and preferences

• hl_consent records the cookie-banner choice and its version, with a one-year lifetime.
• wordpress_* and wp-settings-* support WordPress login and settings. Their lifetime depends on the cookie and session type.
• currency_code stores the selected display currency for up to one year.
• holder_user_settings stores visitor preferences, such as favorites; the server mechanism can set a lifetime of up to two years. Supported preferences may be transferred to the account after login for synchronization.

Blocking these entries can reset currency, preferences or login state. Account storage differs from cookie storage: deleting cookies does not delete account data.

Analytics and your choice

Google Analytics and Yandex Metrica load after you select “Accept”. Holder does not load these tags before a choice or after a saved rejection. Analytics permission does not grant Google advertising storage, advertising user data or ad personalisation.

“Decline” saves a rejection. “Cookie settings” in the footer reopens the same choice. On withdrawal, Holder disables Google Analytics collection and stops the Metrica counter on the open page, including its queued initialisation. Accepting again enables analytics. Withdrawal cannot undo requests already sent or delete history held by a provider.

The choice is stored in hl_consent with policy version v2 for up to one year. A material change asks for a new choice rather than carrying over an earlier acceptance. Without saved permission analytics stays off, including when Global Privacy Control is present. An explicit saved choice takes precedence.

Analytics cookies such as _ga, _ga_* and _ym_* support statistics. Metrica can record page interactions, clicks and session replay when Webvisor is enabled. Loading a tag sends connection information to the provider. Rejecting stops further tag activity but does not erase all previously created records; these can be cleared through the browser’s site data settings.

Recent history and server-side search

The hl_recent localStorage entry contains recent searches and viewed items for search suggestions. It is a separate local history; entries older than 90 days are excluded when the feature processes it. You can clear it through the browser's site-data controls.

Search also has its own server-side log. It may include the query, selected result and technical fields, including a logged-in user's identifier. Clearing localStorage therefore does not delete the server record. See the privacy policy.

Important news read status

Entries named holder:notifications:v1:guest:news:* in localStorage remember which important news you have read on this device. This prevents the red indicator from reappearing for an opened article, including its translation. Each entry contains an article identifier and timestamps. It is not sent to the server or synchronized across devices or accounts. Entries expire up to 14 days after publication and are removed when the feature runs. Clearing site data resets these marks. If persistent storage is blocked, the feature uses tab storage or memory for the current page.

holder:notifications:v1:preferences:news-muted stores whether important-news notifications are turned off on this device until you change the setting or clear site data. It does not change account price alerts and is not sent to the server. If localStorage is blocked, the choice applies only to the current page.

Providers and contact

For provider information, see the Google privacy policy and Yandex privacy policy. A partner's own rules and settings apply after you visit its website.

Send Holder data questions to the operator, individual entrepreneur Vladislav Aleksandrovich Chalin, at me@holder.io. For a cookie issue, include your browser, selected setting and observed behavior.

Revision: 23 October 2026.