Ext Ops Panel
Open dashboard
Permissions and history

Is StormRacer: Lichess Tactics Pro safe to install?

StormRacer: Lichess Tactics Pro asks for 6 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.

StormRacer: Lichess Tactics Pro

Chrome extension by StormRacer · Productivity · Education

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.

Site access
Access to specific sites only
Data collection
3 kinds of data declared
Publisher
No store badges
Audience
37 users · 5.0/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: 3 match patterns.

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 specific pages only: 10 site patterns.

Show the remaining 7
  • https://lichess.org/storm only lichess.org
  • https://lichess.org/training/* only lichess.org
  • https://lichess.org/training only lichess.org
  • https://lichess.org/streak only lichess.org
  • https://lichess.org/streak/* only lichess.org
  • https://*.lichess.org/streak lichess.org and all its subdomains
  • https://*.lichess.org/streak/* lichess.org and all its subdomains

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 · Education, 17% 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

37 users

Users
+1 since 01.09
31-40 · 30 readings
2026-09-22: released 1.0.32026-09-24: released 1.0.42026-10-23: released 1.0.5
  1. 2026-09-0136
  2. 2026-09-0240
  3. 2026-09-0734
  4. 2026-09-0838
  5. 2026-09-0937
  6. 2026-09-1535
  7. 2026-09-1634
  8. 2026-09-2033
  9. 2026-09-2132
  10. 2026-09-2531
  11. 2026-09-2632
  12. 2026-09-2831
  13. 2026-10-0435
  14. 2026-10-0834
  15. 2026-10-0935
  16. 2026-10-1033
  17. 2026-10-1334
  18. 2026-10-1633
  19. 2026-10-1834
  20. 2026-10-1933
  21. 2026-10-2034
  22. 2026-10-2135
  23. 2026-10-2234
  24. 2026-10-2435
  25. 2026-10-2539
  26. 2026-10-2838
  27. 2026-10-3040
  28. 2026-11-0136
  29. 2026-11-0437
  30. 2026-11-0537

What the store shows

The store shows none of its badges on this listing. Most listings carry none.

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 (9, was 8) (changed: pages it runs its code on, browser permissions)

Versions we have seen

  1. Version 1.0.5 · Asked for more permissions (9, was 8) (changed: pages it runs its code on, browser permissions)
  2. Version 1.0.4
  3. Version 1.0.3

Who publishes it

StormRacer. This listing has been in the store since 2026-03-16 and was last updated on 2026-10-23.

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. AI Chess Tutor No permissions at all · No permissions declared 34 users
  2. Lichess Puzzler No site access · 3 permissions 4 users
  3. Lichess Woodpecker No site access · 3 permissions 58 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 StormRacer: Lichess Tactics Pro access?
Specific sites only: 3 match patterns. It declares 6 browser permissions.
What data does StormRacer: Lichess Tactics Pro collect?
The developer declares that it collects these kinds of data: Personally identifiable information, User activity, Website content. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has StormRacer: Lichess Tactics Pro asked for more permissions over time?
Its permissions changed once while we watched, on 2026-10-23.
Does StormRacer: Lichess Tactics Pro 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 StormRacer: Lichess Tactics Pro · Alternatives to StormRacer: Lichess Tactics Pro

Where the data comes from: how the catalog is built