You just answered yourself: so people will keep the history on and they can keep training on the data.

Beyond being a dark pattern, it's far easier to build a product that simply doesn't save things that could cause trouble. You can't have someone "accidentally" use a set of data if that data never exists. You can't have another integration accidentally fail to filter out "bad data" if it doesn't exist.

I've used this pattern in a few side projects. I never, ever have to worry about accidentally storing/moving/integrating data that doesn't exist.

Expediency. Perhaps they'll separate the two later on, because this is the fastest way to get to some easy user control right now. They're in a hurry to make this available while GPT is blowing up in usage/popularity with the public, to help reduce the blowback on privacy.

The US Congress for example just purchased a bunch of licenses to start messing with ChatGPT at their offices.

I assume because it's a hassle for them. I've noticed that when busy they have issues with chat history right now. It could also be tightly coupled and just a pain to remove right now. We have no idea how the app was built.

I think you have answered your own question.

Somewhat more charitably though it could be that it’s far easier to ensure you never train on something you don’t store.

My hope is that if they aren't showing us the history then they literally aren't keeping it _at all_ (though they might keep it 30 days still for LE?).

That's probably just a dream and they just want to push you into keeping it on while they keep it for later just in case?

On the bright side this can be fixed with a client side extension :D

Why would a user want to disallow training?