Forms and submissions
A form reaches a page via a module that looks it up by slug; submissions live in a table with no hard link back — trashing the form hides them.
A form is an ordinary content node — its fields, its steps, the success message, the redirect URL and the notify-on-submit addresses all live on that one record, so building, editing and trashing a form works exactly like any other content.
How a form reaches a page
The form and formEmbed modules place a form on a page by its slug, not by a fixed reference to the record you built — rendering, validation and the success behaviour are all looked up fresh from the form definition at the moment someone visits the page. Change a field on the form and every page embedding it picks up the change immediately; there's nothing to republish on the page side.
Where submissions live
A submitted entry is stored in a table of its own, keyed by the form's content id — but that key isn't a hard database link back to the form. Unlike version history, which is set up to be removed automatically when its content is, a submission has no such tie: nothing in the database keeps the two in step for you.