MailBridgeAPI · Terms of Service
MailBridgeAPI terms of service
Read from MailBridgeAPI's own page on 2026-11-10. 7 statements quoted word for word; anything the page does not say is shown as unstated, never guessed. APIs.io verifies none of it.
Effective date
Not stated on the page.
Permitted use
summary: Mailbox ownership or authorization
Connect only a mailbox you own or are authorized to use.Read from MailBridgeAPI's own page on 2026-11-10
Prohibited use
summary: Illegal or unauthorized purposes
Users must not use the service for any illegal or unauthorized purposes.Read from MailBridgeAPI's own page on 2026-11-10
summary: No reverse engineering
Users must not reverse engineer, decompile, or otherwise attempt to derive source code from the service.Read from MailBridgeAPI's own page on 2026-11-10
Caching
The page states nothing on this.
Redistribution
The page states nothing on this.
Attribution
Governing law
jurisdiction: jurisdiction where Mailbridgeapi is registered
The agreement shall be governed by the laws of the jurisdiction where Mailbridgeapi is registered.Read from MailBridgeAPI's own page on 2026-11-10
Liability cap
Mailbridgeapi is not liable for any direct, indirect, incidental, or consequential damages resulting from the use or inability to use the service.Read from MailBridgeAPI's own page on 2026-11-10
Termination notice
Change notice
Mailbridgeapi reserves the right to modify these terms at any time.Read from MailBridgeAPI's own page on 2026-11-10
Rate or usage limits referenced
The provider must allow compatible SMTP or IMAP access, and its limits still apply.Read from MailBridgeAPI's own page on 2026-11-10
Document
Download YAML · schema: API Commons Terms of Service 0.1.0 · transcribed by claude-haiku-5-5, checked verbatim against the fetched page