Ext Ops Panel
Open dashboard
Permissions and history

Is Meet Local Recorder safe to install?

Meet Local Recorder asks for 6 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.

Meet Local Recorder

Chrome extension by TAMALAMPUDI SAMEER REDDY · Productivity · Tools

Open in the Chrome Web Store
What the developer says, and 2 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
6 kinds of data declared
Publisher
No store badges
Audience
7 users

What data it declares

The developer declares that it collects these kinds of 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: 1 match pattern.

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: 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.

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.

How usual this is for its category

In Productivity · Tools, 20% 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 6 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

7 users

Users
+7 since 12.10
0-8 · 11 readings
2026-10-12: appeared in the store2026-10-12: released 0.3.02026-10-13: released 0.4.12026-10-16: released 0.4.2
  1. 2026-10-120appeared in the storereleased 0.3.0
  2. 2026-10-132released 0.4.1
  3. 2026-10-166released 0.4.2
  4. 2026-10-197
  5. 2026-10-206
  6. 2026-10-228
  7. 2026-10-237
  8. 2026-10-266
  9. 2026-10-288
  10. 2026-10-297
  11. 2026-10-317

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. Changed where it works (changed: optional site access)

Versions we have seen

  1. Version 0.4.2
  2. Version 0.4.1 · Changed where it works (changed: optional site access)
  3. Version 0.3.0

Who publishes it

TAMALAMPUDI SAMEER REDDY, who publishes 2 listings we track. This listing has been in the store since 2026-10-11 and was last updated on 2026-10-16.

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. Local Meeting Recorder No site access · 1 permission 3 users (last published figure)
  2. Meet Auto-Record No site access · 1 permission 3 users
  3. Au3Meet – Google Meet Audio Recorder Access to specific sites only · 5 permissions, 2 site patterns 27 users

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 Local Recorder access?
Specific sites only: 1 match pattern. It declares 6 browser permissions.
What data does Meet Local Recorder collect?
The developer declares that it collects these kinds of data: Personally identifiable information, Health information, Financial and payment information, Authentication information, Personal communications, Website content. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has Meet Local Recorder asked for more permissions over time?
Its permissions changed once while we watched, on 2026-10-13.
Does Meet Local Recorder 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-10-31.

Back to Meet Local Recorder · Alternatives to Meet Local Recorder

Where the data comes from: how the catalog is built