Stored locally
Drafts, templates, saved webhooks, and related builder state are primarily stored in your browser’s local storage.
Legal
Privacy Policy
This policy explains what Meowhook stores, what it sends to Discord, what stays in your browser, and what limited information may be processed when you use Discord-connected delivery or contact features.
Processed when needed
Discord account, guild, and channel information is processed only when you use login, channel delivery, or bot install flows.
What Meowhook may collect or process
The exact data involved depends on which features you use. A plain local draft session is not the same as using Discord login and bot delivery.
Information stored in your browser
- Draft tabs, message content, embeds, uploaded file references, and builder state.
- Saved webhooks, custom templates, backups, theme choice, and recent local workspace preferences.
- These items are generally stored on your device in browser-managed storage.
Information processed for Discord login and delivery
- Your Discord user ID, username, global name, avatar, and related OAuth session data.
- Servers you are allowed to manage and channels available for Discord app delivery.
- Bot-install status for selected servers so Meowhook can show whether interactive components are available.
Information you explicitly submit
- Webhook URLs and payload content when you choose to send through a webhook.
- Channel delivery payloads when you choose to send through the Discord app route.
- Feedback form submissions when you contact the site through its feedback flow.
How the information is used
Data is used to provide the features you ask for, not to build an unrelated profile about you.
Core product functions
- To restore your local drafts, templates, saved webhooks, and visual preferences.
- To validate webhook or Discord delivery setup and send messages you explicitly choose to send.
- To show the correct Discord account, manageable servers, available channels, and bot access state.
Support and maintenance
- To respond to feedback or troubleshoot product issues.
- To monitor reliability, prevent abuse, and understand basic site usage patterns.
Browser storage and server-side processing
Meowhook uses a mix of browser-local storage and limited server-side processing depending on the feature.
Local browser data
Drafts and related workspace data are designed to stay local to the browser profile you are using. If you clear local storage, switch browsers, or use a different device, those local items may not follow you.
Session cookies
Discord-authenticated features use secure session cookies so Meowhook can recognize your signed-in Discord session.
Server-side requests
When you use Discord-connected delivery, Meowhook may temporarily process Discord API responses needed to fetch guilds, channels, bot status, and send requests. Short-lived in-memory caches may be used to reduce repeated Discord API calls.
Your choices and controls
You can control a meaningful amount of what Meowhook stores or processes by how you use the app.
You can
- Disconnect your Discord account from the app interface.
- Clear or replace local drafts, saved webhooks, templates, and backups from your own browser.
- Choose not to use Discord-connected delivery if you only want local builder and webhook flows.
Things to keep in mind
- Webhook URLs are sensitive credentials. Treat them like secrets and avoid sharing them carelessly.
- If you submit content to Discord through Meowhook, that content is also subject to Discord’s own retention and policy rules.
Important note
If you need company-specific disclosures, regional privacy rights language, or formal compliance text for a particular jurisdiction, you should review and adapt this policy before relying on it in production.
Contact
If you have privacy questions about Meowhook or its Discord integration, use the public contact profile below.