Solutions · Privacy-first & local by default
Most browser tools answer "where does my data go?" with a privacy policy. These answer it with architecture: the screenshot is composed on your machine, the recording is converted in the tab, the feed list and read state sit in local storage, and the page you are watching is watched from the session you are already signed into. For the core job, most of them have nowhere to put an account even if you wanted one.
Capturing a screenshot, recording a tab, searching bookmarks and reading feeds all happen in the browser. ScrnCap's capture path does not make a single network request, and ReelCap converts to MP4 or GIF in the tab.
FeedLens keeps subscriptions, read state, stars and cached articles in local storage. Bookmark Commander reads the bookmarks your browser already has. Auto Refresh watches a page inside your own session, so nothing has to be handed to a hosted checker.
Where there is an AI feature you switch it on yourself, and only the text you point it at is sent, for that one request. Nothing runs in the background before or after.
Turn the RSS firehose into a 5-minute brief.
Subscriptions, read state, stars and cached articles live in your browser's local storage — no account to create, and no server that knows what you read. AI summaries are opt-in and sent one request at a time.
Take command of a thousand bookmarks.
Search, the side-panel manager and the duplicate and dead-link cleanup all run against the bookmarks your browser already has, offline and free. An account comes in only for AI organize and cloud backup.
Screenshot any page. Then make it yours.
The free capture path is fully local and makes no network request at all, so our servers never touch the image. Even the Pro exports are composed on a canvas in your own browser.
Record web demos that point where you point.
Recording needs no account, and the Pro extras — click auto-zoom, MP4 and GIF export — run in the tab as well. Your video is never uploaded to be processed.
Reload a page on a timer. Get told the moment it changes.
It watches a page from inside the session you are already signed into. That is why it can see a dashboard behind a company login that a hosted monitor never could — and why that page's contents never have to be given to anyone.
For the core job, no. Capturing, recording, reading feeds, searching bookmarks and refreshing or watching a page all work as soon as you install. Accounts come in only where a paid or synced feature needs one, and each product page says which is which.
That the feature still works with the network off. It is not a promise in a privacy policy, it is a statement about where the code runs: the screenshot is composed in your browser, the video is converted in the tab, the feed cache is in local storage.
The text you point it at, for that one request. AI is opt-in in every one of these products — you switch it on, and nothing is collected in the background before or after.
From the paid tiers people use professionally: AI organize and cloud backup, beautified and batch exports, click auto-zoom and video export, alerts that leave the browser. The free local features stay free, and every price is public on the product page.