Skip to content
Back

Personal Data Processing Policy

Version 2026-11-15.3. Effective from November 15, 2026.

Revision dated 15.11.2026 (version 2026-11-15.2, replaces 2026-11-15.1): the Russian brand of the service was renamed and the Telegram bot is now @PyatnitsaAI. The terms, the Service Provider's details and prices did not change.

1. General provisions

This Policy defines personal data processing and protection procedures at real dots (formerly BotSeller). Operator: Individual Entrepreneur Ivan Sergeevich Korotchenya, Tax ID (INN) 772879669220, Individual Entrepreneur Registration Number (OGRNIP) 326774600582095, correspondence address: Office 645, Floor 64, Building 1, 8 Presnenskaya Embankment, Moscow, 123317, Russia, e-mail: ivan.korotchenya@gmail.com.

The Policy applies to the market.dipwriter.eu website, the dashboard, web chats at chat.dipwriter.eu, the real dots app for Windows, macOS and Linux, Telegram bots, the mini app, the support service and related products. The Operator is guided by Federal Law No. 152-FZ and other applicable laws.

2. Data subjects and categories

  • Website visitors: IP address, browser and device information, request date and time, technical logs, necessary localStorage/sessionStorage data, and, with analytics consent, an anonymized visitor identifier, campaign link tags, landing page and referrer, page views, and website element clicks.
  • Account users: email address, irreversible password hash, email verification status, and sign-in information for website-created accounts; Telegram ID, chat ID, username, and name for accounts created or verified through Telegram. A Telegram account may have no email or password. Passwords and one-time codes are not stored in plain text.
  • Customers: selected product and plan, subscription status and duration, auto-renewal consent, charge amount and frequency, technical identifier for payment details saved by the bank, orders, payments, top-ups, balance and transaction log, refunds, promo codes, referral rewards, and receipt details. The Operator does not receive full bank card details.
  • Integration users: phone number, technical Telegram session, identifiers of bots, groups, topics, and business connections, settings, and connection status.
  • Service content: requests, AI responses, files, Listen-mode recordings and transcripts, assistant memory, support and bot messages, chat/topic names and related metadata that the user provides or allows the Service to receive.
  • Evidence of consent and security: versions of accepted documents, acceptance time and source, sign-in events, errors, usage information, and attempted abuse.

3. Purposes and legal bases

  • Registration, identification, sign-in, and account maintenance: data subject consent and entering into and performing a contract.
  • Providing trial access and AI features, creating a workspace at the user's request, connecting Telegram, storing history, executing commands and support — consent, performance of the contract and the legitimate interest in keeping the Service working.
  • Payments, refunds, receipts, accounting, and tax records: contract and statutory obligations.
  • Service notifications, support responses, and security messages: contract performance and legitimate interest. Advertising is sent only with separate prior consent.
  • Fraud prevention, incident investigation, backups, and logging: the legitimate interests of the Operator and users, and security obligations.
  • Processing third-party data in user content: documented instructions from the user as controller of that data and the user's lawful basis.

4. Processing operations and methods

Processing is automated and, for support inquiries or incident investigations, may involve an authorized person. Operations may include collection, recording, organization, accumulation, storage, updating, retrieval, use, transmission, anonymization, restriction, and deletion.

real dots may automatically route a request to a selected AI model, track limits, and deliver a response. The Operator does not make decisions producing legal consequences for individuals solely on the basis of such automated processing.

5. Cookies, browser storage, and web analytics

First-party analytics assesses acquisition channel effectiveness and identifies where users cannot complete an action. The legal basis is visitor consent and, for abuse prevention, the Operator's legitimate interest.

A cookie notice appears on the first visit. “Accept” allows Yandex Metrica and Google Analytics to load. “Necessary only” stops analytics collection, deletes the bs_vid cookie, web analytics cookie identifiers, and related browser storage entries, and prevents third-party counters from loading. You can change your choice anytime through “Cookie settings” at the bottom of the website and of the app download page. You can also refuse in your browser settings by blocking or deleting cookies. Refusal does not restrict access to the Service.

Previously collected anonymized visit records may be retained for the period specified in Section 8. Account-linked records are deleted on request under Section 10.

  • Strictly necessary: authentication, security, unfinished sign-in state, referral attribution, and interface state. These are always used because the Service cannot operate without them.
  • First-party source analytics: the bs_vid cookie with an anonymized random visitor identifier (retained for 2 years), campaign link tags (utm_source, utm_medium, utm_campaign, utm_content, utm_term, yclid, gclid, ysclid), landing page URL, referring page URL, device type, page views, and website element clicks. The random identifier is not inherently linked to an individual; after sign-in, it is linked to the account so the Operator can identify the customer's acquisition channel.
  • Third-party web analytics load only after the visitor's separate consent in the cookie notice: Yandex Metrica (YANDEX LLC, Russia) and Google Analytics 4 (Google LLC, USA), if it is enabled on the website. Before consent, their scripts are not loaded and no requests are sent to their servers. They receive anonymized visit information: page address and title, referral source, device and browser type, approximate location based on the IP address, time on the website, clicks on website elements, and completed goals (for example, a submitted sign-up form, a started payment, or a Download click), without email, name, or chat content. To do this, they store their cookie identifiers in the browser (_ym_uid, _ym_d, and related cookies for Yandex Metrica; _ga and _ga_* for Google Analytics) for up to 2 years. On public pages, Yandex Metrica also builds click maps and records page activity (Session Replay): cursor movements, scrolling, clicks, and viewed page content.
  • Session Replay does not capture what is typed into input fields: all fields are marked as non-recordable and shown as asterisks. Third-party web analytics are not loaded in the account dashboard, the mini app, web chats at chat.dipwriter.eu, or the real dots desktop and Android apps; Session Replay and click maps are turned off on the page shown after payment.
  • Google Analytics is configured without advertising features: Google signals and ad personalization are turned off, and advertising cookies are not used. Google Analytics data is processed on Google LLC servers, including in the USA, which is a cross-border transfer; the Operator enables Google Analytics only in compliance with Article 12 of Federal Law No. 152-FZ.

6. Data localization and processing locations

The Service's central database holds account and authentication data, payment and subscription data, and service metadata: request time and status, the selected model, limit usage, technical identifiers and workspace status. The text of assistant conversations is not stored in the central database.

Assistant conversations, files, transcripts, assistant memory and the Telegram session are stored in the user's separate workspace (an isolated container), including during trial access. A workspace is created when the user starts connecting it; until then the Operator stores only account data. Access to data and backups is restricted.

To produce a response, the request text and the context it needs — parts of the conversation, the content of attached files and memory — are sent from the workspace to the provider of the selected AI model (Anthropic for Claude models, OpenAI for GPT models) and processed on its servers outside Russia under the provider's terms. For automatic model selection, the last few messages of the conversation in shortened form, with recognized keys and passwords removed, may be sent through the Operator's central service to a third-party model selection service; the Operator does not store them.

Audio for transcription is processed by a speech recognition service on the Operator's servers; the temporary file is deleted after processing and the transcript is saved in the workspace. Questions to the website assistant and support requests are processed by the Operator's central system, including with an AI provider, and are stored separately from the workspace.

Features chosen by the user may involve processing in foreign systems, including Telegram, AI providers and dedicated work environments. The route depends on the connected services and the user's instructions; a Russian entry point to the website does not mean that all data is stored in Russia.

7. Recipients and cross-border transfers

The Operator transmits only data necessary for a particular feature, enters into required agreements, and assesses recipients. Transfers to a foreign country are cross-border transfers and comply with Article 12 of Federal Law No. 152-FZ, including prior notification of Roskomnadzor where required. If a lawful route cannot be ensured, the relevant feature must be restricted.

Third-party platform policies apply to their independent processing. Users may decline optional integrations or choose an available processing route.

  • Telegram, if the user has connected it: authentication, message delivery, bots, the mini app and Telegram Business.
  • AI model providers (Anthropic, OpenAI and the website assistant's provider): processing text, files and context when the user chooses the relevant Service feature.
  • A third-party model selection service: the last few messages in shortened form without recognized keys and passwords, used only for automatic model selection.
  • Hosting, cloud infrastructure, and dedicated work environment providers: hosting, storage, backups, and technical data processing.
  • Transactional email providers: delivery of verification codes, access recovery, and mandatory service notices.
  • TBank JSC, the online cash register operator, and banks: payment, SBP, receipts, refunds, and fraud prevention once payments are connected.
  • xRocket processes cryptocurrency payments when selected: the invoice identifier, amount, currency, payment status and technical URLs used to confirm payment.
  • YANDEX LLC: anonymized visit data for the website and the app download page, completed goals, and session recordings (Session Replay), if the visitor consents to web analytics. Processing takes place on infrastructure in the Russian Federation under Yandex Metrica's terms.
  • Google LLC (USA): anonymized visit data for the website and the app download page and completed goals, if Google Analytics is enabled on the website and the visitor consents in the cookie notice; the data may be transferred outside Russia and is processed under Google Analytics terms.
  • Government bodies and other parties: only where transmission is required by law or necessary to protect rights.

8. Retention periods

Once the purpose is fulfilled, data is deleted, anonymized, or restricted unless further retention is required by law, a dispute, or an active contract.

  • One-time email verification or password reset codes: up to 10 minutes, with only a protected verification value stored. Telegram sign-in, recovery, or connection requests: up to 5 minutes and until the first confirmation.
  • The text of assistant conversations is not stored in central telemetry. History, files, transcripts and memory are kept in the user's workspace; service metadata and limit usage are recorded centrally.
  • Trial access: when it ends, the workspace is stopped and kept for 14 days, then deleted together with its data. If the user pays for a plan within that period, the workspace and data are kept.
  • Paid subscription: when the paid period ends, the workspace is stopped and kept so that work can continue after renewal. If payment for the current period is refunded, the workspace is deleted together with its data. The workspace and data can be deleted earlier on request as described in section 10.
  • Temporary file transfers: generally up to 7 days unless another period is shown to the user.
  • Account, integration, and support data: while the account is active or the data is needed for its purpose, then deleted or minimized, taking the applicable limitation period into account.
  • Payment, fiscal receipt, and accounting documents: for the statutory retention period.
  • Web analytics records (visits, referrals, clicks): up to 24 months, then deleted or aggregated without a visitor identifier.
  • Consent evidence and security logs: as long as needed to demonstrate lawful processing and protect rights.

9. Data subject rights

  • Receive information about processing, sources, purposes, legal bases, retention periods, and recipients.
  • Request correction, restriction, or deletion of incomplete, outdated, inaccurate, unlawfully obtained, or unnecessary data.
  • Withdraw consent and object to processing based on legitimate interest.
  • Challenge the Operator's actions before Roskomnadzor or a court and use other remedies available by law.

10. Requests and withdrawal of consent

Send an email to ivan.korotchenya@gmail.com with the subject “Personal data.” Include your Telegram ID/username or account email, your request, and information sufficient to verify your identity without collecting excessive data. Requests are handled within statutory periods.

Withdrawing consent does not affect the lawfulness of previous processing. After withdrawal, the Operator stops processing based solely on consent unless another legal basis exists; this may prevent sign-in, assistant operation, or support.

11. Security and incidents

The Operator restricts access and uses authentication, logging, backups, component updates, isolated work environments, and contractor oversight. Users should grant integrations only necessary permissions and avoid sending secrets in ordinary messages.

In an incident, the Operator takes steps to contain it, investigate it, and notify the competent authority and affected individuals where and within the timeframes required by law.

12. Policy updates

Policy version: 2026-11-15.3, effective from November 15, 2026. The current text is always available at market.dipwriter.eu/privacy. Material changes are communicated to users. If purposes change or new consent is required, it is requested separately.

Revision 2026-11-15.3 added cookie, Yandex Metrica, and Google Analytics details to Section 5. The User Agreement and the personal data processing consent (version 2026-11-15.2) did not change, so you do not need to accept them again.