> For the complete documentation index, see [llms.txt](https://docs.dimo.org/explained/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dimo.org/explained/frequently-asked-questions.md). # Frequently asked questions ### **Privacy** **Q:** Does DIMO sell my data to my insurance company? **A:** DIMO has never sold any data and never will. ### Usefulness **Q:** Why should I connect other than for the rewards? **A:** Because your car is your biggest asset. DIMO helps you manage it. ### **Token** **Q:** How do I earn weekly rewards every Monday? **A:** Connect in DIMO Mobile and drive at least once per week. Earn the most with [the adapter](https://dimo.co/pages/dimo-lte) and build a streak for even more. You don't earn more for driving extra miles. **Q:** Are you selling my data when I sign up? Where do the rewards come from? **A:** No, rewards are not funded by selling your data. You decide who it's shared with. When DIMO was created, 450 million tokens were set aside for driver rewards. **Q:** So what's the business model? Why does the DIMO token matter? **A:** When you share your car with apps like DIMO Mobile, the developer pays a monthly fee. More apps = more demand for DIMO tokens. --- # 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.dimo.org/explained/frequently-asked-questions.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.