chobitmail
login

Terms of Service

This English text is a convenience translation. The Japanese version is the official text and prevails in case of any conflict.

Article 1 (Scope)

  1. These Terms set the conditions for using the email inbox service “chobitmail” (the “Service”) provided by nanabit Inc. (“we”, “us”, or “our”).
  2. By using the Service, you are deemed to have agreed to these Terms.
  3. Rules and limits posted on the Service or in our documentation (including the API reference) form part of these Terms. If they conflict with these Terms, these Terms prevail.

Article 2 (Definitions)

In these Terms:

  1. “Service” means the service that issues disposable email addresses and lets you retrieve messages via API or similar means so you can verify email flows in software tests such as E2E tests.
  2. “One-time address” means a disposable email address with an expiry (TTL) issued by the Service, and its corresponding inbox.
  3. “API key” means credentials we issue to authenticate API access to the Service.
  4. “Registered user” means a person who completed registration under Article 3.
  5. “Received data” means the body, headers, and extracted links/codes of messages received by a one-time address.

Article 3 (Registration)

  1. Registration requires authentication with a GitHub account.
  2. For registration we obtain only the GitHub numeric user ID and login name. We do not obtain the email address or other profile data stored on GitHub.
  3. We may refuse registration or revoke it after approval if any of the following apply:
    1. You were previously suspended under Article 11
    2. We determine you are an anti-social force (e.g. organized crime) or have dealings with such forces
    3. We otherwise determine registration is inappropriate

Article 4 (Service description)

  1. The Service is provided so registered users can verify email-related flows when testing systems they manage (E2E tests, QA, etc.).
  2. The Service is receive-only and does not send email.
  3. One-time addresses have a TTL. When it expires, the address and received data are deleted automatically and cannot be restored.
  4. Links, codes, and similar extractions are mechanical results; we do not guarantee accuracy or completeness.
  5. The Service is currently a free beta. During the beta we may change features and limits without notice.

Article 5 (API key management)

  1. Registered users manage API keys at their own risk.
  2. The plaintext key is shown only once at issue; we do not redisplay it later.
  3. You must not transfer, lend, share, or sell API keys to third parties, except configuring a key in CI you control for tests within your organization.
  4. Actions taken with an API key are deemed your actions. Except in cases of our willful misconduct or gross negligence, we are not liable for damage from key leakage or misuse.
  5. If you know or suspect a key leak, disable or delete the key from the dashboard promptly.

Article 6 (Limits)

  1. The Service has limits such as concurrent one-time addresses, creation rate, received messages, TTL, stored messages, and message size. Specific values are in the API reference and other documentation.
  2. We may change limits for stability and abuse prevention.
  3. Requests over limits return errors; mail over limits is discarded without notifying the sender.

Article 7 (Prohibited uses)

Registered users must not:

  1. Use the Service to bypass third-party authentication or identity checks (including bulk account creation, signup abuse, or providing disposable addresses for that purpose)
  2. Use addresses as destinations for systems you do not manage, without the operator’s permission
  3. Use addresses as real contact mailboxes or for non-testing purposes
  4. Use the Service to send, receive, or relay illegal content or content that infringes third-party rights
  5. Create addresses in bulk, mail-bomb, hold wait connections permanently, or otherwise overload the infrastructure
  6. Transfer, lend, share, or sell API keys, or let third parties use the Service (except Article 5(3))
  7. Resell the Service or provide a product embedding the Service to third parties without our prior written consent
  8. Circumvent limits, suspensions, or other technical controls (including via multiple GitHub accounts)
  9. Violate law or public order
  10. Engage in other conduct we deem inappropriate

Article 8 (Received data)

  1. Received data is deleted when the address expires or you delete it. We do not back up received data and will not restore it.
  2. We do not log message bodies. We may retain metadata (sender domain, recipient, API key id, timestamps, etc.) for a limited period for abuse investigation and enforcement of these Terms.
  3. Attachment bodies are not stored; only metadata such as name and size is provided.
  4. You are responsible for handling information in received data (including third-party personal data) in compliance with applicable law.
  5. Personal data handling is governed by ourPrivacy Policy.

Article 9 (Non-delivery and discard)

  1. Mail matching any of the following is discarded without notifying the sender. We are not responsible for such discards:
    1. Mail to nonexistent or expired one-time addresses
    2. Mail exceeding limits (message count, stored count, or size)
    3. Mail with executable attachments or other mail we discard for security reasons
  2. We do not guarantee delivery to the Service or how quickly messages become available. You acknowledge that our receiving domain may be restricted by third-party senders or blocklists.

Article 10 (Changes, suspension, termination)

  1. We may change, suspend, or terminate the Service without prior notice to registered users.
  2. We may suspend all or part of the Service if, among other cases:
    1. We perform maintenance or upgrades
    2. Provision is difficult due to disaster, outage, or cloud failures
    3. We otherwise determine suspension is necessary
  3. Except for our willful misconduct or gross negligence, we are not liable for damage from changes, suspension, or termination under this Article.

Article 11 (Suspension and deregistration)

  1. Without prior notice we may suspend use or cancel registration if:
    1. You breach any provision of these Terms
    2. You engage in (or we reasonably believe you may engage in) prohibited conduct under Article 7
    3. We need to investigate following a third-party abuse report
    4. We otherwise determine continued use is inappropriate
  2. Measures apply per GitHub account. Affected users lose API and dashboard access; received data is deleted when addresses expire.
  3. We are not liable for damage from suspension or deregistration.

Article 12 (Intellectual property)

IP rights in the Service belong to us or our licensors. Permission to use the Service under these Terms is not a license to those IP rights.

Article 13 (Disclaimer of warranties)

  1. We make no warranty, express or implied, that the Service fits any particular purpose, has expected features/accuracy/usefulness, remains available, or is free of defects.
  2. The Service is provided as a beta “as is” with no SLA or uptime commitment.

Article 14 (Limitation of liability)

  1. Except for our willful misconduct or gross negligence, we are not liable for damage arising from the Service.
  2. Even where liable, our liability is limited to ordinary direct damages actually incurred, excluding lost profits, lost business opportunity, data loss, and other indirect or special damages.
  3. Caps for paid plans, if introduced, will be set in those plan terms.
  4. This Article does not limit mandatory consumer protection or other mandatory law where applicable.

Article 15 (Your liability)

If you breach these Terms and cause damage to us or a third party, you must compensate that damage. If a third party claims against us due to your use of the Service, you must indemnify us (including reasonable attorneys’ fees).

Article 16 (Changes to these Terms)

  1. We may change these Terms under Article 548-4 of the Japanese Civil Code. Changes apply from the effective date we post on the Service.
  2. If we determine a change materially affects registered users, we will give reasonable advance notice on the Service or by other means.
  3. Continued use after a change constitutes agreement to the updated Terms.

Article 17 (No assignment)

You may not assign or pledge your status under these Terms or rights and obligations hereunder without our prior written consent.

Article 18 (Severability)

If any provision is held invalid or unenforceable, the remaining provisions remain in full force.

Article 19 (Governing law and venue)

  1. These Terms are governed by the laws of Japan.
  2. The Tokyo District Court has exclusive jurisdiction as court of first instance for disputes relating to the Service.

Contact and abuse reports

For questions about the Service or to report abuse (e.g. bypassing third-party authentication, illegal content transfer), contact:

Effective date: July 18, 2026