How CornerSpot protects your forms from spam

Spam and bot submissions are a fact of life for any public form. The good news: Cornerspot fights them on two fronts. Some protection is fully automatic and invisible — you never set it up. The rest is a small set of submission settings you control from the form's Settings panel. This guide covers both.

The automatic protection: a hidden honeypot

Every Cornerspot form includes a hidden honeypot field that real visitors never see. Automated bots fill in every field they find — including this one — so when a submission arrives with the honeypot completed, Cornerspot quietly discards it on the server before it's ever recorded. There's nothing to configure and nothing to maintain: it works on every form, on every channel, out of the box.

Because the bad submissions are dropped silently, they never appear in your Submissions inbox — there's no "spam" status to review or clean up. The clean inbox is the result.

The controls you set: submission settings

The settings you control sit in the form's Settings panel. Open a form, click Settings in the top-right of the builder, and scroll to the Details section.

1. Open Forms and your form

From the dashboard, select Forms in the left-hand menu, then open the form you want to protect. You'll land in its Builder.

The Forms list in Cornerspot
The Forms list — open the form you want to protect.

2. Open Settings

Click Settings in the top-right to open the Form Settings panel, then find the Details section. This is where the anti-spam controls live.

The form builder in Cornerspot with the Settings button
The form builder, with the Settings button in the top-right.
The Form Settings panel open to the Details section in Cornerspot
The Form Settings panel, open to the Details section.

Limit repeat submissions

Two settings curb the most common nuisance — the same source submitting again and again:

  • Multiple per browser (on by default) controls whether the same browser can submit more than once. Turn it off and a browser that already submitted sees your confirmation message instead of the form, so it can't flood you with repeats.
  • Multiple per email (on by default) does the same for a single email address. When off, a second submission from an address that already submitted is acknowledged but not recorded again.

These two only apply when your form collects an email, so they become available once the form has an Email field.

The Multiple per browser submission limit in Cornerspot
The Multiple per browser toggle in the Details section.
The Multiple per email submission limit in Cornerspot
The Multiple per email toggle, enabled because the form has an Email field.

Email verification: your strongest lever

Email verification (off by default) asks submitters to confirm a code emailed to them before their submission is recorded. It adds one step for genuine visitors, but it's highly effective against spam: a bot that can't receive real mail can never complete the confirmation, so its submission never counts. Turn it on for any form where spam — or being able to reach the submitter — really matters.

Turning on Email verification to fight spam in Cornerspot
Turning on Email verification, which requires submitters to confirm an emailed code.

Save your settings

When your choices look right, click Save settings. They take effect immediately, on every channel the form is published to.

The Save settings button in the Form Settings panel in Cornerspot
The Save settings button applies your spam protection.
The Details section after saving with Email verification on in Cornerspot
The Details section after saving, with Email verification on.

Putting it together

  • The honeypot runs automatically on every form — no setup, no maintenance, and nothing for you to monitor.
  • Turn off Multiple per browser and Multiple per email on forms where each person should submit just once.
  • Turn on Email verification when spam or deliverability matters most — it's the strongest control you can flip yourself.
  • The email-dependent settings need an Email field on the form; add one in the builder if you don't see them enabled.

Was this article helpful?