Privacy Policy

Last updated: 28 October 2026

Related documents: Terms of Service · Contact Us

Introduction

This Privacy Policy describes how Guangzhou Prink International Cosmetics Co., Ltd. (“Prink”, “we”, “us”, or “our”) operates Prink Ads Monitor, an internal Google Ads monitoring setup used to retrieve authorized advertising account mapping and performance metrics through the Google Ads API.

Prink Ads Monitor is operated for Prink’s own advertising-monitoring purposes. It is not presented on this website as a public SaaS product, and it is not integrated into the public Prink cosmetics storefront experience unless a separate integration is later configured and disclosed.

Prink Ads Monitor is not an official Google product and is not endorsed by Google. This policy describes the data-handling practices that apply to the monitoring setup as configured at the time of the last update above.

Information We Access

When an authorized Google Account grants OAuth access and the monitoring components are configured, Prink Ads Monitor may access Google Ads information returned by the configured API queries. In the current configuration, that information may include:

• Google Ads account identifiers and descriptive account names, where returned by configured queries
• Campaign IDs and campaign names
• Ad group IDs and ad group names
• Impressions, clicks, advertising cost, conversions, and related performance metrics enabled in the exporter queries
• Advertising network information, where collected by the configured queries
• Placement display names and placement types, where those collectors are enabled
• Ad approval or review status fields returned by the configured approval queries
• Collection timestamps and monitoring metadata created by the exporter, Prometheus scrape process, or dashboards
• OAuth authorization information and local authentication credentials required for API access (for example, values stored in a local google-ads.yaml configuration file such as client identifiers, client secrets, refresh tokens, and developer tokens)

This page does not publish actual account IDs, campaign IDs, refresh tokens, client secrets, or other credentials.

Based on the inspected query configuration, Prink Ads Monitor is used to retrieve Google Ads advertising-structure and performance metrics. It is not configured to request end-customer personal profiles, payment card details, or unrelated personal contact books. If future queries expand the accessed categories, this policy should be updated.

How We Use Information

Authorized Google Ads data is used only to operate the monitoring functions that are actually configured, including:

• Retrieving authorized campaign and ad group mapping information
• Monitoring advertising performance
• Displaying impressions, clicks, costs, conversions, and related metrics in Grafana dashboards
• Reviewing collection status and historical metric trends in Prometheus and Grafana
• Supporting configured Prometheus alert rules and Alertmanager routing, where those components are running

Not every optional feature described in upstream Ads Monitor documentation is necessarily enabled in every deployment. Feature availability depends on the local configuration.

Google Ads data obtained through Prink Ads Monitor is not sold and is not used for unrelated advertising, advertising targeting of end users, or unrelated commercial purposes outside the authorized monitoring workflow.

Google API Services User Data

Prink Ads Monitor uses Google Ads API access solely to provide and maintain the authorized monitoring functionality described in this policy: collecting configured advertising metrics, storing them in the local monitoring stack, visualizing them, and evaluating configured alerts.

Use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Prink Ads Monitor is not Google-certified and is not endorsed by Google. This policy does not claim unrestricted third-party sharing rights or processing purposes beyond the monitoring functions described here.

Data Storage and Security

The inspected local deployment stores monitoring components and credentials as follows:

• OAuth client credentials, refresh tokens, developer tokens, and related Ads API settings are kept in a local google-ads.yaml file outside the public website repository
• GAARF Exporter reads that configuration, queries the Google Ads API, and exposes metrics for scraping
• Prometheus scrapes those metrics and stores time-series data in its configured local storage volume
• Grafana reads Prometheus data and stores dashboard/admin state in its local data volume
• Alertmanager is present in the stack; the inspected local receiver configuration currently routes to a null receiver unless an operator later configures an external notification channel

Metrics and credentials used by the local Docker-based deployment are stored on the machine or volume hosting that deployment. Google Ads API requests are sent to Google’s services as part of authorized API access. This policy does not claim that all related data never leaves the local machine, because API calls to Google are required for collection, and any future external alert receivers would transmit alert payloads if configured.

No separate encryption-at-rest certification, automated deletion schedule, or third-party security certification for Prink Ads Monitor was verified in the inspected configuration. Operators should protect host access, Docker volumes, Grafana credentials, and google-ads.yaml with appropriate local access controls.

Data Sharing and Third-Party Services

The monitoring setup uses the following components in their usual roles:

• Google Ads API — authorized source of advertising account and performance data
• GAARF Exporter — collection component that runs configured GAQL queries and exposes metrics
• Prometheus — metrics storage and query component
• Grafana — visualization component for dashboards
• Alertmanager — alert routing component; external destinations only if an operator configures them

The inspected local Alertmanager configuration does not currently send notifications to Slack, email, or other external receivers. If an operator later adds such receivers, alert-related metric labels and messages may be transmitted to those services under their own terms.

Prink does not sell Google Ads monitoring data. Sharing is limited to the Google API interaction required for authorized access, the local monitoring components listed above, and any external receivers that an operator explicitly configures.

Data Retention and Deletion

The inspected Prometheus compose configuration does not set an explicit custom --storage.tsdb.retention.time (or equivalent) retention flag. Metric retention therefore follows the Prometheus server defaults for that deployment unless an operator later configures a specific retention period.

Stored materials may be removed according to the actual deployment, for example by:

• Deleting or rotating local google-ads.yaml credentials and related OAuth client secrets
• Removing Prometheus and Grafana Docker volumes or stored TSDB/dashboard data
• Stopping or removing the monitoring containers
• Deleting local dashboard exports or configuration copies retained by operators

Revoking Google OAuth authorization prevents future API access through that grant. It does not automatically delete metrics, dashboards, or configuration copies already stored locally.

Revoking Google Account Access

You can revoke the application’s access to your Google Account from Google’s third-party connections settings:

https://myaccount.google.com/connections

After revocation, Prink Ads Monitor should no longer be able to obtain new Google Ads data through that authorization. Previously stored local metrics and configuration files are not automatically erased by revocation alone and may require separate local deletion by the operator.

Privacy Requests and Contact

For privacy questions, access requests, or deletion requests related to Prink Ads Monitor, contact Guangzhou Prink International Cosmetics Co., Ltd. through the website Contact Us page.

Company email: prinkcosmetics@gmail.com

Telephone: +86 17728879962

Changes to This Policy

We may update this Privacy Policy when Prink Ads Monitor’s functionality, deployment model, or data practices change. The “Last updated” date at the top of this page shows the date of the current version. Continued use of the monitoring setup after an update means the revised policy applies to subsequent data handling.

Also see the Terms of Service for Prink Ads Monitor.