In that case, it’d probably be best to just handle deletions at the application layer (e.g., setting a “deleted_at” timestamp field with scheduled permanent deletions later).
And in terms of data compliance, it’s very important to make sure permanent deletions propagate through your backup systems within a reasonable amount of time - Google Cloud[1], for example, is ~180 days.
Surprisingly enough, it's even simpler than that. You can trivially access a direct URL that serves the entire video or audio (they're served as different files).
Just open up DevTools, look for requests to googlevideo.com, find the request with the video or audio (i.e. content-type response of either video/mp4 or audio/webm), copy the entire request URL, remove the range parameter entirely, open the link, and voila!
And in terms of data compliance, it’s very important to make sure permanent deletions propagate through your backup systems within a reasonable amount of time - Google Cloud[1], for example, is ~180 days.
[1] https://services.google.com/fh/files/misc/gcp_data_deletion_...