Intely · Terms of Service
Intely terms of service
Read from Intely'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: Customer use of Services via authorized end-users
Each Customer end-user of the Services must (a) be a current employee or contractor of Customer using the Services solely only on Customer’s behalfRead from Intely's own page on 2026-11-09
Prohibited use
summary: Reverse engineering and derivative works
reverse engineer, decompile, disassemble or otherwise attempt to discover the source code, object code or underlying structureRead from Intely's own page on 2026-11-09
summary: Timesharing or service bureau use
use the Services or any Software for timesharing or service bureau purposes or otherwise for the benefit of a thirdRead from Intely's own page on 2026-11-09
Caching
The page states nothing on this.
Redistribution
The page states nothing on this.
Attribution
Governing law
jurisdiction: Delaware, USA
This Agreement shall be governed by and construed in accordance with the laws of the State of Delaware without regard to conflicts of law principles.Read from Intely's own page on 2026-11-09
Liability cap
EXCEED THE FEES PAID BY CUSTOMER FOR THE SERVICES UNDER THIS AGREEMENT IN THE 12 MONTHS PRIOR TO THE ACT THAT GAVE RISE TO THE LIABILITYRead from Intely's own page on 2026-11-09
Termination notice
period: ninety (90) calendar days
Either party hereto may terminate this Agreement at any time upon ninety (90) calendar days’ prior written notice for any reason or no reason.Read from Intely's own page on 2026-11-09
Change notice
period: thirty (30) days
Intely or its Authorized Reseller shall provide thirty (30) days’ notice of any change of Fees.Read from Intely'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