metadata-leakage-inventory

Inventory observable metadata and assess linkability, inference, and privacy-claim conflicts.

2|Updated May 6, 2026
One-click install
npx skills add https://github.com/bpcakes/jig-skills --skill metadata-leakage-inventory-bpcakes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: metadata-leakage-inventory
Source: https://github.com/bpcakes/jig-skills/tree/main/plugins/jig-privacy-audit/skills/metadata-leakage-inventory
Command: npx skills add https://github.com/bpcakes/jig-skills --skill metadata-leakage-inventory-bpcakes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Encrypted content does not hide metadata: timestamps, identifiers, recipients, sizes, and notification payloads can still reveal identity, relationships, and behavior. This Skill audits that residual metadata exposure and checks whether observed behavior contradicts product privacy claims and policy statements. ## Core Features & Use Cases - Metadata Inventory and Classification: Enumerate metadata fields across APIs, storage, logs, telemetry, notifications, and third parties, then classify them as operational, avoidable, sensitive, claim-contradicting, or unknown. - Risk Mapping: Map each item to linkability, identifiability, behavioral inference, social graph exposure, and timing inference risks with explicit inference paths. - Claim and Policy Comparison: Compare observed collection, sharing, retention, and controls against marketing claims, privacy policies, and consent settings, producing MLI-prefixed findings with severity and confidence. - Use Case: An E2EE messaging product claims "we cannot see who you contact." Use this Skill to capture API traffic, inspect logs and push notification payloads, and produce an evidence-backed report showing whether contact-graph metadata is actually visible to servers or third parties. ## Quick Start Audit this service's observable metadata across API responses, logs, and push notifications, compare it against the privacy policy claims, and report findings with evidence and severity.

Frequently Asked Questions about metadata-leakage-inventory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit metadata leakage in an encrypted messaging or storage product?

Inventory metadata fields across API schemas, captures, storage, logs, notifications, and third parties, then classify each by purpose, precision, retention, and readers. Map risks such as linkability and timing inference, and compare observed behavior against the product's privacy claims.

What metadata can leak even when message content is end-to-end encrypted?

Sender and recipient relationships, timestamps, message sizes, group membership, filenames, previews, push notification payloads, and device or IP data often remain visible to servers. Traffic analysis can also infer presence and activity from timing, size, and frequency patterns.

How do I check whether a product's privacy claims match its actual behavior?

Build a claim table from marketing pages, privacy policies, and consent screens, then compare each statement against captured traffic, logs, storage schemas, and third-party SDK payloads. Report conflicts as claim-contradicting findings with concrete evidence.

Does hashing or pseudonymizing identifiers prevent metadata linkability?

Not necessarily. Hashing, tokenization, and deterministic encryption can remain linkable or reversible depending on salt and key custody, identifier stability, and join context. The audit treats such fields as potentially personal data until proven otherwise.

What are the limitations of a metadata leakage audit?

Absence of metadata in a sampled trace does not prove absence across environments, feature flags, or background jobs. Policy comparison reports factual alignment, not legal compliance, and some operational metadata is legitimately required for routing, billing, or abuse prevention.