Your data and your choices.
Last updated: 23 September 2026
MRSEO is a search-intelligence brand being developed in Türkiye. It is not currently an incorporated limited company. This notice explains data handling in the website and client workspace. For privacy questions or requests, contact founder@mrseo.net.
Information used by the service
- Enquiries: the name, email, company, website, service interests and message you submit, together with submission time and technical information used to limit abuse.
- Workspace accounts: name, email, project membership, permissions, sign-in sessions and security records. Authentication records can include password hashes, session credentials and two-factor authentication records. MRSEO does not ask for your Google account password.
- Project work: website details, tasks, reports, content plans, imported performance measurements, audit results and AI conversations created in the workspace.
- Technical records: relevant timestamps, IP addresses, browser information, connection status and audit events used to operate and protect the service.
This information supports enquiries, account access, requested analysis, project reporting, customer support and service security.
Connecting Google data
Connecting Google is optional and starts on Google's authorization screen. The Search Console connection requests read-only access to Search Console. The Analytics connection requests read-only access to Google Analytics. These permissions let MRSEO discover accessible properties and web streams, verify your selection, and retrieve performance data. They do not let this connection edit your website, publish content or change Google account settings.
Search Console imports can include clicks, impressions, click-through rate and average position. Analytics imports can include Organic Search sessions, engaged sessions and key events. MRSEO also handles available property identifiers, names, access information and website-stream details needed to select the appropriate source. The selected resource is checked against the project's website.
Selected identifiers, imported measurements and synchronization records are stored with the project. Refresh tokens, which allow later imports without another sign-in, are stored encrypted on the server. Temporary access tokens are used server-side to call Google. Pending authorization records are encrypted and the connection-selection flow expires after ten minutes.
Google data is used for the visible reporting and analysis features you request. MRSEO does not sell Google user data or use it for advertising. Its use and transfer are limited by the Google API Services User Data Policy, including applicable Limited Use requirements.
Optional AI analysis
Before sending an AI Analyst question, you are asked to agree to external processing. When you submit, MRSEO sends your question, a limited recent conversation history and selected project context to OpenAI to generate an answer. Context can include normalized Google performance measurements, project details, tasks, content records, competitors, alerts and conversion information.
Integration credentials and raw provider payloads are excluded from the assembled project context. Do not place passwords, tokens or unnecessary personal information in questions or project text. The request disables stored API responses; provider processing and retention are otherwise governed by the applicable service configuration and provider terms. Questions and answers are saved in your MRSEO conversation history. You can use connected reporting without using AI Analyst.
Access and service providers
Workspace access is restricted through account and project permissions. Authorized project users can view the data made available to their role. Hosting and database services process information required to run the workspace. Google processes authorization and data requests; OpenAI processes information sent through the optional AI Analyst. Authorized administrators may access records for requested support or a security investigation.
Provider processing may take place outside Türkiye, depending on the services and deployment locations used. Information may also need to be handled to address security incidents or applicable legal obligations.
Disconnecting, retention and deletion
The workspace retains project records, imported reports and conversation history until they are removed. Disconnecting a Google source removes that project's stored connection credentials and stops future imports. It does not automatically delete earlier reports or conversations, and it does not revoke MRSEO's Google access for your other projects.
You can revoke the application's Google access in Google Account connections. This can affect all MRSEO connections using that Google authorization.
To request deletion of an account, imported Google data, reports or conversations, email founder@mrseo.net with the relevant account and project. Access to the request will be verified before information is disclosed or removed. Any records that must be retained for an applicable legal or security reason will be addressed when handling the request; disconnecting is not presented as complete data erasure.
Cookies and external resources
The workspace uses authentication and security cookies to maintain sign-in sessions. The Google connection flow uses a short-lived, HttpOnly cookie containing an opaque reference rather than a Google token. Blocking these cookies can prevent sign-in or connection setup.
The site's typography loads from Google Fonts, so your browser contacts Google's font services when loading those resources. Connected Google Analytics reporting concerns the website you select; it does not by itself install an Analytics tracking tag on the MRSEO website.
Questions and requests
Contact founder@mrseo.net to ask about your information, request access, correction, an export or deletion, or raise an objection to processing. Requests are considered under the rules applicable to the information and the person making the request. Changes to data handling will be reflected in this notice; a new use of connected Google data requires an updated disclosure and appropriate authorization.