Skip to content

Safety and responsibility

Dennis edited this page Aug 27, 2026 · 1 revision

Safety and responsibility

Hass-Cleaner provides technical checks, risk information and recovery options. It cannot understand the functional importance of every custom integration, automation or personal configuration.

The final decision remains with the user.

Technical safeguards

Hass-Cleaner blocks or prevents:

  • selection of protected Home Assistant core files;
  • removal of runtime-only entities;
  • execution against files that changed after the scan;
  • recovery that would overwrite an existing file;
  • permanent deletion before quarantine retention expires;
  • execution without the required confirmation;
  • partial file batches when one item fails validation;
  • direct permanent deletion outside expired quarantine.

Backup recommendation

A scan does not require a backup.

A complete Home Assistant backup is strongly recommended before:

  • moving files to quarantine;
  • removing registered entities or device relationships;
  • running Recorder purge.

User responsibility

Quarantine and recovery reduce risk but cannot guarantee that every integration or configuration remains unaffected.

Preferably test:

  • on a non-critical Home Assistant installation; or
  • with one simple and recoverable item.

After a change, verify:

  • integrations;
  • automations;
  • dashboards;
  • history and statistics;
  • Home Assistant logs.

Security issues

Do not publish sensitive security information in a public issue.

Use the repository's private security reporting options when available:

https://github.com/dkwolf1/Hass-Cleaner/security

Clone this wiki locally