Where a form submission goes, and how long it stays

The journey a message takes

The visitor types into a form. The page sends it to a server. The server hands it to a mail service. The mail service delivers it to your inbox.

Along the way it may pass a spam filter, a logging system and a backup. Each of those can hold a copy for its own period.

None of this is sinister and all of it is worth knowing, because a customer asking you to delete their enquiry is asking about all of it.

Knowing the route matters on the day somebody asks you to delete their enquiry, because the honest answer covers every stop rather than the one you can see.

What a form should ask for

The least that lets you reply. A name, one way to reach them, and what they need.

Every extra field is data you now hold, protect, explain and eventually delete. Ask the rest in your reply, where the person can choose what to share.

This is also why our forms carry a short note asking people not to include medical, health or other sensitive details in the message.

Every field is also a small tax on the visitor, which is why shorter forms get finished more often — the point made from the usability side in accessible forms.

Why that note matters

People volunteer far more than you asked. A clinic enquiry can arrive with a diagnosis in it. A legal enquiry can arrive with facts the sender should not have put in writing.

You did not request it and you now hold it. The note reduces how often that happens, which is better for both sides.

If your trade regularly attracts sensitive detail, say in your reply how you would rather receive it.

Setting a retention period

Pick something you can keep to. Enquiries that became jobs stay with the job record. Enquiries that went nowhere can go after a set period.

Write the period down, put it in your privacy policy, and set a recurring reminder. A policy nobody follows is worse than none, because it is a written promise you are breaking.

Short is easier. Less to search, less to explain, less to lose.

Tie the review to something that already happens, such as the end of a quarter. A period nobody has a reminder for is a promise you will break without noticing.

Deletion in practice

Deleting means the inbox, the archive, the spam folder, any forwarded copy, and any system you exported into.

Keep the list of places short so deletion is actually possible. A form that posts to four different tools is four deletions nobody will do.

If you cannot delete from somewhere, know that before you promise you can.

• The inbox itself
• The archive or All Mail folder
• The spam folder, where a copy often sits unnoticed
• Any address the message was forwarded to
• A CRM or spreadsheet you exported it into
• Your phone, if mail is synced there too
• Backups, which is the one you usually cannot reach

Keeping it out of the wrong hands

No email address should appear on your public pages. Publishing one invites the spam that buries real enquiries, which is why the contact form is the route here.

Use a strong password and two step verification on the inbox that receives enquiries. That inbox is where your customer data actually lives.

Every page written by Website Builder Studio passes a check that runs before anything publishes, validated against Google Search Essentials and modern web standards, and forms here post to your own site rather than to a third party.

Two step verification on the receiving inbox is the single highest-value thing on this page. That inbox holds more customer data than the website ever does.

What to tell people

One or two plain sentences on the contact page. What you use the message for, who else sees it, and roughly how long you keep it.

That answers the question before it is asked, and it makes the privacy policy a confirmation rather than a surprise.

Nothing here is legal advice. Retention rules differ by trade and by state, and some records you are required to keep for a set period.