Trust and support
Privacy and data flow
Understand the upload boundary, result exposure and the controls outside the NetConverter bridge.
Files go to the hosted service
The CLI reads the selected configuration and uploads it directly to NetConverter over HTTPS for supported processing. It is not an offline engine. With the full API, selection pins a file and submission sends it; legacy pilot selection has its own confirmed upload flow.
The optional in-app model uses a restricted operation-intent contract. A connected external assistant is a different path: the local bridge exposes permitted tools and filters their results according to workspace exposure and the server’s account grant.
Choose result exposure
| Level | Assistant result view |
|---|---|
none | Restricted verdicts, statuses, counts and identifiers. |
masked — default | Server strict view, tokenized names where enforced by the server, and addresses masked by the bridge. Configuration-content calls are restricted. |
selected | Masked mode with user-selected sections. Selected sections can enable broader content tools; inspect the chosen sections. |
full | Results the server permits for the account. This can expose more detailed content than masked mode. Needed for the guided-migration tools. |
netconverter privacy status
netconverter privacy level maskednone, masked and selected are served from the hosted strict view, which lists no guided-migration or write tools (propose_operations, submit_conversion, apply_mapping_answers); full uses the default view, where the write tools appear only for tenants an administrator enabled. Restart the assistant after changing the level.
Raising exposure requires typing the requested confirmation in a terminal. The workspace setting is the ceiling; a bridge flag cannot raise it on its own. The bridge applies pattern-based secret filtering at every level. Pattern filtering is not a guarantee that all sensitive information is recognized.
Hosted MCP view modes
The table above is the local bridge's folder setting. A connection made directly to the hosted MCP server (api.netconverter.ai/mcp/v1) has no folder level; it uses the view mode set on your account's MCP access.
| Hosted view | Assistant result view |
|---|---|
default — default for new access | IP addresses and CIDRs from your own jobs are shown, and names are returned as written. Credentials are redacted. |
strict | Addresses from jobs are replaced with placeholders, configuration-content tools are hidden and configuration names are tokenized. Credentials are redacted. |
A session can lower the hosted view but not raise it. Ask your assistant to call get_account to see the view in force. Since October 22, 2026 the default view shows your own addresses; before that date it masked them.
The assistant has other tools
An assistant with its own file or shell access may read a configuration independently of the bridge. Configure that client’s restrictions and keep the workspace out of its unrestricted project context. OpenClaw and Codex guidance is printed for manual application; some other client rules can be applied after a reviewed confirmation.
Describe the default path precisely: the bridge can submit a file by path without the assistant first reading its text. That is not a blanket promise that configuration content can never reach an assistant under broader exposure settings or other tools.
Credentials and local files
Credentials use the supported OS credential store, a passphrase-encrypted file, or session memory. They do not belong in the configuration workspace or an AI conversation. The encrypted store does not protect against processes running as you while its passphrase is accessible.
Downloaded outputs are ordinary local files. Protect them with your organization’s storage controls. Bridge activity records contain metadata such as paths, sizes, hashes and job IDs, which can still be sensitive.
Verification boundary
The published verification notes leave the complete backend AI-provider payload audit open. Client tests do not establish that every downstream server provider path has been audited. Use synthetic files for initial testing and obtain the relevant privacy acceptance before using sensitive customer configurations.
Source and release context: Detailed privacy and data flow · Verification limits