Blue is selling an early Blue Phone beta that puts the company’s BlueOS and assistant on a Google Pixel 10 Pro or 10 Pro XL. The company describes the assistant as able to read notifications and messages, operate apps, and run tasks in the background. This is a modified Android phone, not an assistant app for a stock Pixel. Blue’s own terms call Batch 2 a beta and warn that features may change or disappear and that users should expect defects.
How do you get the Blue Phone beta?
Blue’s site says the first Alpha batch is sold out and Batch 2 is shipping in November and December. Its current phone offer is based on a Pixel 10 Pro or Pro XL with BlueOS installed. The company says its own custom Blue Phone hardware is in development for a public launch planned in 2027, so that future device should not be confused with the present Pixel beta. Availability and delivery windows can change; check the order page before making a purchase.
Because BlueOS replaces the stock operating system, the bootloader is unlocked. Blue’s terms warn that Google’s manufacturer warranty and support programs may not apply and that some apps or services, including Google Wallet NFC payments, may not work normally. This setup is materially different from installing a conventional app: it changes which company controls the operating system and how the device handles data.
What information can the assistant access?
Blue’s Nov. 9 privacy policy says the assistant is a privileged part of the operating system. The service can handle message contents and attachments, contacts, call history, photos and files, calendar and notes, notifications, location, assistant conversations and action records. When asked to operate another app, the phone captures the screen and its accessibility description, sends them through Blue’s servers to an AI provider, and stores the capture with the task record. The assistant also reads on-screen text through an accessibility service.
That breadth is central to how a cross-app assistant can act, and it creates a larger data footprint than a typical chatbot. Blue says synced phone data is encrypted in transit and at rest in the United States, is not sold or used for advertising or model training, and is not ordinarily read by staff. The policy says it currently uses OpenAI, Anthropic and Google as AI providers under contracts that prohibit training on the submitted data. These are company statements in its privacy policy, not an independent security audit.
The policy’s Vault is designed for secrets such as passwords and payment cards. Blue says each secret uses AES-256-GCM encryption with a per-account key sealed in a hardware security module, and that the assistant cannot read Vault contents directly; it can ask the Vault to use a secret on the phone after biometric authentication. The policy also describes user controls to review, edit, delete and export data. Users should read the full policy for retention, third-party processors and account deletion details.
What should a buyer weigh?
The convenience proposition depends on giving an assistant operating-system-level context and the ability to take actions. Before buying, ask whether that access is acceptable for the messages, work apps, authentication codes and personal files on the device. Consider the modified-OS consequences for warranty coverage, banking apps, payment features and employer device policies. The fact that Blue publishes controls and detailed terms helps readers evaluate the product, but it does not itself establish that every control works as described.
Blue’s beta status matters too. Its terms warn of defects and possible feature changes, and say users should keep independent backups. VIBPS has not used the device or independently tested its privacy and security claims. The most useful way to evaluate a system like this is to examine exactly what it can read, which actions need confirmation, how task records can be deleted, and how the device behaves when a third-party app refuses access.