Privacy Policy

Last updated 10 November 2026.

This page explains, in plain language, what data the website yasnoseo.by (the Yasno SEO service) collects, why, where it is stored, and how you can ask us to delete it. The data is processed by the owner of yasnoseo.by. Questions and requests: support@yasnoseo.by or the contacts page.

What data we collect

The website address you check and the check result. The report opens via a unique link and is not indexed by search engines.
Email address — only if you provide it yourself and tick the consent box, so we can send you the report. We also store the role you selected (site owner, SEO specialist or agency), the date and version of the consent, and the date the address was confirmed. The consent text is on the consent page (in Russian).
Email report subscription. If you subscribe to the weekly email (it is sent every Monday): email, site address, date and version of consent, confirmation date, date of the last email, and the list of issues from the last check — so we can compare it with the next one.
“We’ll fix it for you” request. Email, phone or Telegram (if provided), a comment, the site address and a link to the report, date and version of consent.
Personal account (Cabinet). If you sign in: email, registration and last-login dates, date and version of consent, a hash of the IP address used to confirm the login. For each login (device): browser string (up to 200 characters), IP hash, login and last-activity dates. The list of sites in the account and which checks belong to them. Check summaries: date, how many issues of each severity, and issue codes — without page text and without personal data. There is no password: sign-in uses a one-time link from an email, and only its hash is stored.
Site crawl — if you start a work plan: public page URLs, titles, descriptions and text excerpts, redirect and response-status information. A fresh crawl (less than 7 days old) of the same site is reused, including for other users with the same site address. The crawl stores only public page data.
Content plan, work plan and advisor tasks — if you use them in the Cabinet. They may include page URLs, search queries (including from Search Console and Yandex Webmaster), titles, briefs, and “done” marks. Content-plan settings (site type, key pages) are stored separately and are not deleted when you disconnect Google.
Weekly search history — weekly snapshots of Search Console and Yandex data, used to compare clicks, impressions and positions.
Google Search Console connection — only if you connect it yourself in the Cabinet. Details are in the Google data section below.
Yandex Webmaster and Metrika connection — only if you connect Yandex yourself in the Cabinet. Details are in the Yandex data section below.
Technical data. To prevent abuse we store a hash of the IP address, not the address itself. Web-server logs record the date and time of the request, the page opened, the response code, the referrer and browser information. In the logs the last part of an IPv4 address is replaced with a zero (for example, 203.0.113.0).
Yandex Metrika data. The site uses Yandex Metrika with Webvisor. It uses cookies and collects visit statistics: which pages were opened, the traffic source, device and browser type, an approximate region, and on-page actions — scrolling, clicks and cursor movements. The cookies used are described in the cookie policy.

We do not collect passport data, payment data or special-category data. We store a phone number or Telegram only if you provide them in a “We’ll fix it for you” request.

Why we use the data

to check the site and show the report via a link;
to send a confirmation email and then a link to the finished report;
if you subscribed to the email report — to re-check the site once a week and send a comparison email (every Monday);
if you submitted a “We’ll fix it for you” request — to contact you about it;
if you use the Cabinet — to send a sign-in link, show your sites, check history, requests, content plan, work plan and advisor tasks, and keep you signed in on the device;
to crawl public pages of the site and build a work plan from that crawl;
if you consented — to write once about the launch of regular reports;
to protect the service from spam and attacks and to find errors;
to understand, from statistics, how people use the site and to make it easier to use.

We do not send advertising newsletters. We do not sell data or share it with other companies for their own purposes.

Yandex data (Webmaster and Metrika)

In the Cabinet you can connect Yandex Webmaster and Metrika in one step via Yandex ID. We request read-only access: information about sites in Webmaster (webmaster:hostinfo) and Metrika statistics (metrika:read). We cannot change anything in Webmaster or Metrika: add or remove a site, request a recrawl, or change a counter or goals. We never see or receive your Yandex password — Yandex issues only an access token, which you can revoke at any time.

What we take from Webmaster: the list of your Webmaster sites; the number of pages in search and of excluded pages; site issues from Diagnostics; popular search queries with impressions, clicks and average position for the last 4 weeks; sitemaps and their errors; a list of the site’s pages in Yandex search (up to 100 URLs) to compare with the sitemap. From Metrika: the list of your counters (number, name, site address); the number of visits from search engines and the bounce rate for the site as a whole and for each search engine, for the last 4 weeks and the 4 weeks before that. We do not take data about individual visitors, their actions, IP addresses or cookies from Metrika. We do not request your Yandex email or other account data (Webmaster only reports an internal user number, which is needed for API requests).

Why: to show this data to you in the Cabinet and in weekly emails about your sites, and to compare it with the sitemap and our check: which sitemap pages are missing from Yandex search, which issues Webmaster reports, whether sitemaps have errors, and whether search visits have dropped. Queries from Webmaster may also appear in the content plan and advisor tasks.

Storage: access tokens are stored encrypted in a database on a server in Russia; the encryption key is stored separately from the database. Data is refreshed once a day and kept while Yandex is connected. Weekly Yandex history is kept for 26 weeks; older snapshots are deleted when a new week is saved. The “Disconnect Yandex” button in Cabinet → Connections revokes access at Yandex and immediately deletes the tokens, Webmaster and Metrika data, and the weekly Yandex history; the same happens when you delete your account. You can also revoke access in Yandex ID: Security → App access — find “Ясно SEO” / Yasno SEO and remove access. After that, data will stop updating, and the Cabinet will ask you to reconnect Yandex; already collected data can be deleted with “Disconnect Yandex”.

Sharing: none. We do not sell Yandex data, do not transfer it to third parties, do not use it for advertising, do not show it to other users, and do not use it to train models. Yasno SEO staff do not read this data unless you ask us for help, it is needed for security, or the law requires it. Yandex (ООО «ЯНДЕКС») is a separate controller of its own data; how Yandex processes your data is described in the Yandex privacy policy.

Google data (Search Console)

In the Cabinet you can connect Google Search Console. We request one permission — view Search Console data (webmasters.readonly). This is read-only access: we cannot change anything in Search Console, submit a site for indexing, or add or remove users and properties. We never see or receive your Google password — Google issues only an access token, which you can revoke at any time.

What we access: the list of your Search Console properties; clicks, impressions, CTR and average position for the site, its pages and queries for the last 56 days; submitted sitemaps and their errors; URL Inspection results for individual pages of your site (whether the page is indexed, why not, and which URL Google treats as canonical). We do not request your email address or any other Google account data.

Why: to show this data to you in the Cabinet and in weekly emails about your sites, and to compare it with the sitemap and our check: which pages Google does not index, which pages lost clicks, and whether sitemaps have errors. We also use it to build advisor tasks, a work plan and a content plan — including page briefs, if you request them.

Storage: the access token is stored encrypted in a database on a server in Russia; the encryption key is stored separately from the database. The Search Console summary is refreshed once a day and kept while Google is connected. Weekly Search Console history is kept for 26 weeks; older snapshots are deleted when a new week is saved. The “Disconnect Google” button in the Cabinet revokes access at Google and immediately deletes the token, Search Console data, weekly Google history, content plans, work plans and advisor tasks for the sites of this connection. The same happens when you delete your account. You can also revoke access on Google’s Third-party apps with account access page. After you revoke access at Google, data will stop updating; already collected data can be deleted with “Disconnect Google”.

Transfer to Yandex Cloud. If you ask us to write content-plan briefs, we send to the Yandex Cloud text-generation service (Yandex Cloud, ООО «Яндекс.Облако») the text of Search Console queries, the page URL and the titles already collected for that page. Click and impression counts are not included in the request to the service. This is done only to prepare content-plan briefs for you. Requests go to the Russia region (ru-central1): according to the Yandex Cloud documentation, the servers of this region are located in Russia. Yasno SEO operates from Belarus, so this is a cross-border transfer (from Belarus to Russia), as is storage on Selectel servers in Russia. We send the header x-data-logging-enabled: false so that Yandex Cloud does not keep these requests or use them to train models. We do not send Google access tokens or full Search Console reports to Yandex Cloud.

Limited Use. We use data obtained from Google APIs only to show you reports and tasks in the Cabinet and in emails, and, at your request, to prepare content-plan briefs. We do not sell this data, do not transfer it to third parties except for processing in Yandex Cloud for this user-facing feature, do not use it for advertising, and do not use it to train models. Yasno SEO staff do not read this data unless you ask us for help, it is needed for security, or the law requires it. Yasno SEO’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google (Google LLC) is a separate controller of its own data; how Google processes your data is described in the Google Privacy Policy.

Where data is stored

The website, database and web-server logs are on Selectel servers in Russia. Emails from noreply@yasnoseo.by are sent through Selectel’s mail service. Yasno SEO operates from Belarus, so placing this data on servers in Russia is a cross-border transfer. Yandex Metrika data is processed by ООО «ЯНДЕКС» under the rules of the Yandex Metrika service. Content-plan briefs, as described above, are processed by the Yandex Cloud text-generation service (ООО «Яндекс.Облако») on servers in Russia (the ru-central1 region).

To measure speed, the address of the homepage of the site being checked is sent to Google PageSpeed Insights (Google LLC, servers outside Russia). Your email, IP address and other data about you are not sent there.

If you write to us at support@yasnoseo.by, the message is processed by the mail service used for that inbox. Its servers may be located outside Russia. A copy of a “We’ll fix it for you” request, including email, phone or Telegram and the comment, is also delivered there so that we can reply. Contacts are also listed at /contacts/.

How long we keep data

checks and reports — 90 days, then they are deleted together with the link;
email and consent details — up to 24 months, or until you ask us to delete them;
email-report subscription — until you unsubscribe; after unsubscribing we delete it within a day; an unconfirmed subscription is deleted after 3 days;
“We’ll fix it for you” requests — 12 months from the request date, or until you ask us to delete them;
Cabinet account, the list of sites in it, and links to checks — until you delete the account;
device login — until you sign out, but no longer than 30 days; if the Cabinet is not opened for 14 days, the login ends earlier;
sign-in link — valid for 15 minutes and once only; the record is deleted after one day;
check summaries for Cabinet history — 90 days;
Google access token and Search Console summary — while Google is connected; deleted immediately when you disconnect Google or delete the account;
weekly Search Console and Yandex history — 26 weeks; older snapshots are deleted when a new week is saved; all snapshots for a source are deleted immediately when that service is disconnected or the account is deleted;
content plan (plan items and technical records of calls to the text-generation service) — while the site is in the Cabinet; deleted immediately when you disconnect Google or delete the account;
work plan and “done” marks — while the site is in the Cabinet; deleted immediately when you disconnect Google or delete the account;
advisor tasks — while the site is in the Cabinet; deleted immediately when you disconnect Google or delete the account;
site crawl — there is no separate automatic deletion period; a fresh crawl (less than 7 days old) is reused; when the account is deleted the shared crawl remains and the link to the account is cleared;
Yandex access tokens and Webmaster and Metrika data — while Yandex is connected; deleted immediately when you disconnect Yandex or delete the account;
outgoing-email queue — 30 days;
web-server logs — 14 days, then deleted automatically;
Yandex Metrika data — under the rules of the Yandex Metrika service.

All periods, storage locations and deletion methods are also collected in a table in the data retention and deletion policy (in Russian).

Your rights

You can ask what data we have about you, ask us to correct or delete it, and withdraw consent to email processing at any time. Write to support@yasnoseo.by from the address in question, for example with the subject “Delete my data” or “Withdraw consent”, or use the contacts page. We will delete the data and reply. If you have a Cabinet account, you can delete it yourself: Cabinet → Account → Delete account. This also deletes logins, the list of sites and history, email-report subscriptions, requests, queued emails, content plans, work plans, advisor tasks, and Google and Yandex connections (we revoke access at Google and Yandex). When the account is deleted, a shared site crawl remains and the link to the account is cleared. You can unsubscribe from weekly email reports in one click via the link in any email. Withdrawing consent does not stop you from checking sites: the report is still available via the link, it just will not be emailed.

If you believe we are violating your rights, you may contact the data-protection authority in your country or a court.

Cookies

The site uses a technical cookie to protect forms, a Cabinet sign-in cookie (only if you are signed in), and Yandex Metrika cookies. Yandex Metrika does not run on Cabinet pages. The Metrika counter loads as soon as the page opens; the “Got it” button in the notice only hides the notice. Which cookies are set, for how long, and how to turn them off is described in the cookie policy. The site works without Yandex Metrika cookies.

Changes

If this policy changes, the new version will appear on this page with a new date.