> For the complete documentation index, see [llms.txt](https://docs.solutioo.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solutioo.de/magento-2-api-connector/fehlerbehebung-and-support/supportpaket-sicherheit-und-datenschutz.md).

# Supportpaket, Sicherheit und Datenschutz

Ein gutes Supportpaket ermöglicht Diagnose ohne unnötige Datenweitergabe.

### Enthalten

* App-/BC-/Magento-Version
* Web Store Code, keine Geheimnisse
* betroffener Prozess und Zeitpunkt
* Magento- und BC-Datensatzschlüssel
* exakte Meldung
* relevante Activity- und API-Logeinträge
* reproduzierbare Schritte
* erwartetes und tatsächliches Ergebnis

### Entfernen/Maskieren

Passwörter, Tokens, Consumer Secrets, vollständige Kundenadressen, Zahlungsdetails und nicht relevante Payloaddaten.

### Screenshots

Nur relevante Bereiche aufnehmen; Browser-URL, Benutzername, Mandant und Daten prüfen.

{% hint style="danger" %}
Keine produktiven API-Geheimnisse in Tickets, E-Mails oder GitBook einfügen. Bei versehentlicher Offenlegung sofort rotieren.
{% endhint %}

### Datenschutz

Zugriff, Aufbewahrung und Löschung der Protokolle mit Ihren organisatorischen Vorgaben abstimmen.


---

# 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.solutioo.de/magento-2-api-connector/fehlerbehebung-and-support/supportpaket-sicherheit-und-datenschutz.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.