Ext Ops Panel
Open dashboard
Permissions and history

Is Fireglass for Fieldglass Timesheets safe to install?

Fireglass for Fieldglass Timesheets declares no browser permissions and no site access in its manifest, which is as narrow as an extension gets. We do not audit code and we do not judge intent; what we can show is what the listing declares and whether that has changed while we have been watching.

Fireglass for Fieldglass Timesheets

Chrome extension by floodmeadows · Productivity · Workflow

Open in the Chrome Web Store
What the developer says, and 1 screenshot

Loading from the Chrome Web Store. Open the listing if it does not appear.

At a glance

Facts, not a score: an ad blocker needs every page and a theme needs nothing, so one number would be wrong about both. Each fact links to its detail.

Site access
No permissions at all
Data collection
Declares it collects none
Publisher
No store badges
Audience
17 users · 5.0/5

What data it declares

The developer declares that it does not collect or use your data.

The developer also certifies that your data is not sold to third parties outside approved uses, not used for purposes unrelated to the extension's core function, and not used to decide creditworthiness or lending.

The listing links to a privacy policy.

This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.

What Chrome asks you to allow

When you add it, Chrome asks you to allow it to:

Derived from the manifest by Chrome's documented rules; the dialog's exact wording depends on your Chrome version and language. Chrome asks again if an update requests more.

What it can reach

No site access is declared in the manifest, so it cannot read the pages you open on its own.

We have not read this listing's manifest since we started keeping permission names. The counts on the card come from the last time we did.

Pages it runs its code on

It runs its own code on specific pages only: 1 site pattern.

A content script is code the extension injects into pages matching these patterns. On those pages it can read and change what you see, whether or not a host permission is listed above.

How usual this is for its category

In Productivity · Workflow, 19% of extensions ask for access to every site. This one: No permissions at all.

The typical extension there declares 3 browser permissions; this one declares no browser permissions.

Counted over the live extensions of the same category after our latest full pass of the store. A share is context, not a verdict: what is normal depends on what the extension is for.

Who uses it and how it is kept up

17 users

Users
-4 since 01.09
16-30 · 27 readings
  1. 2026-09-0121
  2. 2026-09-0322
  3. 2026-09-0421
  4. 2026-09-0619
  5. 2026-09-0916
  6. 2026-09-1518
  7. 2026-09-1617
  8. 2026-09-2019
  9. 2026-09-2120
  10. 2026-09-2518
  11. 2026-09-2819
  12. 2026-10-0522
  13. 2026-10-0829
  14. 2026-10-0930
  15. 2026-10-1028
  16. 2026-10-1619
  17. 2026-10-1821
  18. 2026-10-1920
  19. 2026-10-2118
  20. 2026-10-2220
  21. 2026-10-2322
  22. 2026-10-2419
  23. 2026-10-2518
  24. 2026-10-2717
  25. 2026-10-2916
  26. 2026-11-0117
  27. 2026-11-0217

What the store shows

The store shows none of its badges on this listing. Most listings carry none.

Has it asked for more over time?

This is the question a permission list on its own cannot answer. An extension that shipped narrow and widened later is a different proposition from one that always asked for the same thing.

The permissions this extension requests have not changed since we started watching it.

Who publishes it

floodmeadows, who publishes 3 listings we track. This listing has been in the store since 2020-01-23 and was last updated on 2024-09-28.

How to check or remove it in Chrome

  1. Type chrome://extensions in the address bar and find the extension in the list.
  2. Open its details. The site access setting shows where it can run; set it to run only on click and it reaches a page only after you press its icon.
  3. To uninstall it, choose Remove on the same page.

Questions people ask

What can Fireglass for Fieldglass Timesheets access?
No site access is declared in the manifest, so it cannot read the pages you open on its own. It declares no browser permissions.
What data does Fireglass for Fieldglass Timesheets collect?
The developer declares that it does not collect or use your data. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has Fireglass for Fieldglass Timesheets asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Fireglass for Fieldglass Timesheets publish a privacy policy?
Yes, the store listing links to a privacy policy.

We read the public store listing up to 2 times a day and keep what it declared. We do not install the extension, do not audit its code, do not judge its intent and publish no contact details for its developer. Last read on 2026-11-02.

Back to Fireglass for Fieldglass Timesheets · Alternatives to Fireglass for Fieldglass Timesheets

Where the data comes from: how the catalog is built