Secure online forms, and how to tell if yours is one.
You collect names, phone numbers and whatever people type into the message box. Most people worry about the trip from the browser to the server. The trip is fine. The risk is every copy that exists by Friday.
Where a form leaks, and it is rarely the form
A form is secure when every stage between the visitor typing and you reading is protected. Most audits look hard at the first stage and wave the rest through.
The notification email
The submission lands in an inbox as plain text. It is forwarded to whoever handles quotes, then on to the technician doing the job. Three inboxes, none of them yours, each searchable by anyone with the login.
The export nobody deleted
Somebody pulled a spreadsheet for a report in March. It is in a downloads folder on a laptop that has since been to a conference.
The shared login
One account, four people, one password in a group chat, a common way form data gets seen by someone it was not meant for. No amount of protection on the form itself touches it.
Asking for more than you need
Every field is a liability you volunteered for. A date of birth you never look at is still a date of birth you are holding.
No spam handling
A form with nothing in front of it fills with junk. Real enquiries get lost in it, and the person doing the sorting stops reading carefully by about the fortieth one.
Four of those five are about what happens after the submission lands.
How Lead Source protects a submission
- A submission is covered from the moment it is sent: in transit to us, and again once it is stored. Those are separate protections, and both are in place.
- The database itself decides who can read what, rather than application code. Each account’s leads are walled off from every other account by default, so the separation never depends on a developer remembering a check.
- The visitor’s browser is left as it was found: no cookies and no client-side storage. That keeps the tracking layer out of cookie-consent scope.
What gets kept is your call. Turn a field off and, from that point on, its value is discarded as the submission comes in, before it is written anywhere. Password fields are discarded on every form automatically.
Spam and bot protection sits in front of all of it. Rate limits, honeypot detection and origin checks run before storage, so your lead list stays a lead list.
The data stays yours. You can export it, delete it or move it to another tool whenever you choose.
For the detail on how the stored copy is protected, encrypted forms covers it properly. If your obligations are the pressing part, start with GDPR compliant forms.
No form yet?
A Lead Source form ships with all of the above switched on. For a head start, the free form templates span most industries.
Protecting the lead, and still knowing where it came from
Locking a form down usually costs you information. That is the trade every tool in this category asks you to make, and most buyers make it without arguing.
It is worth arguing about. The reason the trade exists is that a platform which cannot read a submission cannot report on it either. Fair enough. The mistake is assuming the report you want is made of submission data.
It is not. The campaign that sent the visitor, the referrer, the click ID in their landing URL and the pages they read first were never typed by anyone. That data is gathered from the page around them and stored apart from what they submitted.
That lets the two be handled separately. Personal details get locked. The source remains readable.
Say an MSP runs a Google Ads campaign. A prospect clicks it, arrives at /managed-it, moves on to /pricing, and three days later submits the form on /contact. The report shows Google Ads, the campaign, and the three pages in sequence. The prospect’s phone number stays out of it, since the report has no use for it.
Doing both at once is the point. The personal part is protected, and the part showing which spend paid for the lead stays in view. For how the capture side works, form tracking goes into it at length, and you can test what your own form records right now.
Who needs to care about this more than most
Managed service providers
A prospect gives you their current provider, their contract end date and their endpoint count. That is another MSP’s client detail, now held by you, and it deserves the same care as your own records. Most MSP enquiry forms ask for all three up front.
Law firms
Prospective clients describe the matter on the contact form, often in more detail than they intended. You hold it before they become a client, and before any of it is privileged.
Insurance agencies
An insurance quote form can ask for date of birth, licence number, claims history and, at times, health details. In ninety seconds it gathers more identifying information than most businesses keep on a customer across a whole year.
The common thread is timing. The form runs at the point where somebody has decided to trust you but has no evidence yet that they should. Protecting it is the first thing you do for them, and they will never see it.
Still picking a form tool, rather than fixing the one you have? Start with lead capture software. The stretch from submission to CRM record is covered under secure lead capture.
Secure forms, answered.
What is a secure form?
A secure form is one where the submission is protected at every stage between the visitor typing and you reading it. That covers the trip from the browser, the copy that gets stored, who can open it, and what you asked for. A form that only protects the first of those is doing about a quarter of the job.
How do I know if my form is secure?
Follow one submission all the way through and write down every place it stops. The inbox it emails, the people it gets forwarded to, the spreadsheet somebody exported, the CRM record, the login that opens all of it, then ask which of those you actually control.
What makes a contact form insecure?
Usually not the form. The common causes sit elsewhere. A plain text notification email that gets forwarded around, an old export in somebody’s downloads folder, a shared login, then fields nobody ever reads, and no spam handling in front of any of it.
Is it safe to collect personal details through a website form?
Yes, provided the submission is protected in transit, protected in storage, and can only be opened by the people who need it. Businesses do this every day. Most of the care belongs to what happens after it arrives, which is the stage that usually gets the least of it.
Does a secure form slow anything down for the visitor?
No. The visitor sees an ordinary form and fills it in as usual. All of the protection described here runs after they press submit, so they have nothing extra to do or install.
Can I stop a form storing a field I do not want?
Yes. Once you switch a field off, its value is thrown away on arrival, before anything stores it, for every later submission. Passwords are never kept on any form. Asking for less is still the cheapest security improvement available.
Do I lose my marketing reporting if I lock the form down?
Not with Lead Source. The source, the campaign and the pages a visitor read never came from what they typed, so locking down the submission leaves them untouched. The spend that produced the lead stays visible.
Protect the submission. Keep the report.
Each enquiry locked down from the moment it is sent. Its source stays readable.
Start freeFree to start · no card