Privacy Policy — Dork Industry

Last updated: 2 November 2026

Dork Industry (“we”, “us”, “our”) provides the Dork SEO automation service and the Universal Developer Bridge WordPress plugin. This policy explains what data we access when you connect your Google account, and what we do with it. It replaces the previous template text on this page.

Google data we access

With your explicit consent through the 1-click authorisation in the plugin, we read data for the website you connect, and nothing else:

• Search Console data (scope: webmasters.readonly) — search performance: queries, clicks, impressions, CTR and average position, and which pages are indexed. Used for intent-keyword research, competitor context, and the weekly content audit performance layer.
• Google Analytics data (scope: analytics.readonly) — traffic for your site: pageviews, visitors, time on page, bounce and conversion paths, over the audit window. Used for the weekly content audit performance layer and demand research.
• Google Ads data (scope: adwords) — keyword ideas and search volumes from your own Google Ads account, used only for intent-keyword research. Our product does not create, edit, pause or delete your campaigns through this connection.

All three accesses are read-only in how our product uses them. We cannot change your Search Console settings, Analytics settings or data, or your Ads campaigns through this product, and we do not submit sitemaps or request indexing on your behalf.

What we never access

We never access your email, Drive files, YouTube account, or any other Google product beyond the three scopes above. We never read email content, files, or personal messages. We never sell your data.

How we use your data, including AI-assisted services

Your site’s data is used only for your site: to generate SEO drafts, research demand, and run weekly content audits for that site. Our service is AI-assisted: performance and keyword data may inform article topics and audit decisions, and article writing runs through the large language model provider whose API key you added yourself in the plugin vault. Your Google data is never shown to another customer, never used to train a shared model, and never combined into another customer’s report.

How tokens are stored

Each connected site’s Google refresh token is stored encrypted (AES-256-GCM) in our backend database, tied to that site’s license only. Tokens are never returned to the browser, never shown in the plugin interface, never logged, and never shared with another customer. Only the backend service that needs them can decrypt them. Your Google tokens are never sent to your LLM provider or SERP provider — those providers receive only the prompts and queries needed for your articles.

Third-party sharing

None, except the providers you choose yourself: the LLM provider whose API key you added in the plugin vault, and the SERP provider configured for your plan. Those providers receive only prompts and queries, never your Google tokens.

Retention and deletion

Data is kept while your subscription is active and your site stays connected. Disconnecting a site in the plugin revokes and deletes that site’s stored Google tokens. You can also revoke access at any time from your Google Account > Security > Third-party access.

Contact and deletion requests

For deletion requests or questions about this policy, contact us at dorktech007@gmail.com.