A clipboard manager built around what we don't see.

Yes — and that's the point. You don't get a paste-buffer for desktop apps; that's intentional. What you DO get is everything we can do well within the browser scope: auto-categorization across 18 content types, AI summaries, OCR on screenshots, YouTube transcript analysis, link summarization, rich social-media previews for 8 platforms, multi-feed TweetDeck-style organization, and full-text search across hours of saved content. For browser-heavy workflows (research, journalism, development, content creation, sales prospecting), that's most of what a clipboard manager is for anyway.

No — this is a positioning choice, not a missing feature. Browser-only is how we keep the threat model small, the Chrome Web Store review fast (limited-scope extensions clear review faster), and the trust ceiling high. If we ever build a desktop companion, it would be opt-in, separately installable, and clearly identified as a system-scope tool — never bundled with the browser extension. Today, none of that exists or is planned.

When you click "Copy" in a browser extension popup (1Password, Bitwarden, LastPass), the credential ends up on the clipboard via the browser's Async Clipboard API. KopyFeed's content scripts can technically observe this — but our sensitive-content detector recognizes API keys, AWS tokens, JWTs, credit card numbers, SSNs, GitHub/GitLab/Slack/Google Cloud/npm/Twilio/SendGrid tokens, PEM-encoded private keys, database connection strings, and high-entropy password-like strings on-device before any sync. Detected content is masked in the UI, auto-expires (10 minutes, optional), and is never sent to the cloud or to AI. Your credentials are technically captured for a few seconds locally; they never leave your device.

That action — pasting into a browser tab — does not trigger a KopyFeed capture. We only capture on copy events that originate inside a browser tab. If you Cmd+C in your terminal and Cmd+V in Chrome, KopyFeed never sees the original copy. Same for copying from your password manager, native Notion app, Slack desktop, or any OS-level utility. The browser-only scope is enforced at the event level, not just the data level.

Universal Clipboard syncs your system clipboard between Apple devices over iCloud — same security model and same threat model as a local system clipboard manager, just with sync added. KopyFeed doesn't replace Universal Clipboard for cross-device system-clipboard sync; we don't compete on that axis. KopyFeed's cross-device feature (paid tiers) syncs your saved browser captures to other browsers signed into the same KopyFeed account. They're complementary tools solving different problems.

Generally yes, though we can't speak to every individual policy. Many enterprise IT policies prohibit system-clipboard utilities because they read process memory, hook system APIs, or sync clipboard data outside the corporate environment. KopyFeed's Chrome extension uses only the standard Manifest V3 clipboard permissions, scoped to browser tabs, and runs entirely within Chrome's existing extension sandbox. The full list of extension permissions is published in our Privacy Policy. For regulated environments, the excluded-websites list lets IT block capture on internal domains entirely.

Some Chrome extensions request the `clipboardRead` permission, which lets them read the system clipboard when the user interacts with the extension (and only at that moment — Chrome enforces user activation). KopyFeed requests this permission too, but uses it only for writing to the clipboard from the Side Panel (copying a clip back out) — not for reading the system clipboard. Our capture happens at the in-page copy-event level via content scripts, which is a different mechanism with a narrower scope. The Chrome Web Store listing and our Privacy Policy document exactly which APIs we use and why.