It's Friday, September 4th: Welcome to The Stress Test 🔍

Apple documents exactly what your employer can't touch on a phone you own, and there is no equivalent line drawn around the work AI account you type into.

🔍THE STRESS TEST

IT Can't Read Your Texts. They Can Pull Your Chat Transcripts.

One safety story a week, pressure-tested for what's actually happening underneath the surface.

When you start a new job, you are generally given three options for keeping work and personal separate: take a company phone, add work email to the phone you already have, or keep the two completely apart and put nothing work-related on any of your personal devices.

I got that exact choice this week, starting a new job. If you have had that conversation, you know the worry: whether someone in IT can read your texts, see your photos, or tell where you are.

All three of those options are about hardware. Nobody in that meeting mentioned which AI account I would be typing into, and that turns out to be the one that decides how much of me my employer can read.

So let's stress-test what those three options actually keep separate.

Putting a work email on an iPhone you own runs through what Apple calls User Enrollment. Apple's documentation says organizational management there "is restricted to that Managed Apple Account and managed apps" and that a user's personal Apple Account and personal data "are never touched by management." Work data sits separately and is removed when the enrollment profile comes off, without affecting anything of yours. The company phone is the other arrangement, Device Enrollment, which Apple describes as giving the organization more controls and configurations. So the option that sounds like the compromise, putting work on my own phone, is the one where the documentation says my side is off limits. That holds only if your company enrolls personal phones that way. Some push the organization-owned configuration onto personal hardware instead, which is one question to IT and worth asking before you decide.

The account you type into is a different story. Anthropic's Compliance API gives Enterprise organizations programmatic access to the underlying chats, files, and projects in a claude.ai organization, plus transcripts of Cowork, Claude Code, and Claude for Microsoft 365 sessions. One access key reaches every endpoint. Nothing in the documentation says the person whose chats those are gets told.

None of that is hidden or unusual. Enterprises need legal hold and eDiscovery, every major vendor ships something equivalent, and Anthropic publishes the whole spec. It just moves the real boundary off the hardware and onto the login. A phone you own has a personal side that management does not touch. A work AI account does not have one. Everything you type there sits where your employer can reach it.

We have this backwards because a phone feels like the thing being invaded and a chat window feels like a room with the door shut.

I still haven't picked a phone option, but the half-formed 1am thoughts are definitely staying on my personal account.

Each week, we highlight AIC chapters doing groundbreaking work with their members around the world. Tag us on socials to be featured!

🌍 Hack for Humanity is live. Our global civic hackathon opened September 1 across 120+ chapters in 50+ countries and runs through October 31, building on the three themes our communities named in June: job displacement, technical literacy, and accessibility.

💡 San Francisco | My Luu and Holly Uber Host Founders at Hanwha AI Center

Image from My Luu

Last week, The AI Collective gathered at Hanwha AI Center for an evening co-hosted by My Luu and Holly Uber. The room became a space for real conversations, with people sharing the hard things they were navigating and leaving with clearer next steps. Thank you to the volunteers and behind-the-scenes team who made the night possible. This is what community looks like: showing up honestly, listening closely, and making room for one another.

🚀 San Francisco | SF Demo Night Gives 8 New Teams the Stage

Image from AI Collective

SF Demo Night brought The AI Collective and Roam to the AWS Builder Loft for live demos, audience questions, and community voting. Eight early-stage teams took the stage, with the room doing what this community does best: asking sharp questions, sharing feedback, and making new connections around ambitious ideas. The next founder on that stage could be you. Join The AI Collective here.

🫵 Want your message in front of 200,000 AI builders?

Our partners and sponsors get exclusive placements across the newsletter and access to AIC's in-person network — demo nights, dinners, hackathons, and forums across 180+ chapters.

For all inquiries, send us a note at [email protected].

The AI Collective is built by volunteers across 180+ chapters in 40 countries.

Thank you to the thousands of volunteers around the world who make this work possible. We truly could not do this without you.

🧑‍💻 About the Editors

Noah is a researcher, innovation strategist, and ex-founder thinking and writing about the future of AI and the workforce. His work and body of research explores the economics of emerging technology and organizational strategy. Outside of AIC, Noah heads research for Centaurian AI.

About Joy Dong

Joy is a news editor, writer, and entrepreneur at the intersection of AI and blockchain. Whether she is demystifying complex systems in her newsletter TEA. Joy’s mission is to make emerging tech accessible and actionable for everyone.

Lindsay is an AI engineer, researcher, and writer focused on how AI systems behave in practice and what it takes to make them safe. Her work sits at the intersection of AI safety, governance, and product design. At AIC and in her newsletter, Hidden Layer, she writes about the questions that matter most as these systems scale.

Add Your Thoughts

Avatar

or to participate

Keep Reading

View more