JSKAPPSJSKAPPS
← JSK ClipKeep

JSK ClipKeep privacy policy

Last updated: 9 October 2026

Overview

ClipKeep saves what you copy so you can get it back later. Everything it saves is encrypted and stored in your own browser, on your own machine. It has no analytics, no trackers, and loads nothing from anyone else's servers. We cannot see your clips, and there is no server holding them for us to see.

Information we collect

We collect no personal information. ClipKeep has no accounts of its own, no telemetry and no usage reporting.

What ClipKeep stores locally, in your browser, is:

  • The text or image of each clip you copy, encrypted
  • The site each clip came from, its timestamp, and any tags you add
  • Your settings, including your never-capture list
  • If you connect a JSKAPPS account: your API key and the tier it resolved to
  • A random ID for this installation, made on your device

If you connect a JSKAPPS account, that account is governed by the JSKAPPS privacy policy. ClipKeep sends it two things, only to check which plan you hold: your API key, and a random ID created for this installation. The ID is not derived from your device, browser or identity; JSKAPPS stores only a hash of it and uses it to count how many installations a key runs on. On Firefox, nothing is sent until you allow it when you press Connect, and you can withdraw that in Add-ons → ClipKeep → Permissions and data. Nothing about your clips is ever sent.

How we use it

Only to show you your own clipboard history on your own device. It is not used for anything else, because it never reaches us.

Permissions and why we need them

  • storage — to save your clips and settings on this device.
  • clipboardRead — to read what you copy, so it can be saved to your history. Nothing is sent anywhere.
  • clipboardWrite — to put a clip back on your clipboard when you select it.
  • unlimitedStorage — so your history can grow without an arbitrary size cap.
  • alarms — to schedule clean-up of old clips and expiry of detected secrets.
  • activeTab — to paste into the page you are on, only when you ask it to.
  • scripting — to insert a clip into the page's text field at the moment you paste.
  • tabs — to record which site each clip came from, and to know when you are on a never-capture site.
  • offscreen (Chrome and Edge only) — to run a hidden page that watches for clipboard changes. It has no access to any website.
  • sidePanel (Chrome and Edge only) — to open ClipKeep in the browser side panel.
  • Access to all websites — a copy happens on a page, so the extension has to be present to notice it. It reads only what you copy, never the rest of the page.

Firefox does not use the offscreen or sidePanel permissions; it uses an event page and the native sidebar instead.

Data storage and retention

Clips live in your browser's local database, encrypted with AES-GCM-256. They stay until you delete them, until an automatic clean-up rule removes them, or until you uninstall the extension — which removes the database entirely.

Detected secrets are different: they are hidden behind a mask in the list and deleted automatically after a few minutes unless you pin them. The value itself is kept, encrypted, for that window, because a clipboard manager that could not give you back the key you copied would be useless — it is hidden from view and short-lived, not withheld from you.

Names, tags, folder labels and timestamps are stored readable rather than encrypted, because the database has to be able to search and sort them. Clip content and snippet content are always encrypted.

Sharing and third parties

We do not sell or share your data. There is no third party involved: no analytics provider, no crash reporter, no content delivery network, and no remote fonts or images.

Security

Every clip is encrypted with AES-GCM-256 before it is written to disk. This protects against someone reading the extension's database directly — copying your browser profile, inspecting the disk, or recovering deleted files.

Turning on the optional PIN adds a second layer: your data key is wrapped with a key derived from your PIN using PBKDF2-SHA256 at 310,000 iterations, and the vault is sealed while locked. That protects against someone with access to your unlocked computer.

Being honest about the limit: default encryption does not protect against malware already running as you, because the key has to be reachable for the extension to work. The PIN level is where a strong claim is defensible.

Your choices

  • Pause capture at any time from the panel title bar.
  • Add any site to the never-capture list, or remove any of the 36 shipped defaults.
  • Delete any clip, or set automatic clean-up rules.
  • Export everything as JSON, with no account, at any time.
  • Uninstall to remove the local database completely.

Install and uninstall pages

Two moments open a page on jskapps.com. Both are listed here in full, because they are the only times ClipKeep causes a request you did not ask for.

When you install it, a browser tab opens our guide at jskapps.com/apps/clipkeep/docs?src=install. It happens once, on a first install only — updating ClipKeep never reopens it. The only thing the address says is that you arrived from an install rather than from a search.

When you uninstall it, your browser opens a short feedback page. This happens after ClipKeep is already gone, and the address carries exactly three things:

  • v — the version you had. For example 0.2.0. So a problem can be tied to a release.
  • days — how long you had it, as a bucket. One of 0, 1, 7, 30 or 90. Whether people leave on day one or after months.
  • tier — one of three words. instant, free or paid. Whether a plan changed the answer.

days is never a date and never the real number — it is rounded down to one of those five values, and it is left out entirely if we do not know when you installed. There is no account id, no email, no key, no clip, no site you visited, and nothing that identifies you or your machine. You can see the exact code that builds it: core/lifecycle/uninstall-url.ts in the published source.

If you would rather send nothing at all, close the tab when it opens — or disconnect from the network before uninstalling. Nothing is sent from inside ClipKeep; the browser opens a normal web page, and closing it ends the matter.

Changes to this policy

If this policy changes we will update the date at the top and note what changed in the extension's release notes.

Contact

Questions about privacy? Email info@jskapps.com.