client-ids

Enforce privacy library usage to protect sensitive identifiers in Ledger Live.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Ledger-Wallet-LLC/ledgerwallet --skill client-ids
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: client-ids
Source: https://github.com/Ledger-Wallet-LLC/ledgerwallet/tree/main/.cursor/skills/client-ids
Command: npx skills add https://github.com/Ledger-Wallet-LLC/ledgerwallet --skill client-ids

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The privacy library centralizes and protects sensitive identifiers (DeviceId, UserId, DatadogId) used within Ledger Live, ensuring they are never exposed through logs or UI and are accessed only via controlled export paths.

Core Features & Use Cases

  • Unified, privacy-protected ID handling for all Ledger Live modules.
  • Explicit export methods and allowlist-driven usage to prevent accidental leakage.
  • Redaction mechanisms in toString() and toJSON() to prevent sensitive data exposure in logs and serialized data.

Quick Start

Install and integrate the @ledgerhq/client-ids library in your codebase and begin using the export API at system boundaries.

Frequently Asked Questions about client-ids

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

FAQPage Schema
How do I prevent sensitive identifiers like DeviceId and UserId from leaking in Ledger Live logs?

To redact sensitive identifiers in serialized data, implement redaction mechanisms within toString() and toJSON() methods using a centralized privacy library, preventing DeviceId, UserId, and DatadogId exposure across Ledger Live modules.

How do I control the export of privacy-protected user IDs in a JavaScript application?

You control the export of privacy-protected user IDs by defining explicit export methods and utilizing an allowlist-driven approach via export-rules.json, restricting sensitive identifier access to approved use cases only.

What is the best way to manage device IDs for analytics without exposing user privacy?

Managing device IDs for analytics without exposing privacy requires routing all identifier access through controlled API boundaries and a centralized privacy library, ensuring explicit export method requirements are satisfied.

Do I need an allowlist to use the privacy library for ID management?

Yes, you need an allowlist defined in export-rules.json to use the privacy library for ID management, as it ensures only explicitly approved use cases can access sensitive identifiers like DeviceId and UserId.

When should I redact sensitive identifiers in toString and toJSON implementations?

You should redact sensitive identifiers in toString and toJSON implementations whenever handling DeviceId, UserId, or DatadogId across Ledger Live development, preventing accidental data exposure in logs and serialized outputs.