BYTESTEWARD / SUPPORT

Storage recovery should never feel like a leap of faith.

ByteSteward measures first, protects active work, and requires a separate approval before any supported change. If the route is not clear, stop here—your data remains untouched.

Report a problem ↗View source and releases ↗
01Inspect

Read-only evidence explains what owns the space.

02Approve

Every change names one exact target and what stays untouched.

03Verify

ByteSteward rescans and records the measured result.

COMMON ROUTES

Pick the sentence closest to what you see.

START HERE

A recovery route is unclear

No action should require guessing. Stop before approval, keep the item protected, and include the exact screen and macOS version in a support report.

NOTHING CHANGED

A scan or inspection looks stuck

Scanning is read-only. Leave ByteSteward open, check the active-operation banner, and use Refresh only after the current operation reports completion or a visible error.

ACCESS

A folder is unavailable

Open Privacy & Access in ByteSteward, revoke the stale folder permission, then choose the folder again with the native macOS picker.

APP STORE EDITION

A specialist tool is unavailable

The sandboxed App Store edition never invokes installed database, container, Git, model, package, or Xcode command-line tools. Unsupported routes remain protected.

A USEFUL SUPPORT REPORT

Share evidence, not private content.

  • ByteSteward version and macOS version
  • The visible status or error, and the action immediately before it
  • A screenshot with usernames, paths, account names, and data redacted
  • Whether the app came from the Mac App Store or a direct release

Never attach recovery keys, passwords, cloud tokens, database contents, environment files, or private project source.