Why Peekly runs entirely in your browser

A lot of browser extensions describe themselves as “privacy-friendly” while quietly routing your activity through a server somewhere. Peekly’s architecture makes that structurally impossible for the core feature: when you preview a link, the extension fetches that page directly from your browser, the same way opening it in a new tab would. There is no Peekly server positioned to see it, because none is involved.

What that actually means

• No account or login is required to use previews, Feed view, or the AI assistant.
• Your settings, theme, and excluded-sites list live in Chrome’s local storage, scoped to your browser profile, never synced to us.
• If you add an AI provider key, it’s stored the same way and used only to call that provider directly. We never see it, and it’s never proxied through anything we run.

The tradeoff, honestly

Running everything locally means Peekly can’t offer things that genuinely require a server. Cross-device sync of your browsing activity, for instance, isn’t something we do, because it would mean building the exact server-in-the-middle we’re avoiding. What you get instead is an extension where “we don’t see your data” isn’t a policy promise, it’s just how the thing is built.