Privacy Policy

Last updated October 10, 2026

In short. WorkBox works on your computer and has no server of its own. It does not collect, sell or share your personal data, and nothing you save is sent to the developer. There is no account, no analytics, no advertising and no tracking. The few network requests it makes are listed in section 3.

1. What stays on your device

Everything you create or save with WorkBox is stored locally in your browser, using the extension's own storage (chrome.storage). This includes:

None of this is sent to the developer or to any server. If you uninstall the extension, this data is removed with it. The export feature only creates a file or link on your own device when you ask for it. Backups leave out clipboard items marked Private or Password; notes and tasks are exported as they are. A backup file or link is not encrypted, even if you have set a password: it contains your texts in plain text, so keep it somewhere safe.

Who is in control. The developer never receives, sees or has access to this data, and cannot read, recover or delete it for you. It stays under your control, in your own browser profile. This is also why the developer does not collect or process your personal data in the usual sense.

How the clipboard history is built. While your browser is running, WorkBox reads the system clipboard in the background every few seconds, and also records what you copy or cut on web pages. This means text and images copied in other applications are added to the history too, as long as the browser is open. Items detected as passwords, API keys, email addresses or phone numbers are marked Private and hidden on screen. Deleting an item removes it from the list for good. You can switch this off at any time (Settings > Privacy > "Save what I copy"), and list websites where nothing you copy is ever saved ("Private sites").

Encrypting the clipboard. When you set a password, your texts are encrypted before they are written: the text of each item, the preview kept for very long ones, and the compressed body of those long texts. WorkBox uses a single random key for all of it; your password only protects that key, which is why changing your password never rewrites your texts.

That key is held in memory for the duration of the browser session and is never written to disk. Three consequences are worth knowing. One unlock covers a whole browser session, not every time the popup opens. While the vault is locked — between starting the browser and that first unlock — texts you copy wait in memory only; they are never stored in the clear, and they are lost if you close the browser before unlocking. The recovery code starts with WP and is shown once; it is never saved in your clipboard history, even if you copy it. And if you lose both your password and the recovery code shown when you set it, the encrypted texts cannot be read again, by anyone, including you.

This covers text only. Images, notes, tasks, the last passwords you generated, and the details attached to each item (its type, its date, its size) are still stored as plain data in your browser profile. The password lock on its own does not change that.

2. What WorkBox never does

3. The only network requests

WorkBox contacts the internet only in the situations below. None of these requests goes to the developer.

WorkBox only keeps dates locally (when you last exported a backup, when you last saw a reminder, when it last checked for an update) to decide when to remind you.

Links you open yourself (from the clipboard list, a scanned QR code, a note) are ordinary browser navigation: the browser loads the page as if you had typed the address, and those websites' own policies apply.

4. Why WorkBox asks for permissions

5. Your choices and control

6. Changes

If this policy changes, the new version ships with a new version of the extension, the date above is updated, and notable changes are listed in the changelog.

7. Contact

For any question about this policy, use the support contact shown on WorkBox's page in the extension store.