Your AI Vendor Says 'Trust Us' with Your Data. There's a Better Option.

Your AI vendor says "trust us" with your data. At the end of June, ByteDance's Doubao (豆包) officially ends its free tier and starts charging for API calls. The discussion in developer communities quickly shifted from pricing to a different question: all this data flowing to cloud AI services every day — where exactly does it go?

Around the same time, NVIDIA spent significant stage time at GTC 2026 presenting the full-stack confidential computing capabilities of the Vera Rubin architecture. Jensen Huang's message was clear: future AI chips need to keep data encrypted throughout the computation process, making it inaccessible in plaintext to anyone — including the cloud service provider.

Two signals pointing to the same trend: data security in AI services has moved from "someone mentioned it once" to "you need to answer this directly."

The Data Path Through Cloud AI Is More Complex Than You Think

Most developers have a simple mental model of cloud AI: I send a request, the model returns a result, and my data is gone.

The actual data flow is more involved. A typical cloud AI call touches these steps:

• Request data travels over HTTPS to the service endpoint


• The service may queue the request while waiting for GPU allocation


• During inference, input data exists in plaintext in server memory


• After inference, whether inputs/outputs are cached or used for subsequent training depends on the provider's privacy policy


• Logging systems may record request metadata or partial content

At each step, data is potentially accessible. Providers typically say "we don't look at your data" and "your data won't be used for training" in their privacy agreements. These are contractual commitments. You need to trust that they'll honor them.

This is the "Trust Me" model.

Trust Me vs Verify Yourself

If you roughly categorize data protection approaches in AI services, two paradigms emerge:

Trust Me

Data leaves your device and is processed by a third party. The provider guarantees security through contracts, security audits, and compliance certifications. You can't independently verify that your data wasn't accessed — you trust their word.

Most cloud AI services operate this way. OpenAI, Anthropic, Doubao, and others. NVIDIA's Vera Rubin confidential computing adds a hardware-level protection layer (TEE — Trusted Execution Environment), encrypting data during computation so even the service provider can't see plaintext. This is a significant upgrade to the Trust Me model, but fundamentally, your data still left your device.

Verify Yourself

Data never leaves your device. Inference runs locally. Screenshots and task descriptions are not uploaded to any external server. You don't need to trust any third party because the data physically stayed put.

This is the core advantage of on-device AI. No privacy policy fine print to review. No provider security compliance to evaluate. No cross-border data transfer regulations to worry about. Data doesn't leave the device — that's the simplest and most thorough protection there is.

The open-source community is already shipping this model.

GUI Agents Make the Privacy Problem Worse

GUI agents are one of the most privacy-sensitive AI application categories.

With a traditional LLM call, you know what you're sending: a text prompt, a question. But GUI agents continuously capture screen content to understand the current state. Everything on your screen goes into the model.

Your bank balance displayed while you're on a banking website. The commercial terms in a contract you're editing. The subject lines of other emails visible while you're composing a reply. A GUI agent needs to "see" all of this to function. If inference runs in the cloud, every screenshot gets uploaded.

This is why on-device inference in GUI agent scenarios isn't just "a better option" — in many cases it's a requirement.

Mano-P's 4B on-device model achieves roughly 80 tokens/s decode speed on Apple M5 Pro — responsive enough for smooth GUI automation. With the

Charging for AI Isn't the Issue — Data Flow Is

Back to the Doubao pricing news. Charging for AI services is a reasonable business model. Good models deserve to be paid for. The real question isn't "should I pay" but "while I'm paying, what's happening to my data."

For public information retrieval and generation, cloud services remain the most efficient option. For scenarios involving personal privacy and enterprise confidentiality, spending the cost of a Mac mini to move inference on-device might be the more prudent approach.

You can switch tools. Data leaks are irreversible.

If you're looking for a GUI agent solution that runs entirely on-device, check out Mano-P on GitHub. Apache 2.0 open source, supports M4+ devices with 32GB RAM, install via brew tap Mininglamp-AI/tap && brew install mano-cua. If you find the project useful, a GitHub star would be appreciated.