Support

Scanning and results

• Q: Does scanning read file contents? A: No — only directory and file metadata; the directory-open flags used for scanning are read-only and non-blocking options only, with no write flags.
• Q: Which locations does "Cleanup Items" scan? A: Only four — user and app caches (~/Library/Caches), user logs (~/Library/Logs), crash reports (~/Library/Application Support/CrashReporter), and installers in the Downloads folder (DMG/PKG/ZIP/XIP/ISO, marked "Confirm Recommended").
• Q: Why do results say X locations were not counted? A: Locations unreadable due to permissions or file-state changes are recorded as coverage gaps only and never enter the cleanup list; the UI marks the uncounted number.
• Q: Are Capacity Distribution percentages computed against total disk capacity? A: No — the denominator is "total counted in this scan"; when nothing was counted it shows "No capacity counted yet" instead of 0%.

Permissions

• Q: Is Full Disk Access required? A: No. Everything works without it; protected directories are simply excluded from statistics, and the UI marks how many directories were not counted.
• Q: When are permissions requested? A: Full Disk Access guidance appears only when scan results contain unreadable directories and you click "Learn How to Grant" yourself; Notifications are requested only when you enable an alert category in Settings and the system has not yet granted permission.
• Q: How do I revoke them? A: In-app deep links go straight to system settings — Full Disk Access to the Full Disk Access pane in Privacy & Security, Notifications to the Notifications pane.
• Q: What happens if I decline Notifications? A: Alerts do not pop up, but evidence cards and trends update as usual, and no other feature is affected.

Execution and recovery

• Q: Are files ever permanently deleted? A: No — the only action is moving confirmed selections to the system Trash; the entire codebase has exactly one Trash call site and no permanent-deletion entry.
• Q: Can a mistake be undone? A: Before you empty the Trash, you can put files back in Finder.
• Q: Why didn't available space change after deleting files? A: Space occupied by files still in the Trash may not be freed yet, so available space does not fully increase immediately — the execution receipt says this too.
• Q: What if execution is aborted midway? A: The receipt marks the current item as aborted and all later items as not executed; if receipt construction fails it is not silently patched, and the frozen plan stays unchanged and is never auto-replayed.
• Q: Do Space Change deltas prove Sin Clean's cleaning effect? A: No. They only report deltas in scanned category totals, with no inferred cause; the receipt's succeeded capacity, the disk's free-space change, and category totals are three independent sets of numbers that never reconcile against each other.

Updates

• Q: When are updates checked? A: The channel manifest is requested only when you click "Check for Updates…" — no background checks, no silent updates.
• Q: Can a failed update break the current app? A: Replacement is multi-step and rollback-capable at each step; on failure it attempts automatic restoration — a successful restore reports "The current version has been restored automatically", and a failed restore states honestly that the backup remains in its original directory.
• Q: What checks does an update package go through? A: Manifest Ed25519 signature verification, strict build-number comparison, channel and minimum-system checks, plus package byte count, SHA-256, disk headroom, and same-volume requirements — with a signature trust gate after unpacking.
• Q: What does an update leave behind? A: The staging directory ~/Library/Caches/SinClean/Updates/ is emptied when the flow ends (success or failure); failures and leftover events are written to the local ~/Library/Application Support/SinClean/update-rollback.log — no networking, no upload.

Uninstalling and leftovers

• Q: What should I do before uninstalling? A: Quit Sin Clean first; if you want to keep any records, note the local data paths listed below first.
• Q: Is dragging it to the Trash enough? A: Not entirely. Four leftover locations outside the app bundle need checking — see the uninstall guide below.
• Q: Does "Restore Default Settings" clear the Ignore List? A: No. The Ignore List is a local file that needs separate clearing; "Restore Default Settings" does not clear it either.
• Q: Does uninstalling delete files I cleaned? A: No. Uninstalling handles only the app itself; files already in the Trash remain yours to manage in Finder.

1. 01

   Quit the app

   Quit Sin Clean from the menu bar and the app; confirm the menu bar icon is gone.

2. 02

   Check each local data path

   Check in order: Operation History ~/Library/Application Support/SinClean/operation-history.json; system health trends ~/Library/Application Support/SinClean/system-health/trends.json; Space Change records and salt file ~/Library/Application Support/SinClean/space-change-history.json and space-change-salt.txt; the Ignore List ~/Library/Application Support/Sin Clean/ignore-rules.json (directory name contains a space); the update rollback log ~/Library/Application Support/SinClean/update-rollback.log.

3. 03

   Drag to the Trash

   Drag Sin Clean from "Applications" to the Trash, then empty the Trash.

4. 04

   Check the four leftovers

   ~/Library/Application Support/SinClean/, ~/Library/Application Support/Sin Clean/, ~/Library/Caches/SinClean/ (including the Updates staging subdirectory), and the defaults domain com.sinclean.app.

5. 05

   Handle the defaults domain

   Run `defaults read com.sinclean.app` in Terminal to view the settings in this domain; once you confirm they are no longer needed, you may clear it with `defaults delete com.sinclean.app`. The domain is kept locally by the system; these commands come from system tools, not product features — whether to run them is your call.

Sin Clean performs exactly one action on confirmed selections: moving them to the system Trash. Before you empty the Trash, you can check and restore items in Finder.

One thing to remember: space occupied by files still in the Trash may not be freed yet, so available space does not fully increase immediately.

• Restoration is done by Finder; Sin Clean offers no restore entry and does not record "original paths" for automatic restoration.
• Operation History reviews completed cleanups and uninstalls read-only; you cannot execute anything from it, nor restore past selections.
• "Open Trash" on the Operation History page only opens the Trash in Finder and modifies no records; "Clear History" only deletes the locally kept history summaries and read-only details.

• The page you were on (e.g. "Space Cleanup → Space Analysis").
• The steps you took (where you started, what you clicked).
• The text you actually saw (the UI wording, as verbatim as possible).
• Screenshots (the full screen including the confirmation dialog or message).

These four fields come from the feedback requirements in the product's Local Trial Guide: state the page, the steps, the text you actually saw, and screenshots.

This round prioritizes these problems: won't open, crashes, truncated text, results not matching the scope, execution without selection, wrong information in confirmation dialogs, and permission descriptions not matching behavior.

Support email

tiandi.sin@gmail.com

GitHub Issues

blacstar7/sinclean-updates (button above)

Both channels are provided by user decision: email suits feedback with attachments or follow-ups; GitHub Issues suits bug reports and feature suggestions. When writing to tiandi.sin@gmail.com, prepare materials per the "What to include in feedback" checklist on this page for faster handling.