Why on-device execution matters for private tasks

Updated 2026-10-03

Private work needs access to your browser session, files, and installed apps. Where execution happens matters, but on-device execution alone does not mean every reasoning decision stays on the device.

The problem

A remote operator may require uploaded files or a remote login. BackBrain acts on the Windows PC where the work already is.

What local changes

Passwords and one-time codes stay on the PC and are not written into transcripts. Credential screens are not sent to a cloud model. Other task text can go to a model you chose. Local-only mode blocks cloud model calls; it is a setting, not the default.

Passwords are protected with Windows encryption and used only at sign-in. Session-only entry can keep a password in memory for one task and clear it afterward. Files are not uploaded to a BackBrain server. Learning stays on the PC.

Myths

Installed locally does not mean offline. Websites need the internet. A cloud model may receive task text with secrets removed. Local-only mode must be selected if you want to block cloud reasoning calls.

Privacy checklist

• Know whether you selected a cloud or local model.
• Credential screens are not sent to cloud models.
• Secrets are removed from transcripts.
• Reading can be quiet when allowed. Send, pay, buy, and submit need approval for the task.
• Delete always needs a clear request and an exact-file confirmation.