Privacy policy
Jumper Publisher runs in your own Cloudflare account. This page explains what that means for your data.
Summary
- Your Publisher, your website files and your visitors' traffic live in your Cloudflare account. Jumper MCP does not operate them and cannot read them.
- Jumper MCP runs only the one-time installer. It holds a temporary Cloudflare sign-in and your installation progress for up to one hour while it sets up your Publisher, then erases all of it. It keeps no record of your installation.
- Publisher has no analytics, no tracking, no advertising, and does not send usage data to Jumper MCP.
- Files you ask Publisher to publish become public websites. Your conversation does not.
Your Publisher
After installation, Publisher is a Cloudflare Worker in your account. You are its only owner. It stores the following in your account's Cloudflare storage (a Durable Object and a KV namespace created for it):
- Website files and history. The files your AI client sends to publish, earlier published versions (snapshots) for undo, and drafts that were never published.
- Operation records. Publish, restore and unpublish progress, with error messages from Cloudflare. Credentials and signed links are never written to these records.
- Your owner password, stored only as a salted PBKDF2 hash, plus sign-in sessions for your control panel.
- Your Cloudflare API token, encrypted with AES-GCM using a key kept in your Worker's secrets. Publisher uses it only to call the Cloudflare API on your account.
- AI client connections. For each AI client you approve: the name it reports, the address it returns to after sign-in, the approval time, the last time it was used, and its access tokens.
Publisher's own logging is turned off (Cloudflare Workers observability is disabled in its configuration). What Cloudflare records about your Worker is governed by your Cloudflare account settings and Cloudflare's policies.
Publisher contacts only:
- the Cloudflare API, to deploy, update and unpublish your websites;
- publisher.jumpermcp.dev, when you press Check for updates in your control panel, to download signed Publisher releases. This is a plain file download; Publisher sends no account, project or personal data with it;
- file download hosts that you, as the owner, have explicitly allowed. This list is empty by default.
The installer
The installer at publisher.jumpermcp.dev is operated by Jumper MCP. It runs once, when you install Publisher.
- You sign in to Cloudflare and approve a limited set of permissions (account settings read, Workers Scripts edit, Workers KV edit). The installer receives a temporary Cloudflare credential, stores it encrypted, and uses it to create your Publisher.
- The credential is erased when installation completes, when you restart, or after one hour at the latest.
- The installer sets one cookie,
__Host-installation, to recognise your installation session. It expires after one hour. - While the installation runs, the installer keeps its progress: the chosen Cloudflare account, your
workers.devsubdomain, and the names of the Publisher Worker and storage it creates. This lets you resume after an interruption. The list of account names you choose from is discarded as soon as you pick one. - One hour after you sign in to Cloudflare, the installer erases the entire installation record, including the credential and progress. Jumper MCP keeps no list of installations.
- The installer never sees your owner password, your Cloudflare API token, your website files, or your conversations.
AI clients
Publisher works with AI clients such as Claude and ChatGPT. When you connect one, it signs in to your Publisher, and you approve it on a page served by your Publisher. The AI client then sends Publisher the files and instructions needed to list, read, change and publish your projects.
What the AI client provider does with your conversations is governed by that provider's own privacy policy (for example, Anthropic for Claude and OpenAI for ChatGPT). Publisher receives only what the AI client sends in tool calls, and does not receive your conversation history.
Images, ZIPs and large files can be sent through one-time upload links that expire after 10 minutes. Download links for exporting a project expire after 5 minutes; anyone holding one can download the export until it expires.
You can see and revoke every connected AI client in your Publisher's control panel under AI connections.
Third parties
- Cloudflare hosts your Publisher, your websites and the installer, and processes the related requests, including visitor IP addresses, as an infrastructure provider. See Cloudflare's privacy policy.
- Your AI client's provider processes your conversations under its own policy.
Jumper MCP does not sell, rent or share personal data, and does not use it for advertising or for training AI models.
Retention and deletion
| Data | Kept |
|---|---|
| Published versions | The latest 20 successful publications per website |
| Unpublished drafts | Up to 24 hours |
| Upload links | Single use, 10 minutes |
| Export links | 5 minutes |
| Installer Cloudflare credential | Until installation finishes, at most 1 hour |
| Installer progress record | 1 hour, then erased completely |
| Installer session cookie | 1 hour |
| Everything else in your Publisher | Until you delete it |
You control deletion. In your control panel you can unpublish a website, delete a project and its history, revoke AI clients, and replace your Cloudflare API token. To remove Publisher completely, delete the Publisher Worker, its storage, its KV namespace and your website Workers in your Cloudflare dashboard, then revoke the API token. The uninstall guide lists each step.
What becomes public
Every file you publish is served on the public internet at your website's address, which is on your workers.dev subdomain and may contain your name if your Cloudflare subdomain does. Copies that visitors, search engines or caches have already made stay outside your control after you unpublish. Review what you share before you ask your AI client to publish it.
Contact
Questions or privacy concerns: [email protected].
If this policy changes, we update this page and the date at the top.