Personal vs work accounts (and why it matters)

Dev’s work ChatGPT flashed a limit at 4:40pm. The churn export was still open in Sheets: 19 rows, customer_id, months_active, last_invoice, and a notes column with three personal emails sitting in plain text. He already had Plus on a personal Gmail from weekend scripts. He switched tabs, pasted the sheet, and asked for the top three churn drivers. The work tenant never saw the file. Legal asked on Friday where the export lived. Nobody could find it in the company workspace.

This is Part 9 of Phase P, and Part 3 of AI setup from zero. Part 1 opened the account and the card. Part 2, browser vs mobile vs desktop, picked the surface. This part is the identity: personal vs work, and why the email (or SSO) on the login is the legal person in the room. The chooser stays at Which AI product should I use?. As of writing (August 2026), confirm the live admin screen the week you click.

What you’ll learn

• Why the email or SSO on the account is the legal person, not the tab you meant to use
• What “Sign in with Google, Apple, or Microsoft” glues, and why you often cannot unglue it
• How ChatGPT Business / Enterprise, Claude Team, Gemini for Workspace, and Copilot on Entra differ from consumer seats
• What IT can see (usage, retention, e-discovery) and what a personal Plus hides from legal
• A this-week rule: one personal box, one work box, and never a 19-row customer sheet in the personal one

The email is the legal person in the room

A chat looks like a window. The vendor treats it like a contract. The identity on the login is the customer: you, or your company. If the avatar shows dev.personal@gmail.com, the 19 rows sit in a consumer account, even if the prompt said “summarize churn for the Q3 board.” If the avatar shows the company Google and you paste a kid’s history essay, that essay is now org data. The window did not care about your intent.

Part 1 already said pick the identity before the plan. Retention, training defaults, who can export the thread, and who owns the file after you quit all follow the login, not the topic. A new tab does not create a new legal person. Keep both boxes if you need them. Split the email if it is doing two jobs.

Rule of thumb: The email (or SSO) on the account is the legal person in the room. Do not sign a client draft in with a shopping Gmail. Do not sign homework in with the company Google.

Sign in with Google, Apple, or Microsoft

The big buttons are convenience. They are also glue. “Sign in with Google” means this product now treats that Google account as the identity. Same for Apple and Microsoft. ChatGPT’s own help (as of writing) is blunt: if you started with a social login or SSO, you generally cannot later switch that account to a plain email and password. Enterprise customers can sometimes get a reset through their rep. Consumer accounts stay glued.

The Google you click might be the wrong Google. Chrome is logged into photos and shopping. The work Google is the other chip in the account switcher. You tap the blue button at 4:40pm and you have signed a client file into the photos identity. Apple is worse on a work laptop, because the personal Apple ID is already signed into the App Store from the $19.99 duplicate in Part 1. Microsoft is a personal Outlook vs an Entra work account. Connectors follow the same identity: ChatGPT’s Google app (as of writing) can only see the Google you chose, and a second Gmail replaces the first. Connecting work Drive to personal Plus is still a personal Plus with a work Drive attached.

1. Open the avatar. Read the email out loud. Gmail, iCloud, or a personal Outlook means the personal box.
2. A company domain means the work box, even if you opened the tab from home.
3. “Sign in with Apple” on a managed Mac still lives with the Apple ID, not with IT.
4. If the work Google is also how you pay Plus on your Visa, you already mixed billing and identity. Fix the login before you add files.

Work seats vs consumer seats

Consumer ChatGPT (Free, Go, Plus, Pro), Claude Free / Pro / Max, Gemini on a personal Google, and Grok on grok.com or X are personal products. You are the customer. You pick the data controls. There is no company admin and no e-discovery hold. If a vendor trains on consumer chats unless you opt out, that toggle lives in your settings. Read it.

Work seats are a different product family even when the chat looks identical. Names move. As of writing, OpenAI sells work ChatGPT under Business and Enterprise (Team was the earlier label). On those seats the company is the customer. Business data, including conversations, files, and outputs, is not used to train models by default. Qualifying orgs can set retention. Admins manage members and SSO. Enterprise adds user provisioning, audit logs, and a compliance export path. That is the seat Dev bounced off at 4:40pm. A limit there is annoying. Pasting the same sheet into personal Plus does not inherit those controls.

Claude Team (as of writing) wants a business email and at least two members. Upgrading from Pro on a work email creates a new organization. Personal Free / Pro / Max stays separate unless you migrate chats, projects, files, and memory into the Team org. Once content is in the organization, it cannot move back. Enterprises can claim the company domain, so you@company.com on a personal Claude may get pulled. Gemini on a work Google is not your photos Gemini. Where Gemini Apps is a core service on the Workspace license, chats are not used to improve generative models. Where it is only an additional service, they may be reviewed and used to improve Google’s products. Check the badge at gemini.google.com. Copilot on a work Entra account gets enterprise data protection; prompts can show up in Purview e-discovery. Grok is personal unless IT bought a written deal.

What IT can see

People hear “admin” and picture a manager reading every prompt at lunch. That is rarely how it works, and it is the wrong comfort. The honest picture is records, not a nosy human on a stool.

On work ChatGPT, admins can see usage, manage members, and (on Enterprise) pull audit-style logs. They may not live in your Tuesday draft. They can reconstruct that a file was uploaded, by whom, and when a hold lands. On Claude Team, the org owns the workspace once you are in it. On Gemini for Workspace, Keep Activity is on by default for 18 months unless an admin sets 3, 18, 36, or off. You cannot flip that yourself. Work users also cannot delete chats in the Gemini mobile app the way a personal Google can. Education tenants can search Gemini conversations in Vault. Copilot on Entra logs prompts into the same compliance world as mail.

Personal Plus hides the thread from IT. For a customer churn sheet, that is a hole. Legal cannot find the 19 rows in the tenant. The vendor still has them under consumer terms. If you opted into training, or never found the toggle, the sheet may sit in a consumer training pile. The company cannot issue a deletion request the way it can against its own workspace. You have made the file both more public (vendor consumer policy) and less findable (no work record).

Two mixes that create a record you cannot unsay

Mix A is Dev: customer data in a personal box because the work seat hit a cap. Mix B is Sunday-night homework in the company Google because that was the logged-in chip. One leaks outward (the vendor’s consumer world). One leaks inward (the company’s retention and e-discovery). Deleting the visible thread does not fix it. Consumer backups and admin retention do not follow your trash can. A kid’s essay in work Gemini can sit for 18 months and show up in a lawsuit that has nothing to do with homework.

A third mix: you opened ChatGPT with the work Gmail in 2024, paid Plus on your Visa, and now IT buys Business. Domain claim or a Team invite later, and that history may be treated as company property. Claude’s migrate path is one-way on purpose. If the writing was personal, move it to a personal address before someone claims the domain. A fourth mix is the laptop. “Sign in with Apple” on a managed Mac still belongs to the Apple ID. IT’s MDM can wipe the device. It cannot produce that chat for a client audit. Pick the browser profile the same way you pick the email. Part 2 covered surfaces. This is the login sitting on those surfaces.

Worked example: 19 rows in the wrong box

Here is the sheet Dev pasted. Toy numbers, labeled as an example, in the shape of a real churn pull: 19 customers, a notes field nobody should have left in the export.

Sixteen more rows like that. Three had personal emails. One had a cell number. Dev asked personal Plus for “top 3 churn drivers, keep it board-ready.” Friday, legal asked for the export as part of a customer complaint on C-1108. The Drive folder had the original Sheet. The AI draft lived only in Dev’s Gmail Plus history. No workspace log of the upload.

Fix, in order. Wait out the work-seat limit, or ask IT whether a higher cap or a different model exists on the same login. Do not open the personal tab as overflow. Strip notes, emails, and phone numbers before any upload (the files part of this series comes after 2FA). If the paste already happened, copy the useful draft into a work doc by hand, stop using the personal thread, and tell whoever owns privacy that a consumer account saw the 19 rows.

A checklist you can paste into the team note from Part 1:

Identity checklist (one block per product)
Product: [ChatGPT / Claude / Gemini / Grok / Copilot]
Login email in the avatar: [ ]
Sign-in method: [password / Google / Apple / Microsoft / company SSO]
This login is for: [personal | work]
Work files allowed here: [yes / no]
If the seat hits a limit: [wait | ask IT | switch model in the SAME login]
Do not open the other box as overflow
Kids / homework / medical: never on the work login
Customer names, emails, 19-row exports: never on the personal login
Connectors (Drive, Gmail, GitHub): only on the matching identity
Screenshot date: [ ]
Owner: [Dev]

If the avatar email is Gmail and the task is C-1108, stop. If the avatar is the company domain and the task is a seventh-grade essay, switch.

Common mistakes

• Treating a work-seat limit as permission to overflow into personal Plus.
• Clicking “Sign in with Google” while Chrome is on the photos account.
• Opening Claude Pro with you@company.com, then being surprised when the domain is claimed.
• Connecting work Drive to a personal ChatGPT “so the files are handy.”
• Using the company Gemini for a kid’s homework because it was already logged in.
• Assuming deleted personal chats are gone from the vendor, or that IT can see personal Plus if they need it for a case.

How to practice this week

Open each AI product you use. Screenshot the avatar email. Fill the checklist once per product. If a customer file already sits in a personal history, stop pasting more and tell privacy. If personal writing sits under a work domain, copy it out to a personal login before someone claims the domain. Next in this series: 2FA, recovery, and shared family or team plans (Part 4 of setup, Part 10 of Phase P). Identity comes first. The chooser stays at which door. Related: P1 writing, P2 coding, P3 files, P4 privacy, Learn, and Practical AI.

Quick recap

• The email or SSO on the login is the legal person. Intent does not override it.
• Sign in with Google, Apple, or Microsoft glues that identity. Check the avatar before you paste.
• Work seats (ChatGPT Business/Enterprise, Claude Team, Gemini for Workspace, Copilot on Entra) are company contracts. Consumer Plus is not a backup seat.
• IT can retain and export work chats. Legal cannot find a 19-row paste that only lives in personal Gmail.
• One personal box, one work box. Never customer files in the personal one. Never homework in the work one.

Sources

• OpenAI: changing ChatGPT sign-in method (Google, Apple, Microsoft, SSO glue)
• OpenAI: business data privacy (work seats, training default, retention, admin controls)
• OpenAI: ChatGPT Enterprise (SSO, admin, compliance language as of writing)
• Anthropic: get started with the Team plan (business email, separate personal org, one-way migrate)
• Google: Gemini Apps with a work or school account (core vs additional service, 18-month Keep Activity, admin control)
• Microsoft: enterprise data protection for Copilot (Entra work identity, logging, commercial terms)
• OpenAI usage policies and Anthropic usage policy (what you may put in a chat)
• AMS: AI setup from zero (this series)

More definitions in Key Terms →

Merch on Etsy

Open store →

Mute Mouse Pad, Data Science Mouse Pad, Analytics Mouse Pad, You're On Mute View on Etsy → You're On Mute White Ceramic Coffee Mug, Data Science Mug, Data Mug, Analytics Mug, Statistics Mug, Programming Mug, Gift Mug, Coffee Mug View on Etsy → Boxplot Mouse Pad, Data Science Mouse Pad, Analytics Mouse Pad, Box Plot, Whisker Plot View on Etsy → Naive Bayes Mouse Pad, Data Science Mouse Pad, Analytics Mouse Pad, Bayesian Mouse Pad View on Etsy →