Privacy Policy for Devaka Tools —SEO Pro Extension

Effective date: May 13, 2026

This Privacy Policy describes how the Devaka Tools — SEO Pro Extension (the “Extension”), a Chrome browser extension, handles information when you install and use it. It is published to meet Chrome Web Store transparency expectations and applicable privacy laws where they apply to you.

If you do not agree with this policy, please do not use the Extension.


1. Data controller and contact

The data controller for personal data processed through the Extension (including analytics described below) is Serhii Koksharov. Independent developer — SEO Analyst.

Privacy and general contact: [email protected]

Use this email for: privacy requests, questions about this policy, objections to processing where applicable, and requests to access, correct, or delete information we hold that is associated with your use of the Extension (including server-side analytics logs, where feasible).

The same contact information may appear on the Chrome Web Store listing for this Extension.


2. Who this policy applies to

This policy applies to end users who install or use the Extension. References to “we”, “us”, and “our” mean the data controller above.


3. Summary

  • The Extension provides on-page SEO inspection (for example, tags, headings, links, structured data) and related tools inside your browser.
  • It stores settings and technical identifiers locally on your device (Chrome storage and extension-scoped storage such as IndexedDB).
  • It sends limited usage analytics over HTTPS to https://devakatalk.com/overlay/analytics.php, where events are appended to server log files. Logs are retained for 90 days, then deleted as part of rotation and retention practices described in Section 5.
  • Optional AI chat sends requests to Google’s Gemini API when you add your own API key; that processing is governed by Google’s terms and privacy notices.
  • The Extension may issue network requests to the sites you audit and related resources (for example robots.txt, or checks involved in indexing features).

4. Information the Extension accesses

4.1 Web pages you open

The Extension injects a content script on pages you visit (as permitted by Chrome). It can read page content and structure available in the DOM of the active tab while you use the Extension on that tab, to render audits, overlays, and tools. This processing is intended to occur locally in your browser for those features.

We do not use our analytics pipeline (Section 5) to collect full page HTML, full page text, full URLs, or chat transcripts. Analytics are limited to event names, technical identifiers, page origin (scheme + host only where recorded), and small, size-capped JSON properties. Content you send to Google Gemini is covered in Section 7.

4.2 Browser tab and session metadata

The Extension may use Chrome tab IDs and browser-generated session identifiers to correlate events within a session. These are technical values, not your name or email.

4.3 Install identifier

The Extension may create and store a random install identifier in chrome.storage.local. It is used to distinguish installations for analytics and diagnostics and is not derived from your Google account by the Extension.

4.4 Settings you choose

Preferences (for example UI layout, theme, optional page keywords, language options for AI answers) may be stored in chrome.storage.local on your device.

4.5 API keys you provide (optional)

If you use AI features, you may enter a Google Gemini API key. It is stored only on your device in extension storage. It is used to call Google’s API (Section 7). We do not intentionally transmit your API key to our analytics endpoint.


5. Analytics and server-side processing

5.1 What we collect (analytics)

The Extension may record usage events including:

  • Timestamp of the event
  • Event type / name (for example, which part of the UI was used)
  • Install identifier
  • Session identifier and tab identifier (numeric, where applicable)
  • Page origin (scheme + host, e.g. https://example.com), when available
  • Small JSON “properties” per event (the Extension limits serialized size to reduce oversized payloads)

We do not design this stream to collect full URLs, query strings, passwords, form values, or chat message content.

5.2 Storage and transmission

  • Events may be queued locally (for example in IndexedDB) before upload.
  • Batches are sent via HTTPS to https://devakatalk.com/overlay/analytics.php, where they are written to append-only style log files (e.g. JSON lines) for troubleshooting, reliability, and aggregate product insight.

5.3 Purposes

We use this information to measure feature usage, detect errors or friction, and improve stability and user experience.

We do not sell personal information and do not use this analytics stream for cross-context behavioral advertising.

5.4 Retention (server-side)

Server-side analytics logs are kept for up to 90 days, after which they are deleted or overwritten as part of log rotation. Locally cached copies on your device may be removed sooner by the Extension after successful sync or housekeeping.


6. Network requests to third-party sites

For SEO and related checks, the Extension may request:

  • The page or site you are auditing (for example HEAD / GET for availability, headers, or body as needed for a check), and
  • Related URLs (such as robots.txt or URLs involved in indexing checks).

Those requests are sent from your browser. Third-party site operators may record them under their own privacy policies.


7. Google Gemini (optional AI features)

If you enable AI features and provide a Gemini API key, the Extension sends requests to:

https://generativelanguage.googleapis.com/ (Google Gemini API)

Google Ireland Limited / Google LLC (as applicable) processes prompts, tool payloads, and other content you include in API requests under Google’s terms and privacy policy, including notices for the Gemini API. See: Google Privacy Policy and Google’s documentation for Generative Language API / Gemini.

We do not control Google’s processing. You choose what to send and are responsible for safeguarding your API key.


8. Other third-party services (overview)

ServiceRoleNotes
Google (Gemini API)Optional AI inferenceOnly when you add an API key and use AI features.
devakatalk.com analytics endpointReceives usage events described in Section 5Operated by the data controller; 90-day log retention.

9. Legal bases and rights (EEA, UK, and similar jurisdictions)

Where the GDPR, UK GDPR, or comparable laws apply:

ProcessingLegal basis (summary)
Usage analytics (Section 5)Legitimate interests in operating, securing, and improving the Extension, in a way that minimizes data and avoids profiling for advertising. You may object to this processing or ask for deletion of server-side records tied to your install where we can reasonably identify them—contact [email protected].
Optional AI via GeminiProcessing is initiated by you when you enter an API key and send requests; the legal basis is typically performance of a feature you request and/or your explicit action, alongside Google’s role as a separate controller or processor under Google’s terms.

You may have rights to access, rectify, erase, restrict, object, and data portability, and to lodge a complaint with a supervisory authority. Because analytics often use a random install ID, please include any details that help us locate your events (for example approximate start date of use, event examples, or the install ID if you export it from diagnostics tools you use).

Contact for rights requests: [email protected]


10. U.S. state privacy (e.g. California)

We do not sell personal information or share it for cross-context behavioral advertising as described in our analytics use (Section 5). Depending on your U.S. state of residence, you may have rights to know, delete, or correct certain personal information, and to appeal decisions. Submit requests to [email protected]. We may need to verify your request.


11. Children’s privacy

The Extension is not directed at children under 13 (or the higher minimum age where local law requires). We do not knowingly collect personal information from children.


12. International transfers

Analytics and contact handling may involve processing in countries other than your own, depending on where servers and email providers are located. We transmit analytics over HTTPS. Where required, we rely on appropriate safeguards (for example standard contractual clauses offered by providers) in line with applicable law.


13. Security

We use reasonable technical and organizational measures, including TLS (HTTPS) for analytics uploads. No system is completely secure.


14. Changes to this policy

We may update this Privacy Policy when our practices or the Extension change. We will adjust the Effective date at the top for material updates. We encourage you to review this page periodically. If the law requires additional notice for your region, we will comply with those requirements.


15. Uninstalling the Extension

Removing the Extension from Chrome usually deletes locally stored extension data (settings, install ID, queued events), subject to Chrome’s platform behavior. Analytics events already received on our servers are deleted in line with the 90-day retention in Section 5.4.


Last updated: May 13, 2026.