# GDPR, Privacy and Cookies

A great place to start is the [checklist provided by gdpr.eu](https://gdpr.eu/checklist/). For most small and medium e-commerce businesses, the *Privacy Policy* is going to be the key GDPR-related document that needs to be created.

### Cookies <a href="#cookies" id="cookies"></a>

This ties in with our platform-level solution to the "Cookie Law" requirements (see '[Cookies](https://app.gitbook.com/o/jjqlLZAJpFOwMwx6xbZs/s/kTaBpmn8aX5KjLYTOO52/~/changes/4/websites/gdpr-privacy-and-cookies/cookies)'). Again, since Pakk knows how your site is configured, it knows which cookies are required so can generate the cookie message, cookie preferences panel and cookie page, all without any intervention from you. As well as the "Cookie Law", this is also an important component of GDPR compliance. In fact, the Privacy Policy links directly to the Cookie page!

### Platform-level solutions to platform-level problems <a href="#platform-level-solutions-to-platform-level-problems" id="platform-level-solutions-to-platform-level-problems"></a>

This is another example of the Pakk philosophy of *platform-level solutions to platform-level problems*. While creating a Privacy Policy might seem like a highly unique endeavour for each business, when you actually look at the process, it would be 90% the same work for each Pakk user. That's why we centralise the solution to the problem. It also means that the burden of keeping the Privacy Policy up-to-date, relevant, correct, well written **shifts mostly to us** and that when we make improvements, every Pakk users gets them straight away.


---

# Agent Instructions: 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:

```
GET https://docs.pakk.io/websites/gdpr-privacy-and-cookies.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
