Ext Ops Panel
Open dashboard
Permissions and history

Is PHI Mask - Keep PHI out of AI safe to install?

PHI Mask - Keep PHI out of AI asks for 4 browser permissions and 1 site pattern. 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.

PHI Mask - Keep PHI out of AI

Chrome extension by PHI Mask · Make Chrome Yours · Privacy

Open in the Chrome Web Store
What the developer says, and 5 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 every site
Data collection
Declares it collects none
Upkeep
Updated 1 day ago
Publisher
No store badges
Audience
18 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

Every site you visit. This extension can read and change the content of any page you open. What access to every site means

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: 30 site patterns.

Show the remaining 27
  • https://aistudio.google.com/* only aistudio.google.com
  • https://copilot.microsoft.com/* only copilot.microsoft.com
  • https://copilot.com/* only copilot.com
  • https://www.copilot.com/* only www.copilot.com
  • https://www.perplexity.ai/* only www.perplexity.ai
  • https://chat.mistral.ai/* only chat.mistral.ai
  • https://chat.deepseek.com/* only chat.deepseek.com
  • https://grok.com/* only grok.com
  • https://poe.com/* only poe.com
  • https://www.kimi.ai/* only www.kimi.ai
  • https://www.kimi.com/* only www.kimi.com
  • https://meta.ai/* only meta.ai
  • https://www.meta.ai/* only www.meta.ai
  • https://lovable.dev/* only lovable.dev
  • https://replit.com/* only replit.com
  • https://base44.com/* only base44.com
  • https://app.base44.com/* only app.base44.com
  • https://aifiesta.ai/* only aifiesta.ai
  • https://chat.v2.aifiesta.ai/* only chat.v2.aifiesta.ai
  • https://www.openevidence.com/* only www.openevidence.com
  • https://m365.cloud.microsoft/* only m365.cloud.microsoft
  • https://copilot.cloud.microsoft/* only copilot.cloud.microsoft
  • https://notebook.google.com/* only notebook.google.com
  • https://chat.qwen.ai/* only chat.qwen.ai
  • https://duck.ai/* only duck.ai
  • https://chat.z.ai/* only chat.z.ai
  • https://www.google.com/* only www.google.com

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.

Sites that can connect to it

Web pages matching these patterns can open a messaging channel to it: 3 site patterns.

Declared as externally connectable in the manifest: a page on these sites can exchange messages with the extension, for example to tell it you have signed in. It does not give the page access to your browser.

How usual this is for its category

In Make Chrome Yours · Privacy, 42% of extensions ask for access to every site. This one: Access to every site.

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

18 users

Users
+12 since 01.09
6-19 · 28 readings
2026-09-05: released 0.3.52026-09-06: released 0.3.62026-09-08: released 0.4.02026-09-11: released 0.4.12026-09-15: released 0.4.2.12026-09-16: released 0.4.2.22026-09-17: released 0.4.32026-09-20: released 0.5.02026-09-22: released 0.5.12026-09-24: released 0.5.22026-09-29: released 0.5.42026-10-17: released 1.1.02026-10-19: released 1.1.12026-10-26: released 1.1.22026-11-01: released 1.1.3
  1. 2026-09-016
  2. 2026-09-038
  3. 2026-09-047
  4. 2026-09-068released 0.3.6
  5. 2026-09-079
  6. 2026-09-0810released 0.4.0
  7. 2026-09-109
  8. 2026-09-1310
  9. 2026-09-1712released 0.4.3
  10. 2026-09-2116
  11. 2026-09-2514
  12. 2026-09-2716
  13. 2026-09-2814
  14. 2026-10-0413
  15. 2026-10-0812
  16. 2026-10-0915
  17. 2026-10-1014
  18. 2026-10-1117
  19. 2026-10-1319
  20. 2026-10-1717released 1.1.0
  21. 2026-10-1918released 1.1.1
  22. 2026-10-2119
  23. 2026-10-2217
  24. 2026-10-2418
  25. 2026-10-2816
  26. 2026-10-2916
  27. 2026-11-0118released 1.1.3
  28. 2026-11-0218

What the store shows

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

The listing says it offers in-app purchases.

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 fewer permissions (5, was 26) (changed: site access, pages it runs its code on, optional site access, sites that can connect to it)
  2. Asked for fewer permissions (26, was 27)

Versions we have seen

  1. Version 1.1.3
  2. Version 1.1.2
  3. Version 1.1.1
  4. Version 1.1.0 · Asked for fewer permissions (5, was 26) (changed: site access, pages it runs its code on, optional site access, sites that can connect to it)
  5. Version 0.5.4 · Asked for fewer permissions (26, was 27)
  6. Version 0.5.2
  7. Version 0.5.1

Who publishes it

PHI Mask. This listing has been in the store since 2026-08-26 and was last updated on 2026-11-01.

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. mask2ai No permissions at all · No permissions declared 4 users
  2. PII Masker No site access · 2 permissions 5 users (last published figure) ★ 5.0
  3. Velum Lite: Mask PII in AI Chats No site access · 5 permissions 16 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 PHI Mask - Keep PHI out of AI access?
Every site you visit. This extension can read and change the content of any page you open. It declares 4 browser permissions.
What data does PHI Mask - Keep PHI out of AI 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 PHI Mask - Keep PHI out of AI asked for more permissions over time?
Its permissions changed 2 times while we watched, most recently on 2026-10-17.
Does PHI Mask - Keep PHI out of AI 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 PHI Mask - Keep PHI out of AI · Alternatives to PHI Mask - Keep PHI out of AI

Where the data comes from: how the catalog is built