Privacy Policy

Google Account and Google Ads Data

The Google Ads connection is part of LITONGWIN Growth BI. Google identifies this application as LITONGWIN Growth BI. Older authorizations may appear under its previous name, Ultron Growth BI. This connection lets you review advertising results in your workspace. When you authorize it, we receive your Google account identifier and verified email address, the advertising accounts available to your Google account, and information for the advertising accounts you choose to synchronize. This may include account names and identifiers, currency and time zone, campaign and ad information, available creative metadata, and daily spend, impressions, clicks, conversions, and conversion values reported by Google. Available creative metadata may include names, advertising text, image references, and video identifiers.

We use this information to connect the right Google account, synchronize the accounts you select, organize reports by project, and show campaign and creative performance. If you enable scheduled synchronization, it refreshes these reports while your authorization remains valid. Our current Google Ads integration reads data for reporting and analysis. It does not create, modify, pause, or delete ads or campaigns, or change bids, budgets, or billing settings. We request Google's Google Ads permission (adwords), together with openid and email permissions to identify the connected Google account. The Google Ads permission has broader capabilities than this integration uses. Its consent description does not mean that our current integration performs the management actions listed above.

If you choose to export a report or enable report delivery to a connected destination, we may send the report data you select to the service you specify, such as Feishu/Bitable. This is controlled by your destination configuration and authorization. These user-selected services may operate under their own terms and privacy notices; they are distinct from service providers that process data on our behalf. The Google-specific use and transfer restrictions in this policy continue to apply.

We do not sell Google user data or use it to serve ads, create advertising audiences, retarget people, or support personalized or interest-based advertising. We do not use Google user data to train or improve general-purpose artificial intelligence or machine-learning models. Any service provider processing this data for us must use it only for the permitted service purpose and follow the same data-use restrictions.

Transfers of Google user data are limited to providing or improving the visible features you choose with your consent, security needs, or legal requirements. In a merger, acquisition, or asset sale, we require your explicit prior consent before transferring Google user data. A general description of corporate transactions elsewhere in this policy does not override these restrictions.

People may view Google user data only with your specific affirmative agreement, for security or legal needs, or for permitted internal operations using aggregated data. These restrictions also apply to data derived from Google APIs, including aggregated or anonymized data.

Our use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. These Google-specific restrictions take precedence over any broader description of data use or sharing elsewhere in this policy.

OAuth credentials are encrypted before storage. Access to connected accounts and imported reports is controlled by workspace permissions and connection ownership. Reports are retained to provide the requested service and are subject to the retention and deletion provisions in this policy. Disconnecting an account does not automatically erase previously imported reports.

You can disconnect Google Ads in Growth BI to stop future synchronization for that connection. You can also revoke access in your Google Account's third-party connections settings. To request deletion of previously stored Google-related data, follow our data deletion instructions. Do not include passwords, authorization codes, or access tokens in a deletion request.