> For the complete documentation index, see [llms.txt](https://docs.reportandrun.com/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reportandrun.com/manual/faq/c150/c157/q505.md). # How do I recover or view my previous reports after changing or losing my phone/device? ## **Report and Run: Cloud** * If you were using the cloud version of Report and Run, [log into the cloud](https://app.reportandrun.com) to access your reports. ## **Report and Run: Offline** * Reports made using the offline version are stored only on the device on which they were created. If you switched phones, you won't be able to retrieve those reports remotely. * If you previously emailed a report to a contact, you might be able to retrieve a copy from the sent folder of your email. * If you have access to your old phone, you can [export the reports to JREP](#report-and-run-offline) and [import them](/manual/report-and-run/data/import-jrep.md) to your new phone. ## Related * [FAQ: How do I backup, transfer and restore my reports from an old device to a new one?](/manual/faq/c150/c157/q506.md) * [FAQ: How do I transfer my data from the offline version of the app to the cloud version?](/manual/faq/c150/c157/q507.md) * [FAQ: What are the differences between the cloud and offline versions of the app?](/manual/faq/c142/c143/q388.md) * [FAQ: How do I import/export JREP files?](/manual/faq/c150/c157/q504.md) --- # 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.reportandrun.com/manual/faq/c150/c157/q505.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.