Gdpr

Audit GDPR compliance, generate privacy policies, and document data flows. Use when auditing practices, drafting policies, or checking consent flows.

Security Scan

The skill's files, runtime instructions, and requested resources are consistent with a local, offline GDPR logging/utility tool that stores logs under ~/.local/share/gdpr and does not request network access or credentials.

Purpose & Capability

The name/description (GDPR audit, policies, data flows) match the provided shell tool and SKILL.md: a local CLI that logs compliance events, exports logs, and shows stats. There are no unrelated credentials, binaries, or config paths requested.

Instruction Scope

SKILL.md and the script instruct only local file operations (create and append logs, search, export, stats). They do not call external network endpoints, read unrelated system configs, or request broad contextual data. All read/write activity is confined to ~/.local/share/gdpr.

Install Mechanism

There is no install spec (instruction-only skill) and the included code is a plain bash script. No downloads, package installs, or external installers are used. The script will be executed locally if the agent runs it.

Credentials

No environment variables, credentials, or config paths are required. The script uses only HOME to build a local data directory, which is normal and proportionate for a local logging tool.

Persistence & Privilege

always is false and the skill does not modify other skills or global agent settings. It persists only its own log files under the user's home directory, which is expected for its purpose.

Assessment

This skill appears to be a simple, offline shell-based GDPR logging utility. Before installing, note that it will create and write logs under ~/.local/share/gdpr (history.log and per-command .log files). If that storage location is acceptable, the tool is coherent with its description. Review the script if you want to confirm there are no changes (it's pure bash and readable). Also be aware exports are written locally (export.json/csv/txt) and the script may produce minor bugs in formatting (non-security). If you need centrally managed, auditable logs or immutable storage, this local approach may not be sufficient.

GDPR v2.0.0 — a security toolkit for managing GDPR compliance workflows from the command line. Log security operations, audit trails, policy changes, and more. Each entry is timestamped and persisted locally. Works entirely offline — your data never leaves your machine.

Commands

Domain Commands

Each domain command works in two modes: log mode (with arguments) saves a timestamped entry, view mode (no arguments) shows the 20 most recent entries.

Command	Description
gdpr generate <input>	Log a generation event (privacy policy, consent form, etc.)
gdpr check-strength <input>	Log a strength check result (password, encryption, etc.)
gdpr rotate <input>	Log a key/credential rotation event
gdpr audit <input>	Log an audit finding or compliance check result
gdpr store <input>	Log a data storage event (what was stored and where)
gdpr retrieve <input>	Log a data retrieval/access event
gdpr expire <input>	Log a data expiration or retention event
gdpr policy <input>	Log a policy change or update
gdpr report <input>	Log a report entry or compliance summary
gdpr hash <input>	Log a hashing operation (data anonymization, etc.)
gdpr verify <input>	Log a verification result (identity, consent, integrity)
gdpr revoke <input>	Log a revocation event (consent withdrawal, access removal)

Utility Commands

Command	Description
gdpr stats	Show summary statistics across all log files
gdpr export <fmt>	Export all data to a file (formats: json, csv, txt)
gdpr search <term>	Search all log entries for a term (case-insensitive)
gdpr recent	Show the 20 most recent entries from the activity log
gdpr status	Health check — version, data dir, entry count, disk usage
gdpr help	Show the built-in help message
gdpr version	Print the current version (v2.0.0)

Data Storage

All data is stored locally at ~/.local/share/gdpr/. Each domain command writes to its own log file (e.g., audit.log, policy.log, revoke.log). A unified history.log tracks all actions across commands. Use export to back up your data at any time.

Requirements

• Bash (4.0+)
• No external dependencies — pure shell script
• No network access required

When to Use

• Auditing GDPR compliance across your organization's data practices
• Logging data access and retrieval events for accountability
• Tracking consent revocations and data subject requests
• Recording key/credential rotation schedules
• Documenting policy changes with timestamps for audit trails
• Managing data retention and expiration workflows
• Generating compliance reports from logged activity
• Exporting audit logs for regulatory submissions

Examples

# Log a compliance audit finding
gdpr audit "User data export endpoint missing encryption — needs fix"

# Record a policy update
gdpr policy "Updated cookie consent banner to include analytics opt-out"

# Log a consent revocation
gdpr revoke "User #4521 withdrew marketing consent via email"

# Track a key rotation
gdpr rotate "API key rotated for payment service, old key expires 2025-04-01"

# Log data storage event
gdpr store "Backup of EU customer PII moved to Frankfurt region"

# Verify identity check
gdpr verify "KYC verification passed for account #8832"

# Log a data expiration
gdpr expire "Inactive accounts older than 2 years purged per retention policy"

# Generate a hash record
gdpr hash "SHA-256 hash of user export file: a3f8c9..."

# Search across all logs
gdpr search "consent"

# Export everything as CSV
gdpr export csv

# Check overall status
gdpr status

# View recent activity
gdpr recent

---

Powered by BytesAgain | bytesagain.com | [e-mail]