Data retention and account closure
What is stored, for how long, backups, exports, and what happens when you close the account.
What the service keeps, for how long, where copies exist, how you get your data out and what happens when you leave. The Subscription page of your organization shows the current values.
Retention periods
| Data | Kept | Notes |
|---|---|---|
| Endpoint inventory (hardware, software, updates, vulnerabilities) | While the endpoint exists | Replaced at every check-in; removed when the endpoint is deleted or unenrolls |
| Command logs and execution history | 180 days by default | Advanced → Data → Execution History Retention (7 to 3650 days) |
| Audit Trail | 365 days by default | Advanced → Data → Audit Trail Retention (30 to 3650 days) |
| Provisioning jobs, with their step log and the local Administrator password they keep encrypted | 365 days by default | Advanced → Data → Provisioning Job Retention (30 to 3650 days) |
| Devices that showed up on the provisioning media and were never provisioned | 30 days without news | Fixed |
| User accounts, roles, groups, automations, alerts, reports, scripts, packages | While the organization exists | Deleted by you at any time, or with the organization |
| Uploaded installers (Software Repository) | While the package version exists | Deleted with the package |
| Sign-in challenges, trusted-browser records, sessions | Until they expire | Pruned nightly |
| Console database backups | 30 days | Nightly, kept on the console server, encrypted at rest by the hosting provider |
| Service availability samples and incidents (status page) | 400 days | Contain no customer data |
Retention sweeps run nightly.
Exporting your data
- Every list (Endpoints, Installed Software, Update Approval, Vulnerabilities, Audit Trail) exports to CSV.
- Every built-in and custom report exports to CSV or PDF, immediately or on a schedule by email.
- The REST API returns the same data as JSON for bulk extraction.
Closing your organization
Subscription → Close Account (administrators only) starts a 30-day period of pending closure, then removes the agents and erases the data:
- Immediately: automations, alert rules and scheduled reports are disabled and new endpoints can no longer enroll. The agents keep running. Every administrator of the organization is emailed the closure date.
- During the pending period (30 days): the console stays readable so you can export what you need; any administrator can Reopen account from the same page and nothing is lost (disabled automations, alerts and reports must be re-enabled by hand).
- At the end of the period: every agent receives an uninstall order at its next poll and removes itself from the computer. One day later the organization is deleted with everything in it: endpoints, inventory, vulnerabilities, groups, automations, history, reports, scripts, packages and uploaded installers, API credentials, settings, the audit trail, and the accounts of users whose only organization it was. Users who also belong to another organization keep their account.
- Within 30 more days: the nightly backups containing the organization age out. Sixty days after the request, no copy remains.
Agents that were offline when the uninstall order was sent never receive it; remove them by hand with IdolbePatchAgent.exe -uninstall (Windows) or sudo idolbe-patch-agent -uninstall (Linux). They cannot re-enroll once the organization is gone.
An organization with no enrolled endpoint can also be deleted immediately from Organizations → Delete.
Deleting a single endpoint
Deleting an endpoint from the console removes its inventory, updates, vulnerability matches and command logs at once. The audit trail keeps the entries that mention it until their own retention expires. The agent on the computer uninstalls itself at its next check-in (agents 0.11.4 and later): the console remembers the deleted hostname and refuses the automatic re-enrollment. A deliberate reinstall from the console download or the one-liner enrolls the computer again.
Deleting a user
Users & API Credentials → delete removes the account and its sessions. Audit entries keep the email address that performed each action, as the trail is meant to.
Requests under data-protection law
Access, rectification and erasure requests about personal data (user accounts, logged-on user names reported by endpoints) go to the support address in the console footer; see the privacy policy.