If you have a free tier with only public content allowed, and a paid tiers that allow paid content... you're going to have to do one of two things when someone cancels:
A) delete a lot of their stuff, or
B) make all their stuff public
Either could be really, really bad.
You could let the user pick between the two options, I guess. But really, most everyone cancelling something like this needs to go through their stuff and decide for each item: "Keep, but make public" or "Delete".
> You could let the user pick between the two options, I guess.
If both options are likely to be extremely undesirable to a substantive fraction of canceling users, that's the best option.
If there was a most-likely-safe option from the user perspective, choosing that by default and having it confirmed would arguably be better UX, but I don't think "keep everything that used to be private and make it public" is really a "clearly-safer option". Nor, even in the cases where it is safer, do I think that this presents the confirmation well.
> But really, most everyone cancelling something like this needs to go through their stuff and decide for each item: "Keep, but make public" or "Delete".
Some people do, but I bet lots of people have collections that very easily fall into either "Delete all" or "Keep all and make public" by the time they cancel (if only because they are only canceling after everything to which that decision wouldn't apply has been migrated to an alternative service.)
A) delete a lot of their stuff, or
B) make all their stuff public
Either could be really, really bad.
You could let the user pick between the two options, I guess. But really, most everyone cancelling something like this needs to go through their stuff and decide for each item: "Keep, but make public" or "Delete".