Privacy Policy

Last updated: November 17, 2026

This policy explains what BestSERP ("we") collects when you use our website and API, why, and your choices. Contact [email protected] with any question.

1. Data we collect

  • Google account data. When you sign in with Google we receive your name, email address, profile picture and a Google account identifier. We do not receive your Google password.
  • API usage. For every request: the endpoint, query and parameters, the result we returned, status, credits charged, timestamps, the API key used (never the full key in readable form), IP address and user agent.
  • Payments. PayPal processes payments. We store the order and capture ids, amount, status and the credits granted. We never see or store card or bank details.
  • Free tools. Inputs you submit (keywords, domains, URLs), your IP address and the results.
  • Support. Messages you send us on Telegram or by email.

2. Cookies and browser storage

We use strictly necessary cookies: a session cookie that keeps you signed in (HttpOnly, 30 days, renewed while you use the site) and a short-lived cookie that protects the Google sign-in flow. Cloudflare Turnstile may set cookies to tell humans from bots. We do not use advertising cookies.

Your browser also stores a few preferences on your device only, never sent to us: whether the dashboard sidebar is collapsed, your last 10 playground searches, onboarding progress, and your cookie choice. A newly created API key is kept in the browser tab's session storage until you close the tab, so the playground can fill it into code samples.

Analytics. When website analytics is on, we use Plausible, which sets no cookies and counts visits in aggregate, and/or Google Analytics, which uses Google's Consent Mode and depends on where you are, as Cloudflare and Google tell from your IP address:

  • In the EEA, the UK and Switzerland (and when your location is unknown), Google Analytics sets no cookies unless you accept them in the cookie banner. Until then it sends Google cookieless measurements, such as that a page was viewed, which Google uses to estimate visit counts.
  • Elsewhere, Google Analytics sets its cookies (_ga, _ga_*) when you visit, without asking first.

Wherever you are, you can turn Google Analytics off completely at any time with "Cookie settings" at the bottom of every page; declining also removes its cookies. Google Analytics' advertising features are never enabled.

3. How we use data

  • To provide the service: authenticate you, run your searches, count credits and show your logs.
  • To prevent abuse and fraud, enforce limits and secure the service.
  • To process payments and keep records required by law.
  • To answer support requests and send essential service messages.

4. Search queries and results

Queries you send are used to fetch results from Google on your behalf. Results may be cached for a short time (about one hour) and served to identical requests. Request logs, including queries and results, are kept for a limited retention period and then deleted.

5. Sharing

We share data only with processors that run the service: our hosting providers, Google (sign-in), Cloudflare (bot protection) and PayPal (payments); and, when we turn them on, an error tracking service (Sentry, which receives error details without request headers, cookies or request bodies) and the analytics provider described above. We do not sell personal data.

6. Retention

Account data is kept while your account is open. Request logs, free tool checks and expired sessions are deleted after their retention period. Payment records are kept as long as accounting law requires.

7. Your rights

In the dashboard, Settings lets you download your data (profile, API keys without their secret part, credits, payments and the last year of requests, as JSON) and delete your account. Deleting it revokes your API keys, ends your sessions, removes your name, email, photo, search queries and IP addresses, and forfeits unused credits. We keep payment records as accounting law requires, and a one-way hash of your Google account identifier so that a new account on the same Google account does not receive free credits again. You can also ask for a copy of your data, its correction or deletion, or object to processing, by writing to [email protected].

8. Security

API keys and session tokens are stored only as hashes. Traffic is encrypted in transit. Access to production data is limited to staff who need it.

9. Changes

We will post changes here and, for material changes, notify you by email. See also our Terms of Service, how credits and refunds work, and the contact page.