First Look subprocessors and platform providers

This page lists the main providers used to host, operate, and support First Look, Zbang's free Google Ads audit. Some of them may act as subprocessors or independent service providers depending on the data flow and your relationship with the advertiser.

First Look is operated by Zbang Ltd (registered in England and Wales as ZBANG LTD, company number 11824205; registered office 71–75 Shelton Street, London, WC2H 9JQ, United Kingdom), referred to as "Zbang" on this page.

Zbang updates this page when the provider set materially changes for this app.

Providers

1. Hosting provider (operator configuration required)

   Role: Application hosting and runtime infrastructure

   Data involved: User account data, encrypted advertising-platform connection metadata, workspace records, generated outputs, and operational logs handled by this deployment. Published processing region: operator configuration required.

   When used: Used to host and run the app.

2. Database provider (operator configuration required)

   Role: Structured application storage

   Data involved: User records, advertising-platform connection metadata, accessible account caches, job metadata, schedules, alerts, targets, reporting configuration, and structured dashboard data. Backend: PostgreSQL. Published storage region: operator configuration required.

   When used: Used whenever the app stores workspace data.

3. Backup provider (operator configuration required)

   Role: Database backup and recovery infrastructure

   Data involved: Encrypted or provider-protected backups of durable application records, according to the deployment's backup contract. Published backup region: operator configuration required.

   When used: Used when backups are enabled for the deployment database.

4. Google

   Role: Identity provider and Google Ads API platform

   Data involved: Google sign-in data, Google Ads account metadata, and Google Ads reporting/configuration data retrieved for the user-selected audit.

   When used: Used when a user signs in with Google and, separately, when they connect Google Ads or run a Google Ads audit.

5. Microsoft

   Role: Microsoft identity and Microsoft Advertising API platform

   Data involved: Microsoft identity, Microsoft Advertising account metadata, and reporting/configuration evidence retrieved for user-selected read-only audits.

   When used: Used only when a user enables and connects Microsoft Advertising.

6. Cloudflare Turnstile

   Role: Adaptive login abuse protection

   Data involved: Browser, device, network, site-origin, and challenge-result signals used to distinguish automated password attempts from legitimate recovery attempts.

   When used: Used only after the account-wide password-attempt threshold is reached.

7. Google Analytics 4 and Meta Pixel

   Role: Optional public-page analytics and marketing measurement

   Data involved: Consent-gated browser, page, device, and coarse interaction signals. Zbang enables GA IP anonymisation and disables Google ad-personalisation signals.

   When used: Loaded only after the visitor grants the corresponding analytics or marketing consent.

8. OpenAI

   Role: Optional AI recommendation and ad-copy generation

   Data involved: For automatic Google Ads account-identity suggestions: account name, top landing domains, and up to 200 sampled search terms. For AI-enabled runs: selected advertising analysis inputs and recommendation prompts/responses. For a separate generate-copy action: selected campaign and ad-group context, keywords, landing-page URL or angle, and chosen copy references.

   When used: Used when AI is enabled for the deployment: automatically when Google Ads account setup is opened, by default for manual Google Ads audit recommendations, when AI is otherwise enabled for a job, or when a user explicitly generates ad copy after an audit.

9. Resend

   Role: Optional scheduled email delivery

   Data involved: Recipient email address, report subject, and the explicitly selected disclosure-safe report payload.

   When used: Used only when email delivery is configured and a user binds an enabled destination to a schedule.

10. Slack or Microsoft Teams

    Role: Optional user-configured webhook destination

    Data involved: The destination webhook receives the explicitly selected disclosure-safe report payload; Zbang stores the endpoint encrypted.

    When used: Used only when the user creates, tests, and enables that webhook destination.

11. Pushover

    Role: Optional operator audit-status notifications

    Data involved: A safe audit completion or failure message, an account-level label, and the configured operator recipient key; row-level customer evidence is not included.

    When used: Used only when the deployment operator configures Pushover credentials.

12. Advertiser landing-page hosts

    Role: Optional read-only landing-page availability checks

    Data involved: A bounded HTTP request to a public landing-page URL already present in the selected advertising account. Response bodies are not retained.

    When used: Used only when advanced landing-page diagnostics are enabled for an audit.