Privacy
Updated 19 November 2026.
How SEOAVA handles account, website and connected-service information.
What this page is
This page describes how the SEOAVA product at seoava.com handles information when you use it. It is a product description, not a law-firm opinion. SEOAVA does not publish a company registration number inside the product.
Account and workspace
Creating an account stores the email address used to sign in, login events, and which workspace and website you selected. Magic-link sign-in uses that email only to send the link you requested.
Websites you add
SEOAVA stores the website address you add and what a public check can read: page URLs, status codes, titles, meta descriptions, headings and similar on-page evidence. Findings, drafts and approvals are saved so you can review them later. SEOAVA does not invent traffic or rankings to fill missing measurements.
Connected services
Google Search Console, WordPress and Shopify are read or updated only after you connect them. Connection tokens are used for the action you asked for, such as reading search performance or publishing a change you already approved. You can disconnect a service from Settings. Saved findings and connection status are separate.
Google user data
Google data is accessed only when you connect the relevant service or use Google sign-in. The sections below identify the OAuth scopes requested by the application and the purpose for each connection.
SEOAVA does not sell Google user data or use it for advertising.
SEOAVA does not allow people to read Google user data except with your consent, when necessary for security, or to comply with applicable law.
SEOAVA’s use of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements.
Google Search Console
Scopes requested: openid, email, and https://www.googleapis.com/auth/webmasters.readonly. Purpose: identify the Google account you authorize, confirm the Search Console property you control, and read its search-performance data for reports and SEO analysis. Data may include the property URL, queries, pages, dates, clicks, impressions, click-through rate, and average position.
Google sign-in
SEOAVA starts Google sign-in through Supabase Auth with the standard scopes openid, email, and profile. Purpose: use the Google account’s email address and basic profile information to authenticate you and establish your SEOAVA session; Google sign-in is not used to read Search Console data.
Data retention and deletion
To request deletion, email privacy@seoava.com from the email address on your SEOAVA account. We may ask you to verify your identity. We will respond without undue delay and within one month of receiving your request. If the request is complex or numerous, the response period may be extended by up to two further months; we will tell you within the first month and explain why.
Search Console data is retained while your SEOAVA account and site remain active. Disconnecting Search Console stops future access but does not automatically delete data already stored. When your account is deleted, SEOAVA deletes all Google user data held for that account, including OAuth tokens, connection and property details, stored Search Console results and derived findings, and Google sign-in identity data. We complete deletion within one month of receiving a verified request, subject to any extension described above.
What SEOAVA does not do
SEOAVA does not sell personal information. Public marketing pages do not require an account. The signed-in app is not a public directory of your websites.