SEO Check Tools

Privacy Policy

Effective: May 29, 2026

This policy describes what happens to information when you use SEO Check Tools at seocheck.tools. We've tried to write it in plain English. If something is unclear, email us.

The short version

  • We don't require an account.
  • We don't use tracking cookies or behavioural ad networks.
  • We don't store the prompts you submit to AI tools or the generated outputs.
  • We briefly hold your IP address paired with the current UTC date, in memory only, to enforce a daily fair-use limit on AI tools. That information is discarded each UTC midnight.
  • We use a small number of third-party services to make the site work — listed in full below.

What we collect, and why

IP address (for rate limiting)

When you use an AI-powered tool we briefly note your IP address paired with the current UTC date in our Redis cache. This lets us enforce a daily limit of 15 generations per tool per IP. The record is held in memory only and is automatically discarded at the end of each UTC day. We do not log IPs anywhere else, do not correlate them with browsing activity, and do not share them with third parties for marketing.

Prompts and outputs (not stored)

When you ask an AI tool to generate something (a title, description, tag list, etc.), your prompt is sent server-side to Anthropic's Claude API and the response is returned to your browser. We do not retain a copy of either. We do hash the normalized prompt and cache the response for 24 hours so that identical follow-up requests don't cost extra compute — this cache key is the hash of the prompt, not the prompt itself.

URLs and channels you paste into utility tools (not stored)

For tools that look up information from YouTube — like the Channel Audit, Visibility Score, Outlier Finder, Niche Check, Channel ID Finder, Tag Extractor, and Keyword Tool — we query the YouTube Data API v3 server-side to fetch publicly available metadata (channel stats, video lists, video stats, search results) and return the result. We cache the response per query for 6–24 hours so popular lookups are fast and cheap. The cache stores only the query and the API response, not who requested it. See the “YouTube API Services” section below for the full disclosure required by YouTube's API terms.

Cookies

We use cookies only for two strictly necessary purposes:

  • Cloudflare Turnstile bot protection. When you use an AI tool, Cloudflare may set a short-lived cookie (cf_clearance, __cf_bm) to identify that you've already passed the bot challenge. These cookies are required for the AI tools to function.
  • Vercel Analytics. Our page-view analytics is the cookieless variant of Vercel Analytics — it does not drop a cookie and does not personally identify visitors. It records page paths and anonymized device-class data only.

We do not use third-party advertising cookies or cross-site tracking cookies. If we add Google AdSense or affiliate program cookies in the future, this policy will be updated and the additions clearly disclosed.

Third-party services involved when you use this site

The minimum set of providers we share data with so the site can function:

  • Anthropic. AI generation requests are forwarded to Anthropic's Claude API for processing. Anthropic's privacy policy: anthropic.com/legal/privacy. Anthropic retains API request data for up to 30 days for trust & safety review before deletion; they do not use API data for model training.
  • Cloudflare. Cloudflare hosts our DNS, provides DDoS protection, and runs the Turnstile bot challenge on AI tool endpoints. Their privacy policy: cloudflare.com/privacypolicy.
  • Vercel. Vercel hosts the site and provides the cookieless page-view analytics. Their privacy policy: vercel.com/legal/privacy-policy.
  • Upstash. Upstash provides the Redis instance we use for rate limiting and short-term caching. Their privacy policy: upstash.com/trust/privacy.pdf.
  • Google (YouTube Data API). When you use a tool that looks up channel or video data, we query the YouTube Data API v3 server-side to fetch publicly available metadata. Google's privacy policy: policies.google.com/privacy. Use of the YouTube Data API is governed by the YouTube API Services Terms of Service: developers.google.com/youtube/terms/api-services-terms-of-service. See the dedicated “YouTube API Services” section below.

YouTube API Services

Several tools on this site — Channel Audit, Visibility Score, Outlier Finder, Niche Check, Channel ID Finder, Historical Tracking, and the Competitor Channel Analyzer — query the YouTube Data API v3 to fetch publicly available channel and video metadata (channel statistics, video lists, video statistics, search results, video category metadata). We do not request OAuth permission to read your YouTube account, we do not access private data on your behalf, and you are never asked to sign in with Google to use these tools.

By using these tools you agree to be bound by the YouTube API Services Terms of Service and acknowledge that data we surface from YouTube is governed by Google's Privacy Policy.

What YouTube-derived data we store

  • Short-term query cache (6–24 hours). Responses to API lookups (channel stats, video lists, video stats) are cached per query so popular lookups are fast. The cache key is the query itself; we do not associate cached data with the IP that requested it.
  • Channel snapshots for Historical Tracking (up to 26 weekly snapshots per channel). When a user opts into tracking a channel, we run a weekly background re-audit and store the resulting metrics (Visibility Score breakdown, subscriber and view counts, upload cadence) so the trend chart can render. These snapshots are keyed by channel ID, not by the user who added the channel.
  • Derived metrics (Visibility Score, sub-scores). Per the YouTube API derived-metrics policy, our Visibility Score is computed by us, clearly labelled as our own metric, and not sourced or implied to be sourced directly from YouTube's API.

How to revoke access and delete YouTube-derived data

Because we don't request OAuth scopes from your Google account, there is normally nothing for you to revoke at myaccount.google.com/permissions. To remove cached YouTube data we hold about a channel, email hello@seocheck.tools with the channel URL or channel ID. We will purge the short-term query cache, any Visibility Score snapshots, and any Historical Tracking history for that channel within 7 days of the request.

Your rights

If you're in the EU, UK, or EEA (GDPR)

Under the GDPR you have the right to access, rectify, delete, or restrict processing of your personal data. Because we do not maintain any persistent record tied to an individual user (no accounts, no profiles, no long-term IP logs), there's typically nothing for us to retrieve or delete on request. If you believe we hold information about you, email us at hello@seocheck.tools and we'll confirm in writing within 30 days.

Our legal basis for processing the limited IP data described above is legitimate interest (Article 6(1)(f) GDPR) — preventing abuse of a free service. You may object to this processing at any time, in which case you may not be able to use the AI-powered tools but the browser-side tools will continue to work.

If you're in California (CCPA / CPRA)

We do not sell or share personal information for cross-context behavioural advertising. We do not knowingly collect personal information from California residents under the age of 16. You have the right to know, delete, and limit the use of any personal information we hold about you. To exercise any of these rights, email hello@seocheck.tools.

Children's privacy

The site is intended for users aged 13 and over. We do not knowingly collect personal information from children under 13. If you believe a child has provided information to us, please contact us so we can investigate.

Data retention summary

  • IP + UTC date (rate limit): in-memory, discarded at UTC midnight
  • Prompt-output cache (AI tools): hash of prompt and output, 24 hours
  • YouTube Data API lookup cache: 6–24 hours per query, keyed by query (not by requester)
  • Historical Tracking channel snapshots: up to 26 weekly snapshots per tracked channel, keyed by channel ID; purged on email request within 7 days
  • Vercel Analytics events: per Vercel's standard retention
  • Server access logs: Vercel's default retention (typically a few days), purged automatically

Changes to this policy

When we change anything substantive — adding a new third party, changing what we collect, adding advertising or affiliate tracking — we'll update the "Effective" date at the top and summarise the change here. Continued use of the site after a change means you accept the new terms.

Contact

Questions about this policy or how we handle data: hello@seocheck.tools.