Skip to content

Sharing

Claspt lets you share pages or individual secret values with anyone — even people who don’t use Claspt. Shared content is encrypted client-side before it ever leaves your device, so the server never sees plaintext.

TypeWhat’s sharedUse case
Page shareFull page content including all secretsSharing a complete credentials page with a teammate
Secret shareA single secret valueSending one password or API key
  1. Right-click a page in the sidebar and select Share, or click the share icon on an individual secret card.
  2. Set a share password — this encrypts the content before upload. The recipient needs this password to view the share.
  3. Configure options — expiry time and burn-after-reading (see below).
  4. Copy the link and send it to your recipient.

The share link format is:

https://app.claspt.app/s/{id}

When the recipient opens the link, they enter the share password in their browser. Decryption happens entirely in the browser — the server only stores and delivers the encrypted blob.

Enable Burn after reading to automatically delete the share after it’s been viewed once. This is ideal for one-time credential handoffs — once the recipient opens and decrypts the share, it’s permanently deleted from the server. No one (including you) can access it again.

Every share has an expiry time. You can configure it when creating the share:

OptionDuration
1 hourShort-lived, for immediate handoffs
24 hoursDefault for quick shares
7 daysFor shares that might not be opened immediately
30 daysMaximum allowed expiry

After expiry, the encrypted blob is deleted from the server regardless of whether it was viewed.

Changed your mind? You can revoke a share before it’s been viewed or before it expires:

  • From the app: Right-click the shared page in the sidebar and select Revoke Share.
  • From the Account Portal: Go to Account Portal > Shares to see all active shares and revoke any of them.

Revoking immediately deletes the encrypted blob from the server. The share link will show “This share has expired or been revoked.”

PropertyDetail
EncryptionAES-256-GCM, client-side
Key derivationShare password is never sent to the server
Server knowledgeEncrypted blob only — no plaintext, no share password
Size limit256 KB per share
TransportHTTPS (TLS 1.3)
  • Maximum share size is 256 KB (covers most credential pages).
  • Shares expire after a maximum of 30 days.
  • Burn-after-reading shares cannot be viewed again after the first decryption — make sure the recipient saves what they need.