CoreDash · Terms of Service
CoreDash terms of service
Read from CoreDash's own page on 2026-11-09. 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: Documents provided for Client use
All documents provided by Core/Dash are exclusively intended for use by the Client.Read from CoreDash's own page on 2026-11-09
Prohibited use
summary: No public disclosure or reproduction of information
The Client is not permitted to make information obtained from Core/Dash public or to reproduce it in any form whatsoever, unless such publication is permitted in writing by Core/Dash.Read from CoreDash's own page on 2026-11-09
Caching
The page states nothing on this.
Redistribution
stance: conditional
The Client is not permitted to make information obtained from Core/Dash public or to reproduce it in any form whatsoever, unless such publication is permitted in writing by Core/Dash.Read from CoreDash's own page on 2026-11-09
Attribution
Governing law
jurisdiction: Netherlands
Dutch law applies exclusively to every agreement between Core/Dash and the Client.Read from CoreDash's own page on 2026-11-09
Liability cap
is limited to the amount that is paid out under Core/Dash's professional / business liability insurance in the relevant caseRead from CoreDash's own page on 2026-11-09
Termination notice
period: 1 calendar month
For agreements with a duration of 1 month or less, the Client may prematurely terminate the agreement with due observance of a cancellation period of 1 calendar month.Read from CoreDash's own page on 2026-11-09
Change notice
These changes come into effect at the announced time of entry into force and after sending the changed terms and conditions, whether or not electronically, by Core/Dash to the Client.Read from CoreDash'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