- Home
- Skills
- Agents & Orchestration
- Make Privacy Deletion Complete
More screenshots
Works with the AI Agents you already use
Make Privacy Deletion Complete
Repair privacy deletion workflows that leave personal data behind in files, caches, search, analytics, logs, or third-party systems.
$1
Make Privacy Deletion Complete
Example session with this skill installed
Identify where user data lives in our Node/Postgres stack and help us implement a durable deletion worker that also hits our S3 buckets and search index.
- Read your context and instructions
- Compiled the make privacy deletion
Project Detected: Node.js, PostgreSQL, AWS S3, Elasticsearch.
Subject Boundary
- Subject: User
- Stable identity: user_id (UUID)
- Tenant scope: organization_id
- Authorization path: middleware/auth.js
Data Inventory
- Primary records: users, profiles, billing_methods
- Derived data: activity_logs, audit_trail
- Files and indexes: s3://uploads/user-{id}, es_index/users
- External systems: Stripe, Postmark
- Backups and logs: CloudWatch logs (retention: 90 days)
Incomplete Erasure Found
- S3 objects remain after DB row deletion
- Data remaining: Profile images, CSV exports
- Destination: AWS S3
- Exposure or recreation risk: Publicly accessible signed URLs persist until expiration.
Connects securely to your tools. The creator never sees your data.
About this skill
The problem
Standard account deletion often leaves fragments of personal data behind in search indexes, object storage, background job payloads, and third-party logs. Relying on simple database cascades fails to handle asynchronous systems, partial failures, or distributed data footprints.
What it does
- Traces personal data across relational databases, document stores, caches, and message queues.
- Builds durable orchestration to manage multi-system erasure with idempotent retries.
- Implements write barriers and tombstones to prevent data recreation from delayed processes.
- Coordinates de-identification for shared business records and retained audit evidence.
- Generates independent verification steps to prove data absence across every destination.
Frameworks & tools
Compatible with standard relational and document databases, S3-compatible object storage, Redis, Elasticsearch, and third-party API providers like Stripe, Segment, or SendGrid.
Why this beats prompting it yourself
Handling erasure manually often misses derived data in dead-letter queues or versioned storage buckets. This skill enforces a strict state model and subject-identity rules that prevent cross-tenant deletion and survive worker restarts, ensuring technical compliance that simple scripts cannot guarantee.
Use cases
- Repairing incomplete deletion logic that leaves orphaned files in object storage.
- Implementing durable erasure workflows that handle third-party API rate limits.
- Scrubbing personal identifiers from analytics events and log traces.
- Preventing account recreation from repopulating search indexes with stale data.
Known limitations
Cannot rewrite immutable backups or physical archives. Does not provide legal advice or determine statutory retention periods.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Agents & Orchestration.
Cannot rewrite immutable backups. Requires existing technical evidence for data discovery. Does not determine legal retention obligations.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 3 months ago
- Software
- prisma
Node.js
Permissions
Permissions are limited to the active local workspace and are used to inspect user-supplied or local workspace files; create or modify bounded local fixes, tests, documentation, or review artifacts; run repository-supported local tests, checks, builds, or parsing commands. The skill package does not require bundled credentials, unrestricted external network access, or automatic production changes.