Basically, when you're talking OLTP write heavy applications, rule #1 is never really delete anything. Doing so becomes heinously expensive in terms of having to lock tables and update indices, so on, and so forth. This is a hard lock situation. I.e. No further transactions can be processed until such time as the deletion completes can be processed. Most systems therefore set a "deleted" flag, which causes the system to act as if the deleted thing is actually deleted, while actually just leaving the information alone.
This works great, as long as everywhere in the system actually honors it. That is not a given. If you were relying on actually being able to make that disappear, however, you're SOL.
Not sure what Google is doing in terms of data architecture/persistence mechanisms nowadays, but it sounds to me like they may just be using a deleted flag.