Privacy Policy

WebHaste is a local-first tool. It doesn't have a server, an account system, or an analytics pipeline — this page explains exactly what little data exists and where it goes.

Last updated: July 25, 2026.

What WebHaste is

WebHaste is a Chrome extension for building static websites. Your project — pages, images, templates, and settings — lives as ordinary files in a folder on your own computer (or a synced folder like Dropbox or Google Drive, if that's where you chose to keep it), accessed through Chrome's File System Access API. The extension reads and writes those files directly; nothing about your site content passes through any server we operate, because we don't operate one.

What's stored, and where

Chrome's storage.local API (local to your browser profile on this device — not synced to a Google account) holds a small amount of extension state:

• A reference to the last project folder you opened, so you don't have to re-pick it every time.
• If you've filled in the Publish dialog: your Cloudflare Account ID, Project Name, and API Token, and/or your Netlify Site ID and Personal Access Token.

That's stored in plain storage.local, not an OS-level keychain — we recommend creating a Cloudflare API token scoped to Pages-edit-only (rather than a full-account token) for exactly this reason. See Publishing Your Site for details.

What gets sent over the network, and to whom

Nothing, until you click Publish. At that point, and only then, the composed pages, assets, and scripts from your own project — plus the credentials described above — are sent directly from your browser to whichever destination you configured in Site Settings:

• Cloudflare Pages (api.cloudflare.com), via Cloudflare's Direct Upload API, or
• Netlify (api.netlify.com), via Netlify's file-digest deploy API.

Those are the only two external hosts the extension is able to contact at all — it's declared that way in the extension's manifest. We (the WebHaste developer) are never in that path and never receive a copy of your site, your files, or your credentials. Once your data reaches Cloudflare or Netlify, their own privacy policies govern it. Choosing Render to Local Folder instead sends nothing anywhere — it just writes composed output to a folder on your own disk.

What we don't do

• No analytics, tracking scripts, or telemetry built into the extension.
• No user accounts, sign-ins, or cookies used by the extension itself.
• No selling or sharing of your data with third parties — there's nothing of yours passing through us to sell or share.

Permissions the extension requests, and why

• storage — to remember your last-opened project folder and (if you use them) your deployment credentials, as described above.
• tabs — so clicking the toolbar icon reuses your existing editor tab instead of opening a new one every time.
• host_permissions for api.cloudflare.com and api.netlify.com — the only two hosts the extension can talk to, used solely for the Publish flow described above.

Websites you build with WebHaste

This policy covers the WebHaste browser extension. It doesn't cover the privacy practices of any website you build and publish with it — if you add your own analytics, embedded forms, or other third-party scripts to your site (see Blocks), disclosing that to your own site's visitors is your responsibility as its owner.

Children's privacy

WebHaste isn't directed at children under 13, and we don't knowingly collect data from them — consistent with the rest of this page, we don't knowingly collect data from anyone.

Changes to this policy

If this policy changes, we'll update this page and its "Last updated" date above.

Contact

Questions about this policy or your data: [email protected].