humanity.llc Create

Help

How this works

One place for the guides scattered across warnings, hub copy, and feature pages. You own your objects — control stays in this browser unless you export a backup.

Ownership & control

You own the object. Humanity keeps control in your browser so you can update, revoke, and prove live state. The network stores public status — not your ability to manage it.

Active in this tab only until you save ownership on this device. Close the tab without saving and you may lose manage access until you restore from backup or a recovery code.

Saved on this device keeps ownership in this browser after you close tabs. Use Open controls on My objects to manage again. Auto-save is on by default after create.

Pick at least one cross-device path before you rely on a card — restore on another device · ways you can lose access.

You do not need every backup type. Choose one path and save what that path requires. humanity.llc never holds your keys and cannot look cards up by handle — there is no password reset.

  • Same browser only — if you saved ownership on this device, reopen the site here and tap Open controls. Works after tab close; does not move to a new phone or browser.
  • Encrypted backup — you need the .hcbackup.json file and the passphrase you chose at export. The file already contains your card ID, so you do not need a scan link separately. Import in the hub under Restore & scan or on /created/ Manage.
  • Recovery code — you need two things: the recovery code you saved at create, and your scan link or profile ID (https://humanity.llc/c/…). The code alone is not enough — it proves you own a card, but the app must know which card to check. Save the scan URL, profile ID, a bookmark, or a photo of your printed QR alongside the code. Import both in the hub under Import recovery code.

Hub search only filters cards already saved on this device — it is not a global lookup by handle. Scanning your own printed hoodie or sticker? Use Restore control on the scan page → restore from scan. More detail: backups & recovery methods.

Printed object (hoodie, sticker). When you scan your own QR on a new phone or PWA, the scan page shows Restore control. That opens your card page with the restore panel — paste a recovery code or import an encrypted backup there. You must have saved one of those on the device where you created or purchased.

By design, we cannot restore lost keys for you. If every path below applies to you, the card may still scan publicly but you cannot revoke, update, or prove live control.

  • Close the create tab without saving on this device and without a recovery code or encrypted backup.
  • Clear site data for humanity.llc, use Private Browsing, or switch to a different browser profile — saved ownership lives only in the browser where you saved it.
  • iOS storage eviction — Safari may delete saved cards after about seven days without a visit, or when storage is low. Add to Home Screen and visit regularly; keep a backup if you rely on this phone.
  • Safari vs Home Screen app — on iPhone they are separate storage. Keys saved in one may be invisible in the other until you import a backup or recovery code.
  • Recovery code without scan link — the code cannot identify your card. You still need the scan URL, profile ID, or something that points at your card.
  • Encrypted backup without both parts — the file alone is useless without the passphrase; the passphrase alone is useless without the file.
  • Wrong backup passphrase — import fails with a plain error; there is no forgot-password flow.
  • Never set up recovery at create — if you skipped Protect and never exported a backup, only the original browser session can sign.

iPhone-specific storage behavior: Safari & iOS keys.

Two stores — do not conflate them. Tab session (hc_created) can sign revoke and live proof. Saved on this device (hc_wallet) survives tab close but cannot sign until keys are restored into the active tab.

iPhone Camera QR opens a fresh Safari tab with an empty session. Use Open controls on saved cards, quiet restore on scan pages, or scan from the Home Screen PWA when possible.

PWA vs Safari — Add to Home Screen shares saved wallet but not tab session. Camera and links from other apps open Safari, not your installed app.

Private browsing — create and save are blocked; storage may be cleared when the session ends. Use a normal browser profile and save an encrypted backup.

Storage pressure / ITP — Safari may evict local data after extended disuse. If the hub shows empty but you had cards, try import backup or recovery key — the operator cannot restore lost keys.

Advanced · for developers

This browser

Status dot — floating trust indicator on steward pages (/, /wallet/, /created/). Tap to open the On this device hub sheet. This is shell chrome, not the live control protocol on scan pages.

Inbox — badge and action rows when this tab is visible: unsaved keys, live-proof requests, card-disabled-since-visit (resolver-confirmed only), and cross-tab key notices.

Browser alerts — opt-in only, and only for live proof when the tab is hidden. Cross-tab keys and custody nudges stay in-app — never OS notifications.

Share network checks on the homepage syncs resolver polls across tabs on this device (you can turn it off). Add to Home Screen is available on steward shell pages — strangers scanning a QR are never prompted to install.

More: device hub feature page · all features · merch funnel (partial) · hosted steward tier (partial, production-gated).

Create & manage

More

On landing, wallet, and card pages, use the small ? at the bottom corner to return here.