Privacy policy

Google User Data (Search Console and Analytics)

SEOWren can connect to Google Search Console and Google Analytics 4 so that your search performance and organic traffic appear alongside the keyword rankings we track for you. These connections are optional: SEOWren works without them, and you choose which properties are linked. This section sets out what we access, why, and what happens to it afterwards.

What we request, and why

• .../auth/webmasters.readonly: Read-only access to Google Search Console. Used to list the properties your Google account can access so you can pick which ones to link, and to read search performance for the linked properties: queries, pages, clicks, impressions, click-through rate, average position, and index coverage counts.
• .../auth/analytics.readonly: Read-only access to Google Analytics 4. Used to list your GA4 properties so you can pick which ones to link, and to read organic-traffic metrics for the linked properties: sessions, users, pageviews, bounce rate, and average session duration.
• .../auth/userinfo.email and .../auth/userinfo.profile: Your Google account’s email address and basic profile, so we can show you which Google account a connection belongs to and confirm you are reconnecting the right one.

Every scope we request is read-only. SEOWren cannot create, modify, or delete anything in your Google Search Console or Google Analytics account, and it does not request access to any other Google service: not Gmail, Drive, Contacts, Calendar, or your Google Ads data.

What we store

• The OAuth access and refresh tokens Google issues, encrypted at rest in our database. They are decrypted only in memory, at the moment we call a Google API on your behalf.
• The email address and display name of the connected Google account, shown in your dashboard so you know which account is linked.
• The identifiers of the Search Console and GA4 properties you link, and your permission level on them.
• The metrics listed above, stored as dated rows so we can chart them over time and include them in your reports.

We never receive or store your Google password, and we never ask for one. Authorization happens on Google's own sign-in screen.

How we use it

Data obtained through these connections is used for one purpose: to provide the SEOWren features you asked for. That means displaying your performance in your dashboard, charting it over time, generating your reports, and raising the alerts you have configured. Specifically:

• We never sell Google user data.
• We do not use it for advertising, retargeting, audience building, or creditworthiness or lending purposes.
• We do not use it to train, develop, or improve generalized or non-personalized artificial intelligence or machine learning models, and we do not permit anyone else to.
• AI features are the one case where Google data leaves our systems. When you ask SEOWren to generate an AI recommendation or report for a project or keyword, we include aggregated Search Console metrics for that project (top queries with their clicks, impressions, click-through rate, and average position) in the prompt we send to our AI model provider (currently one of Anthropic, OpenAI, Google Gemini, or OpenRouter, depending on the model configured). This happens only when you trigger an AI feature, only for the project you are analyzing, and only to produce that output for you. We use these providers under their standard API terms, which do not permit submitted data to be used to train their models.
• Apart from the AI processing described above, we do not transfer Google user data to third parties, except as necessary to run the service (for example, our hosting provider, which stores the encrypted database on our behalf), to comply with applicable law, or with your explicit consent.
• Nobody on our team reads your Google user data as a matter of course. There are three exceptions: our support team may look at it with your explicit permission while working on a request you have raised, our engineers may access it where that is necessary to investigate a security incident or abuse of the service, and we will disclose it where the law requires us to.

Limited Use disclosure

SEOWren's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Retention, disconnection, and revoking access

• We keep Google user data only for as long as the connection is active and you still want the feature.
• Disconnecting Search Console or Google Analytics from your SEOWren dashboard deletes the stored OAuth tokens for that connection, along with the linked properties and every metric we pulled through it.
• Deleting your SEOWren account removes these connections and all data derived from them, along with the rest of your account data.
• You can revoke SEOWren's access directly from Google at any time at myaccount.google.com/permissions. Doing so immediately stops any further access, and we recommend also disconnecting inside SEOWren so the stored data is cleared.

Questions about Google data specifically, or a request to have it deleted, can be sent to support@seowren.com.