T09 · Insecure Skill Coding Practices
- Location
SKILL.md:32- Finding
Mandatory Persistent Storage of Sensitive Child Data Without Consent or Lifecycle Controls
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 32-63
Vulnerability Type: Mandatory persistence of sensitive information concerning minors
Risk Level: MediumVulnerable Instruction Snippet
The following is an English translation of the complete relevant instruction segment:
markdown ## Memory and Tracking Mechanism (Extremely Important) You have persistent memory capabilities and must perform the following operations in every conversation: ### When to Remember Whenever the user describes a new problem, new situation, or provides feedback about the child, you need to use the `update_memory` tool to record key information. ### Memory Categories Organize memories into the following categories, using a clear title prefix for each: 1. [Child Profile] — Basic information such as age, gender, grade, personality traits, interests, and hobbies - Example title: `[Child Profile] Basic Information` - Example content: `7 years old, first grade. Personality traits: energetic, strong self-esteem, and sensitive to fairness.` 2. [Problem Record] — The specific issue discussed during each consultation - Example title: `[Problem Record] 2026-04 Believes the teacher targets him` - Example content: `The child complains that the teacher targets him and that others may do the same thing without being criticized. The child may be unable to distinguish subtle behavioral differences. This is interpreted as a typical manifestation of the egocentric cognitive stage.` 3. [Guidance Recommendations] — Key recommendations previously given - Example title: `[Guidance Recommendations] 2026-04 Strategy for handling "the teacher targets me"` - Example content: `Recommend using the Detective Game to help the child observe differences and using "What was different today?" during dinner to encourage thinking from multiple perspectives.` 4. [Progress Tracking] — Parental feedback about implementation ...[truncated 4510 chars]- Remediation
View remediation
Remediation Suggestions
-
Make persistent memory explicitly opt-in. Provide parenting guidance using session-only context by default. Before the first memory write, explain what will be retained, why it is useful, and how the user can revoke consent.
-
Request approval for each memory category. Allow the user to approve child profile data while declining problem history, inferred assessments, or progress tracking.
-
Apply strict data minimization. Store only information necessary for a user-requested follow-up. Prohibit storage of names, exact schools, addresses, contact details, account identifiers, and other direct identifiers.
-
Separate facts from inferences. Clearly label whether an entry is a user statement, parent interpretation, or model hypothesis. Do not persist speculative psychological conclusions by default.
-
Add review and correction controls. Before writing, display the proposed memory entry and ask the user to confirm it. Provide commands or documented procedures to list, correct, export, and delete all child-related records.
-
Define retention limits. Automatically expire child-related records after a short, documented period unless the user deliberately renews consent.
-
Protect later retrieval. Do not automatically reveal sensitive historical information merely because a new conversation begins. Ask whether the user wants previous records used, and avoid exposing details in contexts where account access may be shared.
-
Record provenance and modification history. Do not silently overwrite conflicting information. Preserve the source and date of each user-approved correction while preventing obsolete information from influencing recommendations.
-
Add authorization and privacy warnings. Ask users to confirm that they are authorized to provide and retain information concerning the child. Advise them not to enter unnecessary identifying details.
-
**Fail safely when memo ...[truncated 136 chars]
-