Terms of Service

1. Service model

Inboxes.Run is a receive-only email service. It does not provide outbound email or act as a domain registrar. Temporary inboxes normally last 24 hours. REST API and receive-only IMAP are access methods for the same receive workflows.

2. API and IMAP

REST API and receive-only IMAP are access methods for Inboxes.Run rather than a separate domain product. API access may require an account and API key. Published or account-specific limits may apply to API and IMAP to protect reliability and prevent abuse.

3. Receive domains

A receive-domain purchase grants account-exclusive use of the specific root domains assigned to your account inside Inboxes.Run while those domains remain serviceable. It does not transfer registrar ownership or DNS control unless a separate written agreement explicitly says otherwise.

• Each purchased root is assigned only to your account while it remains active and serviceable in Inboxes.Run.
• No minimum lifetime, registrar-style expiry date, renewal, permanence or automatic replacement is promised unless separately stated in writing.
• Each purchased root may be used for up to the published active-inbox limit; current product configuration allows up to 100 active 24-hour inboxes per domain.
• If confirmed payment cannot be provisioned because of an Inboxes.Run technical failure at fulfillment time, contact support for activation or refund. Loss of a domain after successful assignment does not by itself create a replacement or refund entitlement except where required by law or separately agreed.
• Receive domains are for inbound email only. Outbound email and registrar ownership are not included.

4. Exact-recipient receive boundary

The ordinary service accepts mail only for active recipients created or provisioned in Inboxes.Run. Unknown, expired and legacy recipients are intended to be rejected before message content is accepted. The service is not a residual-mail or dead-domain catch-all product.

5. Accounts, API and limits

You are responsible for protecting mailbox passwords, account sessions and API keys. Published or account-specific limits may apply to active inboxes, inbox creation, incoming messages, API throughput and IMAP connections. We may enforce or change reasonable limits to protect reliability and prevent abuse.

6. Payments and refunds

The price and terms shown before checkout apply to the selected purchase. If payment is confirmed but purchased domains cannot be assigned because of our technical failure at fulfillment time, contact Support for fulfillment or a refund. Successfully assigned domains do not gain an automatic refund entitlement solely because a domain later stops working, except where required by law or separately agreed.

7. Availability and temporary data

Temporary email is not durable storage. Domains, routes and infrastructure can change. Unless a separate written agreement provides an SLA, the service is provided on a best-effort basis. Do not use a temporary inbox as the only recovery channel or permanent record for data you cannot afford to lose.

8. Suspension and termination

We may restrict or terminate access when reasonably necessary for security, abuse prevention, legal compliance, non-payment or material breach of these Terms or the AUP. We may remove or disable unhealthy supplier roots when reasonably necessary. Removal of a root does not transfer registrar ownership to the customer and does not create an automatic replacement, refund or renewal entitlement except where required by law or separately agreed in writing.

9. Responsibility and changes

You are responsible for using the service lawfully and for respecting third-party rights and service rules. To the extent permitted by law, Inboxes.Run is not liable for loss caused by expired temporary inboxes, unavailable supplier roots, messages that never arrive, third-party sender decisions or reliance on the service as permanent storage. We may update these Terms as the product evolves; the current version will be published here.

10. Contact

For service, payment or legal questions, use the Support link on inboxes.run.

These Terms describe the current product contract. A separate written B2B agreement may add service levels, data-processing terms or commercial conditions.