Browser Extension

Permissions, privacy and troubleshooting

Every permission Fuego DevTools asks for and what your browser says about it, a summary of what it keeps on your computer, and what to do when the panel does not record, the popup sees nothing, or Open in Fuego does not reach Fuego.

Permissions

PermissionWhat it is forWhen
DevTools panelThe Fuego panel and its RecordingAt install
The Firebase console and the Google Cloud consoleThe console extras and the recorder behind their exact values, on console.firebase.google.com and console.cloud.google.com onlyAt install
Active tab and scriptingReading the page you are on, when you open the popupAt install
StorageThe settings and the cost settings, on this computerAt install
Context menusOpen “…” in Fuego on selected textAt install
Talking to apps on this computerReaching Fuego, after I have FuegoOptional, when you ask
Access to firebasestorage.googleapis.comShowing text files and saving files from the Firebase console’s Storage pageOptional, the first time you do either
Access to all sitesThe toolbar badge onlyOptional, when you turn the badge on; given back when you turn it off

Fuego DevTools does not ask to read your tabs or your history, never reads the clipboard, and writes to it only when you click a Copy button. It loads no code from anywhere: everything it runs ships with it, prices included.

What your browser says at install

  • Chrome and Edge (and Brave, Arc, Opera, Vivaldi): “Read and change all your data on all websites”. Chrome adds that line for every extension with a DevTools panel, because a panel can look at any page you open DevTools on. Apart from the two consoles, the badge and the right-click menu, Fuego DevTools reads a page only when you open its panel or its popup there.
  • Firefox: “Extend developer tools to access your data in open tabs” for the panel, “Access your data for sites in 2 domains” for the two consoles, and “Data collection: The developer says this extension doesn’t require data collection.”

Later, only when you ask

  • I have Fuego: Chrome and Edge ask to let it “Communicate with cooperating native applications”; Firefox to “Exchange messages with programs other than Firefox”. That is the channel to Fuego on this computer.
  • The badge: Chrome and Edge ask to “Read and change all your data on all websites”; Firefox to “Access your data for all websites”.
  • Allow, in a Storage file’s preview: Chrome and Edge ask to “Read and change your data on firebasestorage.googleapis.com”; Firefox to “Access your data for firebasestorage.googleapis.com”. Only text files and downloads need it.

The wording can differ slightly from one browser version to the next.

Privacy

Fuego DevTools sends nothing it reads to us or to anyone else: no account, and no analytics or telemetry of its own.

  • The Recording stays in the panel, in your browser, until you clear it, click Reload to record again or close DevTools. An export goes where you save it, and never holds tokens. The recorder that Reload to record adds stays in the page until it reloads or the tab loads another page; once DevTools is closed, it keeps only about the last two minutes of calls.
  • It talks only to Fuego on this computer, once you allow it: to show Fuego’s status, and to send the Fuego link of what you clicked.
  • It keeps on this computer only its settings (the switch of the window shown before the first Open in Fuego, the default cost settings and those of each Firebase project you set up, by project id, and the language of Copy as code), plus, while that window is open, what it shows, and, in a Firebase console or Google Cloud console tab, the last 2,000 Firestore documents the console received, until the tab closes or reloads. Whether the badge is on is not stored: it is the site access your browser granted.
  • Links to fuegoapp.dev, such as Get Fuego (free), say in their address that they come from Fuego DevTools, from which part of it, and which browser you use; the site’s own privacy policy applies there. Once after you first install it, it shows its own welcome page, part of the extension, which loads nothing from the internet; never after an update. When you remove the extension, the browser opens a page on fuegoapp.dev, without tags, with one optional question: we receive your answer only if you send it. Like every page of the site, it loads the services the site’s privacy policy describes: Google Analytics and the Reddit Pixel run only if you allow them in the cookie banner, and the Reddit Pixel never looks for email addresses on the page, not even in the comment box.

The Fuego DevTools privacy policy says it in full, with every permission.

Troubleshooting

The panel

  • No Fuego panel in DevTools. Close DevTools and open it again after installing. The panel comes after the browser’s own tabs: when they do not all fit, look behind the » button at the end of the DevTools tabs.
  • “Firebase on this page, not recording”. Click Reload to record: the recorder has to be in place before the page loads.
  • “No Firebase on this page yet”. The page has not talked to Firebase yet. Click Reload to record in the toolbar, then use the page: its calls show up as they happen.
  • “Recording” on a Google Cloud console page that has nothing to do with Firestore. Fuego DevTools keeps its recorder on every page of that console, for Firestore Studio. It keeps only Firestore calls, so the list stays empty there.
  • “Reloading…” turns back into “Reload to record”. The new page did not come: the browser may have asked whether to leave the page. Leave it, or click Reload to record again.
  • ”… messages were missed”. The page sent more than the panel could read: the totals of that Recording may be low.
  • The cost says “The database location is not visible in the traffic”. Choose it in Cost settings: see Recording and cost.

The popup

  • “The browser does not let extensions read this page”. Browsers keep extensions out of their own pages and of the extension stores.
  • No Signed-in user card. The app may keep its user in memory only; the popup reads the user the Firebase Auth SDK stores in the page.
  • The badge stays off. Your browser did not grant access to the sites you visit; turn the badge on again and allow it.

The consoles

  • The buttons are in a bar at the bottom of the page. The console changed its page: the bar keeps the buttons that come from the address. Copy JSON, the readable dates or the export may be missing until Fuego DevTools is updated.
  • Copy JSON copies “as displayed”. Fuego DevTools did not see the console load that document: reload the console page and open the document again.
  • In Firestore Studio, Copy JSON copies nothing and says Fuego DevTools has not seen the document’s exact values. Open the document again. If the tab was open before Fuego DevTools was there (just after an install or an update), reload the page first. Just after an edit in Studio, open the document again too: Copy JSON never copies the values from before the edit. Firestore Studio has no “as displayed” copy; Exact JSON in Fuego (in the toolbar, Open in Fuego) opens the document in Fuego either way.
  • In Firestore Studio, Copy JSON says the document does not exist. The path holds no document, only subcollections (or the document was deleted): there are no fields to copy.
  • In Firestore Studio, Copy JSON says the document has a field Fuego JSON cannot hold. Rather than copy part of the document, Fuego DevTools copies nothing: open it in Fuego instead, with Exact JSON in Fuego (in the toolbar, Open in Fuego).
  • A Storage file’s preview says Fuego DevTools did not see its details. The console listed the folder before Fuego DevTools was there (just after an install or an update): reload the console page. A file that has no access token is another matter: open it in Fuego.

Opening in Fuego

  • “Nothing happened? Update or get Fuego”. Fuego is not installed, is older than 2.3.0, or the browser’s question about opening Fuego was dismissed. Install or update Fuego, open it once, and try again.
  • “Fuego not found”. Open Fuego once: it tells the browsers where to find it every time it starts, including a browser installed since it last started. Check that Settings ▸ Language and formats ▸ Browser extension is on in Fuego. From a terminal, fuego extension status shows each browser’s entry and fuego extension install writes them now (see Command line).
  • Linux, a browser installed as a Snap or a Flatpak. Chrome, Chromium, Brave or Edge from a Snap or a Flatpak cannot reach apps outside their sandbox, so the extension says Fuego not found even while Fuego runs. Click Try again in that window to send the Fuego link through the browser, or check Don’t show this again so that Open in Fuego always sends Fuego links, which the browser asks about each time.
  • Opera and Vivaldi on Linux. There Fuego writes its entry for Chrome, Chromium, Brave, Edge and Firefox only, so Opera and Vivaldi say Fuego not found too, even while Fuego runs: Try again or Don’t show this again send Fuego links, as above. On macOS and Windows they get the entry too, though they are not tested.
  • Firefox: “Firefox waits a few seconds before it opens another Fuego link.” Firefox lets a page open a Fuego link only so often: try again in a moment.
  • “This page uses more than one Firebase project”. The panel cannot tell which project an operation went to, so it cannot open it: open it from the console instead.
  • “Your Fuego plan does not include this”. See the Free plan.

Something else? Write to us from the contact page.

Safari

Fuego DevTools for Safari will follow on the Mac App Store, with its own permissions: Safari asks for each site rather than at install.