hlr-48-blueprint-for-requesting-data-deletion-t

Facilitate user-initiated data deletion requests from Relying Parties via web, email, or phone.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/sourcelabbg/eudi-knowledge --skill hlr-48-blueprint-for-requesting-data-deletion-t
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hlr-48-blueprint-for-requesting-data-deletion-t
Source: https://github.com/sourcelabbg/eudi-knowledge/tree/main/.ai/skills/hlr-48-blueprint-for-requesting-data-deletion-t
Command: npx skills add https://github.com/sourcelabbg/eudi-knowledge --skill hlr-48-blueprint-for-requesting-data-deletion-t

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the need for users to request the erasure of their attributes from Relying Parties, in compliance with data protection regulations.

Core Features & Use Cases

  • Data Deletion Request Support: Enables Wallet Units to facilitate user requests for attribute erasure from Relying Parties.
  • Multiple Request Methods: Supports initiating requests via external browser (web form), email client, or phone client.
  • Use Case: A user wants to ensure their data is deleted from a service they previously used. They can use their EUDI Wallet to initiate this request through the service's preferred contact method, as logged during the initial transaction.

Quick Start

Use the hlr-48-blueprint-for-requesting-data-deletion-t skill to initiate a data deletion request for a previously presented attestation.

Frequently Asked Questions about hlr-48-blueprint-for-requesting-data-deletion-t

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

FAQPage Schema
How do I request data deletion from a Relying Party using an EUDI wallet?

To request data deletion, use your EUDI Wallet Unit to initiate an attribute erasure request to a Relying Party. The wallet facilitates this request via the service's preferred contact method, ensuring compliance with GDPR Article 17.

What communication channels support GDPR data deletion requests in EUDI workflows?

EUDI data deletion requests support multiple communication channels. You can initiate attribute erasure via an external browser using a web form, an email client, or a phone client to contact the Relying Party directly.

Does a Wallet Unit need to log data deletion request initiations?

Yes, Wallet Units are required to log data deletion request initiations. When facilitating GDPR Article 17 attribute erasure, the wallet may also retrieve necessary contact information from registrars to route the request.

When do I need to use the EUDI attribute erasure process?

You need the EUDI attribute erasure process when you want to ensure your data is deleted from a service you previously used. It facilitates user-initiated requests to Relying Parties for compliance with data protection regulations.

Can I retrieve Relying Party contact information from registrars for data deletion?

Yes, Wallet Units can potentially retrieve contact information from registrars during the data deletion process. This ensures your attribute erasure request reaches the correct Relying Party through their logged preferred contact method.