> For the complete documentation index, see [llms.txt](https://docs.nested-knowledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nested-knowledge.com/policies/policies/legal-and-compliance-policies/regulatory-compliance-policy.md).

# Regulatory Compliance Policy

Nested Knowledge adheres to legal requirements for data protection and information security. Nested Knowledge is located in the United States. Nested Knowledge provides software to countries throughout the world, with the exception of countries sanctioned by the United States.

## GDPR Compliance

Nested Knowledge adheres to the General Data Protection Regulation (GDPR). For details and technical controls, see the [GDPR compliance policy](/policies/policies/legal-and-compliance-policies/gdpr-policy.md).

## California Consumer Privacy Act

Nested Knowledge adheres to the California Consumer Privacy Act (CCPA), as well as the California Civil Code Section 1798.83, also known as the “Shine The Light” law. For information on requesting data and the privacy rights of California residents, please refer to the [Privacy Policy](https://app.termly.io/policy-viewer/policy.html?policyUUID=874bd2cb-bbeb-47bf-8a55-56c29dd8be5a).

## HIPAA

The Health Insurance Portability and Accountability Act (HIPAA) is not applicable to Nested Knowledge because Nested Knowledge does not process any personal health information, and we have no plans to begin processing such data. The clinical data which may be retrieved in the Nested Knowledge application consists of public data from the published scientific literature.

## Other Regulatory Policies

Nested Knowledge remains up-to-date on legal and regulatory obligations including regulations on copyright, document retention, human resources, and artificial intelligence. The company monitors regulatory requirements affecting software-as-a-service businesses.

For related policies: see the [AI Compliance Policy](/policies/policies/artificial-intelligence-policies/artificial-intelligence-ai-compliance-with-legislation.md), [Document Retention Policy](/policies/policies/internal-policies/document-retention-policy.md), and [Notice of Copyright Infringement Policy](/policies/policies/legal-and-compliance-policies/copyright-compliant-policy.md).

## Revision History

For any GDPR-related issues, contact the DPO or CEO (see [Key Contacts](/policies/policies/security-protection-privacy-and-recovery-policies/incident-management-and-response.md)).

| Author      | Date of Revision/Review | Comments |
| ----------- | ----------------------- | -------- |
| M. Williams | 12/13/2025              | Reviewed |
| K. Cowie    | 10/28/2024              | Revised  |


---

# 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.nested-knowledge.com/policies/policies/legal-and-compliance-policies/regulatory-compliance-policy.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.