MusePass

Privacy

Short version: we keep the working records a name service needs, we publish nothing about you that the chain does not already publish, and the private fields of your card never leave your hands. Last updated 2026-10-01.

What is on chain (public, permanent)

A registered name and its owning wallet address are on a public blockchain by construction — that is the product. When you publish a card, what gets written to the name's text record is only the fields you marked public, plus a hash of the whole card. Fields you keep private are not in the transaction, not in the record, and not in the bytes you sign. Records published before 2026-10-01 contained the whole card as the owner submitted it; those cannot be deleted, and that format is not used any more.

What we store on our server

  • The name index: label, owner address, transaction hash, registration date — the same facts the chain already publishes.
  • The sponsorship ledger: which wallet's registration gas we paid, and the transaction hash, so the free-name budget can be counted and published.
  • Registration requests: the label, an expiry, a hashed confirmation token, and the requesting host — deleted or expired after 15 minutes of life.
  • Invitation spend records: the wallet address, the label it took, the transaction hash. Counts are published; the list of who was invited is not.
  • Card version metadata: the content hash and your visibility choices. The private contents of cards are not stored.

What we do not do

  • No accounts, no passwords, no email collection.
  • No third-party analytics, advertising or tracking scripts are loaded by this site.
  • We do not sell, rent or “share” anything — there is nothing to share beyond the public chain records above.

Server logs

The site and API keep standard request logs (IP address, path, timestamp) and use them for rate limiting and abuse prevention. Rate-limit counters live in memory and reset when the service restarts.

Deletion

On-chain records cannot be deleted by anyone, including us. Our working records (index, logs, requests) are operational data tied to public chain events; write to us at support@musepass.xyz with questions or removal requests and we will say plainly what is and is not possible.

This page describes today's product. If a feature is added that changes what is collected, this page changes with it before the feature opens.