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.

Quick finder

Docker and VM search result names, identifying icons, and containing folder paths follow Mask names and icons, including selected results and fallback icons. The search field, placeholder, and typed query remain readable so searching works while Privacy is enabled.

Queries are temporary and are not saved or included in diagnostics. Clear the query or close search before sharing a screenshot or recording when its text identifies a private workload. This presentation behavior does not replace sanitized support-bundle export.

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.

Editor and migration evidence

Editor support history records bounded counts, outcomes, help/disabled-state flags, and layout geometry. It excludes private names, filenames, URLs, search text, form values, and tooltip contents. Up to eight snapshots per Docker/VM type remain for 30 minutes; storage availability can affect retention. Migration history similarly uses allowlisted phases/counts/booleans and distinguishes verification from restoration. Raw migration reports and backups remain private configuration evidence.

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.

Docker preview-context diagnostics retain only bounded row-mode/position counters, handler-integrity and dispatch outcomes, activation category, input method, timestamp, and allowlisted failure reasons. They do not retain folder or container names/IDs, DOM selectors, URLs, or click coordinates.

Recent Settings, Bulk assignment, and snapshot-comparison UI histories contain only allowlisted counts, fixed state labels, and measurements. Each feature and Docker/VM type keeps at most three recent records for 30 minutes; expired records are excluded and records from another plugin version are marked. Dashboard geometry adds row/header/preview measurements and valid before/after movement comparisons. These new UI records exclude names, identifiers, snapshot filenames, search text, paths, URLs, and raw user-agent strings in both sanitized and full exports.

Browser metadata includes a normalized browser family and reported numeric version, rather than the raw user-agent string. A beta/build label may be more detailed than the exported numeric version. Restricted storage can prevent evidence from surviving navigation; it does not block normal operations. Dashboard capture reports a save warning when storage is unavailable, and dismissing a successful capture notice does not delete its evidence.

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.