Subprocessors & providers
Zbang Google Ads Audit subprocessors & platform providers
This page lists the main providers used to host, operate, and support the app. Some of them may act as subprocessors or independent service providers depending on the data flow and your relationship with the advertiser.
Zbang updates this page when the provider set materially changes for this app.
Railway
Role: Application hosting and runtime infrastructure
Data involved: User account data, encrypted Google connection metadata, workspace records, generated outputs, and operational logs handled by this deployment.
When used: Used to host and run the app.
Current deployment database (PostgreSQL)
Role: Structured application storage
Data involved: User records, Google Ads connection metadata, accessible account cache, job metadata, structured dashboard data, and related workspace records.
When used: Used whenever the app stores workspace data.
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 connects Google and runs an audit.
OpenAI
Role: Optional AI recommendation generation
Data involved: Selected Google Ads analysis inputs and generated recommendation prompts/responses related to an opted-in run.
When used: Used only when AI recommendations are enabled for the deployment and requested for a run.
Related documents