We request the data needed for orders, payment, delivery, accounts and replies. The online store neither receives nor stores full bank-card details.
1. General provisions and Controller
1.1. This Policy governs personal-data processing and protection on arm-v.ru and related Arm‑V services.
1.2. Data Controller: Individual Entrepreneur Artem Yuryevich Konovodov, Taxpayer ID 771383921182, Primary State Registration Number 317774600139642, address: apt. 85, bldg. 1, 47 Keramichesky Proyezd, Moscow 127540, Russia.
1.3. For access, correction, deletion or withdrawal requests, contact info@arm-v.ru or write to the Controller's address.
1.4. This Policy applies to visitors, buyers, account users, warranty applicants and people who contact us.
2. Purposes, data and retention
| Purpose | Data | Basis and period |
|---|---|---|
| Order placement and fulfillment | First and last name, phone, email, comment, order contents and total, pickup point and delivery data, payment status. | Entering into and performing an agreement at the Buyer's request and compliance with law. Order and settlement records are retained for statutory periods, normally at least five years after the relevant reporting year. |
| Payment and fiscal receipt | Order number, amount, email, phone, transaction identifier and status, receipt data; provider notifications may contain masked card data. | Agreement performance and accounting, tax and fiscal duties, for the applicable mandatory retention periods. |
| Delivery | Name, phone, email where needed, shipment contents and value, city, pickup point, address, delivery identifiers and status. | Agreement performance until delivery is complete; supporting records remain with the order for the mandatory period. |
| Customer account | Name, phone, email, password hash, saved pickup point, order history and technical session data. | Providing the requested service while the account is active or data is needed for related orders. Optional processing stops after a deletion request; statutory order records are retained as required by law. |
| Feedback and support | Email, message, IP address, User-Agent and request date. | Until the request is completed and then as needed to prove the reply, protect rights and comply with law, after which data is deleted or anonymized. |
| Warranty and service | Name, contacts, purchase number and date, device and fault details, diagnostic materials and request history. | Until the case is closed and then as needed for law and protection of rights, after which data is deleted or anonymized. |
| Website operation and security | IP address, User-Agent, date and time, URL, session identifiers, error and abuse-prevention events. | As needed for incident prevention and investigation, technical logs and legal compliance, then deleted or anonymized under the Controller's procedure. |
| Traffic analytics | Yandex Metrica cookies and identifiers, device, browser, navigation and action data, approximate location. | Website analysis and improvement. Retention is governed by counter settings and Yandex terms; users can restrict cookies in the browser. |
3. Legal grounds and processing operations
3.1. Grounds include entering into and performing an agreement at the data subject's request, the Controller's legal duties, consent where required, and legitimate interests that do not override subject rights.
3.2. The Controller does not request special-category or biometric data.
3.3. Automated and non-automated processing may include collection, recording, organization, accumulation, storage, correction, retrieval, use, transfer to authorized processors, blocking, deletion and destruction.
3.4. Required form fields are marked. An order cannot be fulfilled without contacts, order contents and selected delivery; other information is voluntary.
4. Recipients and processors
4.1. Data may be shared only to the extent necessary with:
- CloudPayments for payment processing and transaction status;
- ATOL Online and the fiscal data operator for electronic receipts;
- CDEK or Yandex Delivery for delivery estimates, booking and tracking;
- Yandex Maps and geocoder for city, map and pickup-point search;
- Yandex Metrica for traffic and technical analytics;
- hosting, database and email providers for operation, storage and service messages;
- public authorities where and as required by law.
4.2. Processors are required to maintain confidentiality and use data only for the agreed purpose.
4.3. Full card details are entered directly in the CloudPayments widget. The Website receives only the operation status and identifiers needed to match payment to the order.
5. Cookies, browser storage and analytics
5.1. Technical cookies support account sessions and request protection. An account session cookie may remain for up to 30 days.
5.2. Browser local storage keeps language, cart, selected delivery, last-order contacts and last-order details until site data is cleared, overwritten or deleted by the user.
5.3. With geolocation permission, coordinates are used by the browser and map or geocoding services to show nearby pickup points and may remain with the delivery selection in the browser. Exact coordinates are removed from new server order and profile records. Older technical delivery snapshots may contain them; access is restricted and they are not used to fulfill an order. Permission can be revoked in browser settings.
5.4. Yandex Metrica may set analytics cookies and receive technical visit data. Users can block or delete those cookies; checkout remains available although some analytics functions will be unavailable.
6. Localization and security
6.1. For data collected from Russian citizens, recording, organization, accumulation, storage, correction and retrieval use databases located in the Russian Federation unless law expressly permits otherwise.
6.2. The Controller uses access controls, HTTPS, session and request protection, backups, security logging and other proportionate organizational and technical measures.
7. User rights
7.1. Users may obtain information, request correction, blocking or destruction on lawful grounds, withdraw consent where processing relies on consent, and complain to Roskomnadzor or a court.
7.2. A request should state the full name, information linking the person to the data or order, the requested action and reply method. Reasonable identity confirmation may be requested to prevent unauthorized disclosure.
7.3. Withdrawal does not affect prior lawful processing and does not require deletion of data that must be retained by law or may be processed on another legal basis.
8. Deletion and Policy updates
8.1. When the purpose or legal basis ends, data is deleted, destroyed or anonymized unless retention is legally required or needed to protect rights.
8.2. The current Policy is always available at https://arm-v.ru/privacy?lang=en. New versions apply from publication and do not reduce rights retroactively.
8.3. Policy version: 2026-07-16.