> For the complete documentation index, see [llms.txt](https://academy.pakk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.pakk.io/ecommerce-launch-mega-checklist/legal-and-compliance.md).

# Legal and Compliance

* Are your company details (legal name, address, VAT and company number) clearly displayed on the site and on your policy documents *Pakk sites - Pakk takes care of it for you.*
* Privacy policy: Is it GDPR compliant? Does it have a statement to that effect? Does it specify what data is collected and why? Does it specify with whom data is shared? Does it specify how long data will be kept? Does it explain and link the Cookie Policy? *Pakk sites - Pakk takes care of it for you.*
* Wherever information is collected from customers (e.g. registration forms), are you positively asking for their agreement to the privacy policy? *Pakk sites - Pakk takes care of it for you.*
* Terms and conditions: Are they linked to prominently around the site? *Pakk sites - Pakk takes care of it for you.*
* Before purchase: Are you positively requesting agreement to both terms and conditions and privacy policy? *Pakk sites - Pakk takes care of it for you.*
* Cookie warning. Make sure it respects the 'Cookie Law' in the way it functions. Pay attention to 'essential' versus 'non-essential' cookies. *Pakk sites - Pakk takes care of it for you.*
* Cancellation form: Do you have a simple form that customers can use to request cancellation of their order? Is it linked from the Terms and Conditions? *Pakk sites - Pakk takes care of it for you.*


---

# 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://academy.pakk.io/ecommerce-launch-mega-checklist/legal-and-compliance.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.

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.
