“BYO key” feels cheaper than a firm workspace. For Workday client data it creates a clear controller/processor confusion: the prompt leaves the laptop toward whichever OpenAI or Anthropic account owns the key.
What vendor defaults imply
OpenAI states that by default it does not use API Platform inputs and outputs to train models. Anthropic states commercial API/Team/Enterprise terms do not train on Claude Code prompts unless the customer opts into a partner program. Those statements are about training, not about who is responsible under your client MSA.
Retention still exists on commercial terms (Anthropic documents a standard 30-day retention for commercial Claude Code unless zero data retention is enabled for a qualified organization). OpenAI API data handling is described in OpenAI’s API data docs—re-check them for the current retention language before you brief a client.
Minimum firm rules
- Firm-owned keys or firm workspace only for client Workday content—or an explicit zero-retention product path.
- Keys in the OS keychain / firm secret store, not in chat logs or shell history committed to git.
- Offboarding rotates or deletes the key the same day Workday access is removed.
- Written record of which provider account may see which clients.
Silent BYO is how shadow AI becomes the real processor while the MSA still names the firm.