Splitty · Terms of Service

Splitty terms of service

Read from Splitty'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

Last Updated: March 30, 2026

Permitted use

summary: Personal non-commercial use of the Service
You agree that your use of the Service is solely for your personal non-commercial use and purposes.
Read from Splitty's own page on 2026-11-10

Prohibited use

summary: Commercial exploitation of Services or Content
exploit the Services or Content for any commercial purposes;
Read from Splitty's own page on 2026-11-10
summary: Scraping or collecting user data by automated means
collect personal information about users of our Services, including by automated means;
Read from Splitty's own page on 2026-11-10
summary: Scraping or downloading Service Materials
scrape, download, display, transmit, post
Read from Splitty's own page on 2026-11-10

Caching

The page states nothing on this.

Redistribution

stance: prohibited
Any reproduction or redistribution of Service Materials not in accordance with these Terms is explicitly prohibited
Read from Splitty's own page on 2026-11-10

Attribution

Governing law

Liability cap

OUR MAXIMUM LIABILITY FOR ANY SUCH DAMAGES OF ANY KIND, SHALL NOT EXCEED US$100.
Read from Splitty's own page on 2026-11-10

Termination notice

You agree that Splitty does not need to provide you with notice before terminating or suspending your Account, but it may provide such notice in its sole discretion.
Read from Splitty's own page on 2026-11-10

Change notice

we will use commercially reasonable efforts to notify you by sending a notice to the primary email address specified in your Account, or by posting a prominent notice on the Platform, prior to any new terms taking effect.
Read from Splitty'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