JSK SoundShape privacy policy

Last updated: 7 October 2026

Overview

JSK SoundShape processes audio entirely on your device, inside your browser. It does
not record, upload, or transmit what you listen to, and it does not track the sites you
visit. If you never connect a JSKAPPS account, the extension itself makes no network
requests.

Information we collect

We collect no personal information.

The extension stores the following on your own device, and nowhere else:

• Your equalizer settings, saved per site origin (for example https://www.youtube.com)
• Your saved presets, themes and display preferences
• If you connect an account: your JSKAPPS API key, your account identifier, your plan
  (its name, and the date a trial or a fixed-term plan ends), the time of the last
  licence check, and a random device identifier (see The licence check below)

Apart from the licence check described below, none of this is transmitted to us. It lives
in your browser's extension storage and is removed when you uninstall.

How we use it

Only to make the extension work: to re-apply your settings when you return to a site,
and — if you have connected an account — to determine which features your plan includes.

Permissions and why we need them

On Chrome and Edge:

• tabCapture — to read the audio of the tab you are on, so it can be equalised. It
  is used only on a tab you have explicitly invoked SoundShape on.
• offscreen — to run the audio processing in a hidden document, because a Manifest V3
  service worker cannot host an audio engine.
• activeTab — to identify the tab you clicked on. This grants access to that one tab,
  at that moment, and nothing else.
• storage — to save your settings locally in your browser.
• sidePanel — to show the Studio panel.

On Firefox:

• storage — as above.
• activeTab — as above.
• scripting — to insert the audio processor into the page you are using, because
  Firefox has no tab-capture API.
• optional host access — requested only at the moment you use SoundShape on a site,
  never at install, and you may decline it.

We request no host permissions on Chrome or Edge. The extension cannot read the
content of the pages you visit.

Data storage and retention

Everything is stored locally in your browser and kept until you delete it or uninstall
the extension. We operate no server that holds your settings. If you connect an account,
JSKAPPS keeps, with your key, which app it was used from and the hashed device identifier,
so it can count devices per key; it never receives your settings, sites or audio.

Sharing and third parties

We do not sell or share your data. There are no analytics, no advertising, no
trackers and no third-party scripts in the extension.

There are exactly three moments anything reaches a JSKAPPS server: one request the
extension makes itself, and two pages your browser opens at its request. None of them
carries audio, settings or browsing history:

• The welcome page. When you first install the extension, it opens our
  documentation page once, at jskapps.com/apps/soundshape/docs?src=install. The
  src=install marker tells us the visit came from a new installation, so we can see
  how many people install and read the guide. It carries nothing about you, and it
  happens on a fresh install only — never on an update.
• The licence check. If you connect an account, the extension calls
  https://api.jskapps.com to ask which plan you are on. It sends your API key and a
  random device identifier, and nothing else. It runs when you connect, when you press
  Check again, when the browser starts, and at most every few hours after that.
• The device identifier is a random code the extension generates the first time you
  connect, stores in this browser only (never synced), and keeps until you uninstall. It
  is used to count how many devices your key is used on, to enforce licensing. It is not
  derived from anything about you or your computer — no name, email, address or hardware
  serial — and JSKAPPS stores only a scrambled (hashed) form of it. If you never connect
  an account, no identifier is created.
• On Firefox, Firefox asks your permission before your key — and with it the device
  identifier — is sent at all. If you decline, nothing is sent.
• The uninstall page. If you remove the extension, your browser opens a short
  feedback page. Its address carries the version you had, your plan name, and how long
  it was installed rounded into a broad bucket (0, 1, 7, 30 or 90 days). It carries no
  account identifier, no email, no key, no site names and no settings.

Security

Your settings never leave your device, so there is no transmission to intercept. Your
API key is stored in your browser's extension storage and sent only to
api.jskapps.com, over HTTPS. Once connected, Settings never shows the key again — only
its first 13 characters, the same prefix your JSKAPPS dashboard lists.

The extension's content security policy names api.jskapps.com as the only address it
is permitted to reach. You can read it yourself in the extension's manifest.json.

Your choices

• Export everything at any time from Settings, with no account required.
• Delete a site's profile individually from the saved-sites list.
• Disconnect your account from Settings; the key and the cached plan are removed, and
  the extension returns to Instant — the no-account tier — and keeps working.
• Uninstall to remove all locally stored data.

Changes to this policy

If this policy changes we will update the date at the top of this page and note the
change in the extension's release notes. Material changes will be described in plain
language, not buried.

Contact

Questions about privacy? Email info@jskapps.com.