Ext Ops Panel
Open dashboard
Permissions and history

Is CloudCodes for G Suite Code51qa safe to install?

CloudCodes for G Suite Code51qa asks for 7 browser permissions and 3 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.

CloudCodes for G Suite Code51qa

Chrome extension by Plurilock security private limited · Make Chrome Yours · Accessibility

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 every site
Data collection
2 kinds of data declared
Publisher
Trader
Audience
22 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

Every site you visit. This extension can read and change the content of any page you open. What access to every site means

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 every page you open: the manifest declares a content script for all sites.

Show the remaining 24
  • *://mail.google.com/mail*/x/* only mail.google.com
  • *://accounts.google.com/* only accounts.google.com
  • *://drive.google.com/* only drive.google.com
  • *://docs.google.com/* only docs.google.com
  • *://plus.google.com/* only plus.google.com
  • *://www.google.com/contacts/* only www.google.com
  • *://contacts.google.com/* only contacts.google.com
  • *://sites.google.com/* only sites.google.com
  • *://hangouts.google.com/* only hangouts.google.com
  • *://photos.google.com/* only photos.google.com
  • *://www.youtube.com/* only www.youtube.com
  • *://play.google.com/* only play.google.com
  • *://groups.google.com/* only groups.google.com
  • *://myaccount.google.com/* only myaccount.google.com
  • *://meet.google.com/* only meet.google.com
  • *://calendar.google.com/* only calendar.google.com
  • https://*.google.com/* google.com and all its subdomains
  • *://*.appspot.com/loginpageservlet/* appspot.com and all its subdomains
  • *://*.appspot.com/* appspot.com and all its subdomains
  • *://*.appspot.com/user/login/accountlogin/* appspot.com and all its subdomains
  • *://*.appspot.com/user/login/* appspot.com and all its subdomains
  • *://accounts.google.com/o/openid2/* only accounts.google.com
  • *://accounts.google.com/signin/oauth/consent/* only accounts.google.com
  • *://accounts.google.com/signin/oauth/oauthchooseaccount/* only accounts.google.com

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 Make Chrome Yours · Accessibility, 23% of extensions ask for access to every site. This one: Access to every site.

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

22 users

Users
+1 since 31.08
13-24 · 28 readings
  1. 2026-08-3121
  2. 2026-09-0220
  3. 2026-09-0419
  4. 2026-09-0520
  5. 2026-09-0719
  6. 2026-09-0820
  7. 2026-09-1517
  8. 2026-09-1713
  9. 2026-09-2017
  10. 2026-09-2116
  11. 2026-09-2520
  12. 2026-09-2722
  13. 2026-09-2820
  14. 2026-10-0416
  15. 2026-10-0822
  16. 2026-10-0921
  17. 2026-10-1020
  18. 2026-10-1614
  19. 2026-10-1815
  20. 2026-10-2017
  21. 2026-10-2123
  22. 2026-10-2424
  23. 2026-10-2522
  24. 2026-10-2816
  25. 2026-10-2920
  26. 2026-11-0121
  27. 2026-11-0422
  28. 2026-11-0522

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

Plurilock security private limited, who publishes 6 listings we track. This listing has been in the store since 2014-09-24 and was last updated on 2022-09-05.

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. Revokeit No site access · 3 permissions 6 users (last published figure)
  2. DomainGuard — Corporate Email Domain Policy Access to every site · 2 permissions, 1 site pattern 3 users
  3. oneTwoOne Lockdown Access to every site · 5 permissions, 1 site pattern 100k users ★ 2.3

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 CloudCodes for G Suite Code51qa access?
Every site you visit. This extension can read and change the content of any page you open. It declares 7 browser permissions.
What data does CloudCodes for G Suite Code51qa collect?
The developer declares that it collects these kinds of data: Personally identifiable information, User activity. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has CloudCodes for G Suite Code51qa asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does CloudCodes for G Suite Code51qa 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-11-05.

Back to CloudCodes for G Suite Code51qa · Alternatives to CloudCodes for G Suite Code51qa

Where the data comes from: how the catalog is built