Privacy policy & cookies
Plain-language information on how we process personal data: what we collect, why, where it is stored and how to withdraw consent.
1. Who we are
The Hits.ru website and personal data operator is ООО «НОВЫЕ ИНФОРМАЦИОННЫЕ СИСТЕМЫ» (Russian LLC), tax ID 7729697022. Contact: info@one.ru, +7 (903) 755-33-76. This policy applies to https://hits.ru/ and describes processing under Russian Federal Law No. 152-FZ on personal data.
2. What data we use and why
- Requests: name, email, phone or Telegram, message, services, budget, deadline, language, page without query parameters, date, request ID and consent version, to reply, prepare a quote and arrange a contract.
- Chat: messages, selected language and consent confirmation, to answer service questions. Before separate consent, messages are processed only in the browser.
- Security: connection IP address, essential session, time and request counters. The application stores an HMAC instead of the IP; the web server may keep a separate access log.
3. Cookies and local storage
No advertising cookies, analytics or third-party counters are used. The hits_guard cookie binds a security token to the session: HttpOnly, SameSite=Strict and Secure over HTTPS. Language, theme and notice preferences use localStorage; selected services and the last submission time use sessionStorage. Chat text stays in tab memory. See the cookie policy for details and preference removal.
4. Links to other sites
The site loads no third-party fonts, scripts, players or counters. Following an external link connects you to that service, which processes data under its own rules.
5. Who receives your data
Authorised staff and the hosting provider have access as needed. Requests are first written to private server storage; a notification with the name, contact and description is then delivered to the team through the he.ru HTTPS proxy to Telegram. This is delivery, not public disclosure, and is covered by the separate consent. To contact us without Telegram, use info@one.ru.
If enabled by you, server chat uses the operator’s own model, with no automatic forwarding to third-party cloud AI providers. Messages are not added to the knowledge base or stored by the application as chat history. Consent does not replace the operator’s obligations concerning Russian database localisation and cross-border transfers when foreign services are used.
6. How long we keep data
Primary requests and consent evidence are retained on the server for up to 30 days, with scheduled and API-triggered cleanup. Contract records may be kept separately for statutory periods. Team notifications are deleted under internal procedures when their processing purpose is fulfilled. Request counters are removed within two days and essential sessions after two hours of inactivity. Browser preferences remain until deleted; chat history remains until cleared or the tab is reloaded.
7. Your rights
Processing relies on separate consent for requests or server chat, steps requested before a contract, contractual performance and legal obligations. Technical security serves the operator’s legitimate interests with due regard to your rights. Operations include collection, recording, storage, correction, use, access for authorised recipients, blocking, deletion and destruction.
You may obtain processing information, request correction, blocking or deletion, withdraw consent and complain to Roskomnadzor or a court. Email info@one.ru with a request ID or information needed to locate it. Responses and cessation follow statutory deadlines; records may be retained where another lawful basis applies.
8. Children
Our services are for adults. We do not knowingly collect data from children without the consent of a parent or guardian.
9. Faces, voices and likeness
When content features you or someone you represent, we ask for written consent to film, use the voice and publish. We clone a voice only with separate written consent.
10. Changes to this policy
Controls include HTTPS, private storage, request size and rate limits, source checks, session-bound tokens and data minimisation. The operator manages access, cleanup, backups and incident response. The current policy is published here. Material changes to processing purposes or scope require an appropriate basis and, where necessary, new consent.
Last updated: 2 November 2026