Privacy Policy - AdsPilot

Last updated: 2026-03-20

AdsPilot ("AdsPilot", "we", "our", or "us") provides a web-based service that helps users create structured Google Search campaigns inside their own Google Ads accounts. This Privacy Policy explains how AdsPilot accesses, uses, stores, protects, and deletes information, including Google user data, when you use our website, application, and related services.

1. Who we are

AdsPilot is a campaign creation and workflow tool designed to help businesses prepare Google Search campaigns more efficiently. Users input campaign information, connect their Google Ads account via Google OAuth, select the Google Ads customer account they want to use, and instruct AdsPilot to create campaigns in a paused state for review before activation.

2. Google user data we access

When you connect your Google Ads account, AdsPilot requests access only to the Google data necessary to provide its core functionality.

• Google Ads account access through the Google Ads API scope required to list accessible Google Ads customer accounts and create campaign assets in the user’s own Google Ads account.
• Google Ads customer identifiers, including customer IDs selected by the user.
• Advertising account structures and campaign objects created or managed through the service, such as campaign budgets, campaigns, ad groups, keywords, negative keywords, responsive search ads, and campaign assets.
• OAuth tokens, specifically refresh tokens and temporary access tokens required to maintain the connection between AdsPilot and the user’s Google Ads account.

AdsPilot does not access your Google Account password. AdsPilot does not access Google Ads billing instruments, credit card numbers, invoices, or payment method details through the Google Ads API.

3. How we use Google user data

AdsPilot uses Google user data only to provide and improve the user-facing functionality of the service requested by the user. Specifically, AdsPilot uses Google user data to:

• Authenticate and maintain the connection between the user and the user’s Google Ads account.
• List Google Ads customer accounts available to the connected user.
• Allow the user to select the Google Ads customer account where the campaign will be created.
• Create Google Search campaigns, ad groups, keywords, negative keywords, responsive search ads, and related assets.
• Create campaigns in a paused state so the user can review them before enabling them.
• Activate a previously created campaign only when the user explicitly instructs AdsPilot to do so.
• Diagnose technical issues, prevent abuse, and maintain service security and reliability.

AdsPilot does not use Google user data for unrelated purposes. AdsPilot does not sell Google user data. AdsPilot does not use Google user data for advertising, profiling, data brokerage, or any purpose not directly related to the core functionality described in this Privacy Policy.

4. Other information we collect

In addition to Google user data, AdsPilot may collect and store information submitted by the user when preparing a campaign, including:

• Business website URL and landing page URL
• Business name, product or service description, offer, audience, and differentiators
• Geographic targeting selections
• Daily budget and campaign objective
• Generated draft campaign structure and implementation status
• Internal ownership and access-control identifiers necessary to protect draft access
• Operational logs, rate-limiting data, and security event data needed to protect the service

5. Legal basis and user control

AdsPilot accesses Google user data only after the user explicitly authorizes the connection through Google OAuth. The user remains in control of whether to connect a Google account, which Google Ads account to use, and whether to proceed with campaign creation or activation.

6. How we store and protect data

We use reasonable administrative, technical, and organizational safeguards to protect data against unauthorized access, disclosure, alteration, or destruction. These measures include, where applicable:

• Encryption of stored OAuth refresh tokens at rest
• Use of secure HTTPS connections for data in transit
• Server-side handling of Google Ads API requests
• Access controls intended to restrict draft and campaign access to the relevant user
• State validation, nonce checks, and rate limiting for sensitive OAuth and campaign actions
• Operational controls intended to reduce duplicate or abusive API activity

7. Where data is stored

Data may be stored on infrastructure and service providers used to operate AdsPilot, such as hosting, database, and payment providers. Depending on deployment configuration, draft and operational data may be stored in managed database infrastructure or secure server environments controlled by AdsPilot and its service providers.

8. Data sharing

AdsPilot does not sell or rent Google user data or customer campaign data. We share data only in the limited circumstances below:

• With service providers that help us operate the service, such as hosting, database, infrastructure, analytics, or payment providers, subject to contractual or operational controls
• When required by applicable law, regulation, legal process, or enforceable governmental request
• To protect the security, integrity, rights, or safety of AdsPilot, our users, or others
• As part of a merger, acquisition, financing, or sale of assets, subject to appropriate safeguards and notice where required

Any sharing of Google user data is limited to what is necessary to operate the service and comply with law.

9. Data retention

AdsPilot retains data only for as long as reasonably necessary to provide the service, maintain security, comply with legal obligations, resolve disputes, and enforce agreements.

• OAuth credentials may be retained while the user keeps the Google Ads connection active and while needed to provide the requested functionality.
• Campaign drafts and related inputs may be retained while the user continues using the service or until deletion is requested, subject to backup and legal retention requirements.
• Security and operational logs may be retained for a limited period as reasonably necessary to detect abuse, troubleshoot problems, and protect the service.

10. Revoking Google access

Users can revoke AdsPilot’s access to their Google account at any time through their Google Account security settings. Once access is revoked, AdsPilot will no longer be able to access the connected Google Ads account through Google OAuth unless the user reconnects the account.

11. Deletion requests

Users may request deletion of stored data associated with AdsPilot by contacting us at the email address listed below. Upon a verified request, we will take reasonable steps to delete or de-identify applicable stored data, subject to legal, security, fraud-prevention, backup, and operational retention requirements.

12. Children

AdsPilot is intended for business and professional use and is not directed to children.

13. International processing

Depending on where our infrastructure or service providers operate, information may be processed in countries other than the user’s country of residence. Where required, we take reasonable steps to protect personal data in accordance with applicable law.

14. Changes to this Privacy Policy

We may update this Privacy Policy from time to time. If we make material changes, we will update the date above and publish the revised version on this page.

15. Contact

For privacy, data deletion, or support requests, contact:

carlosleme88@gmail.com