The Cirqle · Terms of Service
The Cirqle terms of service
Read from The Cirqle's own page on 2026-11-10. 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: Personal printing and extracts
You may print off one copy, and may download extracts, of any page(s) from our site for your personal useRead from The Cirqle's own page on 2026-11-10
Prohibited use
summary: No commercial use of site content
You must not use any part of the content on our site for commercial purposes without obtaining a license to do so from us or our licensors.Read from The Cirqle's own page on 2026-11-10
summary: No unauthorized access or attacks
You must not attempt to gain unauthorized access to our site, the server on which our site is stored or any server, computer or database connected to our site.Read from The Cirqle's own page on 2026-11-10
Caching
The page states nothing on this.
Redistribution
The page states nothing on this.
Attribution
required: true
Our status (and that of any identified contributors) as the authors of content on our site must always be acknowledged.Read from The Cirqle's own page on 2026-11-10
Governing law
jurisdiction: Netherlands
If you are a consumer, please note that these terms of use, its subject matter and its formation, are governed by Dutch Law.Read from The Cirqle's own page on 2026-11-10
Liability cap
The Cirqle’s total liability is capped at the total fees paid by the user in the preceding 3 months.Read from The Cirqle's own page on 2026-11-10
Termination notice
period: 90 days
Users may cancel their subscription by providing 90 days' written notice.Read from The Cirqle's own page on 2026-11-10
Change notice
We may revise these terms of use at any time by amending this page.Read from The Cirqle's own page on 2026-11-10
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