In this article

The Limit Display of Personal Data setting reduces or restricts personally identifiable information (PII) shown in the DNSFilter dashboard and exports.

This setting controls how user and device details appear across the application, including logs, reporting, exports, and synchronization tools. Only users with Admin permissions or higher can update this setting.

Enabling stricter privacy modes reduces the visibility of user and device identifiers and disables the collection of certain Roaming Client fields that may contain PII.

Important considerations

• Privacy settings affect dashboard visibility and exported data
• Stricter privacy levels limit forensic detail in logs and reporting
• Sync tools and user-based policy assignments are hidden but still applied when user identifiers are hidden

Review internal compliance requirements before selecting a privacy level to ensure operational needs and privacy expectations are aligned.

Privacy levels and data visibility

Limit Display of Personal Data controls

1. Navigate to Organization and select Settings (from the MSP dashboard, navigate to MSP > Settings)
2. Locate Limit Display of Personal Data
3. Select the desired privacy level
4. Save changes

Changes apply Organization-wide and affect dashboard views and exports moving forward. Existing data is not retroactively hidden.

Multi-Tenant (MSP) dashboard and Organization controls

For MSP environments, privacy controls can be managed at both the MSP dashboard level and Organization level.

MSP dashboard level

The privacy setting configured at the MSP dashboard level acts as the default for all managed Organizations.

MSPs can:

• Apply the same privacy setting to all Organizations
• Bulk update multiple Organizations
• View and manage overrides

Organization-level override

An individual MSP Organization can override the MSP-level privacy setting.

When overridden:

• The selected privacy level updates for that Organization
• The change is recorded in the MSP dashboard Override grid for visibility

Overrides may be set:

• From within the individual Organization
• From the MSP dashboard for one or multiple Organizations

Limit display of personal data FAQs

Q. How does this feature affect my organization’s GDPR compliance?
A. Your organization’s compliance with GDPR is determined solely by your own legal counsel and your own internal requirements. This feature is designed to enhance certain privacy features of our service.

Q. Can I turn this feature on and off again?
A. Yes. If after enabling this option, you decide to disable it again, you must wait for each Roaming Client to check in with the DNSFilter dashboard before Client Name and Username data is available again.

Limit display of personal data troubleshooting

If the Limit Display of Personal Data option was enabled before entering a Friendly Name for each Roaming Client, it might be difficult to differentiate between devices within the DNSFilter dashboard.

To identify Roaming Clients after the data has been redacted, compare the ID of the Roaming Client within the dashboard with the Client ID of the device. Obtain the Client ID of the device using multiple methods:

Command line or terminal window. Run this command, which will return the client_id of the Roaming Client:

nslookup -type=txt debug.dnsfilter.com

Windows Registry. Lookup the agent on the local device:

HKEY_LOCAL_MACHINE\SOFTWARE\DNSAgent\Agent\ClientId

For Windows Roaming Client version 3.0.0 and later, the ClientId is now located in the appsettings.json file under the path C:\Program Data\DNSFilter, Inc\Settings

macOS Library Application file. Lookup the agent on the local device:

Standard Agent: cat /Library/Application\ Support/DNSFilter\ Agent/daemon.reg MSP/Whitelabel Agent: cat /Library/Application\ Support/DNS\ Agent/daemon.reg