Privacy Policy
Last Updated: 13 October 2026
Welcome to QuickSEO (https://quickseo.ai). This privacy policy explains what information we collect, how we use it, who we share it with, and your rights regarding your data.
1. Information We Collect
Account Information
When you sign up, we collect:
- Email address: If you sign in with a one-time code, this is the only account information we collect at sign-up.
- Profile data: If you sign in via Google OAuth, we also collect your full name and profile picture as provided by Google.
Google Authorization
QuickSEO asks Google for these permissions:
- Your email address and basic profile (
userinfo.email,userinfo.profile), when you sign in with Google. - Read-only access to Google Search Console (
webmasters.readonly), with offline access so we can read your data when you are not on the page. "Continue with Google" asks for it together with sign-in; if you sign in with a one-time code, you grant it in a separate Google step when you connect Search Console. We cannot change anything in your Search Console account.
To use that access, we store:
- Google OAuth tokens: The access and refresh tokens Google issues to us. They are encrypted with AES-256-GCM before they are written to our database, are reachable only by our backend service, and are used only to call the Google Search Console API on your behalf.
Google Search Console Data
The tables and charts on your dashboards — keywords, search queries, page performance (clicks, impressions, average position, CTR), and device and country breakdowns — are fetched from the Google Search Console API when you view them and are not saved once the page has been delivered. To keep the all-websites overview fast, each website's daily totals for the selected date range may be cached by our hosting provider for up to 30 minutes.
To provide insights, opportunities, index monitoring and alerts, our servers also read Search Console data for each website you add on a schedule (about once a day) and store what those features need in our database:
- The properties you add: The Search Console property (for example
sc-domain:example.com), the website address, and your permission level on that property. When you open the property picker, we read the list of properties your Google account can access in order to show it to you; we save only the ones you select. - Insights: Each website's recent click totals and the verdict we show about them — for example whether clicks moved more than usual in the week of a Google ranking update — and the date the data runs to.
- Opportunities: The pages we suggest you work on, with the search queries they appear for, their clicks, impressions, click-through rate and average position, our estimate of the extra clicks, and the page title and description we read from your public page. We also store whether you marked each one done or dismissed it, and when.
- Fix measurements: For each opportunity you mark done, the page's clicks and impressions in the weeks before and after, and the website's total clicks over the same weeks.
- Index monitor (paid plan): The URLs we check, taken from your sitemaps and from pages with Search Console impressions, and the answer Google's URL Inspection tool gives for each: whether it is indexed, Google's coverage state, when Google last crawled it and which canonical it chose, plus a history of changes. These checks use the same read-only access; they never ask Google to index a page or change anything in Search Console.
- Traffic alerts (paid plan): For each alert, the weekly click totals it compared.
We also store the list of Google's announced ranking updates, which is public information and not about you.
Search Console data leaves our servers in two cases: if you connect an AI assistant to our MCP server, that assistant receives Search Console data in response to its own requests (see Section 3); and the alert and weekly emails we send you include figures from it (see Emails).
Website Settings and Audit Results
For each website you add, we store:
- Branded terms: The words we use to separate branded from non-branded searches. We pre-fill them from your domain, and you can edit them in the website's settings.
- Page groups: The names and URL rules of any page groups you create.
- Technical SEO audit results: When you add a website, and then weekly, our servers request its public homepage, robots.txt, sitemap and a sample of its pages, and run automated checks on them. We store the latest result — scores, the issues found and the URLs they affect — and a history of past results. The audit only reads what any visitor could read; it does not log in to your website.
MCP Connections
If you connect an AI assistant or agent to our MCP server (a paid feature), we store:
- Authorization codes and tokens: Stored only as one-way hashes, together with the client they were issued to, their expiry, the time they were last used and whether you revoked them. You can revoke a connected client from the MCP page in the app.
- A request log: One row per tool call, recording which tool was called, whether it succeeded, and when. We use it to enforce rate limits and to investigate problems. It does not record the data the tool returned.
Billing Information
When you subscribe to a paid plan:
- Stripe customer ID: We map your account to a Stripe customer record.
- Billing address: Collected by Stripe during checkout.
- Subscription status: Plan, billing cycle, and payment status are synced to our database.
We do not store credit card numbers or full payment details — these are handled entirely by Stripe.
Emails
We send account email — sign-in codes, billing notices, receipts and messages about your trial — and lifecycle email about getting started with QuickSEO. We also email you about your websites: a weekly summary of what changed, and on the paid plan an email when Google starts a ranking update and an alert when a website's clicks drop well below their usual range. You can turn each of these off on your account page or with the unsubscribe link in each one; we store those choices and a log of the alerts we sent, so the same alert is never sent twice. When you sign up, we add your email address and first name to our contact list in Resend, our email provider. Resend reports when our emails are delivered, opened, clicked, or bounced, and we store those events against your account.
Every marketing email we send carries an unsubscribe link, and a one-click unsubscribe header your email client can act on directly. Unsubscribing stops all marketing email from us immediately. You can also reply to any of our emails, or write to support@quickseo.ai, and we will remove you. Messages about your own account — sign-in codes, billing notices and receipts — are not marketing and are not affected by unsubscribing.
Feedback
If you send us feedback from inside the app, we forward your message to our internal Telegram channel together with your user ID and email address, so we can reply.
Free SEO Tools
Our free tools do not require an account and we do not store what you enter into them. Several of them do send your input somewhere else in order to produce a result:
- Text, URLs, and page copy you submit to our AI-powered tools go to OpenAI.
- The image alt-text generator takes an image URL, not a file upload. Our server fetches that URL, then sends the image it downloaded to OpenAI.
- The domain you enter in the Domain Rating checker goes to Ahrefs.
- The hostname you enter in the SSL checker is sent to crt.sh, a public Certificate Transparency log search service, and our server also requests that host directly over HTTP and HTTPS.
- The domain you enter in the AI training data checker is looked up in the public Common Crawl index.
- The domain you enter in the DNS lookup tool is resolved by our server through the public DNS system.
- Tools that check a page or website you name fetch it from our servers.
Don't paste anything confidential into them.
Data From Retired Features
Earlier versions of QuickSEO offered features we have since retired. If your account used them, the data they stored — for example a copy of your website's public content, answers we collected from AI chatbots, drafted articles, and publishing connections (whose credentials are encrypted) — is no longer used to provide the service and is not sent to any third party. It stays on your account until you delete the website it belongs to, or your account, and it is included in your data export.
One exception keeps running: if you installed our crawler-tracking snippet on a website while your plan included it, that website keeps reporting requests from AI and search-engine crawlers to us — the crawler's user agent and IP address, the page path, and the response status. We delete those records after a year. Remove the snippet from your website to stop it.
If you gave us your email address through a free report or an email course we used to offer, we keep that record (your email address and the details you submitted) until you ask us to delete it, or until you delete a QuickSEO account that uses the same email address.
Usage and Analytics Data
- Datafast: We use Datafast analytics to track page views and events. Datafast uses cookies (visitor ID and session ID) for visitor tracking. If you start a checkout, we pass your Datafast visitor and session IDs to Stripe as metadata so we can attribute the subscription to the visit that led to it — which links that otherwise pseudonymous visitor ID to your customer record. We also report requests from AI and search-engine crawlers to Datafast from our server.
- Vercel Analytics: Performance metrics are collected by our hosting platform.
- Google Tag Manager: Used for conversion and marketing analytics. GTM is the container we configure tracking pixels in, currently including:
- Facebook Pixel (Meta): Used for conversion tracking and retargeting on Facebook and Instagram. Subject to Meta's Privacy Policy.
- Reddit Pixel: Used for conversion tracking and advertising attribution on Reddit. Subject to Reddit's Privacy Policy.
- Google Analytics: Used for website traffic analysis and conversion tracking.
- Our Content Security Policy also permits other marketing and measurement endpoints we may enable through the same container. That list is not exhaustive, but it currently includes Google Ads, Microsoft Advertising (Bing), Microsoft Clarity, and Meta's Conversions API Gateway.
- Meta Conversions API: When you register, start a checkout, or start a trial or subscription, our server reports that event directly to Meta. The report includes a SHA-256 hash of your email address and of your user ID, your IP address and browser user agent, and Meta's
_fbp/_fbccookie values if your browser has them; for checkouts, it also includes the plan's price and currency. To report a completed checkout, we store your IP address, user agent and those cookie values on the Stripe checkout session when you start it. These server-side reports mirror the events the Meta Pixel reports from your browser, and like that pixel they are not gated by the cookie banner. - Email engagement: Resend reports when our emails are delivered, opened, clicked, or bounced, and we store those events against your account.
- The Google Tag Manager container itself loads on every page. In the EU/EEA, UK, Switzerland, and Brazil we set Google Consent Mode to "denied" by default until you accept. Consent Mode is a signal Google's own tags honour — it withholds analytics storage, advertising storage, advertising user data, and ad personalization from them. It is not something we can enforce on non-Google pixels such as Meta's or Reddit's, which are configured inside the GTM container. In those regions, Datafast and Vercel Analytics do not load at all until you accept, and never load if you decline. Everywhere else they load on every page unless you have recorded a refusal through our Cookie preferences control, which we honour wherever you are — see Section 8.
Cookies and Local Storage
- Authentication cookies: Set by Supabase to manage your session.
- Sidebar state cookie: Remembers your dashboard sidebar preference (
sidebar_state, 7-day expiry). - Datafast cookies: Visitor ID and session ID cookies for analytics.
- GTM/Google Analytics cookies: Only set with your consent in regulated regions.
- Facebook Pixel cookies: Used for ad targeting and conversion measurement. Only set with your consent in regulated regions.
- Reddit Pixel cookies: Used for ad attribution and conversion tracking. Only set with your consent in regulated regions.
- Local storage: Dashboard preferences — the selected date range, chart grouping, and the branded/non-branded filter for each website; your cookie consent choice; and which sign-in method you last used.
reCAPTCHA
We use Google reCAPTCHA v2 (the "I'm not a robot" checkbox) on our sign-in form to prevent spam and abuse. reCAPTCHA may collect hardware and software information, such as device data and application data, and send it to Google for analysis. Your use of reCAPTCHA is subject to Google's Privacy Policy and Terms of Service.
2. How We Use Your Information
- To provide our services: Fetching Google Search Console data for the websites you add, building your dashboards and insights, finding opportunities and measuring the ones you mark done, checking indexing with Google's URL Inspection tool, sending the alerts and summaries you have turned on, running technical SEO audits, and answering requests from MCP clients you authorize.
- To process payments: Managing subscriptions, billing, and account status via Stripe.
- To send email: Sign-in codes, account and billing notices, and lifecycle emails via Resend.
- To handle support: Feedback you submit in the app is forwarded to our internal Telegram channel together with your user ID and email address.
- To improve the product and measure our marketing: Usage analytics help us understand feature adoption and performance; conversion events tell our advertising partners which ads led to a sign-up or subscription.
- To prevent abuse: reCAPTCHA and rate limiting protect against spam and unauthorized access.
- To run background jobs: Inngest runs our scheduled and queued work — technical SEO audits, lifecycle emails and routine data clean-up — on your behalf. Job payloads can include your user ID, email address, first name, and website IDs and addresses.
3. Third-Party Services and Data Sharing
We share data with the following third-party services as necessary to operate QuickSEO:
| Service | Data Shared | Purpose |
|---|---|---|
| Supabase | Account data, all application data | Database hosting and authentication |
| Google OAuth / Search Console API | OAuth tokens, the properties you add, the URLs we inspect | Sign-in, reading your Search Console data and index status |
| Google reCAPTCHA | Device/browser signals | Bot and spam prevention on sign-in |
| Stripe | User ID, email, billing address, Datafast visitor/session IDs, and the browser details listed under Meta Conversions API | Payment processing |
| Resend | Email address, first name, email content (including figures from your Search Console data in alert and weekly emails), delivery and engagement events | Account, billing, lifecycle, alert and weekly emails |
| Inngest | Job payloads including user ID, email address, first name, and website IDs and addresses | Background job scheduling |
| Vercel | Application hosting, request logs, page performance metrics, cached Search Console daily totals | Hosting and performance analytics |
| Datafast | Usage events, visitor/session cookies, crawler request metadata | Analytics |
| Google Tag Manager | Conversion events (with consent in regulated regions) | Marketing analytics |
| Facebook / Meta | Page views and conversions from the Meta Pixel; hashed email address and user ID, IP address and user agent from our server | Advertising measurement and retargeting |
| Reddit Pixel | Page views, conversions (with consent in regulated regions) | Advertising attribution |
| Telegram | Your user ID, email address and message text when you send feedback | Internal support notifications |
| AI assistants you connect over MCP | Your websites, Search Console data and technical SEO audit results | Serving our MCP server to a client you authorize |
| OpenAI | Anything you submit to our free AI-powered tools | Free tools |
| Ahrefs | The domain you enter in our free Domain Rating checker | Domain Rating lookup |
| crt.sh | The hostname you enter in our free SSL checker | Certificate Transparency lookup |
| Common Crawl | The domain you enter in our free AI training data checker | Index lookup |
| Public DNS | The domain you enter in our free DNS lookup tool | Resolving DNS records |
MCP clients receive data only if you authorize one yourself, and only while you have access to the MCP server. Once data is returned to an MCP client, it is handled under that client's own terms and privacy policy.
We do not sell your personal data to any third party.
4. Data Security
- Storage: All data is stored on secure servers provided by Supabase (PostgreSQL with Row Level Security).
- Encryption: Data is encrypted in transit (TLS) and at rest by our database provider. Google OAuth tokens are additionally encrypted at the application level with AES-256-GCM before they are written to the database, as are any publishing credentials and webhook signing secrets left from retired features. MCP authorization codes and tokens are stored only as one-way hashes.
- Access control: Database queries enforce user-level access controls to prevent unauthorized data access.
- Security headers: We implement Content Security Policy, X-Frame-Options, X-Content-Type-Options, and strict referrer policies.
- API authentication: All authenticated API routes verify user identity and resource ownership before processing requests.
5. Data Retention
- Account data: Retained for as long as your account is active.
- Google Search Console data: Dashboard tables and charts are not retained — they are fetched when you view them, apart from the daily totals our hosting provider may cache for up to 30 minutes. Insights, opportunities, fix measurements, index monitor results and alert records are kept until you remove the website or delete your account; we keep only the 60 most recent opportunity checks per website, and a URL no sitemap or Search Console report has listed for 14 days leaves the index monitor (its change history stays). The properties you added and your OAuth tokens stay in our database until we delete them; there is no in-app disconnect button today, and deleting a website does not clear your tokens. You can revoke QuickSEO's access from your Google Account permissions page at any time, which stops any further access. Deleting your account removes the stored tokens.
- Website settings and audit results: Retained until you remove the website or delete your account.
- MCP request log: Retained for as long as your account is active.
- Records from retired features: As described in Section 1.
- Marketing unsubscribes: If you unsubscribe from marketing email, we keep a record of your email address on a suppression list so that we do not email you again. This one record survives account deletion — without it, a later campaign could reach you again.
- Analytics data: Datafast retains analytics according to their own policies.
- Payment data: Stripe retains billing records according to their data retention policy and applicable financial regulations.
Removing a website — from "Add or manage websites" or from the website's settings page — deletes that website's data, including its settings, page groups, audit results, insights, opportunities, fix measurements, index monitor results, alerts and any data left from retired features. Deleting your whole account, from your account page, deletes your account and every website on it — see Section 6. Some data may be retained in backups for a limited period or as required by law.
6. Your Rights
Depending on your jurisdiction, you may have the following rights:
- Access: Request a copy of the personal data we hold about you.
- Correction: Request correction of inaccurate or incomplete data.
- Deletion: Request deletion of your personal data and account.
- Data portability: Receive your data in a structured, machine-readable format.
- Objection: Object to the processing of your personal data under certain circumstances.
- Consent withdrawal: Withdraw your consent to data processing at any time, without affecting the lawfulness of processing based on consent before withdrawal.
- Restrict processing: Request that we limit the processing of your data under certain conditions.
How to Exercise These Rights
Deletion and portability are self-serve. Both live in the Your data card on your account page:
- Delete your account. You type your email address to confirm, and we permanently delete your account and every website on it — its settings, branded terms, page groups, audit results, insights, opportunities, fix measurements, index monitor results, alerts and any data left from retired features — along with your email preferences and alert log, your Google OAuth tokens, your MCP connections and request log, and any records held under your email address from a free report or email course we used to offer. It is immediate and we cannot undo it. If you have a subscription that can still be billed, cancel it in the billing portal first: deleting your account does not cancel a Stripe subscription, so we block deletion until billing has stopped. You can delete as soon as you have cancelled, even if paid time is still running.
- Export your data. Downloads a JSON file containing your account details, subscription history, and every website with its settings, page groups, audit results, opportunities, fix measurements, index monitor results and any data left from retired features. On the free plan, opportunities you can't see in the app are exported as their type and estimate only, as they appear there. API keys and OAuth tokens are excluded — an export is not a way to read back a secret.
The one thing we keep is the marketing suppression record described in Section 5.
Everything else — access, correction, objection, restriction, or anything the two controls above do not cover — is handled manually: email us at support@quickseo.ai from the address on your account, tell us what you want, and we will action it and confirm when it is done. We aim to respond within 30 days.
You can also remove an individual website, which deletes that website's data but keeps your account; and you can revoke QuickSEO's access to your Google account from your Google Account permissions page, which stops any further Search Console access.
GDPR (EU/EEA)
If you are in the EU/EEA, you have all the rights listed above under the General Data Protection Regulation. Our cookie consent banner gates analytics and advertising storage in regulated regions — see Section 7 for exactly what it does and does not cover.
CCPA (California)
If you are a California resident, you have the right to know what personal information we collect, request its deletion, and opt out of any sale of personal information. We do not sell personal information.
7. Cookie Consent
If your browser's timezone places you in the EU/EEA, UK, Switzerland, or Brazil, we display a cookie consent banner with Accept and Decline buttons. Be aware of exactly what each one does:
- Decline keeps Google Consent Mode set to "denied" for analytics storage, advertising storage, advertising user data, and ad personalization, and stops the Datafast analytics script and Vercel Analytics from loading at all. We record your refusal so the banner does not come back.
- Accept grants Consent Mode and loads Datafast and Vercel Analytics.
- Ignoring the banner stores nothing, so it is treated as a refusal for that visit — nothing is granted and nothing beyond the GTM container loads — but the banner will appear again on your next visit.
- The Google Tag Manager container itself loads on every page regardless of your choice, so that our tags can be detected. Consent Mode governs Google's own tags; non-Google pixels loaded through the container, such as Meta's and Reddit's, are not covered by it and we cannot enforce your choice on them from the container. The server-side Meta Conversions API reports described in Section 1 are not covered by the banner either.
- Essential cookies (authentication, session management) are always active as they are necessary for the service to function.
- Outside those regions we do not show the banner and all of the above load on every page, as they always have — unless you record a refusal yourself through Cookie preferences, which we honour wherever you are.
Your choice is stored under cookie-consent in your browser's local storage, as accepted or declined. To change it, use the Cookie preferences control, which reopens the banner. You will find it in the footer of our marketing pages — including this one, the home page, pricing, blog, docs, and tools — and, if you are signed in, in the Privacy card on your account page. The reopened banner shows what you currently have saved and can be closed without changing it. Switching from Accept to Decline reloads the page so the analytics scripts stop running immediately. Clearing this site's local storage also resets the choice. You can also email us at support@quickseo.ai and we will handle it.
Region detection uses your browser's timezone rather than a geographic IP lookup. It is an approximation: a browser reporting an unreadable timezone is treated as regulated, but a browser reporting, say, a US timezone while physically in the EU will not see the banner. Use the Cookie preferences link if you want to record a choice regardless of where we place you.
8. Children's Privacy
QuickSEO is not intended for use by children under the age of 16. We do not knowingly collect personal data from children.
9. Changes to This Policy
We may update this privacy policy from time to time. Changes will be posted on this page with an updated "Last Updated" date. Your continued use of QuickSEO after changes are posted constitutes your acceptance of the updated policy.
10. Contact Information
For any questions, data requests, or privacy concerns, contact us at:
- Email: support@quickseo.ai