With Google's new 'DOXing' policy for Google Play Developers (publishing the full home address of individual/hobby developers if they choose to monetize their apps following their new ID verification requirements), I have decided to remove all paid for options from one of my apps and move it to a new account which will have no monetized apps at all - thereby preserving my privacy (to a degree).

I have removed com.android.billingclient:billing:6.2.0 from my build.gradle and have modified my code so that any calls to functions in this library are no longer used and the app now compiles and runs.

In setting up the new developer account I selected that the account would not be used for monetized apps, but I am concerned that if I transfer an app to that new account and that app has some remnants of in-app billing code (or AdMob code etc) then the transfer process may automatically enable monetization on the new account resulting in my full home address being published.

Is there a way to check that my app DOES NOT contain any monetization code before I request the transfer?

Is there a list of all libraries that may trigger the 'monetized account' switch in Google Play?

The app I am migrating at the moment only contained in-app purchases, but that leaves me with another consideration. I do not want the in-app purchase products to transfer over to the new account as that would surely trigger the monetized account switch. Is it enough to deactivate the in-app products before transfer, or could there existence trigger the monetization switch?

I've searched around for info about this and haven't found anything that answers these specific questions.

I contacted Google support with other questions about migrating and haven't received any reply whatsoever... and reading various forum and blog posts it seems I am not alone in this, and when Google have replied to people their answers have been less than useful.

My current full list of libraries used is as follows. Is there anything in here that could flag as monetization, or do I have to dig deeper into my code to ensure it is safe to transfer without triggering the monetization flag?

implementation 'com.android.support:multidex:1.0.3'
implementation 'androidx.legacy:legacy-support-v4:1.0.0'
implementation 'androidx.appcompat:appcompat:1.6.1'
implementation 'com.google.android.material:material:1.11.0'
implementation 'com.google.code.gson:gson:2.10.1'
implementation 'androidx.constraintlayout:constraintlayout:2.1.4'
// billing for in-app purchases
//    implementation 'com.android.billingclient:billing:6.2.0' // Removed as Monetization removed
implementation 'com.google.guava:guava:27.0.1-jre'

implementation 'com.google.android.play:asset-delivery:2.3.0'
implementation 'com.google.android.play:feature-delivery:2.1.0'
implementation 'com.google.android.play:app-update:2.1.0'

// For in-app review flow
implementation 'com.google.android.play:review:2.0.2'

// Import the Firebase BoM
implementation platform('com.google.firebase:firebase-bom:32.8.0')
implementation 'com.google.firebase:firebase-messaging'

I'm really concerned about this, so I really want to make sure my app is 'clean' with regards to monetization before I initiate the transfer to the new account.

(I also have another monetized app that many years ago included AdMob ads. I removed them years ago, but I am also concerned that there may be remnants of code in that app that could trigger the monetization flag).