PolyCode SEOBuddy Privacy Policy

1. Data SEOBuddy processes

• •Keyword queries you submit to Keyword Research or related SEO tools, so the backend can request provider metrics.
• •Domain names from supported search-result pages when SERP Overlay requests domain metrics.
• •The page you explicitly audit. On-Page Audit reads technical page signals in the browser, including title/meta, headings, structured data, image-alt, link, canonical/robots and local browser performance signals.
• •Tracked sites, tracked keywords and rank-position history when you enable Rank Tracker.
• •Account and authentication data needed for sign-in, such as your email address and password hash.
• •License and entitlement data required to activate, validate, refresh or deactivate a SEOBuddy license.
• •Google Search Console data only after you explicitly authorize Google OAuth for your account.

2. Data SEOBuddy does not intentionally collect

• •General browsing history outside supported SEOBuddy operations.
• •Keystrokes, unrelated form fields or passwords entered on websites you visit.
• •Precise location data for advertising or profiling.
• •Provider API credentials inside the browser extension bundle.
• •Personal data for sale to advertisers or data brokers.

3. How data is used

• •Provide keyword, SERP, backlink, competitor, on-page and rank-tracking features requested by you.
• •Authenticate accounts, enforce plan limits and validate licenses.
• •Maintain rank history and generate rank-tracking summaries or email digests when those features are in use.
• •Operate, secure and troubleshoot the service using bounded technical logs and usage counters.

4. External services

Depending on the feature and your plan, SEOBuddy can use DataForSEO for SEO metrics, Google Search Console after your OAuth authorization, and Yandex APIs for supported Russian-market data. Payments and subscription changes are handled on the PolyCode website through the payment providers offered there; the browser extension does not collect card details.

5. Security

• •Network traffic uses HTTPS/TLS.
• •Account passwords are stored as password hashes rather than plaintext passwords.
• •Provider secrets stay on the backend and are not shipped in the extension.
• •Stored Google OAuth credentials are encrypted before database persistence using the backend encryption layer.
• •Central license runtime/refresh tokens are sealed with authenticated encryption before the backend token store receives them.
• •License identity and paid-feature decisions are validated server-side; the extension cannot authoritatively upgrade its own plan.

6. Storage and retention

SEOBuddy stores account, entitlement and feature data only as needed to operate the service and your enabled features. Rank Tracker necessarily retains tracked sites, keywords and position history so historical charts can work. Provider responses may be cached for bounded operational periods. We do not promise a fixed retention period here unless a product workflow or applicable law requires one; deletion requests are handled through the privacy contact below.

7. Your choices and rights

• •You can stop extension processing by disabling or uninstalling SEOBuddy.
• •You can disconnect optional Google Search Console access.
• •You can request access to, correction of, export of or deletion of personal data associated with your account, subject to legal or security retention requirements.
• •Where GDPR or other applicable privacy law grants additional rights, those rights continue to apply.

8. Commercial Public Beta

SEOBuddy is currently offered as a Commercial Public Beta. Provider coverage and some metrics can vary by search engine, region and plan. Directional SEO estimates are presented as estimates and are not treated as guaranteed search-engine outcomes.

9. Policy changes

We may update this policy when SEOBuddy data flows or providers materially change. The date at the top of this page identifies the current published version.