> For the complete documentation index, see [llms.txt](https://docs.rtkdata.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rtkdata.com/commercial/contracts-and-legal.md).

# Contracts & Legal: Terms & Privacy

Legal references for RTKdata.com: Terms of Service, Privacy Policy, and Imprint, plus Kansi Solutions GmbH company details, VAT ID, and support contacts.

Official legal references (hosted on rtkdata.com):

* [Terms of Service](https://rtkdata.com/terms/)
* [Privacy Policy](https://rtkdata.com/privacy-policy/)
* [Imprint / Legal Notice](https://rtkdata.com/imprint/)

***

## Company

**Kansi Solutions GmbH** · Rotenbergerweg 24 · 66640 Namborn · Germany

HRB 107712 · VAT ID DE346326134 (see [Imprint](https://rtkdata.com/imprint/)).

Expertise you can trust: We provide expert support directly from Germany: the birthplace of the NTRIP protocol. We ensure your GNSS equipment receives the most reliable corrections, backed by the engineering standards of the region where network RTK was invented.

***

## Support & Contact

* Technical support: <support@rtkdata.com>
* Sales: [Contact](https://rtkdata.com/contact/)


---

# 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.rtkdata.com/commercial/contracts-and-legal.md?ask=<question>&goal=<user_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.
