last updated july 2026
maigo is an independent, solo-developer project. these terms are short and plain on purpose: read them, and email [email protected] with anything unclear.
maigo provides disposable email domains and inboxes for software testing and qa. use it for testing purposes, not for receiving real personal or production correspondence.
i aim for 99.9% uptime and treat paying customers’ issues seriously. that said, this is a one-person operation: there is no formal sla, and the service is provided "as is," without warranties of any kind, express or implied.
to the fullest extent permitted by law, maigo and its operator are not liable for any indirect, incidental, or consequential damages arising from use of, or inability to use, the service, including lost data, lost revenue, or missed test cycles. use at your own risk, and don’t route anything mission-critical through it without your own backups.
plans are priced for real but reasonable test traffic. accounts that abuse shared infrastructure (spam relay, bulk unrelated mail, abusive automation) may be rate-limited or suspended without notice.
one account (one org) gets 2,500 api requests/day on its main key, plus another 2,500/day on a separate extended key: 5,000 total for the account. creating a domain and reading an email each cost one request, so that’s roughly 2,500 emails/day within fair use. this is a per-key usage cap. separately, each individual user within an org is also rate-limited (requests per second), a different, independent control from the per-key daily cap. the unlimited plan raises the per-key caps to 10x (~50,000 requests/day).
plans are billed monthly and can be cancelled anytime, with no lock-in contracts. no refunds for partial months, but no hard feelings either; just email to cancel.
these terms may change as the product evolves. meaningful changes will be posted here with an updated date, not slipped in as surprise clauses.