SEO Control

Privacy Policy

How SEO Control handles your information. Last updated October 24, 2026.

SEO Control helps you check public websites and, when you choose, view reports from Google Search Console and Google Analytics. The service is operated by Maksim Streltcov, based in Latvia. For privacy questions and requests, contact [email protected].

Information we process

  • Account and device information. We create an account and device identifier when you start, even if you do not sign in. We store a protected device credential, platform, settings and activity needed to keep your sites and results available. If you choose Apple or Google sign-in, we receive the provider identifier and the name or email the provider supplies. Apple may supply a private relay email.
  • Website checks. We process the website addresses you enter, response status, page titles, links, metadata, extracted technical facts, findings and availability history. The public audit profile stores extracted facts rather than complete page bodies. Addresses and page text can contain personal information; avoid submitting private documents, access tokens or sensitive information in URLs.
  • Optional Google reports. We receive the resources you can access and save reports for the property you select. Search Console reports include dates, clicks, impressions, search queries, page URLs and indexing information. Analytics reports contain aggregate traffic, engagement, page paths and query strings, and aggregate recent activity. We do not request individual visitor identifiers or individual event histories. Connecting Analytics does not install a visitor tracker on your site.
  • Notifications, feedback and support. If you enable push, we store your push token and notification preferences. If you send feedback in the app or contact support, we receive the message, any screenshots and, if you allow it, app and device details. Do not send passwords or authorization tokens.
  • Security and operation. Our infrastructure processes connection IP addresses and request metadata. The application uses hashed rate-limit identifiers for abuse prevention. A hash is still treated as potentially identifying information. We retain limited operational logs and backup copies as described below.

Why we use information

We use this information to provide the features you request, connect your devices, show reports and their measurement dates, deliver enabled notifications, answer support requests and protect the service. Where applicable, requested service processing supports our agreement with you; optional Google access and notifications follow your choices; security processing supports our legitimate interest in preventing abuse. We do not sell personal information, use it for advertising, or combine it with advertising profiles.

Google access and your choices

Google connections are optional. We request only webmasters.readonly and analytics.readonly. These permissions let us read permitted resources and reports; they do not let us edit your site or Google settings. We never ask for your Google password. Authorization tokens are encrypted on the server. Google report data is used to provide your requested reports. We do not use it to train general-purpose models. Our use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

Disconnecting one source stops its updates and hides its reports in SEO Control. If another Google source remains connected, we keep the shared authorization needed for that source. Local disconnection does not necessarily revoke a permission in Google. You can remove SEO Control in your Google Account connections; this can stop both sources belonging to this application project. Disconnecting the last source requests a provider revoke. External revoke is confirmed separately and may be detected by the next request or refresh, rather than immediately.

Retention and deletion

InformationRetention and removal
Active account and private reportsKept to provide the service while the account is active. Account deletion removes active account records, private snapshots, credentials, connections and account subscriptions.
A Google source you disconnectReports become unavailable immediately and are scheduled for deletion after 30 days unless you reconnect.
Google access that expires or loses property accessUpdates stop; previous reports retain their measurement dates. After 90 days without recovery the connection returns to a connect state; source history is retained for one further calendar year, then removed.
Provider revoke retry materialA limited encrypted credential may remain in a restricted retry queue for at most 24 hours. This does not permit continued report collection after disconnection or deletion.
Application rate-limit bucketsExpire 24 hours after their last request and are removed by maintenance.
Operational logsKept for up to 30 days, then deleted.
BackupsEncrypted database backups are kept for up to 14 days in the European Union, then deleted.
Shared website measurementsPublic checks of a website are kept while at least one account follows it, and deleted 30 days after the last account stops following it.
Feedback messagesDeleted 90 days after the last message in the conversation, or earlier when you delete your account.

Deleting the app alone does not delete the server account. Use the account deletion action in the app or request deletion through Support. We verify the request using only the information needed to identify the account. Never send the device secret. Deletion of your account does not remove measurements independently requested by another account or change information on the original public website. We must separately handle any personal information in retained shared measurements and backup copies; immediate destruction of every copy is not promised.

Where your information is processed

Our server, database and backups are in the European Union:

ServiceWhereWhat for
HetznerGermanyRuns SEO Control: our server, database, website checks and reports. Uptime checks of your website run from this server.
Cloudflare R2European UnionStores encrypted database backups.

These providers process information outside the European Union:

ServiceWhereWhat for
CloudflareUnited States, global networkSpeeds up and protects connections between the app and our server. Sees connection details such as your IP address.
GoogleUnited StatesOptional Google sign-in, the Search Console and Analytics data you choose to connect, and page speed measurements for your website address.
AppleUnited StatesOptional Sign in with Apple and delivery of push notifications to your iPhone.
ExpoUnited StatesPasses push notifications to Apple. Receives your push token and the notification text, which may name your website. Only when push is on.
SentryUnited StatesCollects crash reports from the app so we can fix errors. Crash reports do not include your Google data or account email.
AhrefsSingaporeProvides Domain Rating. Receives only your website address.

We give each provider only the information its function needs, and they process it under their standard contractual clauses or equivalent safeguards. Tools we use internally to watch our own server receive no information about you. We do not disclose private Google reports to other customers. Human access to Google data is limited to consented support, security investigations, legal requirements, or permitted aggregate internal operations under Google's Limited Use rules.

Your rights and contact

Depending on the law that applies, you may ask for access, correction, deletion, restriction, portability or object to processing, and withdraw optional consent. Contact [email protected]. We will respond within the applicable legal period and explain any permitted exception. You may complain to your competent data protection authority. Withdrawing Google access does not undo past processing or itself delete saved reports.

SEO Control is intended for website owners and people checking public websites. It is not directed at children. We will update this page when our practices change and seek a new permission where a new use requires it.