Privacy

How ClipX protects your clipboard

Everything ClipX records stays on your machine. Your history is stored locally, and nothing in it is ever uploaded anywhere.

ClipX also guards against recording things it shouldn't: it can detect sensitive content such as passwords, credit card numbers, and API keys, and keep it out of your history. If you prefer to leave no trace at all, your history can live in memory only, so nothing is written to disk. And you can have old entries purged automatically, or everything cleared when your computer locks or restarts.

Optional plugins follow the same rule. Sharing moves clipboards between your machines directly, without any cloud service in the middle, and MCP gives AI assistants access to your history through a local-only server that never leaves your computer.

What we log: the app

The only thing ClipX itself sends over the network is an update check that asks our server whether there is a newer version. This request sends which build you are using (32 or 64-bit, stable or beta; we need this to check for the correct version). The request never sends your clipboard, your settings, or any record of what you do in the app. There is no feature tracking of any kind.

The update check is on by default but optional. You can decline it when you install ClipX, or turn it off at any time in the Settings dialog. With it off, the app makes no network requests at all (unless you have installed a plugin such as Sharing or MCP for this purpose).

What we log: the website

When a ClipX update or plugin package is requested, or when your copy of ClipX checks for updates, our server keeps one aggregate row so we can gauge rough volume and prioritize future work. It records:

• the build(s) involved (main app and/or plugins, architecture and stable/beta channels)
• where a package request came from, such as the website, app updater, plugin browser, or plugin updater
• your approximate country (no precise geolocation)
• a one-way hash of your IP address, never the address itself

We are not part of any analytics networks and do not use the site for cross-site tracking. We do not use or retain anything that ties a download or an update check back to a specific person or a specific installation.

If you deliberately send feedback on the website, we store the message and the name or email address if you choose to provide any. Your feedback is private, and we do not attach your IP address or other request metadata to it.

The feedback page uses Google reCAPTCHA to limit automated submissions. Its challenge loads from Google, so Google receives the normal connection and browser data needed to provide it. No other site page uses third-party scripts, fonts, or CDNs.

Why do we store an IP hash

The hash lets us estimate the number of unique users, and detect and block abuse. We never store the IP address itself and we fold it into a one-way hash together with a secret that changes every day, so the resulting value cannot be followed from one day to the next. This is the only hint we get of the size of our current userbase. As limiting as it is for us, we have chosen to limit the data we keep to this single, anonymous value because we value your privacy.

For even more privacy

Turn the update check off to stop automatic checks: untick it during install, or switch it off in Settings.

ClipX will then only connect if you later choose an online action such as browsing plugins or downloading an update.

How long we keep this information

Individual rows are retained for up to 12 months and then discarded. Download and update-check rows leave only aggregate counts; feedback is deleted.

Questions? Use the feedback form.