> For the complete documentation index, see [llms.txt](https://docs.moasure.com/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.moasure.com/en/moasure-lx1/settings/account-management/enable-disable-analytics.md).

# Enable / Disable Analytics

This setting allows you to control whether anonymous analytics data is shared with Moasure.

Analytics helps improve overall app performance, identify issues, and support users more effectively. The data collected is anonymous and used only to improve stability and reliability across Moasure products.

Analytics is **enabled by default**, but you can turn it off at any time.

#### Location in the App

**Settings → Account & Device Management → Enable Analytics**

***

### How to Turn Analytics On or Off

1. Tap the **Settings** icon (bottom right of the app).
2. Tap **Account & Device Management**.
3. Toggle **Enable Analytics** on or off.

***

### What Happens if You Disable Analytics?

* The app continues to function normally.
* No measurement data, images, or project content are shared.
* Support may have less diagnostic information available if you contact us for help.


---

# 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.moasure.com/en/moasure-lx1/settings/account-management/enable-disable-analytics.md?ask=<question>&goal=<user_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.