> For the complete documentation index, see [llms.txt](https://help.givechariot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.givechariot.com/onboarding/trust-and-safety/data-privacy.md). # Data Privacy Chariot is designed to limit the data it interacts with, uses, and stores, reducing exposure to sensitive information. ### Data Storage Chariot’s systems are built to store only what is necessary, and only for as long as needed. With DAFpay, for example. Chariot’s system stores items that a donor user submits to be shared with the receiving nonprofit and does not store sensitive details such as username, password, account balance & donation history. *** ### Transparency & Disclosure Chariot is committed to clear and transparent data practices.All users are prompted to review and accept the appropriate policies before interacting with the platform, including: * [Terms of Service](https://www.givechariot.com/legal-donors) \[DAFpay​ Donors] * [Terms of Service](https://www.givechariot.com/legal-nonprofit) \[Nonprofits On Chariot] * Terms of Service \[DAF Providers On Chariot] [\[Request\]](https://www.givechariot.com/contact) * [Privacy Policy](https://www.givechariot.com/privacy) Before getting on Chariot, you should review these documents in full. All users are prompted to review and accept the appropriate policies before interacting with the platform, including. {% hint style="info" %} More detailed internal procedural documents related to data handling are available upon request for potential partners performing diligence. {% endhint %} *** ### Data Flows Chariot’s technology is proprietary and sensitive — therefore, we limit public descriptions of the platform’s backend functionality. Request additional details at --- # 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://help.givechariot.com/onboarding/trust-and-safety/data-privacy.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.