Privacy
Last updated 1 September 2026.
Short version: this site has no cookies and no analytics, and the Wove software makes exactly one network call you didn't ask for — a check for a newer release.
This website
- No cookies are set, by us or by anyone else.
- No analytics, no tag manager, no tracking pixels, no A/B tooling.
- No JavaScript runs on any page here — just static HTML and CSS.
- No fonts, scripts or images are loaded from third-party domains.
- There is no form and no email capture, so there is nothing for us to store.
The site is served from Cloudflare’s edge, which keeps short-lived operational logs (IP address, request path, user agent) the way any web server does. We don't build profiles from them and we have no separate copy.
The update check
A running Wove installation asks updates.usewove.com/latest.json once a day
whether a newer release exists. That endpoint is a small Cloudflare Worker that proxies the
public GitHub releases API and returns three fields:
version— the latest tag, without thevurl— the GitHub release pagenotes— the release notes, truncated
The request carries no query parameters, no installation identifier, no site URL, no version of yours, no content and no usage statistics. The response is the same bytes for everyone and is cached at the edge for five minutes. Nothing about the caller is recorded beyond Cloudflare's ordinary edge logs.
It is not required. Set WOVE_UPDATE_CHECK=0 in the environment and Wove never
makes the call; you'll just need to watch
the releases page yourself.
Your own installation
Wove is self-hosted and Apache-2.0. Your content, your media, your users and your audit log live in your SQLite file and your storage bucket. We never see them. If you configure an AI provider you bring your own key, and those calls go directly from your server to that provider under their terms — not through us.
Contact
Questions or corrections: open an issue on GitHub. If this page ever stops being accurate, that's a bug — please report it.