> For the complete documentation index, see [llms.txt](https://docs.racemap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.racemap.com/live-tracking/delete-a-tracking-map.md). # Delete a tracking map Permanently remove a tracking map, or archive it to take it offline while keeping the data. Deleting a tracking map for good is reserved for RACEMAP admins. Your event settings have no delete button, so you cannot remove a map yourself — ask us and we delete it for you. Contact the RACEMAP team at [racemap.com/#contact](https://racemap.com/#contact) or . Include the **event ID** from the browser URL so we find the right map. {% hint style="info" %} Deleting is permanent: the live map and its assets are removed. RACEMAP keeps event history snapshots, so support can still recover a map deleted by mistake. Before you ask, check whether [archiving](#archive-instead-of-deleting) is what you need. {% endhint %} ### Check whether archiving is what you need Most requests to delete a map are really about one of these: * Take a finished event offline, * take the map out of our public event lists and the RACEMAP App, * keep the GPS data for a later replay or export. An archived event is taken offline: its Tracking Map and Leaderboard are not served. Requests to the `current`, `distance`, `times` and `ranks` Data API endpoints are rejected with HTTP 400, and the public participant list returns an empty list to anonymous callers ([Data API conditions](/api.md)). You can restore it at any time. ### Archive instead of deleting 1. Open your event in the RACEMAP admin. 2. Go to **Advanced settings → Danger Zone**. 3. Click the archive button (**Archiv**). It becomes **Dearchive** — click it again to restore the event. {% hint style="warning" %} Archiving is not deleting. The map stays in your account and can be restored at any time. Only a RACEMAP admin can remove it for good. {% endhint %} --- # 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.racemap.com/live-tracking/delete-a-tracking-map.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.