> For the complete documentation index, see [llms.txt](https://docs.scribeware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scribeware.com/into-the-weeds/your-data-in-scribeware.md). # Your Data in ScribeWare The only things you really need to save in ScribeWare are your template or library narratives. The reason you need to save them is not for use in the current document you are using but for **FUTURE** use. Your templates and libraries are data that you likely want to recall over and over again and have it show up the same each time. In these cases, you need to save the template or narrative if you want it to show up as you have it modified. ### We believe that The Data You Collect Does not Belong to Us. WE DO NOT SELL YOUR DATA. There is currently a lot of pressure in the industry from large corporations who want access to your data. If you are seeking refuge from this type of corporate behavior, you are safe with us. ### Do I need to back up my data? You can, but there is no need. Data is backed up in our cloud services and about as safe as you can get. If that system goes down there are likely significant problems with the world computing system. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.scribeware.com/into-the-weeds/your-data-in-scribeware.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.