> For the complete documentation index, see [llms.txt](https://legal.incard.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://legal.incard.co/privacy-policy/cookie-policy.md).

# Cookie Policy

Our Cookie Policy explains what cookies are, how we use them on our website, the types of cookies we use, and your choices regarding cookies.

By using our website, you consent to the use of cookies in accordance with this policy. You can manage your cookie preferences at any time through the cookie consent banner.

**What are Cookies?**

A cookie is a small text file that is placed on your device when you visit our website. Cookies help us provide a better user experience, understand how our website is used, and improve our services.

**How We Use Cookies**

We use cookies to make our website work properly and to improve your experience.

**Necessary cookies** are essential for the basic functionality of the website and are always active. **Other cookies** (Functional, Analytics, Performance, and Advertising) are only used with your prior consent.

You can customise your preferences or reject non-essential cookies at any time via the cookie consent banner. Disabling some cookies may affect your browsing experience.

**Types of Cookies We Use**

We categorise cookies into the following groups:

**1. Necessary Cookies** Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data. → These cookies are **Always Active**.

**2. Functional Cookies** Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

**3. Analytics Cookies** Analytics cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

**4. Performance Cookies** Performance cookies are used to understand and analyse the key performance indexes of the website which helps in delivering a better user experience for the visitors.

**5. Advertising Cookies** Advertisement cookies are used to provide visitors with customised advertisements based on the pages you visited previously and to analyse the effectiveness of the ad campaigns.

**6. Uncategorised Cookies** These are cookies that are being analysed and have not yet been classified into a category.

**Third-Party Cookies**

We may also use third-party cookies from services. These cookies are governed by the respective third parties’ privacy policies.

**Managing Your Cookie Preferences**

You can manage your cookie preferences at any time by clicking on the cookie settings link in the footer or through the cookie consent banner that appears on your first visit.

You can also set your web browser to refuse cookies, delete cookies, or alert you when cookies are being sent. Please note that disabling certain cookies may impact your experience on our website.

**More Information**

For more information about cookies, you can visit:

* [AboutCookies.org](https://www.aboutcookies.org)
* [AllAboutCookies.org](https://www.allaboutcookies.org)
* [Network Advertising Initiative](https://www.networkadvertising.org)


---

# 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://legal.incard.co/privacy-policy/cookie-policy.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.