Best practice for user deletion when user data is stored in multiple locations

I am using a custom database connection in my auth0 tenant.

When a user decides to delete their account, I notice that I should not be attempting to delete the record(s) directly via the database but rather should call auth0 to do it on my behalf.

That’s totally fine, but here’s my conundrum:

The user data is stored across multiple collections (tables for the SQL heads) – so, in this case, would it be best practice to append to the auth0 deletion script such that that script will handle the rest of the necessary deletions across all collections or should I call auth0 to delete the user record it directly manages and then delete the other collections via my API?

Thanks for any info.

Actually, I just noticed that deleting a user in the auth0 management panel (via the UI, haven’t tried the management api yet) that is using a custom database connection does not actually result in that user being removed from the database.

The same is true in reverse if the user is deleted from the database.

How and when do these two sync?

Furthermore, I noticed that when blocking a user the database record is not updated. This seems to indicate that some information is still stored in auth0 and some is stored in my database.

Edit: Tried deleting with management api, does not affect custom DB.

I don’t understand. I guess this feature is not at all what I was expecting.