What Gist does on your device vs. on our servers
Your browsing history never reaches our servers. A content fingerprint may be sent before you click. After you click, we process, cache the summary, and delete the source.
Your browsing does not reach our servers until you ask it to.
Before you click — on your device
Gist checks the pages you open against a local on-device index to decide whether to suggest a Gist. No page URLs, no page content, and no browsing history reach our servers as part of this check.
On a local-index miss, a derived content fingerprint — not the URL, not any page text — may be sent to our servers to verify availability. Your browsing habits are never reconstructed from this signal.
After you click — on our servers
When you click Gist (or paste a URL into /try), the source is sent to our servers. We read it, generate the layered summary, and return it to your reader.
Two things then happen:
- The finished summary is cached — so you can re-open it instantly, and so a share URL can render for anyone you send it to.
- The original source payload is deleted. We do not keep the article, the PDF, or the video.
Share pages are explicit
A Gist becomes public only when you create a share link. Nothing is published by default. No Gist appears on the web unless you put it there on purpose.
Delete is a real option
If you created a share link and want it removed, send the URL through contact support. If you want your account and reading history deleted, ask from the email on the account. See Delete my data for the specifics.
What is next
- The layers — what actually reaches our servers after you click.
- Delete my data — how to remove a share or delete your account and history.