> For the complete documentation index, see [llms.txt](https://docs.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didomi.io/fr/gestionnaire-des-reglementations/cadres/protocole-mondial-de-confidentialite-gpp/chaine-gpp/sections-de-confidentialite-des-etats-americains/kentucky-kcdpa.md).

# Kentucky (KCDPA)

La section de confidentialité du Kentucky sera définie dans le `gppString` pour l'utilisateur final si le pays/la région/l'État de l'utilisateur final est inclus dans la configuration régionale pour **Loi du Kentucky sur la protection des données des consommateurs** dans l'avis de consentement GPP.

<table><thead><tr><th width="120.199951171875"></th><th width="87.13336181640625">Valeur</th><th>Description</th></tr></thead><tbody><tr><td>ID de section</td><td>26</td><td>La section de confidentialité du Ketucky est enregistrée sous l'ID de section 26 dans le GPP.</td></tr><tr><td>Préfixe API</td><td><code>usky</code></td><td>La section de confidentialité du Kentucky est enregistrée avec le préfixe d'API <code>usky</code>.</td></tr></tbody></table>

### Encodage de la section

Le tableau ci-dessous détaille les différents champs de la section de confidentialité du Kentucky.


---

# 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://docs.didomi.io/fr/gestionnaire-des-reglementations/cadres/protocole-mondial-de-confidentialite-gpp/chaine-gpp/sections-de-confidentialite-des-etats-americains/kentucky-kcdpa.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.