SeoVision

Privacy Policy

Last updated October 7, 2026

This policy explains what personal data SeoVision collects when you use our website and dashboard, why we collect it, who we share it with, and the choices you have. We aim to collect the minimum needed to run the service.

Who we are

SeoVision (“we”, “us”) is operated by ENVOXE INC and runs the websites at seovision.io and tryproscale.com and the dashboard application. This policy covers all three. For privacy questions or to exercise your rights, contact us at support@seovision.io.

What we collect

  • Account data — your email address and authentication credentials, handled by our auth provider (Supabase). We never see or store your password in plain text.
  • Project data — the domains, brand descriptions, tracked prompts and settings you add so we can run audits and AI-visibility scans for your project.
  • Connected-account data— when you connect a store or CMS (for example Shopify, WordPress, Wix or Webflow), Google Search Console, Google Analytics or Google Merchant Center, we access only the scopes you approve. For a connected Shopify store this means reading your blog content and files, publishing articles you approve to your blog, and reading your store’s orders, customers and analytics reports, as the Shopify section below sets out. For a WooCommerce store connected through our SeoVision Publisher plugin, it also means reading the store’s orders once you allow it in the plugin, as the WooCommerce section below sets out. We never access payment information. Access tokens are encrypted and stored server-side only. Google Search Console, Google Analytics, Google Merchant Center, Shopify orders and WooCommerce orders each have their own section below, which sets out exactly what we read and what we do with it.
  • Usage data — your plan, the features you use, and quota counts, so we can operate the product and enforce fair use.
  • Technical data — standard server logs (browser type, timestamps) needed for security and debugging.

The market data shown in the product (search metrics and AI-visibility results) is not your personal data — see our Data Sources page for how it is produced.

How we use it

  • To create and secure your account and sign you in.
  • To run the audits, AI-visibility scans and content generation you request.
  • To communicate with you about your account and service changes.
  • To improve the product, diagnose problems, and meter paid usage.
  • To comply with legal obligations.

We do not sell your personal data, and we do not use it to train machine-learning models.

Who we share it with

We share personal data only with service providers (“data processors”) that help us run the product, under contract and only for that purpose:

  • Supabase — authentication and database hosting.
  • Vercel — application hosting.
  • Resend — transactional email (e.g. account and notification messages).
  • AI providers (such as OpenAI, Anthropic, Google, Perplexity and xAI) — to run AI-visibility scans and generate content. We send the prompts and content needed to produce your results; we do not send your account password.
  • SEO & market-data providers — to retrieve search volume, difficulty, domain rating and SERP signals.
  • Google — when you connect Google Search Console, we call Google's APIs to read your site's search performance and the index status of its pages. When you connect Google Analytics, we call Google's APIs to read your website's Analytics reports. When you connect Google Merchant Center, we call Google's APIs to read your products' status in Google and their free-listing performance. See the three Google user data sections below.
  • Payment processor (Stripe) — card payments and subscription billing are handled by Stripe, a PCI-compliant payment processor. We receive limited billing metadata (such as your plan, status, and the brand and last digits of your card) but never see or store full card numbers.
  • Shopify — if you install our app from the Shopify App Store, your subscription is billed by Shopify through its Billing API. We receive limited subscription metadata (plan name, status, billing period) and never see your card details.

We may disclose data if required by law, or to protect the rights and safety of our users and the service.

Google user data (Search Console)

Connecting Google Search Console is optional and always starts with Google's own consent screen, where you choose the Google Account and approve the access. This section sets out exactly what SeoVision does with what we receive.

  • What we access — with the Search Console permission you grant, we read the list of properties your Google Account can access and, for the property you select, its search performance (the search queries your site appeared for, the pages that appeared, clicks, impressions, click-through rate and average position) together with the Google index status of individual pages on your site. We also read the email address of the connected Google Account, so the dashboard can show you which account is linked.
  • What we use it for— to display these reports inside your SeoVision dashboard, to check whether the articles we publish for you have been indexed by Google, and to suggest article topics for searches your site already appears for. When you connect an AI assistant to your SeoVision account through the SeoVision MCP server, we also return these reports to that assistant when you ask it for them, the same reports your dashboard shows you. During a trial, we also email you one short summary of these reports a few hours after you connect: a few of your figures, the search that brought you the most visitors, and the searches closest to the top of Google's results. Nothing else.
  • What we never do — we never sell this data, never use it for advertising or ad targeting, never use it to train generalised artificial-intelligence or machine-learning models, and never make it available to other SeoVision customers.
  • Who can see it — the members of your own SeoVision account. Our infrastructure providers (see above) process it on our behalf under contract. If you choose to turn one of these search queries into an article, that query is sent to the AI provider that writes the article for you, acting on our instructions for that single request. An AI assistant you connect through the SeoVision MCP server receives the reports you ask it for. To write the trial summary email, the figures and searches it quotes, together with the description of your business from your project, are sent to the AI provider that drafts two short passages of it, acting on our instructions for that single request. A copy of that email is kept in our email log, so our support team can answer your reply.
  • How it is stored — the credential Google issues is encrypted before it is stored and is never sent to your browser. The search data is kept in our database for as long as the connection is active, so the reports stay available to you.
  • How to disconnect— the Disconnect button on the integration page deletes the Search Console data we synced for that project and the stored credential. When no other SeoVision connection (Search Console, Google Analytics or Merchant Center, in any project) uses that Google Account, it also revokes SeoVision's access at Google. You can revoke access yourself at any time from your Google Account permissions page.

SeoVision's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Google user data (Google Analytics)

Connecting Google Analytics is optional and always starts with Google's own consent screen, where you choose the Google Account and approve read-only access to your Analytics data. This section sets out exactly what SeoVision does with what we receive.

  • What we access — with the read-only Google Analytics permission you grant, we read the list of Google Analytics accounts and GA4 properties your Google Account can access. For the property you select, we read its reporting time zone and currency, so the reports are shown correctly, and its aggregated reports: active users, new users, sessions, views, events, key events and total revenue by day, sessions by traffic channel, active users by country, views by page title, key events by event name, by traffic channel and by page, and active users over the last 30 minutes by minute and by country. For the Real business impact card on your project Overview, we also read sessions, views and total revenue from organic search, and the same three totals for all traffic channels together, for the period you choose and the equal period before it. These are totals that Google reports, not records of individual visitors. We also read the email address of the connected Google Account, so the dashboard can show you which account is linked.
  • What we use it for — to display these reports inside your SeoVision dashboard, on the Analytics pages and in the Real business impact card on your project Overview, so you can see how the articles and backlinks SeoVision creates for your site affect its organic traffic, and to check that the connection works. When you connect an AI assistant to your SeoVision account through the SeoVision MCP server, we also return these reports to that assistant when you ask it for them, the same reports your dashboard shows you. When Google Analytics recorded revenue from organic search, the one trial summary email described in the Search Console section above quotes that total for the last 30 days. Nothing else.
  • What we never do — we never sell this data, never use it for advertising or ad targeting, never use it to train generalised artificial-intelligence or machine-learning models, and never make it available to other SeoVision customers.
  • Who can see it — the members of your own SeoVision account. Our infrastructure providers (see above) process it on our behalf under contract. An AI assistant you connect through the SeoVision MCP server receives the reports you ask it for. When the trial summary email quotes your organic revenue, that total is sent to the AI provider that drafts part of the email, acting on our instructions for that single request.
  • How it is stored— the credential Google issues is encrypted before it is stored and is never sent to your browser. We store the connected Google Account's email address and the name and ID of the account and property you selected. We do not store the Analytics reports: each time you open the Analytics pages or your project Overview, or an AI assistant you connect through the SeoVision MCP server asks for them, SeoVision requests them from Google at that moment and keeps no copy. The one exception is the trial summary email: when it quotes your organic revenue, that one total is kept with the copy of the email in our email log.
  • How to disconnect— the Disconnect Analytics button on the integration page deletes the stored credential, the Google Account's email address and the property selection for that project. When no other SeoVision connection (Search Console, Google Analytics or Merchant Center, in any project) uses that Google Account, it also revokes SeoVision's access at Google. You can revoke access yourself at any time from your Google Account permissions page. Doing so ends every SeoVision connection that uses that Google Account.

SeoVision's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Google user data (Merchant Center)

Connecting Google Merchant Center is optional and always starts with Google's own consent screen, where you choose the Google Account and approve the access. Google offers a single permission for Merchant Center, shown as “Manage your product listings and accounts for Google Shopping”. It covers both reading and changing Merchant Center data, because Google has no read-only version of it. SeoVision uses it only to read, as set out below, and does not change your products, feeds or account settings. This section sets out exactly what SeoVision does with what we receive.

  • What we access— we read the list of Merchant Center accounts your Google Account can access and, for the account you select, its name and time zone. For that account we read each product's ID, title, brand, price, availability and image link, whether Google shows it in its free product listings, the issues Google reports for it in free listings and in ads with their descriptions, and Google's estimate of its click potential. We also read the issues Google reports for the account, and the clicks, impressions and conversions your products received from free listings, with the clicks and impressions from Shopping ads beside them, by day and for your top products, for the period you choose and the equal period before it. These are figures Google reports about your products, not records of individual shoppers. Last, we read the email address of the connected Google Account, so the dashboard can show you which account is linked.
  • What we use it for — to display this inside your SeoVision dashboard, on the Merchant Center pages and in the Real business impact card on your project Overview, so you can see which of your products Google shows, what Google reports wrong with them in free listings and in ads, and how many clicks free listings bring to your store, and to check that the connection works. Nothing else.
  • What we never do — we never sell this data, never use it for advertising or ad targeting, never use it to train generalised artificial-intelligence or machine-learning models, and never make it available to other SeoVision customers.
  • Who can see it — the members of your own SeoVision account. Our infrastructure providers (see above) process it on our behalf under contract.
  • How it is stored— the credential Google issues is encrypted before it is stored and is never sent to your browser. We store the connected Google Account's email address and the ID, name and time zone of the Merchant Center account you selected. We do not store your product data, issues or performance figures: each time you open the Merchant Center pages or your project Overview, SeoVision requests them from Google at that moment and keeps no copy.
  • How to disconnect— the Disconnect button on the Merchant Center integration page deletes the stored credential, the Google Account's email address and the account selection for that project. When no other SeoVision connection (Search Console, Google Analytics or Merchant Center, in any project) uses that Google Account, it also revokes SeoVision's access at Google. You can revoke access yourself at any time from your Google Account permissions page. Doing so ends every SeoVision connection that uses that Google Account.

SeoVision's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Shopify orders, customers and store analytics

SeoVision's Shopify app reads your store's orders, customers and analytics reports once you approve it on Shopify's own permission screen. Shopify shows that screen when you install the app. If you installed it earlier, Shopify shows it the next time you open the app, or when you press Allow access to orders on the Orders page of your SeoVision dashboard. A store connected through its own custom app shares this information only if you add those permissions to that app. Shopify classes this information as protected customer data, and this section sets out exactly what SeoVision does with it.

  • What we access— for each order: its number and dates, totals, discounts, refunds and currency, the items ordered (title, variant, quantity, SKU and price), the sales channel, and the shipping country, region and city. The visits Shopify recorded before the order: where each came from (a search engine, an AI assistant, a website, an email or an ad), the page it landed on without its query string, its UTM tags, when it happened, how many days passed before the order and whether it was the buyer's first order. The buyer: their Shopify customer ID, name, email address, phone number and shipping address. From your store's own analytics reports: sessions, visitors, page views, sessions that added to cart and sessions that completed checkout, by day, traffic source, landing page and country. These report figures are totals, not records of individual visitors.
  • What we use it for — to show you, on the Orders page and in the Real business impact card of your project Overview, which of your sales and visits came from organic search, from AI assistants and from the articles SeoVision publishes for you, what buyers are worth by how they first found you, and each order with its buyer. Nothing else. We never contact your buyers.
  • What we never do— we never sell this data, never use it for advertising or ad targeting, never use it to train generalised artificial-intelligence or machine-learning models, and never make it available to other SeoVision customers. A buyer's personal details are never sent to AI assistants through the SeoVision MCP server.
  • Who can see it— the members of your own SeoVision account. SeoVision staff look at orders only to give you support or to answer a data request, and our support tools never show them a buyer's name, email address, phone number or address, including when they open your dashboard to help you. Every time someone opens a buyer's details, we record who opened them and when, and keep that record for 12 months. Our infrastructure providers (see above) process it on our behalf under contract.
  • How it is stored— orders are stored in our database so your history keeps growing. A buyer's name, email address, phone number and address are encrypted (AES-256-GCM) before they are stored, and only our servers can read them. The analytics reports are stored as daily totals.
  • How long we keep it, and how it is deleted— for as long as the store is connected. Pressing Disconnect on the Shopify card, or connecting a different store, deletes the store's orders, buyers and reports from that project at once. If you uninstall our app, Shopify sends us a shop erasure request 48 hours later and we delete everything we hold for the store. When a buyer asks your store to erase their data, Shopify relays the request and we delete that buyer's orders. When a buyer asks for their data, we send the store owner what we hold within 30 days.

WooCommerce orders and customers

On a WordPress site running WooCommerce, our SeoVision Publisher plugin lets SeoVision read the store's orders once an administrator allows it on the plugin's settings page, under WooCommerce orders. Until then SeoVision reads no order. Every read is a request from SeoVision that the plugin answers, and the plugin never sends anything by itself.

  • What we access— for each order: its number, dates and status, totals, discounts, refunds and currency, the items ordered (name, variant, quantity, SKU and price), how it was placed (for example at checkout or in the store's admin), and the shipping country, region and city (the billing ones when there is no shipping address). The source WooCommerce's own order attribution recorded for the visit before the order: the kind of source, the referring website's domain, the UTM source, medium and campaign, and the first page of the visit without its query string. The buyer: their name, email address, phone number and shipping address, and the store's customer number when they have an account. From the billing address we read only the country, region and city. An order awaiting payment, failed or cancelled reaches us as its number and status only, so we drop our copy. WooCommerce keeps no report of your store's visits, so we read none.
  • What we use it for — the same as for Shopify above: the Orders page and the Real business impact card of your project Overview. Nothing else. We never contact your buyers.
  • What we never do, who can see it, how it is stored— exactly as for Shopify above. To tell a returning buyer from a new one without a customer account, we keep a one-way keyed code of the buyer's email address with each order, never the address in the clear outside the encrypted buyer details.
  • How long we keep it, and how it is deleted— for as long as the store shares its orders. Pressing Stop sharing orders in the plugin deletes the orders and buyers we hold within an hour. Disconnecting the WordPress site in SeoVision, or connecting a different site, deletes them at once. If the plugin is removed or WooCommerce is switched off, we delete them after 48 hours. An order deleted in WooCommerce leaves our copy within an hour. When you erase a customer's personal data in WordPress (Tools, Erase Personal Data), we delete that buyer's orders within an hour, and Export Personal Data lists the orders we hold for them.

Cookies & advertising

We use strictly-necessary cookies to keep you signed in and secure your session. We also use the Meta (Facebook) pixel and Meta's Conversions API to measure how our advertising performs — for example, which visits followed an ad — so we can reduce wasted ad spend. This may set cookies from Meta (such as _fbp), and for conversions we share limited event data with Meta, including a hashed (non-reversible) form of your email when you are signed in, so Meta can match the event to an ad without receiving your raw details.

Where the law requires consent for advertising cookies (for example in the EU/UK), we will ask for it before these cookies are set. You can opt out of ad personalisation in your Meta ad settings and manage cookies through your browser.

Data retention & deletion

We keep account and project data for as long as your account is active. You can delete your account from your settings or by contacting us; we then delete your personal account data, except where we must retain limited records to meet legal, accounting, or fraud-prevention obligations. Disconnecting a store or CMS revokes our access to it going forward. Disconnecting Google Search Console additionally deletes the search data we synced from it. Disconnecting Google Analytics deletes the stored credential and property selection, and we never keep a copy of your Analytics reports. Disconnecting Google Merchant Center deletes the stored credential and account selection, and we never keep a copy of your Merchant Center data. When the last SeoVision connection that uses a Google Account is disconnected, we also revoke SeoVision's access at Google for that account.

If you uninstall our app from your Shopify store, we immediately disconnect the store and delete the stored access token, so we can no longer read or publish anything. We also honour Shopify’s mandatory data-erasure requests: when Shopify sends a shop or customer redaction request, we delete the related store records, including the orders and buyer details we hold. Disconnecting the store deletes its orders, buyers and reports from that project at once.

For a WooCommerce store, stopping the sharing in our plugin, removing the plugin or disconnecting the site deletes the store's orders and buyers, as the WooCommerce section above sets out.

Your rights

Depending on where you live (including under the EU/UK GDPR and the California CCPA), you may have the right to access, correct, export, or delete your personal data, and to object to or restrict certain processing. Contact us at support@seovision.io to make a request. We will not discriminate against you for exercising these rights.

International transfers & security

Your data may be processed in countries other than your own, including the United States. We use reputable providers with appropriate safeguards, and we apply industry-standard measures (encryption in transit, encrypted tokens, access controls) to protect your data. No method of transmission is perfectly secure, but we work to protect your information.

Changes to this policy

We may update this policy as the product evolves. We will revise the “last updated” date above and, for material changes, provide a more prominent notice.