Bot Protection on Account Creation and Public Forms¶
How Public Survey and Report Links Stay Protected covers protection for respondent-facing survey and report links specifically. This one is about a different set of entry points: account sign-up, login, and general public-facing forms like the contact page - each is a natural target for automated abuse in its own right, and each is protected accordingly.
Sign-Up and Login¶
Creating an account and logging in are both protected against automated, scripted attempts - a real person signing up or logging in normally isn't affected, but scripted account-creation attempts or repeated automated login attempts are guarded against. This runs invisibly in the background rather than requiring you to solve a puzzle or challenge as part of normal use.
Public Contact and Compose Forms¶
Forms available to the public without requiring sign-in first - like a contact form - use a visible, managed verification step rather than an invisible one, since these forms don't have an existing authenticated user to establish trust the way a logged-in action does. This is a standard, brief verification step you'll recognize from most sites that offer a public contact form.
Why Different Forms Get Different Protection¶
The right protection depends on the context: an authenticated action (like replying inside an existing conversation) can rely on invisible protection because there's already an established, logged-in identity behind it. A fully public, unauthenticated action (like a first-time contact form submission) benefits from a more visible verification step, since there's no existing account relationship to lean on.
What This Protects Against¶
The goal across all of these is the same: keeping automated scripts from mass-creating accounts, brute-forcing logins, or flooding public forms with spam, while keeping the experience smooth for an actual person using the platform normally.
FAQ¶
Will I ever be asked to solve a visible challenge when I'm already logged in?
Authenticated actions generally rely on invisible protection rather than a visible challenge, precisely because you're already a known, logged-in user.
Does bot protection ever block a real user by mistake?
It's designed to act on patterns consistent with automated abuse rather than normal individual use - a real person signing up or logging in the ordinary way shouldn't be affected.
Is this the same protection used on survey and report links?
No - those are respondent-facing links with their own specific protections. See How Public Survey and Report Links Stay Protected for that side of things.
Can I turn off bot protection for my own account or forms?
No - it's a baseline protection applied consistently, not an optional setting.
For the respondent-facing side of link protection, see How Public Survey and Report Links Stay Protected.