> For the complete documentation index, see [llms.txt](https://docs.duplicati.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplicati.com/duplicati-console/confidential-processing.md). # Confidential processing This page describes confidential processing in the Duplicati Console, which limits what the console stores about an organization that handles confidential or protected information. Confidential processing is a mark on an organization in the Duplicati Console for organizations that handle confidential or protected information, such as health records or special categories of personal data. When it is set, the console limits what it stores about the organization, and the features that would require storing backup contents or log text in the console are turned off. {% hint style="warning" %} Enabling confidential processing does not by itself permit storing HIPAA protected health information or GDPR special categories of personal data in the console. Storing such data requires a signed contract with Duplicati. Contact Duplicati before storing such data in the console. {% endhint %} ## What changes For an organization with confidential processing, the following applies: * **Reduced backup reports.** Machines send reports with log message ids only, and not the log text. The console rejects reports that contain full log text, so a machine that is set up to send full reports has its reports refused until it is reconfigured. * **No backup configurations.** [Backup configurations](/duplicati-console/backup-configurations.md) cannot be created or assigned, and the **Configurations** tab is hidden. Connection links do not offer configurations to apply. * **No managed backups.** [Managed backups](/duplicati-console/managed-backups.md) cannot be created, and the **Managed backups** tab is hidden. * **No AI summaries and summary reports.** The AI analysis of backup reports and the summary reports are not available, and the settings for them are hidden. A confidential sub-organization is also left out of the summary reports of the organizations above it, even when they [include the machines of sub-organizations](/duplicati-console/using-the-duplicati-console.md#summary-reports-for-sub-organizations). Monitoring, alerts, restore tests, remote access, [Duplicati Storage](/duplicati-console/duplicati-storage.md) and the other console features work as usual. The backend enforces the same limits as the console, so the features cannot be reached through the API either. Organizations with confidential processing are marked with a shield icon in the list of organizations. ## Where it applies Confidential processing applies to the organization it is set on and to all of its [sub-organizations](/duplicati-console/organizations-and-sub-organizations.md). A sub-organization of a confidential organization is confidential as well, and this cannot be changed on the sub-organization. The setting is found under **Settings → General** for the organization, where the description says whether the organization is confidential, and whether the mark is set on the organization itself or inherited from a parent organization. ## Enabling confidential processing An owner can set the mark when creating a sub-organization, by checking **Processes confidential or protected information** in the dialog. The sub-organization is then confidential from the start, so no full reports are stored for it at any time. For an existing organization, and for a top-level organization, confidential processing is enabled by Duplicati support. Contact support with the name of the organization. {% hint style="info" %} Once enabled, confidential processing can only be disabled by Duplicati support. The reduced reports that were received while the mark was set are not expanded afterwards. {% endhint %} ## Preparing the machines The machines in a confidential organization keep running their backups as before, and the reports arrive in the console with the log message ids. The report pages in the console show the messages that correspond to the ids, so the status of a backup, the number of files and the warnings and errors are still visible. The free text from the log, such as file names that failed, is only available in the log on the machine itself. If a machine was connected before the organization became confidential, no change is needed on the machine: the console tells the machine to send reduced reports when it connects. --- # 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.duplicati.com/duplicati-console/confidential-processing.md?ask=&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.