Ext Ops Panel
Open dashboard
Permissions and history

Is r12: grid overlay & layout inspector safe to install?

r12: grid overlay & layout inspector asks for 3 browser permissions and declares no blanket site access. 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.

r12: grid overlay & layout inspector

Chrome extension by r12 · Productivity · Developer

Open in the Chrome Web Store
What the developer says, and 5 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.

Data collection
Declares it collects none
Upkeep
Updated 280 days ago
Audience
90 users

What data it declares

The developer declares that it does not collect or use your 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

No site access is declared in the manifest, so it cannot read the pages you open on its own.

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, 30% 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 3 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

90 users

Users
+27 since 01.09
63-90 · 30 readings
  1. 2026-09-0163
  2. 2026-09-0365
  3. 2026-09-0466
  4. 2026-09-0670
  5. 2026-09-0769
  6. 2026-09-0967
  7. 2026-09-1072
  8. 2026-09-1376
  9. 2026-09-1575
  10. 2026-09-1773
  11. 2026-09-2076
  12. 2026-09-2274
  13. 2026-09-2578
  14. 2026-09-2680
  15. 2026-09-2878
  16. 2026-10-0473
  17. 2026-10-0872
  18. 2026-10-0979
  19. 2026-10-1080
  20. 2026-10-1386
  21. 2026-10-1689
  22. 2026-10-1888
  23. 2026-10-1986
  24. 2026-10-2187
  25. 2026-10-2283
  26. 2026-10-2387
  27. 2026-10-2484
  28. 2026-10-2586
  29. 2026-10-2990
  30. 2026-10-3190

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

r12. This listing has been in the store since 2025-11-16 and was last updated on 2026-01-25.

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. Grid Lines Ruler Runs its code on every site · 1 permission 7k users ★ 4.3
  2. Bootstrap Grid Overlay - Web Layout Tool Runs its code on every site · 1 permission 8 users
  3. Grid Overlay Pro Runs its code on every site · 2 permissions 431 users ★ 5.0

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 r12: grid overlay & layout inspector access?
No site access is declared in the manifest, so it cannot read the pages you open on its own. It declares 3 browser permissions.
What data does r12: grid overlay & layout inspector collect?
The developer declares that it does not collect or use your data. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has r12: grid overlay & layout inspector asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does r12: grid overlay & layout inspector 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 r12: grid overlay & layout inspector · Alternatives to r12: grid overlay & layout inspector

Where the data comes from: how the catalog is built