other
- Location
SKILL.md:13- Finding
Unspecified Persistent Retention of Meeting and Organizational Data
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 13–17 and 139–147
Vulnerability Type: Privacy and excessive data retention
Risk Level: MediumRelevant source excerpts (translated into English):
markdown **Memory system**: - Remember common meeting-format preferences - Remember commonly used resolution templates - Remember the user's role and department informationmarkdown ### Automatic learning - Record the user's preferred formatting adjustments - Remember frequently encountered attendee names - Accumulate an industry terminology dictionary ### Continuous optimization - Optimize extraction accuracy based on user feedback - Learn the meeting-minute styles of different companies - Iterate the output formatTechnical Analysis
The Skill declares that it will remember attendee names, user roles, department information, company-specific styles, and other meeting-derived information. These instructions extend beyond transient processing of content needed to generate meeting minutes.
Meeting records may contain personal information, confidential business discussions, internal organizational structures, customer details, and commercially sensitive terminology. The Skill does not define whether memory is session-scoped or persistent, nor does it specify informed consent, data minimization, tenant isolation, retention periods, access controls, encryption, deletion procedures, or mechanisms for users to inspect and revoke stored information.
This is not classified as
T02: Agent Memory Poisoningbecause the reviewed instructions do not direct the agent to persist attacker-controlled behavioral rules. The concern is privacy and excessive retention of user and organizational data rather than poisoning the agent's future behavior.Attack Path
- A user provides a meeting transcript containing attendee names, roles, departments, internal terminology, or company-spec ...[truncated 1362 chars]
- Remediation
View remediation
Remediation Suggestions
- Make all persistent memory features disabled by default and require explicit, informed user consent before enabling them.
- Process meeting content transiently unless persistence is strictly necessary for a user-requested feature.
- Do not retain attendee names, roles, departments, transcript contents, customer information, or company-specific terminology by default.
- Store only narrowly scoped preferences, such as a selected output template, and avoid linking them to meeting participants or confidential content.
- Clearly document what is stored, why it is stored, where it is stored, who can access it, and how long it is retained.
- Enforce per-user and per-organization isolation so retained data cannot affect or appear in unrelated sessions.
- Apply encryption in transit and at rest, least-privilege access controls, retention limits, and automatic deletion.
- Provide controls for users to inspect, correct, export, disable, and permanently delete stored memory.
- Add an explicit instruction prohibiting the retention of raw meeting transcripts and sensitive personal or business data.
- If memory is unavailable or consent has not been granted, state that no information will be retained after the current session.