HappyMail
Privacy Policy
Last updated: June 28, 2026
This Privacy Policy explains how HappyMail, a Discord-native disposable email service operated by LucussHK, handles information when you use the bot or receive or send email through a HappyMail address.
1. Information We Process
HappyMail may process and store:
- Discord user IDs, server IDs, channel IDs, thread IDs, and message IDs;
- alias names, alias owner IDs, status, notes, and block rules;
- email sender, recipient, subject, timestamps, size, and routing status;
- outbound sender, recipient, subject, status, error text, and body previews;
- plain-text or HTML-derived message previews, verification codes, and links;
- attachment names and counts, but not attachment file bytes;
- basic operational logs needed to run and debug the service.
2. How Information Is Used
We use information to:
- create, reserve, mute, delete, and route aliases;
- deliver email previews into Discord threads or channels;
- send outbound messages from registered aliases when outbound SMTP is configured;
- detect spam, apply block rules, and reduce abuse;
- show service statistics and channel status summaries;
- operate, secure, troubleshoot, and improve HappyMail.
3. Discord Delivery
Email content delivered to Discord is also handled by Discord. The visibility of those messages depends on the Discord server, channel, forum, thread, and role permissions configured by that server. HappyMail cannot control copies, screenshots, exports, notifications, or moderation actions performed inside Discord.
4. Operator Audit Mirror
HappyMail may copy all inbound messages, including registered and unregistered recipient mail, to an owner-only operator audit channel. This audit mirror is used for service administration, abuse review, spam investigation, and debugging. Users should assume the service operator can review email content received by HappyMail.
5. Email Content and Attachments
HappyMail is designed to avoid storing raw MIME messages and attachment bytes. The service may still store message previews, subjects, senders, recipients, extracted links, extracted verification codes, and attachment names so that emails are readable in Discord. For outbound mail, it may store the sender, recipient, subject, body preview, send status, and error text.
6. Retention
HappyMail keeps message records only as long as configured retention and storage rules allow. Older messages, unregistered mail, blocked mail, spam, muted mail, and other low-value records may be deleted sooner when storage pressure rises. Copies already posted to Discord may remain until deleted in Discord.
7. Sharing
We do not sell personal information. Information may be processed by the infrastructure required to run the service, including Discord for bot delivery, Cloudflare for DNS, HTTPS, and network protection, and the server hosting provider or local server infrastructure used to run HappyMail.
8. Security
HappyMail uses practical safeguards such as limited attachment handling, Discord permission controls, alias ownership checks, block rules, storage limits, and automatic cleanup. No internet service can be guaranteed perfectly secure.
9. Your Choices
You can use bot commands to list, mute, unmute, or delete aliases you own. You can ask a server manager to remove messages from Discord or apply block rules when needed. Avoid using HappyMail for anything that should remain private, permanent, or recoverable.
10. Children's Privacy
HappyMail is not intended for children or for use outside Discord's permitted age requirements.
11. Changes
This policy may be updated as HappyMail changes. The updated date above reflects the latest published version.
12. Contact
For privacy questions, contact the HappyMail operator through the Discord server where the bot is installed.