> For the complete documentation index, see [llms.txt](https://vayl.gitbook.io/vayl-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vayl.gitbook.io/vayl-docs/help-center/getting-started/whats-the-difference-between-forget-and-delete.md).

# What's the difference between forget and delete?

Both stop a fact from being returned as current, but they differ in what they keep:

* **`forget`** retracts a fact but **keeps it in history**. The current answer no longer includes it, yet an audit or a history query can still see that it was once true. Use it for correctness.
* **`delete`** **permanently erases** a subject, history included — the GDPR right to be forgotten. It also redacts the value from decision snapshots and issues a signed erasure receipt. Use it for privacy.

If in doubt, `forget`. Reach for `delete` only when the data itself must be gone.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://vayl.gitbook.io/vayl-docs/help-center/getting-started/whats-the-difference-between-forget-and-delete.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.