CampaignOps

Privacy Policy

Last updated: July 22, 2026

CampaignOps is operated by Aleksei Kunitsin, individual developer. This policy explains how the operator handles information used by the service.

1. Information We Collect

CampaignOps collects the following information when you use our service:

  • Google account information (name, email address) provided through Google OAuth sign-in
  • Google Ads account data, including campaign names, budgets, performance metrics, and configuration settings
  • Safe service diagnostics such as status codes and Google request IDs when supplied
  • For authorized test operations, normalized operation requests, lifecycle audit events, and verified resource observations
  • When live Keyword Research is permitted, bounded research inputs and normalized keyword ideas

2. How We Use Your Information

We use the collected information to:

  • Authenticate your identity and authorize access to the application
  • Display live Google Ads campaigns in read-only mode
  • Generate performance reports, analytics, and CSV exports
  • Validate, confirm, audit, and verify operations that are restricted to the registered Google Ads test client
  • Provide a separate public demo using local sample-data simulations

Production accounts are permanently read-only. Durable mutation and Keyword Research records are stored only for the protected workflows described above; OAuth refresh tokens are not stored in those records.

3. Data Security

We implement appropriate technical and organizational measures to protect your data. All communication between your browser and our servers is encrypted via TLS. Access tokens are stored securely and are never exposed to client-side code.

4. Third-Party Services

CampaignOps integrates with the following third-party services:

  • Google OAuth 2.0 — for user authentication
  • Google Ads API — for read-only production data, bounded test-account operations, and gated Keyword Research
  • Vercel — for hosting the web application and processing application requests
  • Neon — for durable database storage of the protected workflow, audit, health, idempotency, and Keyword Research records described above

Google services are subject to their respective privacy policies. Vercel and Neon process service data as infrastructure providers to the extent required to host and operate the workflows described in this policy.

5. Google API Services Usage Disclosure

CampaignOps's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

6. Data Retention

Google Ads reporting responses and public demo simulation events are not persisted as application records. Protected test-operation audit, idempotency, verified resource observations, health evidence, and enabled Keyword Research runs are retained as necessary to secure, operate, and review the service. You may contact us regarding retained data, subject to applicable security and legal retention obligations.

7. Changes to This Policy

We may update this Privacy Policy from time to time. Any changes will be posted on this page with an updated revision date.

8. Contact Us

If you have questions about this Privacy Policy, please contact us at ads@campaignopsapp.com.