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 -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog: https://googleadsdeveloper.blogspot.com/ =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads API Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/y7HzH000000000000000000000000000000000000000000000QMKRJE003pUk5SJ2QY-xUJ_lRtedQg%40sfdc.net.
