jinraiko-ads-mcp Privacy Policy

Effective date: November 11, 2026
Last updated: November 11, 2026

About this application

jinraiko-ads-mcp is operated by 深圳市振庭贸易有限公司. It is an internal tool for viewing and analyzing the performance of Google Ads accounts that the Operator has authorized. It is not an official Google product.

Data access and use

The application uses Google OAuth to obtain authorization to read advertising reports from those accounts. OAuth credentials, including the refresh token and related Google Ads API credentials, are stored in a local environment file on the workstation that runs the application. They are used to maintain that authorized connection and to retrieve the reports described in this Policy. They are not stored in this website or in the ERP snapshot.

Depending on the report requested, the application currently retrieves:

  • Advertising account ID, descriptive name, currency, and time zone
  • Campaign ID and name
  • Ad group ID and name
  • Ad ID and ad name (an ad name may be absent)
  • Keyword ID, keyword text, match type, and quality score, or search term text
  • Spend, impressions, clicks, CTR, CPC, primary conversions, conversion value, and value/spend ROAS calculated from the applicable metrics

The application does not currently retrieve Google Ads creative or asset identifiers, or Google Ads geographic or audience-country breakdowns. Application reports cover a chosen period of 1–90 complete days ending yesterday in the ad account’s time zone and are aggregated over that period. A collector may also store a single account-level total of spend, impressions, and clicks for the previous complete day.

We use this information for internal advertising analysis and to display summarized results in the Operator’s internal tools and ERP reports. The application’s current Google access is used for query and analysis. It does not automatically create advertisements, change budgets, or pause or otherwise modify campaigns. This is a limit of current behavior, not a claim that the Google OAuth scope itself is read-only.

Storage and processing

Report results may be temporarily cached in the application process’s memory, saved in local reporting files on the operator workstation, and included in access-controlled ERP reporting snapshots.

When a collection succeeds, a collector writes a local snapshot of summarized daily account-level totals (spend, impressions, and clicks). When a publish step is run, that snapshot is transferred over an existing authenticated SSH connection to a private directory on the Operator’s internal ERP server. The ERP snapshot contains summarized daily metrics and source status. It does not include OAuth credentials or raw API responses. Ad-level Google Ads tool results are returned through the application and are not part of the ERP snapshot.

When reports are requested through a connected assistant or MCP host, the results are provided to that service for presentation and analysis. Its processing may involve cloud services and conversation history. These results are not necessarily stored only on the local computer.

The following processing is part of the current implementation:

  • Google provides the Google authorization and the Google Ads API used to retrieve the data.
  • The connected assistant or MCP host receives report results for presentation and analysis.
  • The Operator’s internal ERP application stores and displays the published snapshot for authorized internal users.
  • Shopify hosts this public policy and introduction page only. This does not mean that Google Ads credentials are stored in the page.

Access and security

Access is limited to authorized operators and the services used for the reporting workflow. The ERP advertising report is available only to authorized internal users after sign-in and an additional finance verification step. It is not a public advertising API.

Credentials must not be published in source repositories or shared in chat. The application’s tool responses do not intentionally expose authorization tokens or raw authentication errors. Local and server snapshot files are written with restricted permissions, and the server snapshot is kept outside the public web root. This Policy does not claim that credentials or stored reports are encrypted.

Retention and deletion

In-memory report cache entries are kept for 1–6 hours (default 3 hours), or until the application process restarts.

OAuth and API credentials are kept for as long as they are needed to operate the application under a valid authorization.

Daily rows in the local and ERP snapshot files are kept under a 90-day cutoff in those snapshot files. Temporary cache expiration or the removal of a row from those snapshot files does not automatically delete other saved reports, exports, backups, or assistant conversation history.

To request deletion, contact support@jinraiko.com and identify the relevant advertising account. Do not send passwords or authorization tokens. We will assess the request, identify records under our control, and explain the applicable deletion steps and any retention limitations.

Revoking access

You can revoke the application’s access through your Google Account’s third-party connections settings:
https://myaccount.google.com/connections

Revoking authorization prevents further access under that authorization. It does not automatically delete previously saved information, including local reporting files, ERP snapshots, cached results, or conversation history.

Contact and updates

For questions or deletion requests, contact support@jinraiko.com.
We will update this page when our data-handling practices change.