Elon Musk renewed his promotion of Grok Bot’s shopping abilities on October 11, encouraging users to treat the AI agent like an employee that can find products and complete purchases. That convenience requires handing a system access to money, while the company’s newly updated privacy policy places responsibility for payment information and actions on users.

The immediate concern is uploading raw card details into a conversation. A photograph can contain a card number, expiry date and cardholder name, and sometimes its security code. Those details can become part of an agent’s working environment rather than remaining confined to a merchant’s payment form.

Musk’s shopping pitch meets his own privacy warning

In an October 10 post, Musk described the process:

To buy stuff, you can just take a picture of your credit card, drop it in the chat and Grok @Bot will scour the Internet for the best deal on the item you want and order it

He subsequently amplified a user’s claim that Grok Bot had found and ordered an iPhone using a virtual card. That is an account of a purchase, rather than an independent security test.

His October 11 Lego demonstration also included an order screenshot showing shipping and billing details, an email address and partial payment information. Musk later said the displayed address receives his mail and is not where he lives. He published the screenshot himself; that disclosure does not establish that Grok automatically posted private information or that a card was fraudulently charged.

The company’s consumer FAQ already advises users against sharing personal or sensitive information in questions to Grok. Its October 11 privacy update adds an explicit responsibility clause beneath the payment-data section:

We cannot control what you provide us. You are responsible for all actions, including providing payment information and other actions, as if you had taken them yourself.

Card details can outlive a single shopping task

Grok Bot is designed to sign into websites and use tools on a persistent cloud computer. Its published terms, dated September 3, warn that data, browser sessions, credentials, memory and routines may remain in that environment. Bots belonging to the same user can share it, and deleting one Bot may not erase shared credentials.

Those terms call for appropriate human review before financial transactions. They also warn that approval and automated-review controls may miss harmful actions and cannot reverse completed ones. Handing over a card is therefore a decision about continuing access and spending authority, not simply another chat attachment.

The product page says its cloud computer is encrypted in transit and at rest, offers training opt-out and can route sensitive actions through automated review. Those protections matter, but encryption does not prevent an authorized agent from using information it has been given.

Payment-security rules also treat security codes differently from ordinary account information. The PCI Security Standards Council says merchants and service providers must not retain card verification codes after authorization, including for concierge-style future purchases. That standard does not, by itself, establish that this particular service has violated it.

Keep payment authority narrower than the task

Paying for a Grok subscription through an official checkout is a different transaction from placing a card photograph into an agent’s conversation. The privacy policy identifies processors including Apple, Google and Stripe for payments. Users should keep card entry inside verified payment forms and check the merchant before authorizing a purchase.

Anyone experimenting with agent-led shopping should use a limited virtual card where their issuer supports one, set spending limits and review purchases. A virtual card reduces the exposure of the main card number; it does not prevent every mistaken purchase or disclosure.

If card details have already been uploaded, remove the material and revoke unnecessary access, then contact the issuer about freezing or replacing exposed credentials. Check statements for unfamiliar charges. The safest task to delegate is finding the product and comparing prices, while retaining control of the payment.