> For the complete documentation index, see [llms.txt](https://docs.geodin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geodin.com/administration/data-privacy-and-ownership.md). # Data Privacy and Ownership ## Data Privacy & Ownership GeoDin does not access customer data; data ownership and privacy are core principles. The customer controls where data is stored (local, on-premises server, or cloud) and who has access. Data put into GeoDin is not visible to the parent company or to other clients; the platform operates independently. GeoDin does not anonymize or sell customer data. NDA arrangements are available for clients who need to share sensitive project data during configuration or API development; standard NDA templates are provided, or clients can use their own. Customers can run GeoDin in a locked-down corporate environment with no internet access - runtime telemetry or file transfer from GeoDin staff into the customer network is blocked in such setups. --- # 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.geodin.com/administration/data-privacy-and-ownership.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.