docs: note that log deletion does not erase uploaded files (#933) (backport to release/1.16.1) - #934
Merged
Conversation
* docs: note that log deletion does not erase uploaded files Adds one sentence to the Log Retention privacy Warning in both audience copies, en/zh/ja. Code-verified: neither conversation deletion nor scheduled log cleanup removes upload_files records or storage objects. Prompted by two enterprise inquiries about attachment lifecycle. * docs: scope the uploaded-files note to conversation uploads Review fix: the unscoped wording could be read as covering all uploads, but knowledge-document deletion does erase files; only files uploaded in conversations and runs persist. (cherry picked from commit 5a316f8)
Contributor
There was a problem hiding this comment.
Pull request overview
Backports PR #933 to release/1.16.1, updating the Logs “Log Retention” privacy warning to clarify that deleting conversations or cleaning up logs does not delete files that were uploaded within those conversations.
Changes:
- Add a single clarifying sentence to the Log Retention
<Warning>block in the English self-host and cloud docs. - Add equivalent translations of that sentence in the Chinese (self-host/cloud) docs.
- Add equivalent translations of that sentence in the Japanese (self-host/cloud) docs.
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| en/self-host/use-dify/monitor/logs.mdx | Adds clarification in Log Retention warning about uploaded files not being erased by log/conversation deletion. |
| en/cloud/use-dify/monitor/logs.mdx | Same clarification for the cloud audience. |
| zh/self-host/use-dify/monitor/logs.mdx | Chinese translation of the same clarification for self-host docs. |
| zh/cloud/use-dify/monitor/logs.mdx | Chinese translation of the same clarification for cloud docs. |
| ja/self-host/use-dify/monitor/logs.mdx | Japanese translation of the same clarification for self-host docs. |
| ja/cloud/use-dify/monitor/logs.mdx | Japanese translation of the same clarification for cloud docs. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| <Warning> | ||
| ログには完全なユーザー会話が含まれ、機密情報が含まれる場合があります。アプリが現地のデータプライバシー規制に準拠していることを確認してください。プライバシーポリシーを公開し、必要に応じてユーザーの同意を取得してください。 | ||
|
|
||
| 会話を削除したり、ログが保持期間を過ぎて削除されたりしても、その中でアップロードされたファイルは消去されません。 |
| <Warning> | ||
| ログには完全なユーザー会話が含まれ、機密情報が含まれる場合があります。アプリが現地のデータプライバシー規制に準拠していることを確認してください。プライバシーポリシーを公開し、必要に応じてユーザーの同意を取得してください。 | ||
|
|
||
| 会話を削除したり、ログが保持期間を過ぎて削除されたりしても、その中でアップロードされたファイルは消去されません。 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport
This will backport the following commits from
maintorelease/1.16.1: