Skip to content

DocsAccount & security

Security & privacy

Updated Sep 15, 2026

What stays in your browser

Your files, your provider keys (unless you explicitly opt in below), and most of what you do in NextOS lives in your browser's own storage. Nothing about how you use the desktop day to day is sent to our servers unless a feature you're using genuinely needs it - syncing files, calling a hosted model, or running something in the background.

What leaves your browser, and why

  • Files you choose to sync go to the cloud storage provider you connect - Google Drive by default, or another provider you add - never to a third party you haven't authorized.
  • A model call sends only what that call needs (your message and any context you've given it) to the provider you or your plan is using, over an encrypted connection.
  • A background run uses a securely stored, opt-in copy of your provider key so the run can continue without your browser open. This vault is opt-in specifically because it's the one case where NextOS holds something on your behalf instead of your browser holding it.

Encryption, in plain terms

Anything stored on our servers on your behalf - a cloud storage connection's credentials, a provider key you've opted into the background-run vault - is encrypted before it's stored, using a key that isn't derived from anything guessable about your account. Even someone with access to the underlying storage can't read it without that key.

Connections between your browser and our servers, and between our servers and any provider or storage service, are encrypted in transit.

Guardrails on what an agent sends

If you're on a team with governance policy configured, an admin can turn on automatic screening of what agents send to a model: redacting things that look like personal information or secrets before they ever leave, and flagging attempts to manipulate an agent through its input (prompt injection).

Your own account's security

You can require a password in addition to (or instead of) Google or GitHub sign-in, and a team can enforce single sign-on so only people signing in through your organization's identity provider can ever join.

What's next