Privacy policy

SEODatum is operated by Красолуцкий Сергей Евгеньевич (“SEODatum”, “we”, “us”). Questions and requests about personal data can be sent to vip.41243@gmail.com.

When you sign in with Google, SEODatum receives your Google account subject identifier, verified email address, display name, and profile image URL. We use this information to authenticate you, maintain your account, show your identity, and manage project access and invitations.

When you choose to connect a Google account to a project, the current integration requests read-only access to Google Search Console and Google Analytics. It receives the granted permissions, OAuth access and refresh tokens, connection time, available Search Console sites and Analytics accounts or properties, their identifiers and names, and reporting data for resources you select.

Search Console reports can include clicks, impressions, click-through rate, average position, dates, search queries, and pages. Analytics reports can include users, sessions, page views, engagement rate, dates, and organic-search traffic metrics.

The current integration does not request Google Ads account data and does not create or change Google Ads campaigns, Analytics properties, or Search Console sites. If a Google Ads data flow is introduced, this policy will be updated before that data is requested.

We use Google user data to authenticate you, list resources available to your connected account, let you select a project resource, retrieve read-only reports requested by you, show saved reports and history, refresh authorized access, protect the service, diagnose errors, and answer support requests.

Our handling of Google user data follows the Google API Services User Data Policy, including its Limited Use requirements. Google user data is limited to providing or improving user-facing features that are visible in SEODatum.

We do not sell Google user data or use it for advertising, retargeting, credit decisions, or data-broker services. Transfers are limited to providing visible features with your consent, security, applicable law, or a merger, acquisition, or sale of assets with your explicit prior consent. People do not read Google user data unless you affirmatively agree to a specific review, it is necessary for security or legal compliance, or it is aggregated for internal operations as permitted by law.

We do not use Google user data to develop, improve, or train generalized (non-personalized) artificial intelligence or machine-learning models. Our employees, agents, contractors, and successors must follow these restrictions. If our use of Google user data changes, we will update this policy and provide the notices and consent required before using the data for a new purpose.

Project owners can invite members and assign roles. Authorized members can access project data within their role. You can also approve an MCP connection. An authorized MCP client can read project data and, where its role permits, perform project actions. Google-derived reports may therefore be shown to authorized project members or returned through an authorized MCP connection. Google credentials and OAuth tokens are not exposed to members or MCP clients.

On seodatum.com, we use Google Analytics and Yandex Metrica to understand visits and improve the public site. These services may process page URLs, referrers, device and browser information, approximate network-derived location, and cookies or similar identifiers. Yandex Session Replay is disabled. These scripts run only on the production seodatum.com host.

Google OAuth tokens are stored server-side in encrypted form using AES-256-GCM and are bound to the SEODatum user and provider. Tokens are not returned to the browser. OAuth connection attempts use a short-lived one-time state and PKCE, and Google API requests use HTTPS.

We store account identity, encrypted integration credentials, selected project resources, reports, project settings, membership and access records, and service activity needed to operate and protect SEODatum.

The current service does not publish a fixed automatic retention deadline. Account information and project data are retained while needed to operate the account, provide the project and its history, protect the service, or meet legal obligations.

Removing a Google resource from one project stops that project binding, but does not by itself revoke Google permission or erase a shared connection or saved project history. Deleting a project removes its project-linked integration bindings and reports.

You can revoke SEODatum’s access in your Google Account permissions. To request deletion of your SEODatum account, encrypted Google connection, or retained project data, email vip.41243@gmail.com from the address associated with your account. We may verify the request and retain information where required by law, to resolve disputes, or to protect the service. You can also request access to or correction of your personal data through the same address.

We may update this policy when our integrations, data use, storage, recipients, or user controls change. The current version and effective date remain available on this page.