Or don't include sensitive data in your test set or build system. If you include something in a release that you should not have included, then you are respons

Or don't include sensitive data in your test set or build system. If you include something in a release that you should not have included, then you are responsible full stop, and a revocation system is not a solution. This sort of functionality should not be used to fix developer mistakes; you can't do this sort of thing with desktop applications either, and once again, for good reason. Even if Google initiates a mass revocation, that doesn't mean the application is no longer in the wild. Users who want to exploit your mistake could just as easily do one ogf the following: - Disconnect their phone from a data connection or wifi signal - Dump their current ROM/data to a backup image using a 3rd party bootloader - Extract the .apk from the phone using root access, using an app like Titanium Backup - Install the .apk from a source other than the Market, so that the revocation system will ignore it Google's mass-revocation system only "works" because it is designed to remove malicious applications from the phones of unsuspecting users. If you make sensitive data public, it becomes public data, period; there's no going back.