Baah, why was i so transparent. I did point out that it was OS and that we'd be self-hosting it. In hindsight, might've been better not to even mention Airbyte. .

"Airbyte should have its own API token and all you have to do is sign in with your AdWords account."

@Jared Rhizor (Airbyte) Their response doesn't make me optimistic. How can Airbyte have its own token and not have it leaked if it's not SaaS ?

Yeah it’s impossible to do what they’re saying in a self-hosted environment.

I wonder if you can just instruct users to request token by saying "it's X app, which is whitelisted".

the Google response seems to fundamentally misunderstand Airbyte, and I really think a lot is just getting lost in translation. I honestly think if I can get someone on the phone for 15 minutes they can see this does not violate the policy (but they refused). context: I’ve been going back and forth with them for 1+ month about getting us whitelisted

omg this is brutal!

FWIW they’ve accepted all application from our users when they don’t mention Airbyte 🤷🏼

Google Ads token request has always been a mess to me. Thanks for looking into it. I added a PR with a note about this in the Google Adwords documentation.