Edgewright
Privacy
Last updated 2026-10-01
Edgewright turns a plain-English description into a working Cloudflare Workers app. Here is everything it keeps and why.
If you connect your Cloudflare account
Cloudflare gives us an access token and a refresh token, limited to the permissions shown on Cloudflare's consent screen (Workers scripts, Workers KV and D1, read and write). We store them so we can deploy and update the apps you ask for, in your account. We use them for nothing else. Disconnect deletes your session immediately, and you can revoke Edgewright at any time from your Cloudflare dashboard.
What you build
We keep your app's description, the generated source files, the names of the KV/D1 resources it uses, and a short log of your edit requests, so later edits can pick up where you left off. The app itself runs in your Cloudflare account (or, for an unconnected preview, in ours).
Previews without an account
If you build without connecting, the preview runs on our Cloudflare account and is deleted automatically after about three hours unless you claim it into your own account. To limit abuse we count builds per network address using a one-way hash of your IP; the count expires within about an hour.
The AI model
Your description and your app's source are sent to DeepSeek's API to generate and edit the code. Don't put secrets or personal data in a description.
Phone number (optional)
If you give a phone number to be texted when a build finishes, we use it only to send that message. It is kept with that build's record and never used for marketing.
Analytics
edgewright.dev uses Google Analytics to count visits. The apps you build do not include it unless you ask for it.
What we don't do
We don't sell data, show ads, or read anything in your Cloudflare account beyond what an Edgewright build needs.