Terms and disclaimer

Turp Terms and Disclaimer

Effective date: August 5, 2026

Turp is free, downloadable open-source client software—not a hosted AI, cloud, account, or support service. The Apache License 2.0 governs copying, modification, and distribution of Turp’s licensed source code and is the primary software warranty and liability document. These short terms explain use of the official build. Mandatory rights that cannot lawfully be waived remain unaffected.

1. Third-party services

Turp connects the device to AI providers, local servers, websites, storage providers, and other endpoints selected and authorized by the user. Those services, including GitHub, are independent third parties with their own terms, privacy practices, availability, restrictions, and prices. The Turp maintainer does not operate them, act for them, or receive their charges.

Users are responsible for choosing providers and models, protecting credentials, having authority to submit content, reviewing provider settings and terms, and paying provider, network, storage, tax, or subscription charges. Provider capability, pricing, and availability metadata shown by Turp may change or be incomplete.

2. AI output and local execution

AI-generated text, code, files, searches, sources, calculations, images, and tool requests may be wrong, incomplete, unsafe, outdated, biased, or rights-infringing. Turp does not create or verify a selected provider’s output. Review important output independently; it is not professional legal, medical, financial, or security advice.

Code, commands, packages, generated interfaces, and tools executed locally can modify or delete files, use network access, consume device or provider resources, expose supplied information, or produce unexpected results. Permission prompts, workspaces, Android isolation, and other controls reduce some risks but are not a guaranteed sandbox. Inspect commands and keep independent copies of important data.

3. Data and backups

Users choose what they send, where they send it, and where backups are stored. Backup, export, restore, encryption, provider access, and future compatibility are not guaranteed. A passwordless Turp archive is not encrypted by Turp. Keep the archive password and an independently tested backup. Disconnecting a provider may not delete data already held by that provider.

4. GitHub and support

GitHub operates the repository, Issues, pull requests, accounts, and hosting under GitHub’s own terms. A GitHub issue or other public project post is not a private support ticket, formal legal notice, or privacy-request channel. The maintainer makes no commitment to monitor, acknowledge, answer, investigate, preserve, fix, or remove a post.

No uptime, response time, maintenance, update, security-fix date, continued distribution, feature compatibility, data recovery, or other support commitment is made. The maintainer may change or stop distributing the official build at any time, subject to obligations that applicable law does not allow to be excluded.

5. No warranty and limitation of liability

As stated in Sections 7 and 8 of the Apache License 2.0, and to the maximum extent permitted by applicable law, Turp is provided “AS IS”, without warranties or conditions of any kind, and no contributor is liable under any legal theory for damages arising from use of the software unless applicable law requires otherwise or a contributor separately agrees in writing.

Without expanding that licence, this includes risks involving inability to use Turp, data or credential loss, provider conduct or charges, AI output, local execution, backups, third-party content, GitHub, and modified builds. Nothing in these terms excludes or limits fraud, wilful misconduct, death or personal injury caused by negligence, or any consumer right or other liability that applicable law does not permit to be excluded or limited.

6. Law and changes

The laws of Türkiye apply to these terms, without removing any mandatory consumer protection or mandatory court right that applies in another jurisdiction. If a provision is unenforceable, it is limited only as much as necessary and the remainder continues. The effective date and public repository history identify changes.