Privacy Mode toggle promoted to the editor toolbar
AetherCut v1.7.57 shipped on Feb 2026.
What's new in v1.7.57?
- The Privacy Mode kill switch is no longer buried inside the About AetherCut dialog — a compact "Privacy Mode · X cloud calls" chip now lives directly in the editor's header toolbar, between Performance Mode and the Help button.
- Both surfaces share the same usePrivacyMode hook so flipping one updates the other in real time. Tooltip on hover: "One-click kill switch for every cloud AI tool. Verifiable in DevTools.".
- Pinned by regression so a future agent can't silently demote it back to the About dialog.
Using the toolbar Privacy Mode toggle without breaking your flow
The practical win here is not just that the Privacy Mode control moved; it is that it now sits in the same line of sight as the rest of your editing decisions. In real use, that changes behavior. If you open AetherCut to trim a local interview, clean up a screen recording, or prepare rough cuts from sensitive client footage, you no longer have to remember that a kill switch exists somewhere inside an informational dialog. You can glance at the header, see the current state, and decide before you touch any AI-assisted action. The “Privacy Mode · X cloud calls” chip is especially useful because it does two jobs at once: it exposes whether the lockout is active, and it gives you a quick signal about whether anything in the current session has tried to reach a cloud-backed tool. That makes the control feel less like a buried preference and more like an operational status indicator.
A simple way to use it is to treat the toggle as part of your session setup. Open the project, look at the toolbar, and decide whether this edit should be fully local from start to finish. If the answer is yes, enable Privacy Mode before you run transcript generation, AI search, auto-tagging, or any assistant feature that might otherwise depend on remote processing. If the answer is no, leave it off while you use the tools you need, then turn it back on when you return to manual editing. Because the toolbar chip and the older surface are wired to the same state, there is no “which one is the real one?” confusion; whichever place you flip it, the current setting is the setting. That matters most in longer sessions, where people often bounce between editing, settings, and troubleshooting panels and can lose confidence about whether a privacy control actually stuck.
One common mistake is assuming Privacy Mode is retroactive. It is not a cleanup button for cloud activity that already happened earlier in the session; it is a stop switch for cloud AI tools from that point forward. If you used a remote feature first and only enabled the toggle afterward, you still got the benefit of blocking future calls, but you did not erase the earlier ones by turning it on late. Another easy mistake is reading too much into the cloud-call count without thinking about timing. If the chip shows a nonzero number, that is a sign to ask when those calls occurred, not just whether Privacy Mode is active right now. Teams reviewing handling procedures should make a habit of checking the state before testing any assistant workflow, not after. The tooltip’s emphasis on verification in DevTools is there for the same reason: trust is better when it is observable. If you are validating a locked-down workflow for legal, enterprise, or internal policy reasons, check the toggle first, perform the action you are worried about, and confirm that no cloud request is attempted while the mode is enabled.
Another subtle failure case is editing by habit. Users who learned to find the switch in the About dialog may keep reaching for the old path and never build the faster toolbar check into muscle memory. That sounds minor, but the whole point of promoting the control is reducing friction at the exact moment a decision matters. The more visible placement only helps if you actually use it as a preflight check. A good pattern is: open project, scan the toolbar, verify Privacy Mode, then start working. For shared machines or demo environments, that habit is even more important because you may inherit the state from the previous user or session expectations that are different from your own. In those contexts, the toolbar location prevents accidental assumptions. You do not need to dig through menus to audit the current state; it is already exposed where you are looking.
If you want to get confident with the new placement, try a quick dry run on a noncritical project. Turn Privacy Mode on from the toolbar, attempt an action that would normally rely on a cloud AI tool, and watch how AetherCut behaves. Then flip the same setting from the other surface and confirm the toolbar updates immediately. That small exercise teaches two things fast: first, where the state now lives in your day-to-day workflow, and second, that both surfaces are synchronized rather than maintaining separate preferences. Once that clicks, the toolbar chip becomes less of a novelty and more of a guardrail you can rely on during real editing work.
Which features does this release touch?
How do I get this update?
Open the editor and you have it. AetherCut runs in Chrome, Edge, Safari and Firefox. There is nothing to install, and you can edit without an account. Open the editor or see how it works.