reCAPTCHA

The reCAPTCHA block adds Google''s bot-detection challenge to your survey. It verifies that the person completing the form is a human, not an automated script. This is critical for public surveys — without protection, bots can flood your results with thousands of fake submissions in minutes, corrupting your data.

When to use it

Add reCAPTCHA when:

• the survey is publicly accessible without a login requirement
• the survey link is shared widely (on social media, in a public email, on a website)
• the survey is a competition entry, giveaway, or any form where a bot submission has value to an attacker
• you have noticed suspicious spikes in submissions from a single IP or at unusual times

You do not need reCAPTCHA when your survey requires login (Supabase Auth protects the submission endpoint), or when responses are gated behind a token-based invite link.

How to configure it

Open the question in the builder and expand Settings:

• reCAPTCHA version — choose v2 (respondent sees a checkbox challenge) or v3 (invisible, score-based — no interaction required unless the score is low).
• Placement — drag the block to where in the survey flow the challenge appears.

Tips

Tip — Place the reCAPTCHA block on the last page, just before the Submit button. This minimises friction for real respondents who only encounter it once they have answered everything, while still blocking bots at the submission step.

Warning — reCAPTCHA is one layer of protection, not the only layer. Use it alongside SurveyKar''s built-in server-side rate limiting — reCAPTCHA alone can be bypassed by sophisticated bots. The combination is significantly more robust.

Warning — reCAPTCHA sends page metadata to Google. If your survey collects data under a privacy policy that restricts third-party data sharing, review Google''s reCAPTCHA data processing terms before enabling it.