Ext Ops Panel
Open dashboard
Permissions and history

Is Meet Reaction Keydown safe to install?

Meet Reaction Keydown 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.

Meet Reaction Keydown

Chrome extension by nacal · Make Chrome Yours · Accessibility

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
Featured
Audience
107 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 does not link 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 Make Chrome Yours · Accessibility, 23% of extensions ask for access to every site. This one: No permissions at all.

The typical extension there declares 2 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

107 users

Users
-2 since 01.09
101-113 · 40 readings
  1. 2026-09-01109
  2. 2026-09-02110
  3. 2026-09-05112
  4. 2026-09-06108
  5. 2026-09-07109
  6. 2026-09-08113
  7. 2026-09-09110
  8. 2026-09-13107
  9. 2026-09-21104
  10. 2026-09-25103
  11. 2026-09-26101
  12. 2026-09-28102
  13. 2026-10-08108
  14. 2026-10-09106
  15. 2026-10-10105
  16. 2026-10-13106
  17. 2026-10-16107
  18. 2026-10-17108
  19. 2026-10-18106
  20. 2026-10-19105
  21. 2026-10-20107
  22. 2026-10-21104
  23. 2026-10-22106
  24. 2026-10-23103
  25. 2026-10-24106
  26. 2026-10-25105
  27. 2026-10-26107
  28. 2026-10-28111
  29. 2026-10-29108
  30. 2026-10-30107
  31. 2026-11-01106
  32. 2026-11-02105
  33. 2026-11-04103
  34. 2026-11-06106
  35. 2026-11-07104
  36. 2026-11-08105
  37. 2026-11-09107
  38. 2026-11-10106
  39. 2026-11-11107
  40. 2026-11-12107

What the store shows

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

nacal. This listing has been in the store since 2023-02-13 and was last updated on 2024-04-22.

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 Meet Reaction Keydown 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 Meet Reaction Keydown 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 Meet Reaction Keydown asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Meet Reaction Keydown publish a privacy policy?
No, the store listing does not link 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-12.

Back to Meet Reaction Keydown · Alternatives to Meet Reaction Keydown

Where the data comes from: how the catalog is built