Holder privacy policy

Data used by each feature

Login and settings. Telegram login uses the Telegram identifier, available name and username, and their association with a Holder account. Account settings, favorite assets and other saved preferences support the selected features and synchronization after login.

Reviews. A review contains text, a public name, date and a rating if provided. Contact information, technical submission details and a consent record may be stored separately. Published text, names and ratings can be viewed by other visitors.

Feedback. The form submits the message, selected topic, page URL, contact for a reply and any images you attach. Technical submission details include the IP address, browser information and the account identifier for a logged-in user.

Search and visits. The search log may include the query, browser language, result count, selected result, time, IP address and logged-in user identifier. Servers and connected technical services also receive connection data when pages load. This supports search, error analysis, statistics and protection against abuse.

Purposes of processing

Data supports login and saved preferences, publication of submitted reviews, handling feedback, operating and improving search, usage statistics and service protection. The specific data depends on the feature: reading a public page, logging in, posting a review and sending feedback involve different information.

Where consent is required for a particular activity, it relates to that action or setting. The existence of this policy does not amount to unconditional consent for every purpose. Processing may also be necessary to provide a requested feature or meet applicable legal obligations.

Public text and external services

Do not include information in a public review that you do not want disclosed. A review taken from an external public post may include a source link. Correcting the Holder copy does not alter the original on another platform.

External services support particular functions: Telegram for login and operational messages; Google Analytics and Yandex Metrica for analytics; technical providers for website hosting and communication. Where notifications are enabled, feedback text and attachments may be sent to the team through Telegram.

A portion of review text without author-selected stars may be sent to an external AI service for sentiment analysis. This does not verify the events or create a rating on behalf of the author. Do not include passwords, seed phrases, API keys or unnecessary personal information in submitted text.

External providers have their own processing terms and may use infrastructure in different countries. Following a link to an exchange or another service subjects you to that service's policy. Holder does not claim that all listed data always remains with a single operator or in one country.

Cookies, local storage and retention

Cookies support login sessions, display currency and settings. Recent search and viewing history is stored locally in the browser, separately from the server-side search log. The cookie policy explains analytics components and controls.

Retention rules differ by record. The search-log cleanup mechanism removes IP addresses from entries older than 90 days; it does not necessarily delete the query or other fields. Feedback cleanup is configured to clear IP and browser details after 90 days and separate attachments after 180 days. These operations depend on scheduled jobs running and do not automatically delete accounts, reviews or entire feedback messages on the same timetable.

Account data and public submissions may remain while the relevant feature or record is in use. Contact the operator about a particular record and its retention. Backups and technical-provider logs may have separate retention periods.

Requests and controls

You can request information about your data, correction, deletion, restriction of processing or withdrawal of consent by emailing me@holder.io. Identify the data and feature concerned, and include the URL for a publication. Protecting the data may require confirmation that you are associated with the account or request.

The scope and handling of a request depend on applicable law and the grounds for retention. Deleting data required by a feature may make that feature unavailable. Do not send a full identity document, password or access key unnecessarily; first explain your request.

Use feedback to report personal information exposed in public text. The current policy is published here; consult it when the features you use change.