> For the complete documentation index, see [llms.txt](https://docs.tosdr.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tosdr.org/site-policy/tosdr-terms/tos-dr-sponsorship-independence-disclosure.md).
# ToS;DR Sponsorship Independence Disclosure
ToS;DR is a not-for-profit organization that primarily relies on the contributions of volunteers, as well as donations, sponsorships, and similar support to sustain our operations. These financial contributions help us continue our work, but they do not influence our ratings or assessment criteria in any way.
Sponsorship does not imply endorsement, nor should our list of sponsors be considered a guarantee that their services align with all aspects of digital rights, such as privacy, data portability, or freedom from network lock-in. While we do not partner with companies we believe to be fundamentally harmful to user rights, sponsorship should not be seen as a certification of their policies or practices.
Our commitment remains to providing independent and unbiased evaluations of online services.
For transparency, we list all of our past and current sponsors, starting in mid-2024.
#### Current Sponsorships:
* Fastly
* Betterstack
* Atlassian
* Startmail
* GitBook
#### Past Sponsorships:
* JetBrains
* DuckDuckGo
* Google Entrepreneurship
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.tosdr.org/site-policy/tosdr-terms/tos-dr-sponsorship-independence-disclosure.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.