Share a snapshot without leaking anything

A share link is the one part of a private analytics account that other people see. It deserves more care than a screenshot and it should behave less like a login than a poster.

The model here is a snapshot: a frozen copy of the numbers you selected at the moment you selected them. A share is never a live window into your account, so nothing you import later appears on a link you already sent.

Open Shares. The snapshot is built from a dashboard range, so choose the period you actually want to talk about — a week, a month, or all time.

If the selected range contains no sessions, there is nothing to publish and the app sends you back to importing instead of creating an empty card.

Only a fixed list of totals can be shared at all: sessions, prompts, responses, tool calls, agents, providers used, active projects, the four duration fields, input and output tokens, and API-equivalent cost.

You tick the ones you want. Nothing outside that list is shareable, which means there is no configuration mistake that can put a message, a title, or an internal record ID onto a public page.

Four optional blocks can be added separately: provider split, model ranking, project ranking, and metric quality coverage. Including quality coverage is a good habit — a number is easier to trust when the card also says how complete it was.

There are two independent switches, and they are deliberately not one.

• Visibility is unlisted or public. Unlisted is the default: the link works for anyone who has it, and nothing points at it.
• Indexing is a separate opt-in, and it is available only for public shares. Leave it off and the page carries a noindex directive.

The link itself is not guessable. Each share gets a slug generated from 24 random bytes, which is why an unlisted link is meaningfully unlisted rather than merely unlinked.

Choose 7, 30, or 90 days, or no expiry.

Pick an expiry whenever the number is tied to a moment — a year in review, a launch week, a conference talk. An expired link returns a 404, exactly like a revoked one, rather than a page explaining what used to be there.

Creating the snapshot opens it. Read it as a stranger would.

The page shows the title, the range and timezone the numbers cover, the fields you chose, and the generation time. If a project name on the card is more revealing than you intended, that is the moment to notice — project rankings are published with their internal identifiers stripped, but the names are the ones you chose yourself.

Every share also has a downloadable image, which is usually the safer thing to post publicly: it carries the same numbers without the link.

The shares list shows each snapshot with its visibility, whether it is active, revoked, or expired, whether it is indexable, and its view count.

Revoke is immediate and permanent for that link. The URL returns 404 afterwards. Since a snapshot is immutable, revoking is the correction mechanism: you do not edit a share, you revoke it and create a new one.

Every snapshot records its own privacy stance alongside the numbers, and three flags are always false: no raw content, no session titles, no internal identifiers.

That is the whole guarantee, and it is narrow on purpose. A share contains totals you selected, from a range you selected, at a moment that is written on the card. Everything else stays in your account.

Privacy, exports, deletion, and sharing documents the same rules from the account side.