Critical security advisoryCriticalFlagged by our vulnerability database: PHP2Shell: two critical PHP flaws affect most WordPress hosting. See if your site is affectedFlagged by our vulnerability database: PHP2Shell, two critical PHP flaws. DetailsFlagged: PHP2Shell. Check your site
HuttenlocherTechnologies

Security · 5 min read · Updated October 23, 2026

Is your contact form sending customer data in the clear?

Short answer: Every form on your site is a promise to the person filling it in. This month we found a local form sending entries over an unencrypted connection, and a credit application asking for Social Security numbers with no privacy policy anywhere on the site. Here’s how to check yours.

Contact forms feel harmless, so nobody looks at them after launch. But a form collects names, phone numbers, addresses and sometimes far more, and all of it has to travel somewhere and be stored somewhere.

What we found on local sites

  • A Grand Strand business whose site has no working secure connection: its certificate is expired, so browsers warn visitors away, and its form sends what people type over plain, unencrypted http.
  • A car dealer whose site takes credit applications, including Social Security numbers, with no privacy policy on the site saying what happens to them.

Check yours in two minutes

  1. Look for the lockOpen the page with your form. The address should start with https and show a lock. If the browser warns you instead, the form isn’t safe to use. Our free website check reports this too.
  2. Look at what it asks forA contact form needs a name, a way to reply and a message. If it asks for a Social Security number, date of birth, card number or health details, it needs to be a proper secure application, not a plain form.
  3. Find out where the entries goSubmit a test entry and follow it: which inbox, which plugin, which outside service. Then ask how long it’s kept and who can see it.
  4. Read your privacy policyIf the form collects personal information, the site should say what you do with it. A template policy that names a different business, or no policy at all, is worse than it looks.

What a safe form looks like

  • The whole site on HTTPS, with browsers told to never use the insecure version.
  • Only the fields you actually need. Every extra field is something you’re now responsible for.
  • Sensitive applications, credit, medical, legal, handled in a secure portal or by a service built for it, not a form that emails a PDF.
  • Notification emails that say a new entry arrived, with a link to sign in and read it, instead of the full contents.
  • Old entries deleted on a schedule, and spam protection that doesn’t make real customers solve puzzles.

Written by Nikita Huttenlocher, founder and lead engineer at Huttenlocher Technologies, a web design and software company in Myrtle Beach, South Carolina.

Questions

We only have a simple contact form. Does this matter?

Less than for an application form, but the connection still matters: a form on a broken HTTPS connection scares people off before they send anything, and browsers say so in red.

Is emailing form entries to ourselves a problem?

For a name and a question, it’s usually fine. For anything sensitive, it means the data now lives in every inbox it was sent to, for as long as nobody deletes it.

Can you build us a secure application form?

Yes. We build forms that store entries in a secure, sign-in-only place, send you a notice instead of the data, and keep only what you need.

Start a project

Tell us what you're building.

A website, a booking system, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.

01The person who'll build it writes back
02A planning call, then a written plan with the price and the date
03A preview on your phone while it's being built
04Launch night handled: redirects, email, Google
843-331-6339

Not ready to talk yet? Run the free website check and see what Google sees.

What do you need?

No newsletter, no sales sequence. Just a reply.