Privacy Policy

Approved advertising changes and conversion uploads

The workbench supports advertising changes and offline click-conversion uploads only after a user previews and confirms an individual request. It stores business event references, stages, timestamps, country, value, optional attribution identifiers, click identifiers and execution records locally. Full click identifiers are not returned in the dashboard or ordinary audit events. The local data directory and backups must be protected by the operator.

When configured and explicitly requested through the AI report button, the Service sends aggregate numerical report metrics to OpenAI for advisory analysis. It does not send account names, search text, URLs, click identifiers, business references or notes in these requests. AI reports cannot execute advertising changes. Requested report summaries can also be sent to the configured enterprise WeChat group after confirmation.

If DeepSeek is selected instead, an explicit AI analysis request sends numerical advertising metrics, aggregate inquiry and date-coverage counts, the four keyword classification tags, country/device/hour categories, an anonymized historical customer-industry sample summary, and temporary anonymous object references. Module analysis uses full filtered numerical aggregates and a disclosed sample of important advertising objects. With the administrator's explicit consent and server configuration, module analysis also sends redacted advertising keyword text, visible search-term text and available creative headlines/descriptions for semantic and copy analysis. Account names and IDs, campaign names and IDs, customer contact information, click identifiers, business references, record notes, URLs, URL parameters, page contents and credentials are excluded. Utility modules use allowlisted aggregate workflow status counts, never raw audit or customer payloads. The Service maps anonymous references back to local objects after the response. Results may be reused in server memory for up to ten minutes for identical data, module, prompt and configuration. Keys remain on the server. AI analysis is manually triggered, does not search the web, and cannot submit advertising changes.

1. Who we are

The Service is an internal advertising analytics workbench operated by RIPPA to analyze Google Ads account data and submit user-confirmed advertising changes. It is not a public advertising, sales, or data brokerage service. For questions about this policy, contact contact@rippa.com.

2. Information we process

• Google authorization information: When you sign in with Google and grant authorization, we store an OAuth refresh token, OAuth client configuration, and Google Ads account identifiers. We do not receive or store your Google password.
• Google Ads data: We use the Google Ads API to read reporting and current configuration data for accounts you have authorized, such as account hierarchy, currency, time zone, campaigns, keywords, search terms, locations, impressions, clicks, cost, and conversions.
• Information you provide directly: Countries, dates, valid B2B lead counts, total lead counts, completion status, notes, exchange rates, budget targets, and review decisions.
• Operational and security data: Operational records, synchronization status, error information, and access logs used for operation, troubleshooting, and security. Logs do not contain OAuth authorization codes or complete secrets.

3. How we use information

We use this information only to: connect to and verify the Google Ads accounts you explicitly authorize; provide reports and analysis of advertising performance, cost, country feedback, and recommendations; save your settings and review decisions; maintain service reliability, access security, and troubleshooting; and comply with applicable legal or regulatory requirements.

We do not sell Google user data. We do not use it for remarketing, credit assessment, or purposes unrelated to providing this Service, and we do not permit third parties to use it for those purposes.

4. Google API Limited Use disclosure

Our use of information received from Google APIs complies with the Google API Services User Data Policy, including the Limited Use requirements. Google Ads data is used only to provide and improve user-visible features of the Service. We do not transfer this data to others except when necessary for security, legal compliance, abuse prevention, or with your explicit consent.

The Service uses the Google OAuth scope https://www.googleapis.com/auth/adwords. This scope is defined by Google and includes advertising management permissions. The Service implements reporting queries and separately confirmed endpoints for budgets, manual keyword bids, keywords, negative keywords, statuses, final URLs, and offline click-conversion uploads. Review decisions alone do not execute advertising changes.

5. Data sharing and processors

We do not sell or rent your personal information. Data may be processed only to the extent necessary to provide the Service by the following categories of recipients:

• Google, for OAuth authorization and Google Ads API access;
• server, network, and security infrastructure providers used to host and protect the Service;
• a WeCom bot configured by you, for account change notifications and user-confirmed report summaries;
• OpenAI, for aggregated numerical AI analysis when configured and explicitly requested;
• DeepSeek, for minimized-data advisory analysis described above when selected, configured and explicitly requested;
• regulators, courts, or other competent authorities when required by applicable law.

Processors are permitted to process data only as necessary for the purposes described in this policy.

6. Storage and security

Data is primarily stored in protected server directories used by the Service, including a SQLite database, access-restricted credential files, and rotating logs. Data is transmitted over HTTPS, and access is restricted through authentication, same-origin checks, and server file permissions.

The Service is hosted on a server in Germany, so data may be processed outside your country or region. We take reasonable measures to protect data, but no method of transmission or storage is completely secure.

7. Retention

Google Ads reports, manually entered feedback, and review decisions are retained for as long as necessary to provide the Service, generally until an administrator deletes them or you submit a deletion request. OAuth refresh tokens are retained until you revoke authorization, replace the authorization, or an administrator deletes them. Security logs are retained for a limited period under a rotating retention policy. Deleted information may remain in short-term backups or records that must be retained by law.

8. Your choices and rights

• You can revoke the Service’s access at any time through your Google Account permissions page.
• You can contact contact@rippa.com to request access to, correction of, or deletion of the Google Ads authorization data we hold about you.
• You can request that future Google Ads data synchronization stop. After Google authorization is revoked, the Service can no longer read the relevant accounts.

9. Cookies and local storage

The Service uses only essential cookies, such as the site session cookie and the OAuth state cookie. We do not use third-party advertising cookies, cross-site tracking cookies, or behavioral profiling. Disabling essential cookies may prevent sign-in or Google authorization.

10. Children and sensitive data

The Service is intended for business operators and is not directed to children. We do not knowingly collect children’s data. Do not submit sensitive personal information, payment card information, or health information that is unrelated to advertising analysis.

11. Changes to this policy

We may update this policy in response to changes in our features, applicable law, or Google API requirements. The revised version will be published on this page with an updated date. Continued use of the Service indicates that you understand the updated policy.

12. Contact us

For privacy questions, data access requests, or deletion requests, contact contact@rippa.com.