Ext Ops Panel
Open dashboard
Permissions and history

Is IHN: Luma to LinkedIn Automation safe to install?

IHN: Luma to LinkedIn Automation asks for 7 browser permissions and 5 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.

IHN: Luma to LinkedIn Automation

Chrome extension · Productivity · Communication

Open in the Chrome Web Store
What the developer says, and 3 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
2 kinds of data declared
Upkeep
Updated 181 days ago
Audience
8 users · 5.0/5

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

Show the remaining 1
  • https://ihatenetworking.space/login* only ihatenetworking.space

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: 1 site pattern.

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 Productivity · Communication, 14% 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 7 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

8 users

Users
+2 since 01.09
5-9 · 24 readings
  1. 2026-09-016
  2. 2026-09-028
  3. 2026-09-047
  4. 2026-09-058
  5. 2026-09-066
  6. 2026-09-088
  7. 2026-09-139
  8. 2026-09-178
  9. 2026-09-216
  10. 2026-09-267
  11. 2026-09-286
  12. 2026-10-085
  13. 2026-10-096
  14. 2026-10-105
  15. 2026-10-136
  16. 2026-10-167
  17. 2026-10-178
  18. 2026-10-187
  19. 2026-10-218
  20. 2026-10-227
  21. 2026-10-238
  22. 2026-10-247
  23. 2026-10-298
  24. 2026-10-318

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

The store lists no publisher name. This listing has been in the store since 2026-03-01 and was last updated on 2026-05-03.

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. Meetlify for LinkedIn Access to specific sites only · 1 site pattern 7 users ★ 5.0
  2. LinkedIn Connect Helper Access to specific sites only · 1 site pattern 3 users (last published figure)
  3. Ewents LinkedIn (DEV) Access to specific sites only · 1 permission, 4 site patterns 4 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 IHN: Luma to LinkedIn Automation access?
Specific sites only: 5 match patterns. It declares 7 browser permissions.
What data does IHN: Luma to LinkedIn Automation collect?
The developer declares that it collects these kinds of data: Personally identifiable information, Personal communications. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has IHN: Luma to LinkedIn Automation asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does IHN: Luma to LinkedIn Automation 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 IHN: Luma to LinkedIn Automation · Alternatives to IHN: Luma to LinkedIn Automation

Where the data comes from: how the catalog is built