Ext Ops Panel
Open dashboard
Permissions and history

Is NL Launch Companion: Directory Autofill safe to install?

NL Launch Companion: Directory Autofill asks for 2 browser permissions and 2 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.

NL Launch Companion: Directory Autofill

Chrome extension by Nick Launches · Productivity · Developer

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
Runs its code on every site
Data collection
1 kind of data declared
Audience
158 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: 2 match patterns.

Worth knowing

Routine for an extension

Pages it runs its code on

It runs its own code on every page you open: the manifest declares a content script for all sites.

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 Productivity · Developer, 31% of extensions ask for access to every site. This one: Runs its code on every site.

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

158 users

Users
+9 since 31.08
149-167 · 18 readings
  1. 2026-08-31149
  2. 2026-09-02152
  3. 2026-09-04153
  4. 2026-09-06156
  5. 2026-09-07158
  6. 2026-09-09159
  7. 2026-09-10161
  8. 2026-09-13166
  9. 2026-09-15167
  10. 2026-09-21166
  11. 2026-09-25164
  12. 2026-09-26166
  13. 2026-09-28162
  14. 2026-10-04156
  15. 2026-10-08158
  16. 2026-10-09155
  17. 2026-10-10158
  18. 2026-10-11158

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

Nick Launches, who publishes 3 listings we track. This listing has been in the store since 2026-07-26 and was last updated on 2026-07-26.

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. Launchelion Autofill for directory submissions No site access · 3 permissions 1 users (last published figure) ★ 5.0
  2. launchin-companion No site access · 3 permissions 2 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 NL Launch Companion: Directory Autofill access?
Specific sites only: 2 match patterns. It declares 2 browser permissions.
What data does NL Launch Companion: Directory Autofill collect?
The developer declares that it collects these kinds of data: User activity. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has NL Launch Companion: Directory Autofill asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does NL Launch Companion: Directory Autofill 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-11.

Back to NL Launch Companion: Directory Autofill · Alternatives to NL Launch Companion: Directory Autofill

Where the data comes from: how the catalog is built