Sharing chats — LADLE docs

Sharing is opt-in and per-chat. Nothing you type is ever public until you explicitly share the chat. When you do, LADLE takes a snapshot of the chat's current active branch (not the raw DB rows) and publishes it at /share/:slug — a public read-only page anyone with the link can view without an account.

What's in the snapshot

The snapshot is a copy of the active-branch messages at share time. It does NOT update as you continue chatting.

Messages on the active branchIncluded (role, content, model, created_at, citations)

Other branches (regenerate siblings)Not included

Image attachmentsCopied to a public bucket (shared-assets/), rendered inline in the share page

PDF attachmentsRepresented as chips — filename + size, but the bytes stay private

Custom instructions / memory / project knowledgeNot included (would leak private context)

Reasoning traces (thinking blocks)Not included

Second-opinion blocksNot included in the public snapshot

URL model and privacy

Every share URL is a random 10-character slug from a-z0-9 (36^10 ≈ 3.7 × 10^15 possibilities).

Share URLhttps://ladle.chat/share/<10-char-slug>

DiscoverabilityNot indexable by search engines by default. Robots.txt disallows /share/*. Setting shared_chats.indexable = true opts a specific share in.

RevokeSettings → Data & privacy → your shares. Sets revoked_at; the public page returns 404 immediately.

Anon accessGET /share/:slug renders without auth. RLS is bypassed via a policy that allows unauthenticated read of un-revoked snapshots by slug only.

Listing and revoking

GET /api/app/shared returns every share the caller has ever created (live + revoked). Settings → Data & privacy displays them with per-share Revoke buttons. Revoked shares stay in the DB (for the historical record) but the public page returns 404. Un-revoking is not supported — sharing again produces a new slug.

Docs: Data export

Task guides in /help: Delete your data.

What's in the snapshot

The snapshot is a copy of the active-branch messages at share time. It does NOT update as you continue chatting.

Messages on the active branchIncluded (role, content, model, created_at, citations)

Other branches (regenerate siblings)Not included

Image attachmentsCopied to a public bucket (shared-assets/), rendered inline in the share page

PDF attachmentsRepresented as chips — filename + size, but the bytes stay private

Custom instructions / memory / project knowledgeNot included (would leak private context)

Reasoning traces (thinking blocks)Not included

Second-opinion blocksNot included in the public snapshot

URL model and privacy

Every share URL is a random 10-character slug from a-z0-9 (36^10 ≈ 3.7 × 10^15 possibilities).

Share URLhttps://ladle.chat/share/<10-char-slug>

DiscoverabilityNot indexable by search engines by default. Robots.txt disallows /share/*. Setting shared_chats.indexable = true opts a specific share in.

RevokeSettings → Data & privacy → your shares. Sets revoked_at; the public page returns 404 immediately.

Anon accessGET /share/:slug renders without auth. RLS is bypassed via a policy that allows unauthenticated read of un-revoked snapshots by slug only.

Listing and revoking

Docs: Data export

Task guides in /help: Delete your data.

Sharing chats.

What's in the snapshot

URL model and privacy

Listing and revoking

Docs stay current. Report drift.

Sharing chats.

What's in the snapshot

URL model and privacy

Listing and revoking

Docs stay current. Report drift.