docs: disclose Tencent COS direct upload in privacy policy - #2
Merged
Conversation
…fallback - Add a Direct cloud upload section: recipient (Tencent Cloud COS), data class (referenced attachments and optional Pro theme snapshot; never note text), ~30-minute single-object STS credential lifetime, in-memory-only use, retention/deletion, and the DocFerry server API-proxy fallback - Publish Share table row and README privacy pointer reference the direct-upload path - Document that hidden dotfile and traversal asset references are excluded from publishing
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
1 participant
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.
Why
The 0.0.67 HOLD review (P1-8) found the public privacy policy did not disclose the Tencent COS direct-upload path, temporary credentials, or the server-proxy fallback. The corrective source (private paid main, PRIVACY-01 fix) already carries this disclosure; this PR syncs the public document.
Changes
No code changes. Mirrors the wording of the reviewed private-repo privacy copy.
Note: GitHub reports 7 high-severity Dependabot alerts on the default branch — flagged for the release hardening track (not introduced by this PR).