OpenAI turns Apple's BYOD habits into its trade-secret defense

Someone photographs a whiteboard on a managed iPhone and the image lands in a personal library, because that is the account signed in for Photos. Users tend to keep work in whichever account syncs without a support ticket. Teams tend to assume the opposite: that work stays in the corporate tenant while the personal account holds nothing but holiday pictures. The BYOD pitch is usually about meeting people where they already work. The thing being done is moving the account of record outside the company.

The two practices OpenAI attributes to Apple push information both ways at once, work product out into personal iCloud accounts and personal messages in to corporate monitoring ^[4][15]. The inbound half is the awkward one for an employer. Monitoring produces records, records are discoverable, and what they document is an environment where the line between company and personal was crossed by configuration long before anyone resigned.

Trade-secret law generally asks whether the owner took reasonable measures to protect the information ^[8]. TNW's read is that Apple's policies on devices, accounts and data could become an important part of the case rather than background to it ^[9]. That is OpenAI's August theory stated plainly in its motion to dismiss: "Apple cannot transform the foreseeable consequences of its own systems and policies into evidence of theft" ^[5]. California leaves Apple little else to work with, since non-compete agreements are largely unenforceable there ^[10], which means preventing the transfer of confidential information has to run through trade-secret law rather than through limits on where a former employee can work ^[17].

The documented moves so far are the July complaint, the August motion to dismiss, Monday's filing, and a public post arguing Apple is getting this wrong, three of them court filings ^[14][7]. The fourth is aimed at the hardware engineers deciding whether to return a recruiter's call, and OpenAI has been hiring exactly those people for the device family Greg Brockman has confirmed it is building ^[11]. TNW also reports the case is already creating delays in that programme ^[13], so the injunction fight matters to OpenAI's schedule whatever the merits turn out to be.

For whoever owns the device profile, the useful exercise is smaller than a policy rewrite. Take the five artifacts you would least like to see at a competitor and name, for each, the account of record and the person who can enumerate every copy. Then plot two axes: does work product live only in accounts the company controls, and does personal content end up in logs the company keeps. The single quadrant where you can later prove what left is yes on the first and no on the second. Convenience puts you in one of the other three, and the invoice arrives as a discovery request, years after the admin who approved the setup has moved on.