> For the complete documentation index, see [llms.txt](https://docs.nimbalyst.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nimbalyst.com/open-safe-private-secure/privacy.md).

# Privacy

Nimbalyst is local first. Files, app state, and agents stay on your machine, and online features move only the data that feature needs.

This page describes what stays on your machine, what data moves when you turn on an online feature, and how to opt out of telemetry.

### Local First, Shared When You Choose

Nimbalyst starts with local files, local application state, and agents configured on your machine. You can use the desktop app without moving a project into a hosted workspace.

Online features move only the data needed for the feature you choose:

* **Local workspace by default**: Project files remain outside Nimbalyst Teams unless you explicitly promote them into the shared team workspace.
* **Nimbalyst Teams**: Shared files and Trackers flow through Nimbalyst's Cloudflare sync service. Team data is encrypted in transit and at rest, isolated per team, and available only to authenticated, authorized members.
* **Personal device sync**: Personal sessions, prompts, drafts, and settings use a separate end-to-end encrypted channel.
* **Optional telemetry**: Nimbalyst collects anonymous product analytics to improve the app. You can opt out under **Settings > Application > Advanced > Analytics**. Telemetry does not include file contents, file paths, API keys, authentication tokens, document content, session content, or chat content.
* **Accounts are optional for local use**: An account is required for online services such as Nimbalyst Teams and personal device sync, not for local editing.
* **API keys and settings protected on disk**: Provider API keys are encrypted at rest, and Nimbalyst's settings files are written with private file permissions (as of v0.77.2).
* **Open source**: Verify how these boundaries are implemented in the source at [github.com/nimbalyst](https://github.com/nimbalyst).

### In-App Feedback Reports

Filing a bug report or feature request from inside the app sends nothing until you approve it:

* Logs are gathered only if you leave the consent checkbox on when starting a bug report.
* Everything gathered goes through an anonymization pass, a scrubbing step plus an AI redaction step over file paths, project names, and identifiers, before you see the draft.
* You review the redacted draft, and the report opens as a pre-filled GitHub issue form in your browser. You submit it yourself on github.com; nothing is posted on your behalf.

The [trust page](https://nimbalyst.com/trust/) lists the subprocessors involved when you turn on team features.


---

# 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.nimbalyst.com/open-safe-private-secure/privacy.md?ask=<question>&goal=<endgoal>
```

`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.