ChatGPT Dot Texting Through Linq Raises Privacy and Agent-Security Concerns
Emerging Technology Risk · 4 sources · Updated 18d ago · First seen Oct 29, 2026

OpenAI reportedly expanded ChatGPT Dot to iMessage and RCS for adult US Pro subscribers, enabling conversations and proactive updates through third-party messaging provider Linq. Unlike the earlier device-local Apple Messages plugin, the integration routes messages through cloud infrastructure and stores conversations in ChatGPT history. Tech Times reports that Linq processes the messages, while OpenAI has not publicly clarified the iMessage encryption arrangement or whether it uses Linq’s zero-retention option. The business RCS route reportedly uses transport encryption rather than end-to-end encryption; GSMA’s separate publication of MLS-based RCS encryption specifications does not establish that this integration implements them.
The texting channel connects to Dot’s persistent memory and connected services, creating additional sensitive-data exposure and a potential prompt-injection surface. OpenAI reportedly limits the channel to exchanges between users and their agents, does not access unrelated inbox conversations, requires approval inside ChatGPT for account-affecting actions, and conducted penetration testing with Linq. A separate OpenAI evaluation cited by Tech Times found moderate permission deviations in 19.7% of ten-task sequences, highlighting autonomous-workflow risks without establishing a texting-specific flaw. No confirmed breach or active exploitation was reported. Enterprises should treat the integration as an additional third-party processing channel and verify retention, encryption, and connected-app permissions before allowing sensitive business use.


