> For the complete documentation index, see [llms.txt](https://help.wotnot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.wotnot.io/deploy/web-chat-widget/cookies.md).

# Cookies

When using WotNot's chatbots on your website, a cookie is placed by default when users begin interacting.

You can disable automatic addition of the cookie by going to:

Settings > Channels > Web > General settings > Cookie setting

* **Always added** - this means the cookie is always added to the client when a chat session starts.
* **Manually added** - this means cookie is not automatically added until a JS method is fired.

{% code overflow="wrap" %}

```javascript
// JS method to manually add the cookie

wn.cookieSettings({“is_allowed”:true})

// "true" means the cookie is added, "false" the cookie is removed if any present. And if the JS method is not used, no cookies are added.
```

{% endcode %}

To check if a WotNot cookie is present in your browser:

* Goto Inspect > Application > Cookies
* Search for keyword "cuid" under domain "app.wotnot.io"

<figure><img src="/files/2wbuhQcDzcQBBi6dY7eM" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.wotnot.io/deploy/web-chat-widget/cookies.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.