AIWeavioAUTOMATION PLATFORM
Legal

Personal Data Processing Policy

Version dated November 11, 2026.

This policy explains how data is processed on aiweavio.com, in the account dashboard at cp.aiweavio.com and in the AIWeavio application, why it is needed and how users can manage their data. The controller is the owner of the AIWeavio service, Russian taxpayer identification number (INN) 370207907687. For personal data enquiries: support@aiweavio.com.

1. Data we receive

1.1. Account data: username, email address, password hash, account identifier, registration and login dates. These are used for registration, authentication, email verification and access recovery. Account passwords are stored as hashes; during login, the password is transmitted over a secure connection for verification.

1.2. Plans, payments and AI credits: selected plan, access period, payment date, amount and status, purchase identifiers, and credit grants and charges. Users enter bank card details on YooKassa's payment service.

1.3. Technical data and analytics: IP address, browser or client information, sessions, request times and outcomes, visited pages, referral sources, campaign tags and approximate region. Analytics uses a visitor identifier and an IP hash; events may be linked to the account after login.

1.4. Support enquiries: messages, conversation identifiers and materials submitted to resolve an issue. AI assistant and PingLess processing is described below.

2. Why data is used

2.1. Data is used to operate accounts, provide free and paid features, account for AI credits, deliver service emails, provide support, diagnose faults, assess website usage and prevent abuse.

2.2. Processing necessary to enter into or perform the agreement relies on that legal basis. Legal obligations and other purposes rely on their respective lawful grounds. Consent is requested separately where required. Advertising messages are sent only with the necessary prior consent; this policy does not replace that consent.

3. Cookies and browser storage

3.1. The website uses cookies for login and session management, and a visitor identifier for analytics. Browser local storage may contain preferences, referral information and support chat history.

3.2. Cookies and local data can be deleted or restricted using browser settings. This may require signing in again and make local chat history or preferences unavailable. Deleting browser data does not automatically delete server records.

4. AI assistant

4.1. To generate a response, the selected AI provider receives the request, relevant conversation history and task context, such as the scenario, tool results and attachments. When visual features are used, this context may include images of the selected window or screen area within the permitted settings.

4.2. For the built-in assistant, AIWeavio's server stores responses, request identifiers and hashes, technical statuses, and token and credit usage information. This supports result delivery, repeat requests and usage accounting. If users connect their own AI provider, processing on that provider's side is governed by its terms.

4.3. Before sending context or images, users should remove unnecessary personal data and secrets. Provider retention and possible use of requests, including model training, depend on the selected service's terms and settings.

5. PingLess

5.1. PingLess processes account, session, selected game or application and node identifiers, network addresses, the connection's public key, connection times and other necessary technical exchange parameters. As of this revision, PingLess nodes are located in Germany, Poland and the Netherlands; the specific node depends on the selected connection.

5.2. Only traffic from selected games and applications in the supported list passes through PingLess. Other traffic uses the normal connection outside PingLess. Connection data supports routing, authentication, diagnostics and service security.

6. Data recipients

6.1. YooKassa and payment participants receive purchase information, payment amounts and identifiers and, where necessary, the email address for a receipt.

6.2. The smtp.bz email service receives the recipient address and service email content, including verification links or codes.

6.3. Telegram receives messages and conversation identifiers when enquiries are handled through the support integration.

6.4. The AI provider and server infrastructure suppliers receive data necessary to process requests, host services and exchange network traffic. Access is limited to the relevant task and requires a lawful basis. Using foreign suppliers or nodes may involve cross-border transfers, which are subject to specific legal requirements.

6.5. Public authorities and other authorised recipients receive data where there is a legal basis for disclosure.

7. Retention and security

7.1. Account data is processed while the account exists and service access is provided. Support correspondence is retained to resolve enquiries and related claims; AI assistant records support result delivery and replay, usage accounting and charge reviews; analytics and technical logs support statistics, diagnostics and security. Retention is limited by the relevant purpose and legal requirements.

7.2. Once the purpose has been fulfilled or a lawful request received, data is deleted or processing ends in accordance with applicable law. Certain payment, obligation and claim records may be retained where there is an independent lawful basis. Backups are also considered when fulfilling deletion requirements.

7.3. Security measures include secure connections, hashed passwords, session management and access controls for administrative functions. Processing when collecting Russian citizens' personal data is organised in accordance with Federal Law No. 152-FZ.

8. Your rights

8.1. You can request information about processing and access to your data, corrections, cessation of processing or deletion where there are lawful grounds. Email support@aiweavio.com with your account or information allowing us to identify your conversation or purchase. Verification of identity or authority may be necessary to protect the data.

8.2. Processing information is provided within 10 working days of receiving a duly submitted request. Where permitted by law, this may be extended by up to 5 working days with a reasoned notice. Corrections and deletion follow the respective statutory deadlines.

8.3. You may withdraw consent. This does not end processing supported by another lawful basis. The controller's actions may be challenged before Roskomnadzor or a court.

9. Policy changes

9.1. Revised versions are published on this page with an updated date. A policy change alone does not authorise using data for incompatible purposes; where new processing requires consent, it is requested separately.