# Page Not Found

The URL `hc/en-us/articles/6416315967004-Cookies-Privacy` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Consent policy - cookies, storage and privacy](https://docs.abtasty.com/account/performance-and-security/consent-policy---cookies-storage-and-privacy.md)
- [About cookies tracking](https://docs.abtasty.com/account/tag-integration/understand-ab-tasty-tag-implementation-methods/about-cookies-tracking.md)
- [How to choose your cookies deposit method](https://docs.abtasty.com/account/technical-implementation/how-to-choose-your-cookies-deposit-method.md)
- [Cookie criterion](https://docs.abtasty.com/assets-library/creating-and-managing-segments/list-of-segment-criteria/cookie-criterion.md)
- [Connect your Slack Workspace to AB Tasty](https://docs.abtasty.com/integrations/other-integrations/productivity/connect-your-slack-workspace-to-ab-tasty.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.abtasty.com/account/performance-and-security/consent-policy---cookies-storage-and-privacy.md?ask=<question>&goal=<user_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.

### Option 2 — Browse the documentation index

Full index: https://docs.abtasty.com/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://docs.abtasty.com/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/account/performance-and-security/consent-policy---cookies-storage-and-privacy.md`).

You may also use `Accept: text/markdown` header for content negotiation.