It's documented in the browsingData API that it can remove other extensions' data:
https://developer.chrome.com/extensions/browsingData

I just checked Click&Clean and it indeed appears to be removing extension data upon request.

I suggest to use chrome.storage.local if you want to persist data without loosing it to other extensions.

Mike, can you check whether this behavior is sane?

Extensions mindlessly deleting other extensions' data is not that nice.

"Mindlessly", sure. "Mindfully"? Idunno. I think it's reasonable to expose the browsing data remover's functionality, but I can see how it could be unexpected.

Deferring to Devlin; I personally think this is probably an argument for better documentation, not for duller tools.

Hi,

Thank you for taking look into this problem. 

I would like to emphasize that most of the Chrome Extension users are not familiar with many developer terms. 

Even if they put a warning that those options may delete other extension's data most of the users will proceed and than will complain on us that we provide bad services and they lost all their data that been collected for month.. 

In my personal opinion such option shouldn't be available at all in Chrome API or for very specific extensions.

<sarcasm>

P.S. Right now for developers like us is a good solution to implement such functionality into our own extensions and start killing all Cleaner extensions first, because otherwise they "kill us"

</sarcasm>

Team Nimbus, did you see my suggestion at the end of comment 1? If you use chrome.storage, then other extensions cannot delete it as easily as DOM storage and databases.

See https://developer.chrome.com/extensions/storage

yes, I will forward to my developers the solution but the problem is that our service is cross-platform and it may be difficult to redo whole thing..

Having the ability to remove data is a useful tool, and, when used correctly, is a good feature.  As with pretty much any extension API, if an extension chooses to use it poorly, it will have bad results.  And, as Rob has pointed out, there are less fragile ways of storing data.

We also already do call this out pretty explicitly in the documentation:
"Seriously: Be careful with protectedWeb and extension. These are destructive operations that your users will write angry email about if they're not well-informed about what to expect when your extension removes data on their behalf."

I'm going to close this, because it sounds like something where the clean up extension needs to manage user expectations better, not something where we should reduce the capabilities of the API.

chrome.storage.local - will not work because it doesn't have search and sorting like in websql

I agree that it is a good feature if you know hot to use it right. That's definitely for advanced users.

"format c:\"  - may be also good command, but do you think it good to provide such option to users who doesn't know what it does?

Here is another example:
Chrome has API to disable other extensions. Will it be fair if we put button "Fix the problem" and disable Click&Clean and same others? Because they do not warn users that FVD Speed Dial database will be erased.

The issue here is that some extensions provide this functionality to users who have no clue what will happen next. Our product gets broken and they don't know why it happens again and again. Click&Clean  - is not only one extension which does it. We are not only one company who encountered such problem.

>>We also already do call this out pretty explicitly in the documentation:
"Seriously: Be careful with protectedWeb and extension. These are destructive operations that your users will write angry email about if they're not well-informed about what to expect when your extension removes data on their behalf."

As I said, Click&Clean and others don't warn that other extensions will be broken. Even though when it happens user have no clue that Click&Clean did that. 

They complain on us, that we provide poor quality service and write all negative feedback because our extension was broken and all data was lost.

People collect their bookmarks for month, can you image how do they react when the lose it?