> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/snyk-data-and-governance/working-with-snyk.md).

# Working with Snyk

How Snyk handles user data responsibly, covering privacy, compliance, hosting, and vulnerability data

Snyk is dedicated to the secure and responsible handling of user data, with a strong emphasis on privacy and compliance. Below are key aspects of Snyk's operations and offerings related to data handling, hosting, vulnerability disclosure, and support:

* [**How Snyk handles your data**](/snyk-data-and-governance/how-snyk-handles-your-data.md)

  Snyk implements robust security measures to protect your data against unauthorized access, disclosure, alteration, and destruction. Our data protection strategies include encryption in transit and at rest, regular security assessments, and adherence to industry-standard privacy laws and regulations.
* [**Regional hosting and data residency**](/snyk-data-and-governance/regional-hosting-and-data-residency.md)

  Snyk offers regional hosting to comply with regional data protection laws and improve service performance. This ensures data residency requirements are met and reduces data latency.
* [**Disclosure of a vulnerability in an open-source package**](/snyk-data-and-governance/disclosure-of-a-vulnerability-in-an-open-source-package.md)

  Through this program, Snyk encourages the community to report potential vulnerabilities in open-source packages, facilitating quick identification, validation, and remediation to enhance security.
* [**Reporting security issues**](/snyk-data-and-governance/reporting-security-issues.md)\
  Snyk requests that vulnerabilities in a Snyk service be reported according to the process explained on this page.
* [**Snyk Terms of Support and Services Glossary**](/snyk-data-and-governance/snyk-terms-of-support-and-services-glossary.md)

  Snyk provides this glossary to outline the scope of support, service level agreements (SLAs), confidentiality commitments, and the responsibilities of Snyk and its customers for transparent and clear service expectations.
* [**Snyk Platform credits**](/snyk-data-and-governance/snyk-platform-access-credits.md)

  How the Snyk Platform Subscription plan consolidates capabilities into flexible, usage-based credits.
* [**What counts as a test?**](/snyk-data-and-governance/what-counts-as-a-test.md)

  How Snyk counts tests against your plan limits, and what does not apply under credit-based licenses.
* [**How Snyk counts assets**](/snyk-data-and-governance/how-does-snyk-count-assets.md)

  How Snyk counts billable assets managed through Snyk Essentials.
* [**How Snyk incorporates generative AI into the platform**](/snyk-data-and-governance/how-snyk-incorporates-generative-ai-into-the-platform.md)

  How Snyk uses generative AI across its platform, including the third-party models that power its AI features.
* [**Snyk for Government (US)**](/snyk-data-and-governance/snyk-for-government-us.md)

  Snyk for Government (US), which helps US federal agencies develop securely within their existing workflows.


---

# 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.snyk.io/snyk-data-and-governance/working-with-snyk.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.