What DesignEx sends, and who decides.

Cloudflare Web Analytics, and nothing else. No Google Analytics, no ad or conversion pixels, no session recording, no third-party embeds. Cloudflare also hosts the site, so it handles the request itself, including your IP address, the way any web host does.

Per page view: the path you asked for, the host of the site that linked you here, an approximate country, and coarse buckets for device, browser, and operating system. Counted in aggregate, with no per-visitor profile.

It sets no cookies and writes nothing into your browser. No local storage, no fingerprint, no identifier that follows you between sites or visits. That is why there is no cookie banner here. Any content blocker stops the script, and every page works with JavaScript off entirely.

Anonymous usage data is on by default during the research preview. The first-run screen says so and points at the switch, and so does the download area on the home page. Section 6.0 covers what changes later.

Counts, yes/no flags, numbers, and values chosen from a fixed list: which agent provider a run used, which model family, how long it took, whether it succeeded, how many tool calls it made. Plus your app and macOS versions, your CPU architecture, and two random identifiers, one made on first launch and one for the current session. Mixpanel stores it for us. It carries no name, email, or account, so we cannot connect it to you, which also means we cannot look up your records to show you or delete them.

Never your designs or prototypes, never your prompts or the model’s replies, never project or thread names, never file names or paths, never your provider account, and never the exact model you picked, only a family name such as “opus” or “gpt”. That is structural, not a promise: every value has to be a number, a yes/no, or one word from a closed list, so there is nowhere for your text to go.

Open Settings at the bottom of the sidebar, choose Privacy, and switch off Share anonymous usage data. It applies immediately, it is remembered, and an update will not turn it back on. One switch, not two: it governs crash reports as well.

Crash reporting answers to the same Share anonymous usage data switch. If it is already off when the app launches, the crash reporter never starts, so nothing is captured in the first place. Sentry receives the reports that do get sent.

The error type, the stack frames, a shortened message, and the same version and identifier facts as section 2.0. Before anything leaves your Mac, file paths are replaced and your computer’s name is cleared. No screenshots, no view hierarchy, no record of what you were doing beforehand.

Whatever the switch says, DesignEx also writes every error to a plain-text log in its own folder on your Mac. That copy is unedited and never uploaded. One edge worth stating: if you switch reporting off mid-session and the app then crashes at the system level, that single report may still upload at the next launch. It cannot happen again once the app has started with the switch off.

This is the one place DesignEx transmits something you wrote: the message you type, plus your email address if you choose to fill it in. Pressing Send is itself the consent, so it is delivered even when Share anonymous usage data is off. Nothing is sent while you type, and nothing is sent if you cancel.

In the menu bar under Help → Send Feedback…, and in the command palette. It exists only in released builds. Treat the box as an email to us, because that is what it is. If you would not want us to read something, do not paste it in.

Feedback is the one thing we could find again, because you wrote it. There is no deletion route yet, so until this page says otherwise, treat what you send as kept.

DesignEx updates itself with Sparkle, the standard open-source updater for Mac apps. A check fetches one small feed file and compares its build number with yours. No usage data rides along, and Sparkle’s optional system profile, which would append your Mac model and language to the request, is switched off. Checks run about once an hour while the app is open, plus whenever you choose Check for Updates… yourself.

Not from here. Download sends you to a public release at github.com/codywhunt/designex-updates, and GitHub delivers the file, so that request falls under GitHub’s privacy practices rather than ours. Update checks fetch from the same place. Every release is signed and notarized by Apple and publishes a SHA-256 checksum.

A number. This site never sees the download and gets nothing back from GitHub, so a download cannot be tied to a visit. All we can read is how many times each file was requested in total, and that figure includes bots and retries.

DesignEx is a research preview: an early build, published to find out whether it is worth building further. On by default is a preview decision, and it rests on two things staying true, that the data is content-free and that the switch is easy to find. If either stopped being true, the default would have to change.

Before DesignEx becomes a general release, usage data becomes opt-in and we ask first. The app records that we have never asked you rather than reading silence as a yes, so a later prompt can reach installs that were never asked.

We update this page when what we collect changes, and the date at the top moves with it. To ask something, use Send Feedback in the app under Help. That is the only route in during the research preview.