other
Warning
- Location
references/项目周报管理框架V2.5.md:332- Finding
Excessive Collection and Indefinite Retention of Workplace Chat Data
- Content
View full analysis
write it directly to a Markdown file. - Image message -> download it to a temporary directory, perform visual recognition, record key information in Markdown, and delete the temporary image. - File message -> download it to a temporary directory, read its contents, record key information in Markdown, and delete the temporary file. Initial collection rules: - Collect messages from the previous 90 days. - Continue pagination until all messages are obtained or the three-month boundary is reached. - Produce a complete Markdown document and last_fetch.json. Chat-message retention policy: - Permanently retain chat collection records without deletion. - Retain records even after project completion or after-sales support. - Do not clean, archive, or delete them. Message filtering: - Do not over-filter; collect everything first and classify it afterward. - Exclude irrelevant conversation, duplicate messages, and non-work content. ``` ### Technical Analysis The Skill's legitimate purpose is to prepare weekly reports, but its documented workflow initially collects up to 90 days of chat history, processes every encountered image and file, and performs filtering only after collection. This creates a data-minimization failure because the collection scope is substantially broader than the current weekly reporting period. Although original attachments are deleted after processing, derived information remains in persistent Markdown records. This may include message text, partic ...[truncated 2731 chars]- Remediation
View remediation