I have no prior knowledge of Droidscript or even android development. I did, however, manage to find this page https://symdstools.github.io/Docs/docs/app/Create

I have no prior knowledge of Droidscript or even android development. I did, however, manage to find this page https://symdstools.github.io/Docs/docs/app/CreateAdView.htm https://symdstools.github.io/Docs/docs/app/CreateAdView.htm This presents a component which Droidscript developers can use to display AdMob ads in their apps. AdMob appears to be a Google property. Some interesting quotes: > The AdView shows advertisement banners from the popular AdMob platform. > Ads are not touchable when running in the DroidScript IDE. So there's a confirmed experience where actual ads are displayed in a non-standard way? Any guesses if this violates Google's ad fraud policy? > Warning: Don't repeatedly click on your own ads unless you are using a valid testId, or Google may suspend your Admob account! So it's the responsibility of individual users to correctly configure their ads to avoid committing click fraud (accidental or otherwise). I can see how Google might come to the conclusion that Droidscript has built a platform for committing click fraud, whether that's their intention or not. This seems incongruent with the wording in the original post: > they ask you for a "complete analysis of your traffic or other reasons that may have led to invalid activity in your appeal". Well, we had no idea what could have caused this and couldn't think of anything we could do Really? No idea? Edit to add: I get that there's a larger debate here around the general fight over device ownership and access to general purpose computing. I'm side-stepping that because I don't have much to add. What I do believe is that this particular piece is hardly concrete enough to bolster the case against Google.