Developer token ownership

[Florin Frătică]

Hi,

We are developing and app which was initially an internal app used by a company and it is now a SaaS app.

Our developer token is still from the MCC of that company and each company that uses our app connects it's MCC to our application via OAuth2.

Is there any issue if the developer token we have doesn't belong to a MCC owned by us? The company that has is doesn't mind and is willing to keep it there, but I am more concerned whether there is any privacy issue.

If we decide / have to use another developer token we would have to create a new project, right (see the warning message from this page: https://developers.google.com/google-ads/api/docs/first-call/dev-token)?

[Google Ads API Forum Advisor Prod]

Hi Florin,

Thank you for reaching out. It won’t be an issue if the developer token belongs to a MCC account not owned by you. The developer token(a.k.a. API key) is only a token used to recognize the user, you could simply imagine it as a license/authorization to access/consume the API. The detailed request/response data are pretty safe in terms of privacy. But if you prefer to use another developer token in a future point of time, you would need to create a new Google API Console project as the old one was automatically paired to the previous developer token in your first API call and that relationship could not be removed.

Thanks and regards,
Xiaoming, Google Ads API Team
 

Xiaoming Google Ads API Team

ref:_00D1U1174p._5004Q2AIEVY:ref