How 320px.ru processes data.

1. Controller

The controller is Sole Proprietor Ayuna Purboevna Ainyukova, TIN 032004278070, PSRNIE 325784700343020, Saint Petersburg, Russia. Registration in the Russian personal-data controllers register: No. 78-26-207367.

Questions and data-subject requests can be sent to info@320px.ru.

2. Data generated during a visit

• Technical logs. The server and infrastructure may record an IP address, request time, URL, response code, user agent and technical errors to operate, secure and diagnose the site.
• Basic analytics. Yandex Metrica immediately receives the actual opened page and a cleaned traffic source. Only standard advertising tags may remain in the URL: yclid, utm_source, utm_medium, utm_campaign and utm_content. Page titles, search phrases, arbitrary parameters, clicks, goals, Session Replay and form data are not sent before permission.
• Expanded analytics. Permission enables page titles, accurate bounce tracking, click maps, outbound-link tracking and Session Replay. Form fields remain protected from recording.
• Email correspondence. When a visitor independently emails info@320px.ru, the sender address, name, message, attachments and email service data are processed to reply and work on the request.
• Diagnostic requests. The free diagnostic form (Russian) collects a website address and email, together with the request time, identifier, status, consent version and a technical repeat-submission marker. It does not ask for a name, telephone number or website passwords.

Even a basic Metrica request necessarily carries technical network and browser data, including an IP address and user agent, and may result in service identifiers being set.

Free diagnostic requests

Website and email addresses are processed with the visitor's separate consent to review public pages, send a report and discuss work requested by the visitor. Submitting the form does not subscribe the visitor to advertising.

The initial record is stored in a private queue on Beget hosting. Notifications are sent to the responsible person's two mailboxes, hosted by Beget and Gmail (Google). Email providers therefore process a copy of the request; Gmail processing may take place outside Russia. Form contents are not transmitted to Metrica.

Records explicitly marked closed are removed from the technical queue after 90 days. Unresolved requests are not automatically removed based on age. This does not delete mailbox messages, which follow section 7. To withdraw consent or request correction or deletion, email info@320px.ru.

Diagnostic page measurement

On /promo/, counter No. 100268948 immediately records the actual landing page from the main document. It receives a cleaned traffic source and only validated yclid, utm_source, utm_medium, utm_campaign and utm_content tags; search phrases, arbitrary URL parameters and form contents are not sent. Yandex receives technical network data; blockers and network failures may prevent delivery.

Separate permission enables three events without field contents: server acceptance of a request, a plugin download link click and a contact link click. Changing the choice does not create another pageview. Session Replay, click maps and automatic link tracking stay disabled on this page, and form fields remain protected from recording.

The px320_promo_analytics_consent cookie stores this page's choice for up to 180 days. Its footer settings button immediately stops expanded transmission and reopens the choice. “Basic measurement only” retains the pageview without goals. The main site's choice is stored separately.

3. How Yandex Metrica is configured

320px.ru uses counter No. 100268948. Basic measurement runs in the main document and records the actual landing page without virtual or service URLs.

“Allow expanded analytics” stores the choice for 180 days and enables Session Replay, click maps, outbound-link tracking, page titles and accurate bounce tracking. “Keep basic measurement” retains the pageview without those features.

Changing modes does not create a second view of the current page. Form-field contents are never recorded.

4. Cookies and changing the choice

The site stores px320_analytics_consent with the chosen mode for up to 180 days. Yandex Metrica may use its own technical cookies and browser storage.

The “Analytics settings” button at the bottom of every page immediately returns to basic measurement and reopens the choice. Removal of technical data already received by Yandex is governed by the counter settings and Yandex documents.

5. Purposes and grounds

• operation, security and diagnosis of the site;
• minimum aggregate visit measurement without page-level routes;
• analysis of specific content after the visitor's choice;
• replying to messages, preparing a proposal and performing agreed work;
• mandatory accounting, contract and statutory record keeping.

Technical processing and minimum statistics are limited to what is required by the controller's legitimate interest in reliable site operation. Page-level analytics follows the visitor's choice. Correspondence is processed to answer and act on the sender's initiative; contract data is processed to perform obligations.

6. Processing providers

Infrastructure and email providers are used to host the site and handle correspondence. ООО Yandex provides analytics. Under the Metrica terms, the site owner remains the controller of visitor data and Yandex acts on the controller's instructions within the service.

7. Retention and protection

Data is kept no longer than required for the stated purpose, service operation and mandatory retention periods. Correspondence is deleted or archived after the task ends unless it remains necessary for a contract, legal defence or statutory duty.

Access is limited by operational need. HTTPS, access controls, backups and infrastructure updates are used. Absolute security of data transmission over the internet cannot be guaranteed.

8. Requests and changes

A person may request information, correction, restriction or deletion and may withdraw a previous consent. Email info@320px.ru with a contact method and enough context to identify the relevant data.

This page is updated when services or processing rules change. The effective date appears at the beginning of the notice.