> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/faqs/nightfall-vs-e-discovery.md).

# Nightfall vs E-Discovery: What's the difference?

Learn the differences between Nightfall DLP and E-discovery

E-discovery and data loss prevention (DLP) are different, albeit conceptually similar. Nightfall is a cloud-native DLP platform.

E-discovery typically pulls messages and files from a platform to store the information in third-party data warehouses, where messages and files can be searched, archived, or retrieved. This serves legal and compliance use cases should the data need to be retrieved or searched for a legal hold.

DLP ensures sensitive data, such as personally identifiable information (PII), isn’t shared inappropriately by scanning for content within messages and files that break selected policies. This serves security and compliance use cases around discovering, classifying, and protecting sensitive data.


---

# 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://help.nightfall.ai/faqs/nightfall-vs-e-discovery.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.