Service Policy

Last updated: Aug 29, 2025

1) Overview

TempMail+ lets you create disposable email aliases, receive messages in real time, and reply with quoted content and attachments. It’s designed for testing, sign-ups, and short-lived flows—not for sensitive or long-term communications.

2) Acceptable Use

  • Do not use for account recovery, financial transactions, or confidential data.
  • No phishing, spam, malware distribution, or illegal activity.
  • Respect rate limits and fair-use guidelines (see Limits below).

3) Message Handling & Retention

  • Messages are fetched from the configured IMAP server on demand. By default, TempMail+ does not intend to persist message bodies permanently; any transient processing or caching is limited to serving the UI.
  • Operators may enable logging for troubleshooting (headers, sizes, timing). Avoid sending sensitive data.
  • Aliases are disposable and may stop receiving messages at any time depending on server policy.

4) Reply Behavior

  • Replies are sent via SMTP using the alias as the visible From: address (when configured).
  • Quoting of the previous message is supported; HTML is sanitized in the UI for safety.
  • Delivery depends on the upstream SMTP/IMAP provider’s policies (SPF/DKIM/DMARC). Replies can still land in spam.

5) Limits

Attachment size (per file)≤ 2 MB
Supported domains≥ 1 Domain
Secure EmailGive password to your email for use later
Fair useReasonable traffic; abuse may be rate-limited or blocked

6) Spam & Abuse

  • The service may surface messages from the provider’s Spam folder for convenience. Use the “Not spam” action responsibly. Automatic moves can be throttled or disabled.
  • We may block aliases, IPs, or messages that indicate abuse.

7) Privacy

  • Message content is handled to display it to you and to enable replies. We do not sell or train models on your emails.
  • Operators can configure supported domains and server credentials via environment variables. Keep your credentials secure and scoped to test accounts.

8) Security

  • Use strong, provider-level authentication for IMAP/SMTP (TLS, app passwords where applicable).
  • UI sanitizes HTML before rendering. Attachments are served as downloads.

9) Availability & Warranty

  • Provided on a best-effort basis, without SLA or warranties.
  • Email delivery and classification are controlled by your mail provider, not TempMail+.

10) Contact

Questions or issues? Reach out to your operator/maintainer. If you run this yourself, document how users can contact you (e.g., a support email or issue tracker).