Ext Ops Panel
Open dashboard
Permissions and history

Is St. Mark's Lutheran Church and School safe to install?

St. Mark's Lutheran Church and School declares no browser permissions and no site access in its manifest, which is as narrow as an extension gets. 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.

St. Mark's Lutheran Church and School

Chrome Web Store listing by casey.defrain

Open in the Chrome Web Store
What the developer says, and 1 screenshot

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
No permissions at all
Audience
98 users

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.

Who uses it and how it is kept up

98 users

Users
+55 since 01.09
43-127 · 36 readings
  1. 2026-09-0143
  2. 2026-09-0475
  3. 2026-09-0576
  4. 2026-09-0674
  5. 2026-09-0775
  6. 2026-09-0876
  7. 2026-09-0980
  8. 2026-09-1376
  9. 2026-09-1577
  10. 2026-09-1774
  11. 2026-09-20105
  12. 2026-09-22103
  13. 2026-09-25105
  14. 2026-09-26127
  15. 2026-10-0897
  16. 2026-10-09101
  17. 2026-10-1099
  18. 2026-10-16105
  19. 2026-10-17103
  20. 2026-10-1898
  21. 2026-10-1996
  22. 2026-10-2197
  23. 2026-10-2295
  24. 2026-10-2394
  25. 2026-10-2495
  26. 2026-10-2594
  27. 2026-10-2895
  28. 2026-10-2988
  29. 2026-10-3095
  30. 2026-11-0181
  31. 2026-11-0484
  32. 2026-11-0686
  33. 2026-11-0796
  34. 2026-11-0895
  35. 2026-11-1198
  36. 2026-11-1298

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

casey.defrain, who publishes 3 listings we track. This listing has been in the store since 2013-07-28 and was last updated on 2013-07-28.

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 St. Mark's Lutheran Church and School 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 St. Mark's Lutheran Church and School collect?
The listing carries no declaration about the data it collects.
Has St. Mark's Lutheran Church and School asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does St. Mark's Lutheran Church and School publish a privacy policy?
No, the store listing does not link 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-12.

Back to St. Mark's Lutheran Church and School · Alternatives to St. Mark's Lutheran Church and School

Where the data comes from: how the catalog is built