UPDATED · 2 OCTOBER 2026
Data policy
How data is handled on lazarev.systems, in the AI Sales Assistant chat, demonstration chat and workspace. This page describes the current service; processing your customers’ data is agreed separately before live channels are connected.
Who operates this website
Evgeny Lazarev, Tax ID 524917142320. Lazarev Systems is the project name; AI Sales Assistant is the product. For data-handling enquiries, contact Telegram: @Lazarevevg.
What data is used, and why
- Contact enquiries: name, email or phone, selected workflow, notes and page address, to respond and agree services.
- AI Sales Assistant website consultant: messages, conversation context and a technical session identifier are used for AI product replies, qualification and the team’s handling of your enquiry. If you provide a contact for follow-up, it is saved with your enquiry and sent to the team through the Answer_sales Telegram notification bot. Authorised team members can view the conversation in the workspace.
- Demo chat: messages, conversation context and a technical session identifier, to generate replies, retain context and review the assistant’s operation. If you request a handoff and provide contact details, they form part of the enquiry.
- Workspace: email, password hash, access settings, company details, enquiries, messages and user actions, to provide access, management and service records.
- Technical data: IP address, request times and parameters, errors and session information may be processed for operation, abuse prevention and diagnostics.
When you provide information
Submitting the form asks us to contact you using the details provided. It does not subscribe you to marketing. AI Sales Assistant processes a message when you send it. Opening the chat does not submit an enquiry to the team. The demo chat starts when you choose to use it. Use fictional test enquiries: do not enter other people’s personal data, passwords, payment credentials, identity documents or medical information. Services and customer-data processing use agreed contractual arrangements; necessary permissions and the parties’ roles are determined for each project.
Which services handle data
The website and application run on Hetzner infrastructure. To generate replies, the request and necessary context may pass through OpenRouter to the selected AI model provider; Groq may also be used as an additional AI model provider through a direct connection. Your selected contact channel, email, Telegram and a connected CRM may receive information needed to respond or hand off an enquiry. External providers may process data outside your country under their own terms. Before live customer channels are connected, providers, processing locations, access and permitted transfers are agreed separately. Do not assume demo data is processed only within your country.
How long data is retained
The current demo and website chat do not automatically delete conversations or enquiries after a fixed retention period. Records may remain after you close the tab. Resetting the chat interface does not delete server-side history. To request information, correction or deletion, contact us via Telegram: @Lazarevevg with contact or enquiry details that allow the record to be found. Do not send a passport copy unless separately necessary. Service records may be needed for contractual and mandatory record-keeping purposes; applicable periods and restrictions are clarified when a request is reviewed. Customer projects have separately agreed retention and deletion arrangements.
Cookies and local preferences
The landing page stores your language and theme preferences in browser localStorage. The AI Sales Assistant chat stores technical conversation access data in the open tab’s sessionStorage and restores messages from the server. This data enables conversation continuity. To identify enquiry sources, the tab keeps the initial page path without query parameters, the referring domain and campaign UTM tags for up to 24 hours. When you submit an enquiry, this context is attached to it so the source can be connected with later sales stages. Analytics events contain neither contact details nor conversation text. Google, Yandex and Meta advertising counters are not currently connected; separate configuration and a consent choice are required before activation. Diagnostic answers stay in the open tab and are sent only if you submit an enquiry containing them. Workspace login uses a protected essential session cookie lasting up to 12 hours. Logout and two-factor authentication are available. Clearing your browser preferences removes local settings, not server-side records.
Protection and your requests
Measures include HTTPS, access checks for company data, password hashing, and login/request limits. Enable 2FA and use a unique password to improve account security. These measures reduce risks but do not provide an absolute guarantee of data security. Use the contact above for access, correction, deletion, restriction or withdrawal of consent where processing relies on it. The scope of rights and grounds for retaining records depend on applicable law and the service concerned.