Ext Ops Panel
Open dashboard
Permissions and history

Is My Insurance Assistant safe to install?

My Insurance Assistant asks for 5 browser permissions and 9 site patterns. 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.

My Insurance Assistant

Chrome extension by dominick.gendusa · Productivity · Workflow

Open in the Chrome Web Store
What the developer says, and 4 screenshots

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
Access to specific sites only
Data collection
Declares it collects none
Publisher
No store badges
Audience
57 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

Specific sites only: 9 match patterns.

Reaches your browsing data or every site

Worth knowing

Routine for an extension

Pages it runs its code on

It runs its own code on specific pages only: 8 site patterns.

Show the remaining 5
  • https://*.nowcerts.com/* nowcerts.com and all its subdomains
  • https://mia.agency/* only mia.agency
  • https://*.mia.agency/* mia.agency and all its subdomains
  • https://mia.test/* only mia.test
  • https://*.mia.test/* mia.test and all its subdomains

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.

What it may ask for later

Not granted when you add it: Chrome asks you the moment the extension requests one of these, and you can refuse. It may later ask for access to every site.

How usual this is for its category

In Productivity · Workflow, 19% of extensions ask for access to every site. This one: Access to specific sites only.

The typical extension there declares 3 browser permissions; this one declares 5 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

57 users

Users
-3 since 31.08
47-60 · 30 readings
2026-09-15: released 1.4.242026-09-29: released 1.4.27
  1. 2026-08-3160
  2. 2026-09-0257
  3. 2026-09-0356
  4. 2026-09-0453
  5. 2026-09-0752
  6. 2026-09-0851
  7. 2026-09-1353
  8. 2026-09-1756
  9. 2026-09-2151
  10. 2026-09-2553
  11. 2026-09-2655
  12. 2026-09-2856
  13. 2026-10-0451
  14. 2026-10-0852
  15. 2026-10-1050
  16. 2026-10-1349
  17. 2026-10-1648
  18. 2026-10-1747
  19. 2026-10-1949
  20. 2026-10-2048
  21. 2026-10-2150
  22. 2026-10-2349
  23. 2026-10-2452
  24. 2026-10-2651
  25. 2026-10-2849
  26. 2026-10-2951
  27. 2026-10-3054
  28. 2026-11-0156
  29. 2026-11-0258
  30. 2026-11-0457

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.

  1. Asked for more permissions (14, was 13)

Versions we have seen

  1. Version 1.4.27
  2. Version 1.4.24 · Asked for more permissions (14, was 13)

Who publishes it

dominick.gendusa. This listing has been in the store since 2025-06-20 and was last updated on 2026-09-29.

Similar extensions that ask for less

Listings close to this one in what they say they do, which declare less reach. Less reach is not a verdict on either: compare what each needs for the job.

  1. BrokerCloud Launcher No site access · 1 permission 16 users
  2. InsuranceM8 Runs its code on every site · 4 permissions 3 users
  3. Agency Toolchest Runs its code on every site · 5 permissions 346 users ★ 5.0

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 My Insurance Assistant access?
Specific sites only: 9 match patterns. It declares 5 browser permissions.
What data does My Insurance Assistant 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 My Insurance Assistant asked for more permissions over time?
Its permissions changed once while we watched, on 2026-09-15.
Does My Insurance Assistant 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-04.

Back to My Insurance Assistant · Alternatives to My Insurance Assistant

Where the data comes from: how the catalog is built