How claim codes, storage redeem codes, and page passwords differ

Know when to use claim codes for consent, storage redeem codes for quota upgrades, and page passwords for per‑page access.

Who it's for

• Creators who need to gate public works with consent, storage, or access controls.
• Users managing multiple HTMLPUT pages and confused about which code does what.
• Support agents handling tickets about gating mechanisms.

Steps

1. Generate a claim code – required for privacy/terms consent before visitors can claim a public work. Learn about claim code privacy and terms.
2. Redeem a storage code – adds quota or upgrades your plan; it does not affect page access. Redeem a storage code to extend or change your plan.
3. Set a page password – restricts a single hosted page; independent of claim or storage codes. Set or change a password on a hosted page.
4. Manage claim‑code credits – purchase packs or monthly credits for bulk generation. Claim‑code credits: lifetime, monthly, and packs.
5. Cancel or change plans – if you cancel a paid plan, claim codes and storage codes behave per the cancellation and renewal policies. Cancel a paid plan and what happens to your files and How billing and renewals work for paid plans.

Gotchas

• Claim codes are tied to consent and terms, not storage.
• Storage redeem codes affect quota/plan, not page access.
• Page passwords only lock a single hosted page; they don’t change storage or claim status.