Outbound data restrictions after searching data sources (#1106)

This commit is contained in:
Thorsten Sommer authored and GitHub committed 2026-10-23 09:27:22 +02:00
1 parent 7ba5f01388
commit 8c5cfa78b6
61 files changed
+1389 -143

No files matched your search

+4 -4
View File
@@ -146,15 +146,15 @@ public sealed record ChatThread
/// <summary>
/// Where this chat may still send data, because of the internal content it holds: mails, a
/// search of the wiki, or an internal web page.
/// search of the wiki, an internal web page, or passages of a data source.
/// </summary>
/// <remarks>
/// The third thing the thread ratchets, next to the data security and the required provider
/// confidence: once internal content is in the thread, every tool which runs afterwards could
/// carry it out, in a search query or in the address of a web page. It only ever gets stricter,
/// and a later change of the settings of a mailbox or of Read Web Page does not loosen it
/// either, because the content was read under the old one. A chat which holds no internal
/// content demands nothing.
/// and a later change of the settings of a mailbox, a data source, or Read Web Page does not
/// loosen it either, because the content was read under the old one. A chat which holds no
/// internal content demands nothing.
/// </remarks>
[JsonInclude]
public OutboundDataRequirement RequiredOutboundDataRestriction { get; private set; } = OutboundDataRequirement.NONE;