Is Native Client SDK (Dev) safe to install?

What data it declares

The listing carries no declaration about the data it collects.

The listing does not link to a privacy policy.

What Chrome asks you to allow

From the permissions it declares, Chrome shows no permission warning when you add it.

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.

Where it runs its code

We have not read this listing's manifest since we started keeping where it embeds its code, what it may ask for later and which sites can connect to it. The next pass of the store fills this in.

How usual this is for its category

In Productivity · Developer, 30% of extensions ask for access to every site. This one: No permissions at all.

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

99 users

• Not updated in the store for over a year: the last update was on 2013-10-24.
• No new version in the last 90 days.

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.

The permissions this extension requests have not changed since we started watching it.

Who publishes it

naclrocks, who publishes 3 listings we track. This listing has been in the store since 2013-10-24 and was last updated on 2013-10-24.

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 Native Client SDK (Dev) 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 Native Client SDK (Dev) collect?

The listing carries no declaration about the data it collects.

Has Native Client SDK (Dev) asked for more permissions over time?

The permissions this extension requests have not changed since we started watching it.

Does Native Client SDK (Dev) publish a privacy policy?

No, the store listing does not link to a privacy policy.