What data does SEOKit access, store and encrypt?
SEOKit reads your Search Console data with read-only permission, keeps your Google tokens encrypted on the server and stores report history only for properties where you turn that on. Here is each permission and each stored item.
✓ Checked against the SEOKit code, privacy policy and Google documentation · October 2026
SEOKit reads your Search Console data with read-only permission, keeps your Google tokens encrypted on the server, and stores report history only for properties where you turn that on. A normal sign-in asks only for your Google identity. Read-only Search Console access is requested when you open a Search Console tool, Google Analytics 4 is asked for separately, and write access to Search Console is a further, explicit grant. The rules that govern all of this are in Google’s API Services User Data Policy, including its Limited Use requirements.
What each permission lets SEOKit do
Permissions are requested in groups, so a feature you do not use does not ask for more than it needs (Google OAuth 2.0 scopes).
Sign-in uses the OpenID and email permissions to learn your account identifier, name, email and picture; it does not read your mail or files, and it does not request Google Drive. The webmasters.readonly permission lets SEOKit list your properties and read aggregated clicks, impressions, CTR and position by query, page, country and device, and it cannot change your sites. The analytics.readonly permission is requested only when you connect GA4 on purpose, and lets SEOKit list properties and read aggregated traffic and conversion metrics.
Write access to Search Console, the webmasters permission, is a separate grant. It is requested only for actions that change Search Console, such as adding a property or submitting a sitemap, and for the MCP write mode; ordinary reports never ask for it, so approve it only when you are about to do one of those things (authorizing Search Console API requests).
What is stored and for how long
Your Google tokens are saved on the server in encrypted form, using Fernet authenticated encryption. The browser cookie holds only a random identifier, with the Secure, HttpOnly and SameSite flags, and a session lasts up to seven days.
Report history is saved only for properties where you switch storage on: date, query, page, country, device, clicks, impressions, CTR and position. It is kept for up to ten years and deleted 30 days after you switch storage off. MCP API keys are stored as a SHA-256 hash plus the first and last characters; the full key is shown once, when you create it. The Slack access token is stored encrypted and stops being used when you disconnect the workspace. The AI features run only when you start them and agree: the provider receives the page URL, the current title and description and up to ten relevant queries, never your Google token or email.
Signing out is not the same as revoking access
Signing out closes the browser session and keeps your encrypted Google connection so scheduled checks can continue. On the sign-out page, “Disconnect Google and sign out” deletes the current saved connection and stops new background checks through it; saved reports remain. This does not revoke the permission in Google. To remove the grant itself, open the list of third-party apps with access to your Google Account and remove SEOKit there (third-party apps with access to your account).
Deleting what SEOKit holds, and safer habits
You can sign out, switch off storage per property and disconnect Slack yourself. To have stored credentials and reports deleted, write to the contact address in the privacy policy; a verified request is completed within 30 days unless the law requires otherwise.
Two habits keep your data safer. Do not paste an MCP key into chats or tickets, because anyone holding it can call the tools it allows; revoke it in the workspace and create a new one. And do not grant write access just in case: approve that permission only when you are about to add a property or submit a sitemap.
Go further
Reports and tools: How the workspace reports, exports and saved views work. Data and metrics: Clicks, impressions, CTR, position and report differences.