Real answer.
there are three types of repositories. private, public, and internal. Internal ones require an enterprise account, so we'll forget about them for now. :)
Any fork of one of those retains it's type. Forks of public repositories are public, and forks of private ones are private. Removing access to a private repository deletes that person's fork.
Deleting a private repository deletes all forks of it, which are also private. If you wish to keep a copy, you have to clone and publish it yourself. Which might not be allowed by the code's license. Deleting a PUBLIC repository makes all of the direct forks new masters.
Only the master can be changed from private to public, or vice versa.
Doing either disconnects all forks, and makes them into new masters, all retaining their existing type.
If you wish to delete your private repository while not deleting the other (private) forks, make it public first, which will make all of the private forks into private masters, then delete the repository.
TL:DR; If the repository is public, your fork is public, and stays forever. If the original is private, your fork is private and will vanish if the master does or you do not have access anymore, and you will have to clone and update repeatedly to be sure of keeping it.
This should hopefully answer all questions about forking and deleting. :)