SDK 1.7.9 - Recaptcha feature documentation

For security reason, the Attendee will provide Passcode or wait in the Waiting Room, then why should again asking Attendee to enter the reCaptcha? The meeting already “enabled with Passcode” should not redirect to reCaptcha page. So please consider this request and remove/disable the reCaptcha for Passcode enabled meetings.

And also, the developers those who are done with customisation on the previous SDK will suffer a lot with this Captch feature. So please reconsider my request and disable the captcha for at least the passcode enabled meetings.


It doesnt make any sense to have recaptcha in some scenarios where user is already logged in to the platform we are integrating to, it degrades UX.

Hi @nvivot @harald.glanzer @darragh.duffy @ken.davis @karthikeyan.ramaraj @pmogollon
Thank you for your feedback, we definitely understand your concerns in regards to the reCAPTCHA feature. If you have any other concerns or scenarios, feel free to post them here and we will send this to our internal teams for review.


Hi here,

Of course i (and my team / company) +20 the future (soon i hope) possibility to deactivate this recaptcha feature as it completely destroy user experience as well as customization made up to now with previous SDK versions.

The goal of this post was indeed to have documentation listing regarding this feature but also to check if there are people who share the same concern as us, and i’m more than happy we are not the only one.

So, as already explained very well before me in this thread,

  • it does not make sense at all to have a recaptcha for application integrating zoom which are already secured in another way / closed to public + protected with password already.

  • if you try to convince us that this is for security reason, then why do you enable to skip the recaptcha when joining as a host ? This is completely non sense. Recaptcha is to protect against bots so should be activated to public meetings only. I understand that you may want to protect yourself (and your clients) against bots for obvious reasons, especially for those who do not protect their applications and give free access to it, but not at the cost of people doing things right.

The web SDK is there for an integration purpose, so you should consider a way to deactivate certain options at the contrary of your native clients.


@Michael_Purnell here is another big reason why you should give us the possibility to deactivate this recaptcha feature

Recaptcha is collecting user’s data.

If you force us to use this, you forces our users to have some of their data collected by Google, which is against the GDPR and other similar laws depending on which country the user is coming from.

As a service company we have to apply the law (same as you by the way, it’s not because you are a US company that European or APAC law do not apply since you have customers from all over the word)

Because of this law, we must provide a way to have the user’s agreement for data collection.
**With SDK 1.7.9, if the user refuse to have his data collected, then we must not collect it. But since you force us to pass by this recaptcha feature not matter the user accept or not, we are now force to tell to our customers : if you don’t accept you cannot have access to our online services, which is a disaster in term of communication and have a direct impact on our economy.

So please, remove it completely or make it optional as soon as possible.


GDPR: good point! even if its not really surprising that zoom doesn’t care about such peanuts

I also request the ability to turn this off. Changing the user workflow this much should have perhaps been discussed with those using your SDK for business purposes before forcing everyone into something that’s only going to cause mass user complaints.

Think about other use cases too - we’re doing conferences. We have people joining 8-15 sessions daily from an agenda with the WebSDK embedded in our site. They (or anyone) would not be too happy about going thru recaptcha for 10 rapid fire sessions. Or even 1 for that matter. It’s annoying. It would be interesting to hear your rationale for implementing this requirement. Considering one has to generate a signature with the public/private key to join - I see no reason for it. Please explain.

You guys are making it very difficult for us to depend on you as a partner and provider. I’m about at the end of my rope. we’ve been waiting for this release since the the previous version made us look bad to customers in production with black screens and missing Safari audio - now I have a fix for that - with a new “feature” that’s just going to cause more and more complaints. We have customers we have demo’d integrations to who will now have another surprise that will probably not be well received. Meaning lost business for both of us.



Hi @tommy @Michael_Purnell

We are in the exact same boat, and this just echoes my points on the thread about the actual 1.7.9 update.

There are really no excuses as to why this functionality was implemented and forced onto us … and broken at that.

Unfortunately, the tones of these messages are going to get worse as time goes on until a proper solution is found. And more importantly, a proper answer is given to us with an explanation. We are trusting our businesses to Zoom, and I am aware COVID-19 has skyrocketed your business, but it doesn’t mean you can leave partners in the lurch.

Please reply with a proper answer that isn’t just copying in some link to docs. We deserve a detailed explanation and a realistic turnaround time.


Hey @SimoneLabianca, @mb_j, @harald.glanzer, @nvivot,

Thank you all for your feedback, we are sharing this with our internal teams to review to see what we can do.


Hi @tommy Is there any callback by which we can catch the recaptcha error? I checked init as well as join error callback it is not caught there.

Hello @tommy
We are facing the same issue after upgrading SDK to 1.7.9 we are getting following issues on the SDK

  1. Join meeting with Zoom reCaptcha integration it says you are in incognito mode whereas I not in a private window.
  2. The meeting is automatically disconnected and reconnecting after some moment
  3. After reconnecting meeting it’s not showing any members and functions are not working properly

@Michael_Purnell Can you expand on why this post is a ‘solution’.

I read it as “we understand your concerns but we are going to do nothing about this, but we will send an email to some internal people”

Some info on what your future plans are would be helpful (we’ll add a disable option or even - this is just how it is guys, deal with it) would help us as we deal with this unforeseen issue…

1 Like

Hey @puravt,

Please see instructions on how to handle the incognito error here:

We have also released version 1.7.10 which fixes an issue where reCaptcha doesn’t work for when the “-” character is within the domain name:


Hey @pomalley,

We are currently exploring the possibility to add an option to turn the recaptcha off.



Hey @harish.venkataraman,

Let me find out.


Hey everyone,

If you would like to request your account be whitelisted to remove the recaptcha feature, please fill out this form:



Hi @tommy,

We have multiple accounts in our company but I can only fill out the form once. What should I do?


We have multiple customers. We use their generated keys. So now, in addition to generating keys, we will have to opt out for each customer. Better than nothing I guess. What I will need to know though, is how long will it take from time of submission till it is turned off? Again, think of use cases. We are embedding for multiple customers. Perhaps it would be better to have this listed as an option on the Zoom marketplace screen where the keys are generated?


Also, btw - I am still interested in hearing the logic behind requiring this - can you comment? Due to the fact that you require a generated signature to use the webSDK , how is the added RECAPTCHA helpful to Zoom security?

1 Like

Hello, when i join meeting whith zoom reCaptcha integration it says you are in incognito mode is in use… help me please