320px / WordPress

Personal data processing policy

How wp-content.ru handles project enquiries, voluntary review requests, and the optional analytics choice.

Revision · 10 Sep 2026

Controller and policy scope.

Controller: ИП Айнюкова Аюна Пурбоевна, Russian tax ID 032004278070, registration ID 325784700343020, Saint Petersburg, Russia. Data contact: wordpress@320px.ru.

This policy covers project messages sent through wp-content.ru. It is not consent and does not automatically cover client data in separate projects.

Project form

Purpose, data, and retention.

  • Purpose: respond to an enquiry and discuss a possible project.
  • Data: name, reply address, optional URL, message, consent version, and minimized abuse-prevention data.
  • The encrypted enquiry is retained for up to 90 days and can be deleted sooner on request.
  • Attachments, passwords, keys, and sensitive exports are not accepted.

Site Audit review

Only the confirmed preview is sent.

  • The default is a name, email, and message with no report data.
  • An administrator may instead choose a sanitized summary, up to 20 selected findings, or the complete redacted report.
  • Site address, local identifiers, private screenshots, and the browser bundle are not accepted.
  • The request is encrypted for up to 90 days. Its response provides a private deletion route with a separate confirmation.

Recipients and infrastructure

Protected storage and email notifications.

Enquiries and review requests are encrypted outside the public wp-content.ru directory. For the ordinary project form, the name, email, optional public URL, and message are also sent to the operational wordpress@320px.ru mailbox on Beget infrastructure so the team can reply. The mailbox copy is deleted no later than the end of the 90-day retention period.

A Site Audit review notification contains only an opaque ID: its contact, message, and report data are not sent by email. Only an authorized operator can open the protected record.

Analytics and cookies

The basic view records the actual landing page.

Yandex Metrica immediately receives the actual opened-page URL, a cleaned traffic source, and only standard advertising tags: yclid, utm_source, utm_medium, utm_campaign, and utm_content. Arbitrary parameters, fragments, clicks, page titles, and form data are not sent in basic mode. The network request provides Yandex with technical connection and browser data, and Metrica may create first-party identifiers.

Click maps, link tracking, page titles, and accurate bounce measurement remain disabled until permission. Permission enables these expanded features without a second page view. Session Replay, form recording, ecommerce, and custom goals remain disabled; form fields are additionally protected from recording. wp320_analytics_consent stores the choice for up to 180 days. See the cookie policy for details.

Rights

Access, correction, or deletion request.

Email wordpress@320px.ru and include the request ID when available. A Site Audit review response also includes a private deletion route. Before disclosure or correction, the controller may request reasonable verification to avoid giving data to another person.