Bepro11 · Terms of Service
Bepro11 terms of service
Read from Bepro11's own page on 2026-11-09. 8 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: Limited right of use of app and services
Bepro grants users a revocable, non-exclusive and non-transferable right of use of the app and its services and contents, limited to the purposes described in these Terms of Use worldwideRead from Bepro11's own page on 2026-11-09
Prohibited use
summary: Obstructing other users or endangering app functionality
Usage of bepro11 in ways that obstruct the user experience of other users or that endanger the functionality of the app is prohibited.Read from Bepro11's own page on 2026-11-09
summary: Copying or distributing content without consent
Without prior written consent of Bepro, users are not allowed to copy, download, publish, distribute, copy or utilize information and content from bepro11 in any way or form other than allowed hereunder.Read from Bepro11's own page on 2026-11-09
summary: Granting third-party access to content
Users are not allowed to grant access to any content to any third party regardless of the methodRead from Bepro11's own page on 2026-11-09
Caching
The page states nothing on this.
Redistribution
stance: prohibited
Users are not allowed to grant access to any content to any third party regardless of the method, included without limitation by forwarding login data, sending pdf match reports, downloading and/or sharing content.Read from Bepro11's own page on 2026-11-09
Attribution
Governing law
jurisdiction: Germany
The laws of Germany apply with the exemption of its provisions concerning conflict of laws.Read from Bepro11's own page on 2026-11-09
Liability cap
In cases differing from the ones listed in paragraphs 1 and 2, liability of Bepro is excluded.Read from Bepro11's own page on 2026-11-09
Termination notice
Change notice
period: 30 calendar days
which Bepro supplied 30 calendar days before the suggested effective date of the changes in written form (email notification shall be deemed sufficient)Read from Bepro11's own page on 2026-11-09
Rate or usage limits referenced
Document
Download YAML · schema: API Commons Terms of Service 0.1.0 · transcribed by claude-haiku-5-5, checked verbatim against the fetched page