Legal
Fuego DevTools Privacy Policy
Effective November 20, 2026
Fuego DevTools is a browser extension for Chrome, Edge and Firefox. It shows the Firestore, Auth, Realtime Database and Storage calls a web app makes, estimates what they cost, and opens them in Fuego. This policy covers the extension. The Fuego desktop app and this website are covered by Fuego’s Privacy Policy. A Safari version will come later, on the Mac App Store: section 10 describes what it does differently.
1. In short
- Fuego DevTools collects no data of its own. It has no analytics, no crash reports and no account, and nothing it reads is sent to us or to anyone else.
- What it reads stays in your browser. A Recording stays in the panel’s memory until you clear it, click Reload to record again or close DevTools. It is saved to a file only if you export it.
- It talks only to the Fuego app on this computer, and only after you allow it. That is why its Chrome Web Store and Edge Add-ons listings mention “website content” (section 6).
- It reads a Storage file only when you ask. On the Firebase console’s Storage page, Preview and Download read the file from Firebase Storage with the link the console itself uses; text files and downloads need your permission first. Nothing is kept.
- It opens fuegoapp.dev only when you click a link to it, and when you remove it. After you first install it, it shows its own welcome page, which is part of the extension and loads nothing from the internet. When you remove it, your browser opens
fuegoapp.dev/devtools/uninstall/, a page of this website like any other, with nothing in its address that says which browser it came from; the website’s own Privacy Policy applies there. - The question shown when you remove the extension is optional. We receive your answer only if you submit it.
- On Safari (coming later), the same extension comes in a small Mac app, which collects nothing either: it reaches Fuego through that app, without your browser’s question, and the extension may read a site only once you allow it there. Section 10 has the details.
2. Who we are, and how to reach us
Fuego and Fuego DevTools are made by MiServe, based in Catania, Italy (VAT ID IT03081990834). For any question or request about this policy, use the contact form or write to privacy@fuegoapp.dev.
3. What the extension reads, and where it stays
Everything in this section happens in your browser, on your computer. None of it is sent to us.
The DevTools panel
- The extension adds a panel named Fuego to your browser’s DevTools. While the panel is open, it checks whether the page has loaded anything from Firebase. To record, you click Reload to record: the page reloads with a small recorder that sees its calls to Firestore, Firebase Auth, the Realtime Database and Cloud Storage for Firebase. The panel shows those calls, the documents and values they carry, and an estimate of their cost. On the Firebase console and the Google Cloud console, where the recorder is always present (see below), the panel can show the console’s calls without a reload. On the Google Cloud console it shows only Firestore calls, and since the recorder is in every page of that console, the panel may read Recording on a page that makes none.
- The recorder never keeps request headers, what a page sends to Firebase Auth and what comes back (only that a call was made, and how it went), or the Realtime Database’s sign-in messages. From the address of a call it keeps only the server it went to (which tells production from the emulators), the path and the few parameters that say what the call is about (the database, a Storage file or folder, the kind of download or upload), never the rest, such as API keys or download tokens. Access tokens are recognized so they can be left out: they are never stored.
- The Recording is kept in memory only, in the panel, and nothing of it is written to disk unless you export it. Clear empties it, Reload to record replaces it with a new one, and closing DevTools ends it. A page that changes its address without loading a new page stays in the same Recording. When the page reloads in any other way, or the tab loads another page, the panel stops recording but keeps what it recorded, to read or export, until you clear it, record again or close DevTools; on the Firebase console and the Google Cloud console, a new Recording starts by itself and replaces it.
- When you select a Realtime Database call in the panel, the panel also looks at the inspected page’s Firebase setup, the way the toolbar button does (see below): the database addresses in the app’s configuration tell which project the call’s database belongs to, so that Open in Fuego can name it. It reads it once, and again each time the tab loads another page, and only what the page already holds: it makes no requests, and the answer it leaves in the page while it reads is removed as soon as the panel has it, or stops waiting for it. A Firestore, Storage or Auth call never makes it look, and on Safari no call does (section 10).
- The recorder that Reload to record adds stays in the page until the page reloads or the tab loads another page, even after you close DevTools, and goes on seeing the page’s calls. While no DevTools panel reads it, it keeps only the calls of about the last two minutes, in the page’s memory: older ones are dropped as new ones arrive, and never more than about 32 MB of them are kept. Like anything in the page, they are within reach of the page’s own scripts. The extension does not read them again: a DevTools panel opened later discards them and offers Reload to record.
Export and copying
- Export saves the Recording as a JSON file, where you choose. The file holds the page’s address without what follows its path, the Firebase project id (never the API key), your cost settings, the extension’s version, your browser’s name, and the calls with their documents. Tokens and who signed in are never exported. Without document contents leaves out every field value; paths, queries with their filter values, counts and sizes stay in the file.
- The copy buttons (Copy as code, Copy path, Copy JSON, Copy config, Copy ID token and the others) write to your clipboard when you click them. The extension never reads your clipboard.
The toolbar button
- When you click the extension’s toolbar button, it looks at the page in the current tab for its Firebase setup: the project id, the app’s configuration, and which Firebase products and library version it uses. It reads only what the page already holds: it makes no requests, writes nothing, and never tests the project’s security rules.
- The Signed-in user card, and the panel’s Auth tab, show the Firebase user the page keeps in its own storage. They read its uid, email, name, phone number, whether the email is verified, sign-in provider, tenant, custom claims, the project it belongs to, and when its token was issued and expires, and they name the user by email, or else by name or phone number. The refresh token never leaves the page. The ID token is decoded in the page, and the token itself is handed to the extension only when you click Show token or Copy ID token.
- The utilities (Firestore REST JSON ↔ Fuego JSON, the timestamp converter, Push ID → creation date, and Decode an ID token) work on what you paste into them, and keep nothing.
The toolbar badge (optional)
- The badge stays off until you turn on Show a badge when a page uses Firebase. The extension then asks your browser for access to the sites you visit, which your browser may ask you to confirm. With that access, a small script looks at each page you open for signs of Firebase: requests to Firebase, Firebase scripts, and the names of the databases the Firebase libraries create in the browser. It never opens those databases, writes anything or makes requests. It tells the extension only that the page uses Firebase, so the extension can mark its toolbar button for that tab.
- Turning the badge off removes both the access and the script.
The right-click menu
- When you choose Open “…” in Fuego on selected text, your browser hands the extension the text you selected, so it can turn it into a Fuego link. If the text is not something Fuego can open, a small window says so and shows the text until you close it.
- On Firefox, the browser also hands the extension your selection each time you right-click selected text on a page the extension has access to (the Firebase console, a tab where you clicked its toolbar button, and every site while the badge is on), so the item shows only for something Fuego can open. The extension checks the text and keeps nothing of it.
The Firebase console and Firestore Studio
- On
console.firebase.google.comandconsole.cloud.google.com, the extension adds a few buttons next to the console’s own (Copy path, Fuego link, Open in Fuego). They are built from the page’s address. - On the Firebase console, the recorder described above is always present, without a click: it records the console’s own Firebase calls in that tab (Firestore, and the Realtime Database, Storage and Auth calls the console makes), with the same limits, so that Copy JSON and Export… can use exact values. The tab keeps the last 2,000 Firestore documents it received, in memory, until it closes or reloads. While no DevTools panel reads them, calls older than about a minute are dropped as new ones arrive, and never more than about 32 MB of them are kept.
- On the Google Cloud console (
console.cloud.google.com), where Firestore Studio is, the recorder is always present too, without a click: in every page of the console, and in the frames the console loads fromconsole.cloud.google.cominside its pages. Firestore Studio loads its documents in one of those frames, which hands its calls to the page’s recorder (a frame that cannot do so keeps them itself). There the recorder looks at the address of each of the console’s calls and keeps only the Firestore ones, never the rest of the console’s traffic, with the same limits, so that Copy JSON and the readable dates in Firestore Studio can use exact values. The tab keeps the last 2,000 Firestore documents it received, in memory, until it closes or reloads. - To show readable dates next to timestamps, on both consoles, it reads the values on screen. On the Firebase console, to copy a document the recorder has not seen (Copy JSON (as displayed)) and to export the results the console shows, it also reads the documents and results on screen. Firestore Studio has no such copy: there Copy JSON copies only the exact values the recorder received, and nothing when it has not seen the document. Export… saves the query’s results as a CSV or JSON file, where you choose; to reach every row you asked for, it turns the console’s pages with the console’s own buttons.
- On the Firebase console’s Storage page, it adds Preview, Download and Open in Fuego to each file. The recorder sees the console list each folder, and the tab keeps the details of the last 5,000 files listed (name, type, size, date, and the access token the console puts in its own download link), in memory, until it closes or reloads; they never go into a Recording. Preview shows an image, a video, a sound or a PDF from that link, as the console’s own side panel does. To show a text file or to save a file, the extension reads it from
firebasestorage.googleapis.com, only after you allow that (section 6), then shows it or saves it where you choose, and keeps nothing of it. A file without an access token is not previewed: the extension never creates one, since that would change the file. - On the Firebase console’s Authentication page, it adds Open in Fuego, Fuego link and Copy JSON to each user. The recorder sees the console list the users, and the tab keeps the details of the last 5,000 users listed (as the console receives them: uid, email, name, phone number, sign-in providers, custom claims, dates and status), in memory, until it closes or reloads; they never go into a Recording. The console is also sent each user’s password hash and salt: the extension drops them before it keeps anything, so they are never kept or copied. Copy JSON writes one user’s details to your clipboard when you click it.
- On the Firebase console’s Realtime Database page, it adds Copy path, Copy JSON and the REST URL of a node. The tab keeps the data the console received for the nodes it shows, in memory, until it closes or reloads, so that Copy JSON can copy a node’s data when you click it.
4. What goes to the Fuego app, and when
Fuego DevTools works on its own. To open things in Fuego, it talks to the Fuego desktop app through your browser’s native messaging: a channel between the browser and apps installed on the same computer. Nothing on this channel goes over the internet.
- The channel opens only with your permission. The first time you click Open in Fuego, a small window explains it. After you choose I have Fuego, your browser asks you to let Fuego DevTools talk to apps on this computer.
- Is Fuego there? Once you have allowed it, the extension asks Fuego whether it is installed and running when you open the toolbar popup and before it shows an Open in Fuego button. These questions carry nothing about the page you are on. Fuego answers with its version and what it can open and, while it runs, the project open in it and the Firebase project ids saved in it, so the button can say Open in Fuego or Add to Fuego. A Fuego with Realtime Database support also gives the names of the Realtime Databases it knows for those saved projects, including the ones it remembers, on this computer, from its last listing of each project’s databases, so that the Realtime Database a page or a recorded call uses can be matched to its project. Like the project ids, these names go only to Fuego DevTools, and the extension keeps them only in memory.
- What you click goes to Fuego, and nothing else. A Fuego link (
fuego://…) is sent only when you click Open in Fuego or Add to Fuego, or choose Open “…” in Fuego on selected text. It names what you clicked: a project and database, a document or collection path, a query, a user, a Storage file or a Realtime Database location. Launch Fuego only brings Fuego to the front. Fuego opens what you clicked on this computer. - When the channel cannot take the link. If you decline your browser’s request after I have Fuego, or once you have turned off the window that explains it, Open in Fuego hands the link to your browser, which opens Fuego the way it opens any
fuego://link, usually after asking you. On Chrome and Edge, the link may also go to your browser when you have allowed the channel but Fuego cannot be reached through it, for example when it is not installed. - What Fuego keeps. Fuego notes, in its settings folder on this computer, when the extension last talked to it and from which kind of browser (Chromium-based or Firefox), so that its Home stops suggesting the extension. The rest of what the Fuego app does is covered by its own Privacy Policy.
5. What the extension stores on your computer
In the browser’s storage for extensions, which only Fuego DevTools can read:
- Cost settings: the database location and edition you choose, for each Firebase project id (
costSettings:<project id>), and the defaults from the extension’s settings page (costDefaults). - The window that explains Open in Fuego: whether it may open (
handoffCard). - While that window is open: the Fuego link and the selected text it shows (
handoffCardWindow). They are removed when the window closes, and the browser clears them when it quits. - Copy as code: the code language you picked last (
fuego.codeLanguage, in the panel’s own storage).
Whether the badge is on is not stored by the extension: it is the site access your browser granted. The extension stores no browsing history, no page contents and no Recordings.
6. Permissions, and why
What each permission is for, and what your browser may show for it.
- DevTools panel (
devtools_page, and on Firefoxdevtools): adds the Fuego panel. Because a DevTools panel can work on any page you inspect, Chrome and Edge show “Read and change all your data on all websites” when you install the extension, and Firefox shows “Extend developer tools to access your data in open tabs”. Apart from the two consoles, the badge and the right-click menu, the extension reads a page only when you open the panel or click the toolbar button on it. - The Firebase console and the Google Cloud console (
console.firebase.google.com,console.cloud.google.com): the buttons, the recorder and the export described in section 3. Firefox shows “Access your data for sites in 2 domains”. activeTab: lets the toolbar button read the current page when you click it. Browsers show nothing for it at install.scripting: reads the Firebase setup and the signed-in user in the page you clicked on, runs the badge’s script while the badge is on, and, on Firefox without the channel described in section 4, opens a Fuego link from the current tab.storage: keeps the settings listed in section 5.contextMenus: adds Open “…” in Fuego to the menu for selected text (see section 3).nativeMessaging(optional): the channel to the Fuego app described in section 4, requested after you choose I have Fuego. Chrome and Edge show “Communicate with cooperating native applications”, and Firefox shows “Exchange messages with programs other than Firefox”.- Access to
firebasestorage.googleapis.com(optional,https://firebasestorage.googleapis.com/*): reads a Storage file when you preview a text file or download a file on the Firebase console’s Storage page (section 3). It is requested the first time you do either, from the preview, and your browser may show “Read and change your data on firebasestorage.googleapis.com”. The badge’s access to all websites covers it too. - Access to all websites (optional,
http://*/*andhttps://*/*): only for the badge. It is requested when you turn the badge on, and your browser may show “Read and change all your data on all websites” (Firefox: “Access your data for all websites”). It is removed when you turn the badge off.
Fuego DevTools does not ask for your tabs or browsing history, your cookies or downloads, the browser’s network-request or debugger access, or permission to read your clipboard.
On the Chrome Web Store and Edge Add-ons, its listing declares one kind of data, “website content”: the Fuego links of section 4, which name what you clicked on a page and go only to the Fuego app on this computer, when you click. They never reach us. On Firefox it declares that it collects no data, and Firefox says so when you install it: “The developer says this extension doesn’t require data collection.”
7. No collection of its own, no sharing, no ads
- Fuego DevTools makes no network requests of its own: no analytics, no crash reports and no code loaded from elsewhere. Its price table is part of the extension.
- It opens a fuegoapp.dev page only when you click a link to one, and when you remove it (section 8). Its welcome page, shown once after you first install it and never after an update, is part of the extension.
- What it reads never reaches us, so we cannot sell it, share it, read it or use it for advertising, and we never will.
- The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
8. Links to fuegoapp.dev, the welcome page and the uninstall question
- The fuegoapp.dev links of the extension’s popup, panel, settings and console buttons carry four tags in their address:
utm_source=fuego-devtools,utm_medium=extension,utm_campaignwith the place you clicked (such aspopuporpanel), andutm_contentwith the edition of the extension you use (chrome,edgeorfirefox; Brave, Opera, Vivaldi and other Chromium browsers use the Chrome edition). They carry no identifier, no version number and nothing about the pages you visited. On fuegoapp.dev, the website’s own Privacy Policy applies, including how the site uses these tags. - Once after you first install Fuego DevTools, it shows its welcome page: a page of the extension itself, which loads nothing from the internet. It never does so after an update. Its links to fuegoapp.dev open only when you click them, and carry no tags.
- When you remove Fuego DevTools, your browser opens
https://fuegoapp.dev/devtools/uninstall/, a visit like any other, without tags: a removed extension has no pages of its own left to show. The page asks one optional question: why you removed it, with five answers to choose from and a box for a comment. We receive nothing unless you submit it. If you do, we receive the answer you chose and your comment. Google reCAPTCHA checks the form against spam. Your answer is stored with the other feedback about Fuego and emailed to the Fuego team. No name, email address or identifier comes with it, unless you type one in the comment. We use these answers only to improve Fuego DevTools, keep them for 24 months, and delete an answer sooner on request. A stored answer is deleted automatically 24 months after it was sent, usually within a day after that date. - Like every page of this website, the uninstall page is covered by the website’s Privacy Policy and loads the services it describes. Google Analytics runs only if you accept analytics cookies in the site’s cookie banner, and the Reddit Pixel only if you accept advertising cookies there. We have turned off the Reddit Pixel’s automatic matching, so it does not look for email addresses or phone numbers on the page, in the comment box or anywhere else.
9. Keeping and deleting your data
How long the extension keeps what it holds:
- a Recording: until you clear it, click Reload to record again or close DevTools (on the Firebase console and the Google Cloud console, and in Safari on a site the panel records, a reload of the page also replaces it);
- the calls the recorder keeps in a page once DevTools has closed: about the last two minutes of them, until the page reloads or the tab loads another page;
- the documents kept in a Firebase console or Google Cloud console tab, and the details of the Storage files, the Authentication users and the Realtime Database data a Firebase console tab received: until the tab closes or reloads;
- what the window that explains Open in Fuego shows: until it closes;
- your settings: until you change them or remove the extension.
If you answer the uninstall question, we keep your answer for 24 months (section 8).
To delete everything the extension stores, remove it: your browser deletes its storage and withdraws its permissions. Short of that, you can:
- change your cost settings in the panel’s Cost settings or on the extension’s settings page;
- turn the badge off, which removes its access to all websites;
- remove its access to
firebasestorage.googleapis.comin your browser’s settings for the extension; - on Firefox, turn off its optional permissions on its page in
about:addons; - on Safari, remove a site’s access in Safari ▸ Settings ▸ Extensions (section 10).
Files you export and text you copy are yours: they stay wherever you saved or pasted them. Fuego’s note of when the extension last talked to it is the file extension-seen.json in Fuego’s settings folder; deleting it only means Fuego may suggest the extension again.
10. Fuego DevTools for Safari
Fuego DevTools for Safari will come later, on the Mac App Store, as Fuego DevTools. It is the same extension, with the differences below; the rest of this page applies to it too. As on the other browsers, nothing it or its app reads is sent to us or to anyone else.
The Fuego DevTools app
- Safari installs extensions from Mac apps, so Fuego DevTools comes in a small app of the same name. The app shows whether the extension is on in Safari, opens Safari’s settings, and lists the steps to turn the extension on and to find its Fuego tab in Web Inspector. Its Help, Privacy and Support links open fuegoapp.dev in your browser; Help and Support carry the tags of section 8, with
utm_campaign=containerandutm_content=safari, and the Privacy link carries none. - The app has no analytics, no crash reporter and no account of its own, keeps no data and makes no network requests. The Mac App Store handles the download under Apple’s own privacy policy. Like every developer, we see from Apple only what it reports to developers: figures such as the number of downloads and, from people who chose in macOS to share analytics with app developers, crash reports of the app.
How it reaches Fuego
- On Safari, the extension does not use the entry Fuego writes for other browsers (section 4). Safari hands its messages to a small part of the Fuego DevTools app that runs on your Mac, in Apple’s app sandbox (an “app extension”). That part receives nothing else, makes no network requests and keeps nothing. It never reads Fuego’s projects, settings or data.
- No question first. Safari lets the extension talk to its own app without asking you, so Safari shows no permission request after I have Fuego (section 4): the window that explains Open in Fuego appears only when Fuego is not found on this Mac.
- Is Fuego there? When you open the toolbar popup and before it shows an Open in Fuego button, the extension asks the app whether Fuego is installed on this Mac and whether it is running. The app answers from what macOS tells any app: where Fuego is installed, the version number of the copy that is running (else of the installed one) and the kinds of Fuego links that copy opens, both read from its own app information when it can, and whether Fuego is among the apps running. These questions carry nothing about the page you are on. Fuego itself is not asked: on Safari the extension never learns the project open in Fuego or the projects saved in it, so its buttons always read Open in Fuego.
- What you click goes to Fuego. When you click Open in Fuego or choose Open “…” in Fuego, the extension hands that one Fuego link to the app, which asks macOS to open it, as when you click a Fuego link anywhere else: Fuego starts if it is not running, comes to the front and opens it. Launch Fuego asks macOS to start Fuego or bring it to the front. When the app finds no Fuego and you choose I have Fuego, it asks macOS to open the link anyway; if that fails too, the extension hands the link to Safari, which asks you before it opens it.
- The setting in Fuego. Settings ▸ Language and formats ▸ Browser extension in Fuego removes the entries other browsers use and does not reach Safari: to stop Fuego DevTools for Safari from opening Fuego, turn it off in Safari ▸ Settings ▸ Extensions. Fuego notes nothing about Safari’s extension: the note of section 4 comes only from the other browsers.
Recording in Safari
- Safari’s Web Inspector cannot reload a page with the recorder, and Fuego DevTools never runs code in the page through Web Inspector. So the panel’s button reads Allow this site, then reload: Safari asks you to let Fuego DevTools access that site. Once you allow it, the extension has Safari put the recorder in that site’s pages as they start loading, and reloads the page.
- Safari adds the recorder only to the pages of that site that load while a Fuego panel that recorded it is open in Web Inspector, even if that panel now shows another site. When you close the last one, the extension stops adding it: a recorder already in a page stays until the page reloads or the tab loads another page, with the limits of section 3 (about the last two minutes of calls, never more than about 32 MB). A site here means its name, whatever the port: while a panel records
localhost:5173, a page oflocalhost:3000that you also allowed gets the recorder too. - While a panel records a site, each page of it that loads (a reload, or a link to another of its pages) brings a new recorder, and the panel starts a new Recording that replaces the last one, as on the consoles (section 3). A page that changes its address without loading a new page stays in the same Recording.
- The panel reads the recorder through the extension itself, in the tab you opened Web Inspector on, the page you inspect: the tab in front when the panel first reads it, and that same tab afterwards, whichever tab or window you bring to the front. The panel’s header shows that page’s title and site, so you can see which page it reads. Like any Recording, what it reads stays in the panel’s memory (section 3). The panel reads a page only through the access you gave its site.
- Safari keeps a site’s access until you remove it, in Safari ▸ Settings ▸ Extensions. While it lasts, the extension may read that site’s pages only as this page describes: the toolbar button’s check when you click it, the panel while it is open, and the badge while it is on.
The rest, on Safari
- The Firebase console and the Google Cloud console: on each console, the buttons and the always-on recorders of section 3 run only once you allow Fuego DevTools there from its toolbar button (Safari marks the button on sites it may not read yet).
- The panel and the Realtime Database: on Safari, selecting a Realtime Database call never makes the panel look at the inspected page’s Firebase setup, as section 3 describes for the other browsers, so a call’s database is matched to its project by the database’s name alone.
- No welcome page and no uninstall page: Safari shows neither, so the visit of section 8 never happens. The extension’s links to fuegoapp.dev carry
utm_content=safari. - Permissions: Safari lists no sites when you turn the extension on: you allow them site by site, as above. The optional access to all websites of section 6 is not only for the badge on Safari: it is also what the panel’s Allow this site, then reload asks for, one site at a time.
nativeMessagingis required on Safari, granted without a question, and reaches only the Fuego DevTools app.devtoolsadds the Fuego tab to Web Inspector, which Safari shows once Safari ▸ Settings ▸ Advanced ▸ Show features for web developers is on. - Turning it off and removing it: turn Fuego DevTools off, or remove a site’s access, in Safari ▸ Settings ▸ Extensions; delete the Fuego DevTools app to remove the extension from Safari.
11. Children
Fuego DevTools is a tool for software developers and is not directed at children.
12. Changes to this policy
We update this page, and its effective date, whenever the extension changes how it handles anything described here. If a new version would ever collect or send anything beyond what this page describes, it will tell you in the extension and ask for your agreement before it does.
Fuego DevTools is an independent tool, not affiliated with, endorsed or sponsored by Google LLC. Firebase and Firestore are trademarks of Google LLC.
