Trust & access
Your data deserves clarity.
How we handle your identity, Google reports, and the AI access you approve.
Privacy policy
Analytics MCP Server is run by M Asif Rahman. Questions, support and deletion requests: asif2bd@gmail.com. Last updated November 19, 2026.
Who we are
Analytics MCP Server (analyticsmcpserver.com) is operated by M Asif Rahman, who is responsible for the personal data described here. Contact: asif2bd@gmail.com.
What the service stores
Google provides sign-in. When you sign in we receive and store your Google account subject identifier, your email address and whether Google has verified it, and your display name. Your identity comes only from the openid, email, and profile permissions; signing in by itself grants no access to Analytics or Search Console data. Sign-in sessions are kept in our database as a keyed hash of a random token stored in an HttpOnly cookie; a session ends after 7 days of inactivity, 30 days at most, or when you sign out.
The application also stores workspace and project settings, source identifiers, consent and grant records, Pro requests, security audit events, and transactional notification delivery records. Once sending is approved, the outbox stores recipient/sender addresses and controlled message content for reliable delivery retries. Google sign-in alone does not authorize analytics access.
When a workspace owner or admin logs a change to a project (for example a rewritten title), we store that change note in our own database: the page URLs, date, type and note they entered, any comparison pages, who added it and when. A change note never holds Analytics or Search Console figures; a before-and-after verdict is computed live from Google when you ask and is not stored. Change notes are never written to Google or to your website. An AI client can add or delete change notes only with its own change-logging permission (changes:write), which an owner or admin must allow separately on that client's consent screen, and only while they remain an owner or admin.
Read-only Google data, with one optional write
When Google data authorization is enabled, the Google sign-in screen also asks for read-only access to Google Analytics and Search Console. You can untick those permissions and still sign in, then connect them later from onboarding or Connections. Data access granted while signing in is used only if your workspace has no active Google connection; it never replaces or widens an existing one. Access is read-only, with one optional exception: a workspace owner may separately allow sitemap submission (see below). The service never deletes anything in your Google accounts. Provider refresh tokens are encrypted before storage. Reports are retrieved to answer your requests; they are not presented as live data when a source is unavailable.
How we use Google user data (Limited Use)
We request two read-only Google permissions, and only to show you your own reports: Google Analytics (analytics.readonly) to list your GA4 properties and read their traffic reports, and Search Console (webmasters.readonly) to list your sites and read their search performance and sitemaps.
Optionally, a workspace owner may also grant Search Console (webmasters) on its own consent screen, from Connections. It is never asked for at sign-in. We use it for one action only: submitting a sitemap of one of your projects to Google when an owner or admin of the workspace, or an AI client they allowed to do so, asks. We record that a submission happened (project, time, outcome), not the sitemap's address or any Google data. Turning it off reconnects read-only access; disconnecting Google removes it in your Google account. When you turn it on or off, we ask Google which Google account approved, and your AI clients stay connected only if it is the same account with the same read-only access.
Analytics and Search Console report data is fetched when you, or an AI client you have authorized, ask for a report. It is kept briefly in server memory to answer repeat requests and is not stored in our database. We store only the identifiers of the property and site you choose, your encrypted refresh token, the identifier Google gives the connected Google account (not its email address), and counts of the Google calls we make (never their content).
Google user data is used only to provide and improve the user-facing features of this service. We do not sell it, use it for advertising, or use it to develop, improve or train generalized AI or machine-learning models. People at the service do not read it, except with your explicit permission, when needed for security or to comply with law. It is transferred to others only to provide the service at your direction, namely to the AI clients and connected apps you authorize and the people you send a report link to (see below) and, for a page-speed check you run, the page URL to Google (see below), or as required by law.
The use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
How we protect your data
We apply these safeguards to Google user data and to the account data described above:
- Encryption in transit. The service is served only over HTTPS (TLS), with HTTP Strict Transport Security. Calls to Google APIs also use HTTPS.
- Encryption at rest. Google refresh tokens are encrypted with AES-256-GCM before they are stored, each bound to its workspace, and the encryption key is kept apart from the database. Google access tokens are kept only in server memory.
- No stored copies of reports. Google Analytics and Search Console report data is never written to our database. It is held in server memory for at most 6 hours to answer repeat requests, then discarded.
- Hashed credentials. Sign-in session tokens, invite links, report share links and AI-client (MCP) access and refresh tokens are stored only as hashes, never in readable form.
- Least privilege. We request read-only Google permissions. The only Google write, sitemap submission, needs its own consent from the workspace owner; an AI client's only other write, change notes in our own database, needs its own consent too. Each AI client gets a separate grant limited to the projects you approve, and every request is checked against your workspace before any data is loaded.
- Restricted infrastructure. The database is not reachable from the internet; only the application can connect to it. Sign-in cookies are HttpOnly, Secure and SameSite, and state-changing requests are protected against cross-site request forgery.
- Private logs. Application logs leave out tokens, cookies, email addresses, request bodies and report data.
- Your control. You can disconnect Google, revoke any AI client or delete your account at any time, as described below.
Teams
A workspace owner can invite people by email as admins or viewers. An invite stores the invited email address and a hash of its single-use link, and expires after 7 days. Members sign in with their own Google account and read the owner's analytics through the owner's read-only Google connection; their own Google data is never requested for the shared workspace. Members see each other's names, email addresses and last activity. Removing a member, or a member leaving, ends their access and revokes the AI clients they connected to that workspace.
Shared report links
A workspace owner or admin can create a link to the written report for one project and date range. Anyone with the link can read that report, generated live from the workspace's read-only Google connection, until the link expires (at most 30 days) or a manager revokes it in Reports. We store only a hash of the link, its project, dates and expiry, never the report data. A link stops working when the person who created it is no longer an owner or admin, or when Google is disconnected or the project's sources change. Shared reports leave out change notes and workspace usage.
AI clients and other providers
Each AI client requires a separate project-scoped grant. Data returned to an authorized client is then subject to that client provider’s policies. A connected app such as WPInsight gets read-only access to one project that a workspace owner or admin chooses. It receives report results, never your Google credentials, and may show them to members of its own workspace according to the sharing settings you choose there; revoke it in Connections at any time. Google processes sign-in and data-access requests. We send account, team-invite and Pro-review emails through toSend (tosend.com), which processes the recipient address and the message, never analytics report data. toSend keeps email logs and content in the EU for 14 days. When you sign up or request Pro, the service operator is emailed your name, email address and, for a Pro request, your reason, workspace name and project names and sites; our stored copy of that email is reduced to a generic notice once it is sent or your account is deleted.
When you run a page-speed check, the page URL (without its query string) is sent to Google PageSpeed Insights and the Chrome UX Report API. The results are not stored in our database; like other reports they are held in server memory for at most 6 hours.
Revocation and deletion
Use Connections to revoke available connections and client grants. An account deletion request ends all sign-in sessions, disables workspace access, clears stored Google refresh tokens, and revokes client grants. It does not currently promise immediate deletion of all audit records or backups. The disabled account record, including your Google subject identifier and email address, is retained so the deletion notice can be sent and the account cannot be silently re-created; it is not promised to be erased immediately. Google third-party permissions can also be revoked in your Google account. Data already received by an AI client is not recalled by revocation.
To have your account record and the audit events that identify you erased, email asif2bd@gmail.com from the address on your account. We complete erasure within 30 days and confirm by email; the copies in database backups then expire within a further 14 days.
Logs and retention
Request logs record generated correlation identifiers, methods, status codes, and timing. They exclude request URLs, query strings, credentials, cookies, and analytics request and response bodies. Audit records can contain internal record identifiers.
- Account, workspace and project records, consent and grant records, and audit events are kept while your account exists, and until erased on request as described above.
- Analytics and Search Console report data is never written to the database; it is held in server memory for at most 6 hours.
- Sign-in sessions end after 7 days of inactivity or 30 days at most; pending invites expire after 7 days.
- The database is backed up nightly and each backup is deleted after 14 days.
Analytics on this website
This website uses Google Analytics 4 (measurement ID G-K1CP95X3SZ) to count visits to our own pages. Google Analytics sets cookies in your browser. We send only the page path and the referring site, never query strings, your email, name, workspace or project identifiers. It never receives the Google Analytics or Search Console report data you view through the service. You can opt out with the Google Analytics opt-out browser add-on.
The same page views are also counted with Umami, a cookieless analytics tool we run ourselves (agent-analytics.asif.dev). It receives the same page path, referring site and page title, plus your browser language and screen size; it sets no cookies.
On the homepage, both also count when someone starts the intro video. The video is hosted on YouTube: nothing loads from YouTube until you press play. Then YouTube's privacy-enhanced player (youtube-nocookie.com) loads in the page and Google's privacy policy applies to that player.
Your controls
See Account for your account controls and Docs for permission boundaries and troubleshooting.