Privacy Policy

Last updated: 4 June 2026

The short version. DWEEB runs entirely in your browser. Your message drafts, webhook URLs, saved messages, and any AI API keys live only in your browser's local storage — they are never uploaded to us. You don't need an account to use the editor. We use privacy-respecting analytics, and a few features (signing in with Discord, the AI assistant) talk to third parties only when you choose to use them. We do not sell your data.

This policy explains what DWEEB (the "Discord Webhook Embed Builder," "we," "us"), hosted at dweeb.faizo.net, does with information when you use the site. DWEEB is free and open source; the source code is available at github.com/FaizoKen/DWEEB.

1. Data stored only in your browser

DWEEB is a client-side application. The following are saved to your browser's localStorage / IndexedDB and are never transmitted to our servers:

The message you're currently editing (auto-saved draft).
Webhook URLs you enter and your list of recently used webhooks.
Messages you choose to save for later.
Attachments/images you add while building a message.
API keys for the optional AI assistant (bring-your-own-key).
Interface preferences (e.g. the last server you connected to).

This data stays on your device until you remove it. You can clear it at any time by clearing your browser's site data for dweeb.faizo.net, or by using the in-app controls (Reset, remove a saved webhook, etc.).

2. Share links

When you create a share link, the entire message is compressed into the URL's # hash fragment (for example dweeb.faizo.net/#s=…). By design, browsers never send the fragment to a web server, so the contents of a share link are not received or stored by us. However, anyone you give the link to can open and read that message, so treat share links accordingly.

3. Sending messages to Discord

When you click Send, Restore, or update a message, your browser talks directly to Discord's API. Your webhook URL and message content go to Discord, not through us. This is governed by Discord's Privacy Policy. A webhook URL is a credential — treat it like a password and only share it with people you trust.

4. Signing in with Discord (optional)

If you choose to sign in with Discord to load a server's roles, channels, and emojis, we use Discord's OAuth flow. From it we receive your Discord user ID, your username/display name, your avatar, an access token, and the list of servers you can manage. This information is stored in an encrypted, HttpOnly session cookie kept in your browser — we do not maintain a server-side account database. The access token is used only to confirm you belong to a server before returning its data, and that data is briefly cached on our proxy to reduce calls to Discord. Signing out clears the session. If you never sign in, none of this applies.

5. The AI assistant (optional)

The optional AI assistant is bring-your-own-key. When you use it, your prompt and your API key are sent through a same-origin proxy on our hosting to the AI provider you selected (e.g. OpenAI, Anthropic, Google, Groq, OpenRouter, or your own Ollama endpoint). The proxy forwards the request and streams the response back; it does not store your prompts or keys. Your use of a provider is subject to that provider's own privacy policy and terms.

6. Analytics

We use Google Analytics to understand how DWEEB is used (for example, how many people visit and which features are popular). Google Analytics may collect information such as the pages you view, your approximate location derived from your IP address, and your device and browser type, and may set cookies. This is governed by Google's Privacy Policy. You can opt out using the Google Analytics opt-out browser add-on, a browser "Do Not Track" / privacy setting, or a content blocker.

7. Hosting and server logs

The site is hosted on Cloudflare. Like most web infrastructure, our hosting and the Discord login proxy process technical data such as IP addresses to deliver the service, apply per-IP rate limiting, and protect against abuse. We don't use this to build user profiles.

8. Cookies

Session cookie — set only when you sign in with Discord (encrypted, HttpOnly), plus a short-lived OAuth state cookie for security. Cleared on sign-out.
Analytics cookies — set by Google Analytics, as described above.

We do not use advertising or cross-site tracking cookies.

9. Third-party services

DWEEB relies on these third parties, each with its own privacy policy:

Discord — webhooks, sign-in, and server data.
Google Analytics — usage analytics.
Cloudflare — hosting and content delivery.
Whichever AI provider you select, if you use the AI assistant.

10. Data retention

Because most data lives in your browser, you control its retention — it persists until you clear it. The Discord session cookie expires automatically and on sign-out. Server-side caches of guild data are short-lived. We do not keep a database of users or message content.

11. Children

DWEEB is not directed to children. You must meet Discord's minimum age requirement (at least 13, or older where your local law requires) to use Discord-related features.

12. Your rights

Depending on where you live (e.g. under the GDPR or CCPA), you may have rights to access, correct, or delete personal data. In practice, most of your data is local and already under your control: clear your browser's site data to erase it, and sign out to clear the session cookie. For anything held on our side, or to make a request, contact us using the details below.

13. Changes to this policy

We may update this policy from time to time. Material changes will be reflected by updating the "Last updated" date above. Continued use of DWEEB after a change means you accept the revised policy.

14. Contact

Questions about privacy? Email [email protected] or join the DWEEB support server.