Privacy policy

1. Data the application accesses

With the signed-in user's authorization, the application accesses the accounts and resources needed for the requested work:

• Google Ads: account details, campaigns, budgets, targeting, keywords, search terms, ads, assets, conversion configuration and advertising performance. The Google Ads permission allows reading and managing advertising data.
• Google Analytics: account and property information, streams, key events, links, definitions and aggregate analytics reports, using read-only permission.
• Google Tag Manager: account and container information, workspaces, versions, tags, triggers and variables. Read access is separate from optional permissions to edit containers, create versions and publish reviewed changes.
• Google Search Console: accessible site properties, search performance and stored URL inspection results, using read-only permission.

The application does not request Gmail, Google Drive or Google Cloud administration access. Separate local credentials are used for advertising, read-only measurement and optional Tag Manager editing and publication.

2. How data is used

Data is used to answer the operator's advertising and analytics questions, inspect measurement, prepare reports and support authorized campaign changes. Requests explicitly identify the Google user profile and target account or resource. Access is limited by the user's Google permissions.

Advertising updates can be prepared and validated before application. Tag Manager changes require an explicit target, a reviewed before-and-after plan and separate authorization; publication is a separate operation. The tool does not change Google Analytics or Search Console settings.

3. AI assistants and other providers

The local tool returns selected data to the operator's chosen MCP client. When the client uses an AI assistant, such as Codex, prompts and selected tool results are processed by that client's AI provider to provide the requested analysis and assistance. This processing is subject to the provider's terms, account settings and retention policy. Local storage of the tool does not mean all analysis remains on the computer.

The operator must use provider settings and account permissions appropriate to the data being processed. Google user data may be shared only as needed to provide the requested user-facing features with authorization. It must not be used to develop, improve or train generalized AI or machine-learning models.

The application does not sell Google user data, use it for advertising profiles or operate a public account-data service. The extension itself does not train AI models. OAuth credentials are used for authentication to Google and are excluded from model-facing results.

Ads Workbench MK's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

4. Storage, retention and security

OAuth credentials are stored in restricted files on the operator's computer. Local reports, connection checks and change records may include account identifiers, campaign settings, advertisement text, before-and-after values and responses from Google.

These local records remain until the operator deletes them; automatic retention expiry is not currently implemented. Credentials and private reports are kept outside the public website and its source repository. Network requests to Google use HTTPS. Access to the computer and the selected MCP client remains the operator's responsibility.

5. Control, revocation and deletion

You can revoke Google access at Google Account connections. Revocation prevents future use of the revoked authorization but does not delete previously saved reports or provider-held conversations.

To request deletion of locally retained application data, contact support@mkworkbench.com.ua and identify the relevant account or report without sending passwords or access tokens. Requests affecting advertising accounts require verification of the requester's authority. Data held by an AI provider must also be managed through that provider's controls.

6. This website and support messages

This website contains no sign-in form, advertising pixels or analytics scripts added by the operator. The hosting provider processes ordinary network request information needed to deliver and secure the pages, such as an IP address and browser request headers.

If you email the operator, your email address and message are used to respond to your request. Please do not include credentials or unnecessary personal information.

7. Updates and contact

This policy will be updated when data handling changes. The effective date appears above.

Operator: Maksym Korkodym
Support: support@mkworkbench.com.ua