JSKAPPSJSKAPPS
← JSK Multi URL Opener

JSK Multi URL Opener privacy policy

Last updated: 2026-10-08

Overview

JSK Multi URL Opener opens and organizes lists of URLs. It is designed to keep your data on your own device: the URLs you paste, the lists and settings you save, and your open history are all stored locally in your browser. The extension has no analytics and no trackers. The only time it contacts a server is if you choose to sign in to a JSKAPPS account, and then only to check which plan you're on — sending your API key and a random install ID, nothing else.

Information we collect

  • The extension itself collects no personal information and sends none of your URLs, lists, or browsing data anywhere.
  • Stored locally on your device: the URLs in the editor, your saved lists (names, tags, folders, URLs), your settings and feature preferences, your theme, saved templates and tokens, environment profiles, schedules, and your recent-opens history.
  • If you sign in with an API key: the key is stored only in this browser. It is never synced to your other devices and is never shared with anyone; it is sent only to JSKAPPS to verify your plan.
  • A random install ID, only if you sign in: the first time you sign in, the extension generates a random identifier for this installation (a UUID) and sends it to JSKAPPS with each plan check, so JSKAPPS can count how many devices a key is used on (for support, and to spot a single key spread across many installs). It is random — not derived from your identity, email, hardware, IP address or anything you do — and identifies this installation, not you. It is stored only in this browser (never synced) and JSKAPPS stores only a one-way hash of it. Using the extension without signing in never creates or sends one.
  • If you sign in to a JSKAPPS account: JSKAPPS receives your account identity to manage licensing and your plan. This is handled by JSKAPPS under its own privacy policy. The extension does not send your URLs or list contents to JSKAPPS.

How we use it

  • To open and organize the links you provide, on your device.
  • To save and reload your lists and settings, on your device.
  • If signed in, to verify your plan (free or paid) so the right features are available, to recognise which account the local data belongs to, and (via the random install ID) to count the devices a key is used on.

Browser permissions and why we need them

  • storage — to save your lists, settings, templates, and history locally in your browser.
  • tabs — to open your URLs in tabs and to read the URLs of your open tabs for the "From tabs" feature.
  • tabGroups — to place opened tabs into named, colored Chrome tab groups (Chrome, Edge).
  • sidePanel — to show the full workspace in the browser side panel (Chrome, Edge; Firefox and Opera use their sidebar instead).
  • activeTab and scripting — to read the links on the current page only when you click "From page", and only for that tab.
  • contextMenus — to add the optional "Open links in selection" item to the right-click menu.
  • Optional permissions, requested only when you use the feature:
  • bookmarks — only when you export a list to a bookmark folder.
  • alarms — only when you create a timed or scheduled open. (On Firefox it is granted at install, because Firefox doesn't allow it to be optional; it is still used only for schedules.)
  • clipboardRead — only when you click the "Paste" button.
  • Access to the JSKAPPS API host — only when you sign in, to check your plan.

The extension requests no access to the websites you browse (no <all_urls> host permission) and runs no content scripts on the pages you visit.

Data storage and retention

  • Your URLs, lists, settings, templates, environments, schedules, and history are stored locally using the browser's extension storage.
  • If you enable cross-device sync, your lists are stored using your browser's built-in account sync (for example, Chrome Sync) so they travel between your own devices. This is your browser account's storage, not our servers. Your API key is never included in sync.
  • Switching accounts erases local data — after asking. Your data belongs to the JSKAPPS account you signed in with. Replacing or rotating a credential for the same account changes nothing. If a key from a different account is connected, the extension asks first; if you continue, locally stored lists, history, templates, environments and schedules are erased (your settings and the install ID stay) so one person's data is never exposed to another on a shared browser.
  • The random install ID stays the same for the life of the installation — including through an account switch, since it identifies the installation, not the person — and is deleted when you uninstall. A reinstall creates a new one.
  • Local data is otherwise kept until you delete it or uninstall the extension. Uninstalling removes the extension's local data.
  • Account and licensing data, if you sign in, is retained by JSKAPPS per its policy.

Installing and removing the extension

Two moments involve opening a JSKAPPS web page. Both are listed here in full.

When you install it, we open our user guide once, so you know how to use what you just added. It runs on first install only — updates never reopen it. Nothing about you is sent.

When you remove it, your browser opens a short, optional survey asking why. This is the only way we learn what went wrong, and answering is entirely voluntary — you can close the tab and nothing is recorded. The web address of that page carries exactly four coarse values, and nothing else:

  • the product you removed;
  • the extension version you were on;
  • roughly how long you had it installed, rounded to a broad bucket (same day, 1 day, 1 week, 1 month, 3+ months) — never an exact date;
  • which plan you were on, as a single word: instant, free or paid.

It carries no account identifier, no install ID, no email, no API key, and nothing you ever opened, typed or saved. The plan word is included so we can tell whether paying customers are leaving for different reasons than free users; it is deliberately coarse and cannot identify you.

If you choose to answer, we store your selected reason and anything you type. The comment box and the "email me back" field are both optional — leave them blank and we have no way to contact you or identify you. The survey page itself sets no cookies and runs no analytics.

Sharing and third parties

We do not sell or share your data. The extension integrates no advertising or analytics SDKs. The only third party involved is JSKAPPS, and only if you choose to sign in (for licensing/plan verification) or choose to answer the uninstall survey described above.

Security

  • Your content never leaves your device. The only data sent anywhere is the plan check described above (your API key and the random install ID), and only if you sign in.
  • Requests are made over HTTPS using your own credential; no shared or third-party API keys are embedded in the extension.
  • Your API key is stored in the browser's local extension storage, is excluded from sync, and can be removed at any time.
  • Dangerous link schemes (such as javascript: and data:) are blocked from being opened.

Your choices

  • Delete individual saved lists, clear your history, or turn off sync at any time.
  • Disconnect your account (which removes your API key) in Settings → JSKAPPS account.
  • Export or reset everything in Settings → Data.
  • Switch off any feature you don't want in Settings → Features.
  • Use the extension entirely offline in Instant mode without an account.
  • Uninstall the extension to remove its local data.

Changes to this policy

If this policy changes, we will update the "Last updated" date above and, where appropriate, note the change in the extension or on the product page.

Contact

Questions about privacy? Email info@jskapps.com.