InstaShare

Optional ownership

Claim anonymous shares and manage them together

InstaShare separates the fast sharing path from the account-management path. You can publish immediately, then use the claim link when a searchable list and signed-in controls become useful.

Past shares come with the device

Claiming attaches shares that already carry the matching device-token hash.

Future shares appear automatically

As long as the device token remains active, later uploads are linked to the same owner.

One management view

My shares lists owned transcripts with titles, dates, size, turn counts, duration, and deletion controls.

How claiming establishes ownership

The claim URL carries the plaintext device claim token to a dedicated flow. After Google authentication, the server associates that token record with the account and updates previously uploaded chats carrying its hash. The public chat URLs and their content do not change.

Later requests from the same device continue sending the claim token. The server resolves the linked owner and stores that owner on new chat documents, so they appear in My shares without another claim action.

Account data is intentionally limited

Google provides the email address, display name, and profile-image URL used by the account session. InstaShare uses a database-backed session and does not ask for a separate InstaShare password.

Signing in is an ownership and management feature. It does not make public shares visible only to the signed-in user, and signing out does not disable links.

Device management remains separate from content management

The account page shows claimed devices, their hostname when supplied, when they were first and last used, and the number of shares made. Revoking a device prevents its current claim token from attaching more uploads. Existing owned shares remain until individually deleted.

How it works

01

Upload anonymously

The skill receives and saves a device claim token.

02

Open the claim URL

The token is carried into the browser claim flow.

03

Authenticate with Google

The device and matching historical shares are attached to the account.

04

Manage continuously

Later uploads appear in My shares while the device remains active.

Important limits

  • Claim URLs and claim tokens grant meaningful authority and should not be shared publicly.
  • Ownership controls mutation and organization; it does not restrict readership of a public share URL.

Related capabilities

Share

Account-free sharing

Create a working InstaShare link without registration, then optionally claim all shares from that device later.

Control

Delete and revoke

Remove a public transcript with its share-specific control or an owner account, and revoke device tokens that should no longer create linked uploads.

Control

Security and privacy controls

See what is protected locally, what becomes public, what the service stores, and which controls remain available after sharing.

Try it in a Claude Code session.

Install the readable skill, then say “share this chat” when the conversation is ready.

Install InstaShareRead security details