Ext Ops Panel
Open dashboard
Permissions and history

Is Journey Capture Extension safe to install?

Journey Capture Extension asks for 6 browser permissions and 1 site pattern. 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.

Journey Capture Extension

Chrome extension by RubberDuck · 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
Access to every site
Data collection
Declares it collects none
Publisher
No store badges
Audience
42 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

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

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: Access to every site.

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

42 users

Users
+9 since 31.08
33-43 · 31 readings
2026-10-11: released 1.13.3
  1. 2026-08-3133
  2. 2026-09-0235
  3. 2026-09-0536
  4. 2026-09-0637
  5. 2026-09-0735
  6. 2026-09-0838
  7. 2026-09-1036
  8. 2026-09-1634
  9. 2026-09-2037
  10. 2026-09-2136
  11. 2026-09-2635
  12. 2026-09-2834
  13. 2026-10-0537
  14. 2026-10-0838
  15. 2026-10-1034
  16. 2026-10-1336
  17. 2026-10-1642
  18. 2026-10-1740
  19. 2026-10-1842
  20. 2026-10-1941
  21. 2026-10-2043
  22. 2026-10-2241
  23. 2026-10-2340
  24. 2026-10-2441
  25. 2026-10-2540
  26. 2026-10-2639
  27. 2026-10-2837
  28. 2026-10-3039
  29. 2026-11-0241
  30. 2026-11-0442
  31. 2026-11-0642

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.

  1. Changed where it works (changed: pages it runs its code on)
  2. Privacy policy link added to the listing

Versions we have seen

  1. Version 1.13.3 · Changed where it works (changed: pages it runs its code on)

Who publishes it

RubberDuck. This listing has been in the store since 2024-10-30 and was last updated on 2026-10-11.

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. QA Capture No site access · 4 permissions 102 users ★ 5.0
  2. JourneyLens — Process Walkthrough QA No site access · 8 permissions 4 users (last published figure)
  3. FlowNest Access to specific sites only · 10 permissions, 2 site patterns 18 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 Journey Capture Extension access?
Every site you visit. This extension can read and change the content of any page you open. It declares 6 browser permissions.
What data does Journey Capture Extension 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 Journey Capture Extension asked for more permissions over time?
Its permissions changed 2 times while we watched, most recently on 2026-10-11.
Does Journey Capture Extension 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-06.

Back to Journey Capture Extension · Alternatives to Journey Capture Extension

Where the data comes from: how the catalog is built