---
title: "BYO API Keys on a Workday Consultant Laptop: Who Is the…"
description: "Personal OpenAI or Anthropic API keys on a laptop create a processing path outside the firm’s workspace. Align MSA, DPA, and key ownership before client work."
url: https://kiweely.com/blog/byo-api-key-workday-consultant-laptop
---

# BYO API Keys on a Workday Consultant Laptop: Who Is the Controller?

A personal API key means the consultant’s provider account processes prompts. Firms need written rules for key ownership, logging, and offboarding—not silent BYO.

-   By Kiweely
-   November 15
-   Updated November 16
-   1 min read

“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

1.  Firm-owned keys or firm workspace only for client Workday content—or an explicit zero-retention product path.
2.  Keys in the OS keychain / firm secret store, not in chat logs or shell history committed to git.
3.  Offboarding rotates or deletes the key the same day Workday access is removed.
4.  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.

## Read next

[All posts](https://kiweely.com/blog)

-   [November 15 ### Why Shared Integration System Users (ISUs) Are a Security Risk for Employee AI Chatbots](https://kiweely.com/blog/why-integration-system-users-are-dangerous-for-workday-ai)
-   [November 15 ### Mapping Microsoft Teams, Slack, DingTalk, and Lark Identities to Workday Worker OAuth](https://kiweely.com/blog/mapping-teams-slack-lark-sso-identities-to-workday-workers)
-   [November 15 ### How Workday’s Twice-Yearly Releases Break In-House MCP Servers and REST Integrations](https://kiweely.com/blog/how-workday-twice-yearly-releases-break-custom-mcp-servers)

### More guides on Integrations and APIs

[All 89 guides](https://kiweely.com/guides#integrations)

-   [Updating Preferred Name, Pronouns, and Contact Information via the Workday Person API](https://kiweely.com/guides/workday-person-api-legal-preferred-name-contact-updates)
-   [Restricting Workday OAuth Token Use by IP with Maintain IP Ranges](https://kiweely.com/guides/workday-maintain-ip-ranges-manage-authentication-policies-api)
-   [Why Browser Single-Page Apps Hit CORS and Token Limits Against Workday APIs—and How to Fix It](https://kiweely.com/guides/workday-cors-browser-api-calls-why-backend-pass-through-needed)
-   [Parsing Workday Business Process Custom Validation Errors Returned by REST and SOAP APIs](https://kiweely.com/guides/workday-business-process-validation-errors-rest-soap-responses)
-   [How Workday Audits Business Processes Initiated via REST or SOAP Web Services](https://kiweely.com/guides/workday-business-process-audit-trail-initiated-via-web-service)
-   [Approving, Denying, and Sending Back Workday Business Process Steps via REST and SOAP APIs](https://kiweely.com/guides/workday-business-process-approve-deny-rest-soap-api)
-   [How Workday Studio PutIntegrationMessage Severity Levels Control Completed-with-Warnings vs. Aborted Runs](https://kiweely.com/guides/workday-studio-error-severity-critical-warning-abort)
-   [How to Fix Workday Studio SDKProfile Not Current and Unsigned Software Startup Errors on Mac and Windows](https://kiweely.com/guides/workday-studio-sdkprofile-not-current-unsigned-macos-errors)

## Your Workday work, done by AI.

Kiweely Vine is the AI agent that builds, deploys and tests Extend apps as real people, makes changes in any Workday task screen, answers from your real tenant and builds reports.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next one in your inbox.

One email a month for Workday teams: what’s changing in Workday and what to retest, one tip tried in a real tenant, and what’s new at Kiweely.
