← CyberChef

CyberChef — Privacy Policy

Last updated: 22 September 2026

CyberChef is an unofficial Chrome extension that opens the CyberChef app beside the page you are reading. Since version 3.0 the extension does not carry a copy of CyberChef: its side panel loads the CyberChef app from https://cyberchef.tools in an iframe, and hands it whatever you selected, pasted or scanned. This policy describes exactly what the extension does with your data. It describes this build's behaviour and nothing else.

It is built on GCHQ's CyberChef (Crown copyright, Apache-2.0) but it is not affiliated with, endorsed by, or operated by GCHQ.

The short version

1. What the extension does with your text

Every way in works the same way, and there is only one:

  1. You perform a gesture — a right-click menu item, the toolbar icon, a keyboard shortcut, the chef keyword in the address bar, Scan this page, or a button in the DevTools tab.
  2. The text is written to chrome.storage.session under a single key. That area is in memory only: it is never written to disk, never synced, and is cleared when the browser closes. It holds one value at a time, and the panel removes it as it reads it.
  3. The side panel passes that value to the framed page as one browser message (window.postMessage), addressed to https://cyberchef.tools and to no other origin. The message carries the text, optionally the names of operations to run (such as from-base64), a short label such as Selection: example.com, optionally a word saying what to do with it (run, magic, scan), and — when the gesture was made on a tab — the address and title of that page, so the app can show where the input came from. The address is sent only when it is an ordinary http or https one. The address bar keyword and the DevTools tab have no page to name and send none.
  4. The page — the CyberChef app — sets the input, runs those operations if there are any, and shows the output.

The extension makes no network request with your text in it at any point, and none with the address or title of the page you were on. A postMessage is delivered by the browser between two documents that are already open; it does not leave your machine.

The framed page can ask the extension for two small things, and both are checked before anything happens. It can ask for a new browser tab at an address it gives, which is opened only if that address is an ordinary https one and at most once a second. And it can ask for a short badge — at most four letters or digits — on the extension's toolbar icon, which the extension clears when the panel closes and when the browser starts. Neither carries any of your text, and neither needed a new permission.

What the extension cannot see. The framed page is a different origin, so the extension cannot read what is in it — not the input once it has arrived, not the recipe you build, not the output. It can only post to it.

Where the text does go. Into that page, which is a web page loaded from cyberchef.tools. Loading it is an ordinary request to that site (and to any service that site chooses to use), made by your browser, the way opening any website is. What the site does with what you type into it is the site's to describe, and it does: cyberchef.tools/privacy.html. If you would rather nothing reached that site, the honest answer is not to use the panel.

2. The DevTools tab

The "CyberChef" tab inside Chrome DevTools lists the requests of the page you are inspecting, and shows their headers and bodies. It reads them from chrome.devtools.network, which exists only while a DevTools window you opened yourself is attached to that page, and only for that page.

Those bodies are read, previewed and searched in the DevTools panel's own process. Inspected requests, headers and bodies are not stored by analytics or sent to the analytics endpoint. Optional analytics counts only the fixed native control actions described in section 6. The two buttons that move anything are Send to panel and a card's own action: both stage the text exactly as section 1 describes, and it goes to the side panel and from there into the framed page.

3. What the extension can read, and when

The extension declares no host permissions, so a fresh install can read no page at all. Framing cyberchef.tools needs no permission: displaying a page in an iframe is not access to it.

Page text is read in exactly two circumstances, and both are a gesture you just performed:

What is read is document.body.innerText, or your selection when there is one, capped at 2,000,000 characters. No content script is declared, so nothing runs on any page unless you ask. Restricted pages (chrome://, the Chrome Web Store, the PDF viewer) cannot be read whatever is granted, and the panel says so rather than failing silently.

4. What is stored, and where

One handoff containing the text you choose to open is held in chrome.storage.session, in memory, until the panel reads and removes it. A first-run flag in chrome.storage.local prevents repeated welcome tabs. Nothing uses Chrome synced storage.

The extension analytics choice is stored locally for up to 365 days. Only after opt-in, a random installation identifier is created locally for up to 365 days. A session identifier is held in browser session storage for at most 30 minutes of inactivity or 24 hours, and browser shutdown clears it. Pending events are bounded in worker memory and are not saved to disk.

The hosted workbench has its own browser storage and privacy policy. Inside the extension, its analytics follow the extension’s shared choice and use separate, extension-scoped identifiers. Ordinary website tabs retain independent consent and storage.

5. Permissions, and why each one is there

Permission Why
contextMenus to add context-specific CyberChef right-click actions and handle clicks
storage the local handoff, first-run flag and optional analytics state described in section 4
activeTab one-shot access to the tab a gesture was performed on
scripting to run the small collector function that returns the selection or the page text, under activeTab
sidePanel to register the panel, open it from a gesture, and bind the toolbar icon to it
devtools_page a manifest key, not a permission: it adds the CyberChef tab inside DevTools and carries no install warning
<all_urls> (optional) not granted at install; only ever requested from the panel's Scan Scan page button, and revocable

Opening a new tab (chrome.tabs.create) and setting the toolbar badge (chrome.action.setBadgeText) need no permission at all, and none was added for them: the first opens a tab the way a link does and cannot read it, and the second draws on the extension's own icon.

There is no tabs, no webRequest, no declarativeNetRequest, no debugger, no cookies, no history, no clipboardRead, no identity, and no content script.

6. Optional first-party analytics

There is no account or sign-in. In the visible first-use prompt or Extension analytics settings, choosing Allow analytics lets us measure use of native controls: panel opens, readiness and retries; right-click actions; shortcuts; page scan requests; deliveries to the panel; and DevTools open, send, run and clear buttons. The same choice also enables content-free operation, feature, performance and coarse device statistics in the embedded workbench, as described in the website privacy policy. We use this to improve CyberChef’s controls and reliability. An action count does not prove that processing succeeded.

Native events contain only an allowlisted action name, extension version, random installation/session/event identifiers, event order and elapsed time, and fixed labels identifying native extension controls. Cloudflare supplies approximate country and server receipt time. No selected text, input, output, recipe, search text, page URL or title, filename, inspected network request, header, body, raw error or fingerprint is included.

Requests go over HTTPS to https://cyberchef.tools/api/analytics, without cookies or a referrer. The same first-party Cloudflare D1 database and private reporting dashboard serve website and extension analytics. The records use separate identifiers: one person using both surfaces may appear more than once. The collector does not store IP addresses or full user-agent strings in analytics records. Cloudflare necessarily processes network metadata when serving and protecting the endpoint.

Raw events are retained for 90 days, installation records for up to 365 days and daily aggregate totals for 730 days. Automated maintenance applies these limits. The internal-testing setting excludes that installation’s activity from production visitor totals.

Turn off analytics stops new collection in native controls and the embedded workbench. It aborts active requests, discards unsent events and removes native and open-workbench analytics identifiers. A closed workbench clears its scoped identifiers when next opened; a new consent period also discards old scoped identifiers. It does not delete records already received; those expire under the retention policy. Re-enabling creates a fresh installation identifier. Analytics failures never stop normal work. Browser privacy signals are respected where exposed by the runtime; blocked requests and worker shutdown can reduce coverage.

The Analytics button inside the workbench opens the extension’s same choice. Choosing Not now is remembered without repeated prompts. A legacy native-only opt-in requires a new choice before enabling both surfaces. Ordinary website tabs keep their own consent setting. The private offline extension has no analytics collector.

7. Other network requests

The side panel loads https://cyberchef.tools/?embed=1&analytics=extension. On first installation, the extension makes one short, credential-free HEAD request to the site to decide whether to open the hosted tour or bundled welcome page. The right-click menu is bundled locally and makes no configuration request. Fonts are also bundled. Optional analytics adds only the endpoint described in section 6.

8. The tour page, opened once when you install

When the extension is installed it opens one tab at https://cyberchef.tools/extension/welcome: a short tour that asks you to try a right-click operation, Magic, and Scan page on a sample note printed on the page itself. It is a page on the site rather than a page inside the extension, so it can be corrected without a store release.

9. The page Chrome opens when you remove it

Chrome lets an extension name one address to open when it is removed (chrome.runtime.setUninstallURL, which must be https, so it is a page on the site). Ours is https://cyberchef.tools/extension/uninstalled.

10. If you answer that question

Pressing Send posts one small request to https://cyberchef.tools/extension/feedback, on the same site as the page you are reading it on.

11. Third parties

Cloudflare hosts the site and processes and stores first-party analytics on our behalf. The extension bundles the fonts it uses rather than requesting them from a font CDN, because a font request is a request.

12. Changes to this policy

If what the extension does with data changes, this document changes with it and the "last updated" date at the top changes too. The current version is always published at cyberchef.tools/extension/privacy, which is the only copy the extension links to.

13. Contact

Questions, corrections, or something in here that does not match what you observe: [CONTACT].