cookies: Required if the extension or app uses the okies API.contextMenus: Required if the extension or app uses the ntextMenus API.browsingData: Gives your extension access to the chrome.browsingData API.bookmarks: Gives your extension access to the chrome.bookmarks API.background: You typically use the background permission with a background page or event page.alarms: Required if the extension or app uses the chrome.alarms API.This serves as an alternative for many uses of, but displays no warning message during installation

Access to the tab lasts until the tab is navigated or closed. activeTab: The activeTab permission gives an extension temporary access to the currently active tab when the user invokes the extension - for example by clicking its browser action.For details on the syntax, see Match Patterns. Many capabilities, such as cross-origin XMLHttpRequests, programmatically injected content scripts, etc., require host permissions. Required if the extension or app wants to interact with the code running on pages. match pattern: Specifies a host permission.The following is an overview of the various permissions declarations possible in extensions in Opera, and what they mean. Permissions declarations allowed in Opera extensions

Do opera extensions compromise privacy