Acceptable Use Policy

Junkmail is designed for receiving signup messages, newsletters, verification codes, and test email without exposing your everyday inbox. Use it lawfully and without harming other people or the shared service.

Do not use Junkmail to

• break the law, facilitate fraud, harass someone, or obtain access to an account or data you are not authorized to use;
• receive or organize material whose possession or handling is unlawful;
• probe, exploit, disrupt, overload, or bypass security, quotas, rate limits, alias allocation, or abuse controls;
• automate signups or mailbox traffic at a volume that degrades the service for others;
• misrepresent a receiving alias as capable of sending, or attempt to use Junkmail infrastructure for outbound email;
• share, sell, or publish access credentials in a way that exposes a private mailbox or enables abusive use; or
• configure a webhook or push destination you are not authorized to use.

Enforcement

Junkmail may rate-limit or temporarily defer traffic, pause an alias, revoke credentials, suspend an account, or permanently ban an account based on the nature and persistence of the risk. Spam scoring labels received mail; it is not used to reject a claimed active alias merely because a message looks like spam. Oversize, blocked-sender, flood, inactive-domain, and inactive-account rules may reject or defer mail at SMTP time.

Rejected-mail handling is count-only. Junkmail does not retain rejected content for an operator to inspect. Operator actions are audited, and the operator console exposes mailbox metadata without a route to incoming message bodies. It also shows the operator’s own outgoing replies.

Report abuse

Email abuse@junksink.com with enough information to identify the incident. Put the information needed to investigate in the message text. Reports are accepted even when a full mailbox is unavailable, in which case only a bounded description and sender metadata are retained. When the mailbox is available, the operator can read the full message and attachments and reply. Stored incoming messages and replies are deleted after ninety days. Do not include passwords, recovery codes, personal access tokens, or webhook secrets.