Privacy Policy

DreamCleanr is built to be local-first. The current product inspects cleanup candidates on your device, writes receipts on your device, and avoids a mandatory hosted account or analytics layer by default.

What DreamCleanr may access

• local process metadata
• selected cache, log, and storage paths
• optional local schedule state through launchd
• optional Docker CLI metadata when Docker is installed
• local DreamCleanr receipt files

What DreamCleanr does not upload by default

• process inventories to a DreamCleanr backend
• cleanup reports to a DreamCleanr backend
• credentials, tokens, or protected session history
• ~/.codex, ~/.claude, or protected application support data

Limited network activity

When you use install and update paths, DreamCleanr may contact GitHub-hosted release surfaces so it can resolve the latest stable version. Those requests are governed by the relevant platform’s own terms.

Retention and choices

DreamCleanr writes receipts locally under ~/Library/Logs/DreamCleanr/reports. You can remove those files, uninstall the schedule, and uninstall DreamCleanr at any time.

Future iPhone and iPad companion

If DreamCleanr launches a native Apple companion app later, this policy will be updated to reflect the exact data categories and App Store privacy declarations for that build.