> For the complete documentation index, see [llms.txt](https://www.locksmith.guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.locksmith.guide/faqs/more/why-are-my-customers-seeing-a-recaptcha-when-logging-in.md).
# Why are my customers seeing a reCAPTCHA when logging in?
While Locksmith does often use the information of already-signed-in customers to decided whether or not to grant access (depending on your settings), Locksmith does this by using the account system *provided by Shopify* for your store, and does not create its own, or directly edit the sign in process in any way.
For security, Shopify may ask your customers to complete a Google reCAPTCHA task, verifying that a human user is present. This is an effective way to prevent bot submissions of orders and contact forms. Locksmith doesn't have any control over these; they're entirely managed by Shopify.
For information on editing the Shopify setting regarding the re-captcha in your store, [see Shopify's guide here](https://help.shopify.com/en/manual/online-store/setting-up/preferences#protect-your-store-with-google-recaptcha), or continue reading for information on how to turn it off...
### Turning re-captcha off
Shopify allows these reCAPTCHA tasks to be enabled or disabled in two categories: at checkout, and on contact forms. That second category is a little misleading: it *also* applies to normal customer login attempts.
To manage these settings, find the "Online Store" navigation category, in your Shopify admin's list of sales channels. From that navigation list, head to the "Preferences" area, and scroll to the very end of the page of settings. You'll find a section titled "Spam protection". Use this section to control your online storefront's settings for Google reCAPTCHA.
If you have more questions about how these work, [contact Shopify support](https://help.shopify.com/en/questions).
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://www.locksmith.guide/faqs/more/why-are-my-customers-seeing-a-recaptcha-when-logging-in.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.