Greetings, program!
If you have landed here it’s because you’ve clicked a “Privacy Policy” link on a product description page for a web browser extension. As of yet, it is still unclear why I have to have such a policy.
I mean, I’m fully supportive of data transparency and want people to know what their apps are doing, but the extension I’ve offered for publication does have anything to do with personal information, also known as PII. Because of this, I’m not entirely sure what this Privacy Policy would say, so I’m trying something different.
Here is the source code for the “Decode Current URL” extension:
function createTab(url) {
chrome.tabs.create({url: url})
}
function updateTab(url) {
chrome.tabs.update({url: url})
}
function decodeUrl() {
chrome.tabs.query({active: true, lastFocusedWindow: true}, tabs => {
let url = tabs[0].url;
happyUrl = unescape(url);
updateTab(happyUrl);
});
}
chrome.runtime.onInstalled.addListener(function() {
chrome.contextMenus.create({"id": "0", "title": "Decode Current URL", "contexts":["all"]});
});
chrome.contextMenus.onClicked.addListener(function() {
decodeUrl();
})
As you can see, there’s no PII being read, reviewed, analyzed, copied, shared, collected, or stored. That’s as best a “Privacy Policy” that I think anyone can offer. If you don’t read JavaScript or if you are worried about what the extension is doing, please do not put yourself at risk: do not use this extension if it causes you concern. It doesn’t do much of anything anyway and while I hope it can help other people, it was originally created for a very specific scenario but since the easiest way to keep extensions in sync is to publish it, I thought I’d share it publicly.
Thanks!
End of line.