Safety and policy
Important boundaries for registry trust, claim email safety, investment language, privacy and third-party records.
- Audience
- Everyone
- Updated
- 2026-07-29
Non-investment position
EditionKey is not a marketplace, broker, exchange, investment adviser, or promise of value. Help content and product UI should avoid language that suggests profit, guaranteed resale, buyback, yield or speculation.
NFT Certificate means the physical card's digital certificate. It does not mean platform-backed financial value.
Shop copy should describe buying physical cards, shipping, self-pickup and certificate claiming. It should not describe NFT trading, price discovery, mystery boxes, platform tokens or investment upside.
Claim email safety
A claim email contains a secure My Cards sign-in invitation for the original purchase email. A valid link signs that email in for one hour, but does not claim or transfer a certificate. The link is not your wallet private key and does not give EditionKey control of your wallet.
EditionKey never asks for wallet private keys, seed phrases or recovery phrases. Do not paste those phrases into any EditionKey page, email reply, chat, form or external wallet prompt.
Claim links expire after 7 days by default. If a link expires, use the expired-link page to request a new link with the purchase email or phone; the page should use generic success text and should not reveal whether a contact matched.
The public Card page does not resend claim emails on demand because a non-buyer could otherwise use a visible Card ID to bother the real buyer.
After a certificate has transferred to a personal wallet, EditionKey cannot resend a claim email to move that certificate again without the wallet's authorization.
Third-party and indexed data
Third-party assets can enter a candidate workflow, but they should not be public by default. Indexed Only records, if introduced, must explain that indexing is not endorsement.
Admins should review source, rights, image suitability, metadata quality and risk flags before publishing.
Privacy
Public pages should use truncated wallet previews and avoid exposing full private user details. Secrets, provider tokens and private keys must never appear in help content, documents or public pages.