Privacy policy — Peek Last updated: October 28, 2026
Peek previews a link only when you request it. This release requires your own AI provider key or a compatible local server. Peek does not provide a hosted AI service or collect analytics.
When you request a preview, the linked page text (or extracted PDF text), source page title and URL (without query strings or fragments), nearby passage, link text, and nearest heading are sent directly to the provider you select: Anthropic, OpenAI, Google Gemini, or your configured compatible endpoint. Your API key is sent to that provider to authenticate requests. Testing a key contacts that provider to check access and list models. Provider terms, retention policies, and usage charges apply.
Peek fetches the destination website directly. Background loading is off by default and requires opting in through Settings. If enabled, it can open the requested destination in a background tab using your existing login session. This can produce normal visit signals on that website. Suspected action URLs are blocked before any fetch; you can disable background loading or exclude hosts in Settings.
Keys, settings, and cached answers are stored locally in your browser profile, not synced. Keys are not encrypted by Peek. Anyone with access to your profile may be able to read them. Cached answers are reused only within the configured period, 24 hours by default. Expired records are removed when accessed; other cached records can remain until cleared or evicted. Set caching to zero to disable new cache writes. Remove the extension or clear its extension storage to delete local data.
Peek's developer does not receive your keys or page content, sell data, use it for advertising, or train models on it. Data is used only to provide the requested link-preview functionality. Peek complies with the Chrome Web Store User Data Policy, including its Limited Use requirements.
Contact: hello@simondoku.com