Public blockchain activity
XDCID names, ownership, expiry, resolver records, wallet addresses, and transactions written to supported public networks are public by design. XDCID cannot make on-chain data private or delete it from a blockchain.
Privacy at XDCID
Public where blockchain requires it. Private where the product can protect it.
This summary explains the platform's current data boundaries. It is written for product transparency and does not change the public nature of blockchain activity.
Payment and receipt records
When supported payments complete, XDCID may store transaction hashes, participants, amount, asset, route, timestamps, and receipt metadata. Access to private history requires a fresh wallet signature. Private references and descriptions are encrypted before storage.
Pay Links
A short Pay Link stores the signed request needed to present and verify checkout. XDCID does not store a private key or sign the payment transaction. Links expire when paid, cancelled, or when their configured retention period ends.
Analytics
Production analytics measure aggregate page visits and a small allowlist of product events. Query strings, URL fragments, XDCID names, Pay Link identifiers, wallet addresses, transaction hashes, amounts, and free-form text are not sent as analytics properties.
Wallet connection
Connecting a wallet exposes the active public address and network to the application. XDCID never requests a seed phrase or private key. Wallet signatures are used only for the purpose described in the wallet prompt.
Retention and control
Payment-history retention is governed by the platform history policy and operational controls. Blockchain records are outside XDCID's control. Do not place secrets or sensitive personal information in public name records or transaction fields.
Never share a seed phrase, private key, password, or exchange recovery code with XDCID or through a public support channel.