# Privacy and feedback

Understand where task data goes, control optional telemetry, and distinguish local data from shared copies.

Data handling depends on the route you use: a local query, a live provider Action, a remote connection, or a published share. Choose the route that fits the task and the audience.

## Data boundaries

| Route | Relevant boundary |
| --- | --- |
| Local Vault search | Reads retained records through a bounded read-only interface. Credentials and private state are excluded. |
| Local provider Action | Sends the operation to the selected source and returns its result. Current Action payloads can be transient rather than added to shared search. |
| Local Cloud read | Returns an authorized selected page and retains that page for later Vault search. |
| Galaxy | Shows source and aggregate record information; it is not a full document-content viewer. |
| Remote MCP | Makes granted operations available to the authorized client while the original computer runs them. |
| Static share | Publishes selected text or file copies separately from the original source. |

Credential protection does not mean all retained document bodies are encrypted at rest. Use appropriate access controls for the local Vault directory.

The agent host also receives the information returned to its task. A local source or local Vault does not imply that an agent conversation itself stays entirely on the same computer.

## Connection credentials

Complete sign-in on the provider page or the protected local authorization form opened for that source. Nonsecret setup fields—such as a public client ID, region, tenant, folder, or library—are separate from credentials.

Temporary connection URLs, device codes, local consent passwords, and signed Galaxy launch links are specific to an access flow. Do not include them in public handoffs or support screenshots. Reopen help when a live link expires.

Changing or disabling a source does not necessarily erase old collected records. Provider revocation, local deletion, remote-grant revocation, and share publication have different effects; see [Permissions and source controls](/docs/vision/settings/permissions).

## Optional usage feedback

The installed feedback command lets you rate a recent search or connector operation:

```sh
indra --root "/absolute/path/to/your/Vault" feedback
```

It offers recent operations and fixed rating/reason choices. It does not request free-text account content. To inspect eligible receipts:

```sh
indra --root "/absolute/path/to/your/Vault" feedback --list
```

Feedback is saved locally for normal enabled telemetry delivery. No response means unrated. A successful operation is not automatically a useful result.

## Disable optional telemetry and feedback

Set either `ZORTEX_TELEMETRY=0` or `DO_NOT_TRACK=1` before launching the relevant product process. For example:

```sh
export ZORTEX_TELEMETRY=0
indra --root "/absolute/path/to/your/Vault" host start
```

In PowerShell:

```powershell
$env:ZORTEX_TELEMETRY = '0'
indra --root "C:/absolute/path/to/your/Vault" host start
```

Restart a running host or MCP client so it receives the setting. Preserve it in the launcher or host environment used for future sessions. Disabling collection now does not establish deletion of previously delivered telemetry.

## Before publishing a share

The current Share link is readable by anyone who has it. It has no expiry, access control, or revocation. It is a static copy: changing the source file later does not update or remove the published copy.

Inspect the selected text and files, honor explicit exclusions, and distinguish content review from metadata-only review. The preview describes the fixed selection; publication rechecks its current evidence. Follow [Sharing context and files](/docs/vision/tools/sharing) for the complete workflow and current file limits.
