Data, privacy, and updates

This guide covers local data, cleanup, privacy settings, and app updates. Before backing up or deleting anything, check which data the operation affects. Before updating, save documents and deal with running tasks.

Locate local data

Open Settings → Data & Storage to view relevant locations and open them in the file manager.

You can track intent documents with Git. Saving only .noea.md files preserves the text, but not all chats, attachments, explanation records, or Agent authentication state. To preserve those too, check their actual locations in settings and include them in your backup plan.

Clear chat data

Data & Storage shows each project's chat-history and attachment storage. Clearing a project removes its local chats, history, proposal records, and attachments. It does not undo changes to implementation code.

Clearing requires confirmation and cannot be undone through the interface. Wait for running chats or tasks to finish, or stop them first.

Deleting a whole project is a separate action that also handles the project folder. See Open and manage projects.

Control error reports and usage analytics

Under Settings → General → Privacy, configure error reporting and usage analytics separately. Both are enabled by default in Release and Nightly builds and can be turned off independently. Development and test builds do not send these reports.

Error reporting uses Sentry to collect filtered exception information, such as app version, error category, and call stacks. Usage analytics uses PostHog to record predefined action names, sequences, and outcomes, associated with a randomly generated installation identifier.

These automatic reports do not contain document or chat text, code, project names, file paths, local logs, screenshots, or session replay. The switches and the question mark beside Privacy explain what is sent.

Turning a setting off stops that collection and clears its unsent queue, but does not retroactively delete reports already sent. Turning off usage analytics removes the random installation identifier; re-enabling it creates a new one. The service may see your IP address during transmission, and reports are stored in the United States.

Nightly also offers enhanced diagnostics, disabled by default. Review the additional data categories before enabling it on that channel.

Separate reporting from Agent work

The privacy switches control Noea's error reports and usage analytics. Messages, references, and attachments you send to an Agent, along with implementation content it reads, enter that Agent's and model service's workflow. Disabling analytics does not disable those requests.

MCP services may also receive data through the tools you enable. Check your Agent, provider, and server configurations to understand how sign-in, model requests, and third-party services handle it.

Send feedback

Choose Feedback at the bottom of the sidebar to describe a problem or suggestion, optionally leaving an email address. Submission sends the text you enter, the optional address, app version, and system information. It does not automatically attach project content, chats, logs, or screenshots.

Feedback is independent of the error-reporting switch. If sending fails, your text is kept so you can retry or copy it. You can also contact [email protected].

Settings → About → Export Diagnostics produces material containing version information, Agent status, and recent logs. Its scope differs from automatic error reports. Review it before sharing.

Check for and install updates

Release and Nightly each check for updates on their own channel. Use Check for Updates in Settings → About to see download progress, preparation status, or the reason for a failure.

Once the download completes, the sidebar's update card offers a restart to update. Save documents and handle active tasks first. Restarting interrupts running chats and workflows, so the app asks for confirmation.

Dismissing the update card only hides it for the current app session. Retry failed updates from About. For installation or data-version issues, see Troubleshooting.