> For the complete documentation index, see [llms.txt](https://knowledge-base.letsgetdigital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge-base.letsgetdigital.com/faq/faqs-for-the-lgd-website/9.-data-protection.md).

# Data Protection (Virtual event)

Privacy is important in nowadays digital world! We take it very serious and if you have further questions please let us know.

**Could you give me more information about AVG/data protection?** \
Let's Get Digital is a fully protected environment. People decide for themselves what information they want to share. A user has to accept the privacy policy when entering the virtual environment for the first time if this is enabled in the settings.

There are a variety of privacy settings available to both users and admins. Users have the following settings in the app they can choose from:

* **Default** - Custom privacy settings set by the admin are applied.
* **Profile hidden** - All information on your profile is hidden from other users (Unless connected)
* **Basic** - Only a users name and profile picture are visible (Unless connected)
* **Profile visible** - The information on your profile is available to all users.

Admins with access to the admin panel can create [custom privacy settings](https://knowledge-base.letsgetdigital.com/the-admin-panel/settings/general-settings-app-+-vp-1/privacy-settings-app-+-vp#custom-privacy) that users can select among the other options listed above. 


---

# 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://knowledge-base.letsgetdigital.com/faq/faqs-for-the-lgd-website/9.-data-protection.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.