Privacy

Privacy

FolderView Plus has two different privacy systems:

1. Runtime privacy masking changes what is rendered on Docker, VM, and Dashboard surfaces.
2. Support-bundle sanitization removes or transforms sensitive diagnostic values before export.

Neither system should be treated as authentication or permission control.

Docker runtime masks

• Names and icons.
• LAN IPs.
• Ports.
• Volume paths.
• Image registries.
• Public IPs.
• Network interfaces.
• External URLs.

VM and Dashboard masks

VM privacy can mask names/icons, disk paths, MAC addresses, public IPs, interfaces, and external URLs. Dashboard uses the saved masks for its Docker and VM cards.

Screenshot placeholder — Privacy options

Capture the Docker Privacy menu with every mask label visible, followed by a masked test row. Use only fictional names and addresses reserved for documentation.

What runtime privacy covers

When enabled, FolderView Plus applies masking to supported rendered text, copied text, labels, tooltips, action/menu content, link targets, and rows observed after initial load. It does not rewrite Docker or VM configuration.

What runtime privacy does not cover

• Browser developer tools, network traffic, or other plugins.
• Unraid pages/elements that FolderView Plus does not own.
• Files exported before Privacy was enabled.
• Screenshots already captured.
• Server logs, terminal history, or browser extensions.
• Authentication or access control.

Always inspect a recording or screenshot before publication.

Sanitized support bundles

Sanitized exports are designed for public issue reports. They redact or summarize names, paths, URLs, IP addresses, identifiers, user-agent values, and other sensitive fields while retaining versions, health states, counts, boolean capabilities, and bounded diagnostics needed for support.

Docker API diagnostics follow the same boundary. A sanitized bundle may include boolean capabilities, provider mode, aggregate success/failure category, retry cooldown, and changed/structural counts. It does not include GraphQL response data, container names or IDs, query text, tokens, cookies, CSRF values, URLs, or raw server errors.

Review the preview before export. Sanitization is allowlist-based, but no automated process can understand every value a user may consider sensitive.

Full support exports

Full/raw diagnostic exports can contain operational identifiers and should be shared only through an explicitly private support or security channel after review. A configuration/environment export is not a support bundle and should never be posted publicly.

Safe support workflow

1. Enable runtime Privacy before reproducing a visual issue.
2. Run Diagnostics.
3. Select sanitized support output.
4. Review the included sections and preview.
5. Open the downloaded file locally and inspect it once more.
6. Attach it only to the intended report.

Report privacy defects privately when they could expose sensitive data. See Security and Package Trust.