Thank you for your feedback. Even when you are pointing out perceived weaknesses in our ad delivery platform, we appreciate that you’re willing to make your voice heard and share your experience with TapContext. It provides an important opportunity for us to clear up misconceptions about our platform and how it works.
We would love for every developer who uses us to fall in love with our model and ad delivery mechanism. We think it’s a powerful new way to show ads. We also recognize that some people just aren’t going to like what we do or how we do it. So right up front, let’s agree that perhaps the TapContext network isn’t a good fit for you or your app. That’s ok.
There may be others, however, who would like to know more about how TapContext works and whether we are compliant with the developer policies… let me try and address all the concerns I’ve seen so far in the 2 forum threads referenced.
First, you are absolutely correct that the developer terms and content policies include any ads or links in your app. That’s why it’s extremely important to pick reputable ad networks who understand the Android ecosystem.
Of course, some of that responsibility also falls on the developer. For example, it’s up to you, as a developer, to rate your app appropriately given the ad networks you include. If you publish your app with an “everyone” rating and then include an ad network that shows location-based ads, you will be in violation of the Google Play developer policy (which requires at least a “Low Maturity” rating if location data is accessed). This is a rather common oversight by app developers, and one that is extremely difficult for ad networks to police. TapContext does not run adult or gambling ads and can safely be distributed in any app with a “Low Maturity” rating or higher.
To clarify regarding the post with screenshots, TapContext does not specifically identify your app (or any other app, for that matter) as a virus. A big part of what makes TapContext unique (and allows us to offer such generous payouts worldwide) is that our ads are contextual. In other words, when the user installs a new app, we partner with a service that asks if the user wants to scan their device for threats and malware. It should be noted that we specifically do not identify individual apps as threats during the subsequent scan.
Please also note that the malware scan, while quick and simple, is 100% real. It is not a fake scan designed to drive clicks and sales. We require all our contextual advertising partners to provide real and verifiable services to the user. In the case of the threat scanner you mentioned, the service provided is both truste and av-test certified. If the user has no threats, the contextual quick scan will tell them they have no threats. If they do have threats, malware, potentially unwanted apps, trojans, etc. then the quick scan will also tell them that.
The only thing “limited” about the scan is that it won’t scan unknown apps (apps not in the service provider’s threat database), and it doesn’t identify the apps that have been flagged. Both of those require the advanced version (which is how you get paid, we get paid, and the service provider gets paid).
Also, contextual ads triggered by real system conditions like a low battery shouldn’t be confused with simulating or impersonating system notifications or warnings. TapContext does not in any way attempt to impersonate system notifications or warnings. We do, however, display clearly identified ads, with proper attribution and opt-out information, for relevant apps and/or services for a low-battery condition. There is a rather large jump between impersonating a system warning and showing a clearly identified ad triggered by a system state. We neither impersonate the Android OS nor try to deceive the user in any way.
We also have other contextual points where we might display an ad. It could be as a result of an action taken by the user (for example, taking a picture might trigger an ad for a backup service or a photo editing app). Or it could be the result of system state (for example, a weak or lost signal might trigger an ad for a tower location app). These are all part of our patent-pending contextual triggering system, and is in no way trying to impersonate the system.
In fact, we feel like we’ve gone above and beyond to be compliant. Even in the screenshots you attached, it is exceedingly clear that it is an ad, which app triggered the ad, and how to opt out of receiving more ads. We do not use system icons or misleading labels in any way. We even changed the background color. We admit that what we’re doing is definitely new and different, and nobody else is currently doing what TapContext is doing. But that shouldn’t be confused with “not allowed.”
Lastly, there is no prohibition by Google against apps charging outside of Google Play, provided those apps aren’t distributed through Google Play. We agree that you cannot distribute your app through Google Play and charge for it using your own merchant processing.
There are other specific provisions, however, regarding advertising and distribution of non-market apps. Specifically, a Play app cannot “cause users to unknowingly download or install applications from sources outside of Google Play” or “use the Market to distribute or make available any Product whose primary purpose is to facilitate the distribution of software applications and games for use on Android devices outside of the Market.” TapContext does not cause your app to violate either of these policies. The user remains at choice and in control throughout the entire process (i.e. they cannot “unknowingly” download and install any advertised product or service). And you, as the developer, control whether the “primary purpose” of your app is to facilitate the distribution of non-market apps.
I hope this clarifies some of the questions surrounding our new ad platform. We are the first to admit that we haven’t figured everything out yet and still have work to do. We do, however, take our developers and their apps seriously. You are our lifeblood. Please continue to use our SDK and find areas where we can improve as a company and a service. If you have questions or concerns, we are here to help. Perhaps, if your app is appropriate, we can even use it as a backend contextual service provider.
We’re excited about this new way of advertising. It opens up many previously unavailable channels for monetizing and distributing your apps. But confusion and misinformation hurts everyone involved. Hopefully I have helped clear things up and addressed your concerns here. If not, I’m sure you’ll let me know 
