Privacy policy — Tino Research

Effective date: September 28, 2026.

Purpose and information accessed

The Tino project owner uses Google's official Google Ads MCP server and the Google Ads API through Codex for their own analysis. The connection can retrieve identifiers of accessible Google Ads accounts and the account information and reporting fields requested by the owner. The specific information returned depends on the query. The Google OAuth permission used is https://www.googleapis.com/auth/adwords. Google documents this scope for Google Ads API access; a separate read-only OAuth scope is not documented. The scope can permit changes as well as reads, subject to the Google Ads account permissions. The workflow described here uses the connection for retrieval and analysis, not automatic campaign changes. Campaign management is not currently implemented in this connection; its description and data practices will be updated before that capability is introduced.

Authorization

The installed local MCP server uses Google's standard Application Default Credentials for authorization. Credentials are handled by the local Google authentication setup. They are not included in these public pages.

Use and transfer

Google processes API requests and returns their results to the local MCP server. The server returns results to Codex for the requested analysis. Information included in tool results and conversations is therefore processed by OpenAI as part of the Codex service. The operator does not represent this workflow as local-only processing. OpenAI's handling of that information depends on the account, applicable service terms and data controls.

Google API data use requirements

Use of information received from Google APIs is governed by the Google API Services User Data Policy, including its Limited Use requirements where applicable. The permitted purpose of this connection is the operator's requested analysis. Transfers to Codex must be limited to that purpose and authorized by the operator. The connection must not be used to sell Google API data or provide it to data brokers.

Storage

Authorization credentials are retained by the local authentication setup. Results and analysis may be retained in Codex conversations and in files or reports the owner chooses to save. The installed MCP implementation logs query text for diagnostics; query text can include query conditions. This connection does not establish a separate fixed retention period or promise that all information is immediately deleted after a query.

Revocation and deletion

The owner can revoke the OAuth application's access in their Google Account permissions. Revoking access stops future authorized access but does not delete previous results or reports. Existing Codex conversations, saved files and diagnostic records must be managed through the respective service controls or local storage. Requests concerning the operator's saved copies can be sent to the published contact address. Deletion of copies held by Google or OpenAI is governed by those providers' controls and policies.

This website

These pages contain no sign-in form, advertising code or application analytics script. Hosting is provided by Cloudflare, which processes requests needed to deliver the pages. Information sent by email is processed by the email provider.

Contact

Timur, founder of the Tino project. Email: [email protected]