Don’t leave generative AI
on personal accounts

Written by Kazuo Yutani, Representative of Metamorphose LLC. Observations from PMO work on what happens after generative AI goes live at financial institutions and corporate teams. Metamorphose offers the Metamon generative-AI usage diagnostic; this article is about keeping personal accounts off the register, and it applies equally to another provider’s assessment or an in-house exercise.

Before the register — don’t leave work on personal accounts

Not putting the AI lead in IT alone is a separate article. So is the order in which company accounts are handed out (rollout order). This article is only about not treating personal subscriptions and personal logins as the place where work lives.

NG (treating the personal side as the place of record)

Work that runs on someone’s personal ChatGPT Plus is listed as where the company’s generative AI lives

The company tenant can be handed out. The floor may be running things on the personal side anyway. Personal use itself isn’t the problem. What you cut first is putting personal accounts on the register.

OK (the one line that lives in the company tenant)

Customer Support runs first-response drafts in the company tenant. Personal accounts (shadow AI) are not on the register

“We’re using it” shouldn’t rest on a self-report from the personal side. Attach the company tenant’s log or a confirmation from the owner. You don’t need to issue a shadow-AI ban first. What you cut first is the place that goes on the register.

This is a split that fits your own usage policy. We don’t make that decision on your behalf. This article is not legal or policy advice.

What tends to remain a quarter after leaving it personal

What was kept first	What tends to remain at the next meeting
Work ran on personal ChatGPT accounts	“We’re using it” comes back. Whether it runs in the company tenant can’t be stated
Personal use was declared “at your own risk”	The ban stays. No single task gets put on the register
A company-wide shadow-AI survey was run	Responses come in. No one line for the company tenant

The first one weighs the most. “We’re using it” from the personal side doesn’t go on the register. Write only the work that runs in the company tenant.

Before work runs on personal accounts, check the one line for the company tenant →We separate the task that belongs in the company tenant from what shouldn’t stay on personal accounts. Our diagnostic (Metamon) starts from that one line. No plan document

What goes in the company tenant, and what stays off the register

Target	Treatment
The task to put in the company tenant first	Can name the one task on the spot. The register and the user list live here too
What shouldn’t stay on personal accounts	Goes on neither the register nor the user list. Before any ban, keep it out of the mix
What moves once the policy is settled	Move it into the company tenant after storage location and data-transfer rules are fixed under internal policy

Don’t ban all personal use at once. A blanket ban defers the blank at the next meeting.

Which departments get accounts, and in what order, is a separate article (who receives a company account). This article comes after that: not putting work that runs on the personal side onto the register.

If you bring in an external assessment, “the one line in the company tenant” is easier to work with than a company-wide survey (our Metamon works on the same premise). A first conversation starts from that one line. Whether to order an assessment or sign anything can wait until you have seen the result of the cut.

The note you can write in-house before the meeting — not a plan document

Department	Category	The one line for the company tenant
Customer Support	Put in first	First-response drafts run in the company tenant only. Personal accounts not on the register
Sales Planning	Not left personal	— (on neither the register nor the user list)
IT	After the policy	— (not moved until storage location and data-transfer rules are settled)

The one line for the company tenant shouldn’t rest on self-reporting alone. Attach one of: a log, a ledger, or a confirmation from the owner.

You don’t need a plan document to take personal accounts off the register. These three columns are what you can write in-house before the meeting. When you contact us, no plan document or internal material is needed either. The form only needs “the company-tenant line” (e.g. Customer Support | first-response drafts | company tenant only) or the name of a department that shouldn’t stay personal (leave it blank if unsure).

No need to hand over a draft company-wide ban first. What the meeting wants is the one line that lives in the company tenant.

---

References
Distribution order: Company-wide rollout starts with one department
How to measure: The three generative-AI adoption metrics
Our service: Metamon (generative-AI usage diagnostic)

This article is a general framing, not legal, regulatory, or contractual advice. Whether personal generative AI use is permitted depends on your own policies and the department responsible.