N-sight data retention: deletion, reports and recovery keys

At a glance

N-sight has different lifecycles for device records, report downloads and encryption recovery keys. The documented 90-day post-deletion key window does not apply to all device history. Account closure also changes key availability. RMMBackup can retain captured N-sight snapshots independently.

Separate N-sight device deletion from the 90-day recovery-key exception, temporary data-dump links and independently retained exports.

Published Updated

On this page

Use retention periods only for their documented resource

Resource What to expect
Deleted device, site or client data N-able describes deletion as permanent; it is not a retention grace period.
Last known Disk Encryption Manager recovery key Available in the Recovery Key Report for 90 days after device deletion.
Recovery keys after account closure N-able says it does not store them after closure.
Offline Asset Tracking dump link in the dialog Available for 24 hours to the requesting account.

Sources: device deletion, Disk Encryption Manager removal, and data-dump download behavior. A link's lifetime does not describe the retention of the file you already downloaded.

Confirm report and history windows for your account

Do not apply the recovery-key period to check results, patch history, audit history or every report. Ask N-able which lookback window and deletion rules apply to each required resource, and whether your account exposes any adjustable retention setting. The sources above do not establish a universal user-configurable retention control.

For each answer, record the resource, account region, applicable product and date of confirmation. N-sight and N-central are different products; Cove endpoint backup retention is another separate policy.

Capture before closing an account

The N-sight export comparison records the inventory-dump download window; keep those files before account access ends.

Generate the required recovery-key report and store it securely before closure. Download outstanding inventory dumps and verify they open. Ask the vendor to confirm export access deadlines and disposal terms for other records; this guide does not infer them from the key policy.

Set retention for independent copies

Choose backup frequency and retention separately. For example, an MSP may create dated inventory copies before every offboarding and regular backups between those events. That is an MSP policy choice, not an N-able default. Keep client and provider identifiers with each original and check older copies periodically.

Official source

Removing devices with Disk Encryption Manager

Related N-able N-sight integration

Review current N-able N-sight backup coverage and availability.