100% local.
Nothing leaves your browser.
Markagent runs entirely on your machine. There are no analytics, no servers, no accounts, and no outbound network requests. You can verify it yourself in Chrome DevTools' Network tab.
What Markagent does not collect
- No analytics, telemetry, or usage metrics.
- No tracking, fingerprinting, or advertising identifiers.
- No accounts, no login, no email — ever.
- No cloud sync. No remote backup.
- No outbound network requests from the extension itself.
Where your data lives
Annotations, screenshots, notes, and copied prompts are kept in your browser's local extension storage. They stay on the device that created them and are never transmitted to Markagent or any third party. Clearing your extension storage or uninstalling Markagent removes everything.
Why Markagent needs host permissions
The Chrome host permission lets Markagent inject its toolbar and read DOM structure on the pages you choose to annotate — capturing the React component, source file (in dev mode), CSS selector, page URL, and viewport size that make your prompts pixel-precise. This access is used locally to build the markdown prompt and is not transmitted anywhere.
Screenshots
Full-page and element-cropped screenshots are generated and stored locally. They are included only in the prompt you explicitly copy — and that prompt goes wherever you choose to paste it. Markagent never uploads screenshots on your behalf.
Copy as markdown
When you click Copy as markdown, Markagent assembles a markdown prompt and copies it to your clipboard. What happens next is up to you: paste it into Claude Code, Cursor, Codex, OpenCode, Antigravity, or any other tool. Those destinations have their own privacy policies, which apply once the prompt leaves your clipboard.
Changes
If this policy ever changes, the "last updated" date above will change with it. The core promise — your annotations never leave your browser — will not.