Privacy
Clear about what’s here.
Honest about what’s next.
This website and the Mac app are different things. Here’s how the site and the current public beta handle data.
01 · Here, today
The website
Aggregate website measurement
We count page views, download and release-note clicks, Get Wield navigation and deliberate demo interactions to improve this website. There is no automatic consent banner: this measurement uses no website visitor identifier, analytics cookies, fingerprinting, session recording, individual browsing history or link to the Mac app’s installation identity.
Your browser sends a bounded event name, known page path and categories such as button placement or release build to this website’s own server. The server sends anonymous counts to PostHog in the United States with a new independent identifier for each count and a date rounded to the day. It does not forward your IP address, browser headers, referrer, query strings, typed content or any visitor/session identifier. A broad US/outside-US/unknown category may be derived from the hosting provider’s country header; collection is otherwise the same everywhere.
You can turn off measurement through Analytics settings in the footer. We remember only this preference in local storage, respect existing opt-outs and browser Global Privacy Control or Do Not Track signals, and remove the previous analytics SDK’s stored identity. Previously accepted counts remain; a request already accepted may finish. PostHog’s current free-plan retention is one year. Counts are not unique visitors, sessions, linked conversion funnels or confirmed installations.
Performance services
Vercel Web Analytics and Speed Insights are no longer mounted on this website. Vercel continues to host the site and may process technical request information as described below.
No forms or accounts
There are no forms, accounts, mailing lists, or payment flows on this site.
Previews stay in the page
The command and Studio interfaces are illustrations running in your browser. They don’t control your Mac. Settings and trigger edits are held in the current page, reset on reload, and are not submitted by the site.
Fonts are self-hosted
The fonts are served by this website. Your browser does not need to request them from Google Fonts.
Hosting and request logs
This website is hosted on Vercel. Vercel may process request information—such as an IP address, browser details, requested URLs, and timestamps—as part of hosting, security, and infrastructure logs.
Those hosting logs are separate from Web Analytics and Speed Insights measurements. Their handling and retention depend on Vercel’s service practices.
02 · Public beta
The Mac app
Wield’s public beta is local-first. App settings and command configuration are stored on your Mac. Local-first does not mean the app never makes network requests.
Keyboard and window permissions
First-run setup asks for Input Monitoring to recognize activation and command input, and Accessibility for features such as controlling other apps’ windows. You can manage these permissions in System Settings → Privacy & Security.
Optional clipboard history
Clipboard recording is opt-in. When enabled, clipboard history is stored locally and encrypted using a key held in macOS Keychain. Clipboard contents can include sensitive information; enable recording only if you want that history saved.
Updates and exchange rates
Wield makes network requests for signed Sparkle automatic-update checks and European Central Bank exchange-rate snapshots used for currency conversion. Automatic update installation is optional. Apps or websites you open through commands may make their own requests under their own privacy policies.
Optional feedback
In feedback-enabled builds, a report is sent only when you choose Send feedback. It contains your description and category, one optional image you explicitly paste, drop or attach, and basic app information only if its checkbox is enabled: app version, build number, macOS version and running architecture. No account is required. Wield does not silently capture your screen or attach command history, keystrokes, clipboard history or file paths.
Reports travel over HTTPS to Wield’s private server inbox. Wield’s operator can read submitted reports and images; there is no public report or attachment link. Reports and images expire 30 days after acceptance, with deletion normally completed within one additional hour. This is application-level retention, not guaranteed erasure from host snapshots or separate network/system logs.
Unsent drafts stay in memory until sent, discarded or Wield quits; there is no saved outbox or automatic background retry. Explicitly copying a report or exporting an image creates a separate copy that you control.
Optional Mac app analytics
Usage analytics is controlled in setup and Studio → Privacy. Build 111 initially defaulted it off; newer releases can enable an absent preference by default while preserving stored opt-outs. An enabled production app sends lifecycle, setup, permission/readiness and category/outcome events to PostHog in the United States under a persistent random installation UUID. No name, email, hardware ID, app names, file paths, clipboard contents or typed calculations are included. This preference is independent of your website choice. Development and update-testing builds do not send production analytics.
Opting out stops capture and new delivery; already-started requests can finish and previously queued events may send after re-enabling. It does not delete server-side data. Studio Privacy can copy the analytics ID for a deletion request through Feedback. Newer releases may change the initial default; the setting stored in your app is preserved.
Public downloads
The installer and release notes are hosted on GitHub, separately from this website. Downloading them sends a request to GitHub and its download infrastructure, which may process request information under their service practices.
This describes the current beta’s known behavior, not an absolute guarantee about all keyboard handling, diagnostics, or network activity. Beta behavior and data handling may change with later releases.
03 · Keeping this current
Release updates
This information should be read alongside the notes for the build you install. The download page links to the current public beta, its release notes, installation guidance, and compatibility limitations.
Current release status