Privacy Policy

Who we are

AutoPSEO is a product of Subcue AI LLC, a limited liability company organized under the laws of the United States ("Subcue AI", "we", "us"), which is the controller of the personal data described here. AutoPSEO provides a web application that reads Google Search Console, Google Analytics 4, Bing Webmaster Tools and Chrome UX Report data on your behalf, turns it into reports, and uses it to plan, write and keep up to date articles for your website. This policy explains what we collect, why, and what you can do about it.

Questions about this policy: contact@subcueai.com.

Data we collect

Account data. When you sign in with Google we store your Google account id, email address, display name and profile picture URL. We do not receive or store your Google password.

Authorisation tokens. Once you connect Search Console or Analytics we store an encrypted OAuth refresh token so reports can be generated without you signing in again. Signing in on its own creates no such token. Tokens are encrypted at rest with AES-GCM and are never exposed to the browser.

Search data. The Search Console, Analytics and Bing metrics we fetch on your behalf: queries, pages, countries, devices, clicks, impressions, click-through rate and position, and from Google Analytics sessions, users, engagement, key events, e-commerce figures and traffic sources. For properties where you enable stored history we keep a daily copy so history survives past Google's 16-month window.

Product data. Properties you add, tags, content groups, topic clusters, annotations, saved filters, shared reports, API keys, alert rules and team invitations, and the topics, drafts and articles the content engine works on for your site, with what it reads from your site's public pages to match their format.

Operational logs. Timestamps, request paths, error messages and, for sign-ins, the IP address, so we can debug problems and detect abuse.

What we do not do

We do not sell your data, we do not share it with advertisers, and we do not use it to train machine-learning models. We do not write anything to your Search Console property unless you explicitly ask us to (submitting or removing a sitemap), and we never write anything to Google Analytics.

Google API Services

Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We request the narrowest scopes that make the product work, and we request them one at a time. Signing in asks only for your name, email address and profile picture; read-only Search Console access, read-only Analytics access and full Search Console access are each a separate consent you give by clicking the button for it, and the app works without the ones you skip. You can revoke our access at any time from your Google account permissions page.

What each permission is used for. Read-only Search Console access shows your reports and alerts, keeps the daily history you switch on, finds the searches your site is shown for without a page that answers them, checks which of your pages already answer a search, and measures the articles we write for you. Full Search Console access is used only for what you ask for: submitting or removing a sitemap. Read-only Analytics access lists the Google Analytics 4 properties your account can read, so you can choose the one that belongs to each site, and reads that property's reports: sessions, users, engagement, key events, e-commerce revenue, traffic sources, pages and visits from AI assistants. They appear in our Google Analytics reports and beside your Search Console data, and the SAM assistant and the AI tools you connect can read them when you ask. We never create, change or delete anything in Google Analytics.

Who sees it. The next section lists everyone we share, transfer or disclose Google user data to. No one at AutoPSEO reads your Google data unless you ask us to for support, it is needed for security or to comply with the law, or it has been aggregated and anonymised.

Sharing, transfer and disclosure of Google user data

We do not sell Google user data, we do not use it for advertising, and we do not use it to develop, improve or train AI or machine-learning models, ours or anyone else's. We share, transfer or disclose it only to the parties below, for the purposes given, and only as far as a feature you use needs it.

Cloudflare, Inc. (hosting and infrastructure). Runs the application and stores and processes all the data we read from Google: the database (Cloudflare D1), caches (Workers KV, which keeps Search Console responses for up to 12 hours and Google Analytics responses for up to 6 hours), file storage (R2), the SAM assistant's conversations (Durable Objects), and the AI models below that run on Workers AI. Every request that carries Google user data to an AI model passes through Cloudflare AI Gateway.

AI models, when you use the SAM assistant or the content engine. The SAM assistant answers with OpenAI's gpt-oss-120b model, which Cloudflare runs on Workers AI; when you ask it a question it can read your Search Console and Google Analytics reports, and what it reads is kept in that conversation. The content engine sorts and reviews article topics with Meta's Llama 3.3, also run by Cloudflare on Workers AI, using the searches your pages get. When the content engine writes, reviews or translates an article, Anthropic's Claude models receive the search the article is for, related searches from your Search Console and the titles and addresses of your pages, and no Google Analytics data. These models process the data only to return their answer and may not use it to train models.

DataForSEO. Receives keywords and returns search results, search volumes and rankings, including searches from your Search Console when the content engine plans an article. It receives no other Search Console data and no Google Analytics data.

People and services you choose. We send Google user data to these only when you set them up or ask for it. Team members you invite see the Search Console and Google Analytics reports of the properties you share with them. A share link you create shows a snapshot of a report, which can include Search Console or Google Analytics figures, to anyone who has the link (behind a password and with an expiry if you set them). Slack, Microsoft Teams or webhook destinations you connect receive the reports and alerts you schedule and any report you send by hand. AI assistants and other clients you connect to our MCP server or REST API, such as Claude or ChatGPT, receive the Search Console and Google Analytics data you ask them for, and their own provider's terms apply to it. Your website receives the articles the content engine writes for it, and the search engines behind IndexNow receive the addresses of pages you submit.

Legal reasons and business transfers. We disclose Google user data when the law, a court order or a valid request from a public authority requires it, or when it is needed to protect the security of the service and its users. If AutoPSEO is merged or acquired, the data passes to the successor only under the commitments in this policy, and we tell you before it does.

Where it is processed. Cloudflare processes the data on its global network, so it can be processed outside the country you are in.

Stripe and Resend, which handle payments and email, never receive Google user data.

Legal basis and purposes

We process account and search data to perform the contract you enter into when you create an account. We process operational logs on the basis of our legitimate interest in keeping the service secure and working. Where we send product emails you can unsubscribe at any time.

Sub-processors

Cloudflare (hosting, database, cache and object storage, EU and global edge; Workers AI and AI Gateway), the AI model providers our AI Gateway routes to for writing, reviewing and translating articles (Anthropic), DataForSEO (search volumes, rankings and backlinks for what you research), Google (the APIs your data comes from), Stripe (payments; they receive your email and billing details, we never see card numbers), and Resend (transactional email such as team invitations). Each is bound by a data-processing agreement.

Retention

Account and product data is kept while your account exists. Stored Search Console history is kept until you delete the property or your account, and for no more than ten years. Operational logs are kept for 90 days.

When you delete a property or your account, we delete its data at once: its records in our database, its files, its assistant conversations, its share links and its Search Console history, and with your account its Google connections and the access of the AI tools you signed in to it. A step that fails is retried every day until it succeeds. Copies cached to make reports faster expire on their own, within 12 hours for Search Console data, 6 hours for Google Analytics data and at most 30 days for analyses. Payment records stay with Stripe where tax law requires them.

Your rights

Depending on where you live you may have the right to access, correct, export or delete your data, to object to processing, and to complain to a supervisory authority. Use the export buttons in the app, or write to contact@subcueai.com and we will respond within 30 days.

Security

All traffic is served over TLS. Refresh tokens and integration secrets are encrypted at rest. Sessions are stored server-side and identified by an opaque cookie that is HTTP-only, Secure and SameSite=Lax. Access to production data is limited to the people who operate the service.

Children

The service is not directed to children under 16 and we do not knowingly collect their data.

Changes

We will update this page when the practices change and, for material changes, notify account holders by email before they take effect.