Ext Ops Panel
Open dashboard
Permissions and history

Is Riffloop - AI Stem Splitter, Chords, Vocal Remover & Looper for YouTube safe to install?

Riffloop - AI Stem Splitter, Chords, Vocal Remover & Looper for YouTube asks for 6 browser permissions and 2 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.

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.

Site access
Access to specific sites only
Data collection
2 kinds of data declared
Audience
852 users · 4.3/5

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

Specific sites only: 2 match patterns.

Worth knowing

Routine for an extension

Pages it runs its code on

It runs its own code on specific pages only: 1 site pattern.

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 · Tools, 20% of extensions ask for access to every site. This one: Access to specific sites only.

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

852 users

Users
+615 since 01.09
237-852 · 31 readings
2026-09-15: released 1.2.22026-10-06: released 1.2.52026-10-09: released 1.2.62026-10-17: released 1.2.72026-10-28: released 1.2.8
  1. 2026-09-01237
  2. 2026-09-03241
  3. 2026-09-04263
  4. 2026-09-06297
  5. 2026-09-07316
  6. 2026-09-09338
  7. 2026-09-10350
  8. 2026-09-13379
  9. 2026-09-15400released 1.2.2
  10. 2026-09-17428
  11. 2026-09-21453
  12. 2026-09-22460
  13. 2026-09-25496
  14. 2026-09-27504
  15. 2026-09-28515
  16. 2026-10-05592
  17. 2026-10-08632
  18. 2026-10-09653released 1.2.6
  19. 2026-10-10653
  20. 2026-10-13663
  21. 2026-10-16719
  22. 2026-10-18741
  23. 2026-10-19757
  24. 2026-10-21771
  25. 2026-10-22786
  26. 2026-10-23798
  27. 2026-10-24818
  28. 2026-10-25821
  29. 2026-10-27833
  30. 2026-10-29836
  31. 2026-11-01852

What the store shows

The listing says it offers in-app purchases.

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. Asked for more permissions (8, was 7) (changed: browser permissions)
  2. Asked for fewer permissions (7, was 8)

Versions we have seen

  1. Version 1.2.8
  2. Version 1.2.7 · Asked for more permissions (8, was 7) (changed: browser permissions)
  3. Version 1.2.6
  4. Version 1.2.5
  5. Version 1.2.2 · Asked for fewer permissions (7, was 8)

Who publishes it

riffloopapp, who publishes 2 listings we track. This listing has been in the store since 2026-06-24 and was last updated on 2026-10-28.

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. Splittr – AI Stem Separator Access to specific sites only · 1 permission, 1 site pattern 95 users ★ 1.7
  2. PlayFlow: Musician Toolbox for YouTube Access to specific sites only · 2 permissions, 2 site patterns 92 users ★ 5.0
  3. Chord Lens: YouTube Chord Finder, Lyrics & Stem Splitter Access to specific sites only · 4 permissions, 1 site pattern 480 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 Riffloop - AI Stem Splitter, Chords, Vocal Remover & Looper for YouTube access?
Specific sites only: 2 match patterns. It declares 6 browser permissions.
What data does Riffloop - AI Stem Splitter, Chords, Vocal Remover & Looper for YouTube 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 Riffloop - AI Stem Splitter, Chords, Vocal Remover & Looper for YouTube asked for more permissions over time?
Its permissions changed 2 times while we watched, most recently on 2026-10-17.
Does Riffloop - AI Stem Splitter, Chords, Vocal Remover & Looper for YouTube 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-01.

Back to Riffloop - AI Stem Splitter, Chords, Vocal Remover & Looper for YouTube · Alternatives to Riffloop - AI Stem Splitter, Chords, Vocal Remover & Looper for YouTube

Where the data comes from: how the catalog is built