I assume that the account is not usable after this. So it is a logical delete and the physical delete is scheduled. I don’t know what would be a better way to phrase it, that would not confuse the users.
I am not trying to defend google, I just had similar UX issues at work.
Correct. Google is banking on users getting withdrawl and crawling back. They all do the same thing, like Meta products. They give you 30 days before deletion because they know most people are addicted and will recover their accounts.
Could be, but it’s more likely that the delete gets put into a message queue and gets processed when the deletion service can handle it. These large deletions are computationally expensive.
Its similar to why the exports take so long to process
It’s like how most people call moving a file into the trash can “deleting.” It is deleted (in a sense), but you can still recover it if you want before the trash can gets emptied.
Or like how even you can actually delet a file from the disk but still be able to recover it before the disk space is overwritten by other files. I’m not saying that this is what Google does when you recover a freshly deleted account (most likely not), but what I’m trying to say with these two examples is that being able to be recovered is not a contradiction with having been deleted
Also I don’t get why you take problem with this. It’s not like it’s another loop to jump through to get to delete the account?
🙄
At least write “is scheduled to be deleted” to make the lie not as obvious.
I assume that the account is not usable after this. So it is a logical delete and the physical delete is scheduled. I don’t know what would be a better way to phrase it, that would not confuse the users.
I am not trying to defend google, I just had similar UX issues at work.
Correct. Google is banking on users getting withdrawl and crawling back. They all do the same thing, like Meta products. They give you 30 days before deletion because they know most people are addicted and will recover their accounts.
Could be, but it’s more likely that the delete gets put into a message queue and gets processed when the deletion service can handle it. These large deletions are computationally expensive.
Its similar to why the exports take so long to process
It’s like how most people call moving a file into the trash can “deleting.” It is deleted (in a sense), but you can still recover it if you want before the trash can gets emptied.
Or like how even you can actually delet a file from the disk but still be able to recover it before the disk space is overwritten by other files. I’m not saying that this is what Google does when you recover a freshly deleted account (most likely not), but what I’m trying to say with these two examples is that being able to be recovered is not a contradiction with having been deleted
Also I don’t get why you take problem with this. It’s not like it’s another loop to jump through to get to delete the account?
Could still be actually deleted, but there’s backups. Technically true.
If you can recover my Data then my Data is NOT deleted.
Just a copy of it, yes.
I mean technically deletion just means to allow the computer to overwrite the data but until this happens it can be recovered.