> For the complete documentation index, see [llms.txt](https://docs.cindereth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cindereth.com/site/profile-and-history.md). # Profile and History Your Profile shows everything you have done through Cinder: totals for tokens burned, tokens sold, and ETH recovered, charts of actions by type and ETH over time, and the full activity table with a chain link per row. ## It follows your wallet History is keyed to your wallet address, not your browser. Connect from any browser or device and the same history loads. Cinder records its own actions as you perform them; it deliberately does not scan your wallet to guess at history, because a transfer looks the same from any app, and guessing would fill your profile with activity that had nothing to do with Cinder. ## Integrity Rows are verified against the chain in the background: anything whose transaction was not sent by your wallet is removed. There is no way to upload or fabricate history. ## Export **CSV** downloads your full history for taxes or records. **Clear** empties the local cache only; history rebuilds from the record next connect. --- # 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.cindereth.com/site/profile-and-history.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.