Privacy policy
This policy explains which personal data the website rmas.dev collects, why and how they are processed and how you can manage them. It follows the Russian Federal Law No. 152‑FZ of 27 July 2006 “On Personal Data”; the Russian version of the policy prevails. Version of 3 November 2026.
Who processes the data
The operator of personal data is Roman Vasilyevich Maslennikov, sole proprietor (INN 180401406869, OGRNIP 323183200019962), the owner of rmas.dev (the operator). Send any questions about the processing of data to hello@rmas.dev.
Which data are processed
From the contact form: your name, email address, the text of the message and the attached files, along with anything you put in the message and the files yourself.
Technical data of the submission: IP address, browser details (User-Agent), the address and language of the page the form was sent from, the date and time.
Visit statistics: Yandex Metrica is used to analyse visits. It may process IP addresses, cookie and browser storage identifiers, device, browser and operating system details, approximate location, referral sources, pages viewed, visit dates, times and duration, and activity on the website. If Webvisor is enabled, it records interactions such as scrolling and clicks. The self-hosted Umami counter may also be used: it does not set cookies or store IP addresses, but collects visit statistics and, if enabled, session recordings and heatmaps. These trackers load only after you consent to analytics.
Why
to answer your message and discuss the task and a possible collaboration;
to protect the form from spam and abuse;
to analyse visits, referral sources and activity, assess page performance and usability, and improve the website.
The data are not used for newsletters or advertising, and no decisions with legal effects for you are based on them.
Legal basis
The data of the form are processed on the basis of your consent (Article 6(1)(1) of 152‑FZ), which you give by checking the box before sending. The form cannot be sent without the consent, but you can still write directly to the contacts on the website. Yandex Metrica and other trackers installed on the website rely on separate analytics consent, given by selecting “Accept” in the cookie banner. If you decline, these trackers do not load; you can still use the website and send messages. Page delivery and protection against attacks through Cloudflare operate independently of the banner choice and require processing technical request data.
How and where the data are kept
Messages and files are kept in the content management system of the website on the server of the operator. Files are never published: only the operator can download them.
The operator gets an email about each message at hello@rmas.dev with every field of the form and the names of the files, without the files themselves. The mail server of the operator forwards a copy of the email to the operator’s Gmail mailbox (Google LLC) through the email delivery service SMTP.BZ.
The website uses the network of Cloudflare, Inc. (USA) to deliver and cache pages, provide HTTPS and protect against attacks and bots. Cloudflare processes IP addresses, browser and device details, requested page addresses, request times and other technical connection information. If Cloudflare Web Analytics is enabled, it also collects page view and performance statistics; according to Cloudflare documentation, this analytics service uses no cookies and does not track individual visitors. Analytics automatically injected by Cloudflare is controlled by Cloudflare settings and is not disabled by this website’s cookie banner.
Google LLC and Cloudflare, Inc. are US companies, so the data may be transferred abroad while these services work. By checking the consent box, you agree to such a transfer too.
Data collected by Yandex Metrica are transferred to its provider, YANDEX LLC, 16 Lva Tolstogo Street, Moscow, 119021, Russia. Automated processing includes collection, recording, organisation, accumulation, storage, correction, use, transfer for operation of the service, anonymisation, blocking, deletion and destruction. Yandex documents linked below also govern processing. Data are not sold or published; transfers to others are limited to the cases described in this policy and those required by law.
How long the data are kept
Messages, files and technical data of submissions are kept while they are needed to answer and discuss a collaboration, but no longer than three years after the last message or until you withdraw your consent, and are deleted afterwards. Your analytics choice is remembered for 180 days. This period is distinct from statistics retention: Yandex Metrica data are kept according to service settings and Yandex documents for the stated purposes, or until processing is stopped where legally required. Contact the operator about deletion of previously collected data. Withdrawal stops further collection by the relevant trackers but does not itself erase previously collected data or cookies.
Your rights
You can:
find out which of your data are processed and get a copy of them;
ask to correct, block or delete the data;
withdraw your consent to the processing.
Write to hello@rmas.dev and describe the information or action you request. For a contact form request, specify the email address used when sending it. Where necessary, the operator will request clarification to verify identity, authority and the connection to the records, to avoid disclosing data to others. Information about the presence and processing of data relating to you is provided within 10 working days of receiving the request; where permitted by law, this may be extended by up to 5 working days with a reasoned notice. Cessation, correction and deletion are carried out within the applicable statutory periods and on the relevant legal grounds; the operator explains any independent legal basis requiring continued retention. You may also turn to Roskomnadzor, the Russian data protection authority, or to a court.
Requests for analytics data
To help locate analytics data, specify the visit period, browser and, if still available, the Yandex Metrica ClientID. You do not need to enable analytics again to submit a request. An email address alone does not link a contact form message to tracker records; a matching IP address does not prove that all records belong to one person either. The operator checks available CMS, analytics and related sources and contacts service providers where necessary. The response describes the scope checked, data established as relating to you, confirmed actions and limitations. An inability to establish a reliable link or access logs in a dashboard is not presented as proof that the provider holds no data. Deletion from the live database is checked separately from files, mail, logs and backups; pending actions are not described as completed.
Protection of the data
The website and its content management system work over HTTPS. Only the operator has access to the messages and files, through a password-protected account; files are stored privately and are not available through public links.
Cookies
The essential analytics-consent-v1 cookie stores only your accept or decline choice for 180 days and is set after you choose. Yandex Metrica may use _ym_uid to distinguish visitors (1 year), _ym_isad to detect ad blockers (20 hours), _ym_visorc_* for Webvisor (30 minutes), and other cookies and localStorage entries described in its documentation. The actual set depends on counter settings. Cloudflare may set necessary technical cookies, including cf_clearance to remember a completed challenge and __cf_bm for bot protection; these do not constitute analytics consent. Use “Cookie settings” in the footer to change your analytics choice: declining reloads the page and stops the relevant trackers loading. You can remove existing cookies and local storage in browser settings; deleting the choice cookie makes the website ask again.
Service documents
Yandex Metrica cookies and browser storage
Changes
The operator may update the policy; a new version applies once it is published on this page, and its date is given at the top.