Privacy
What Deputy reads on your computer, what leaves it, and who receives it. A summary of the privacy policy.
This page summarises the Deputy privacy policy, last updated 10 October 2026, which covers the Deputy extension, deputy-mcp and the Deputy Pro service. The policy is the one that applies; where they differ, it wins.
In short: pages are read on your computer and handed to your agent there. They aren't sent to Razin. Deputy has no analytics, no tracking and no ads, and sells nothing.
What stays on your computer
When an agent you run uses Deputy, the extension reads the pages that agent works on: their content, forms and field values, links and buttons, the console messages and network activity the page produces, and the tab addresses and titles needed to address tabs. It also handles files your agent asks it to upload, and files the browser downloads at your agent's request.
All of it goes only to deputy-mcp on your own computer, over 127.0.0.1, and from there to your agent.
Your own model key
If you set your own OPENROUTER_API_KEY, deputy-mcp sends the page text it needs and your agent's question from your computer directly to OpenRouter, under your own account. Nothing passes through Razin. Remove the key to stop it.
What Deputy Pro's server receives
- Your license key, a few times a day, to check your plan is active.
- Screenshots, only if you allow them. With the setup page's Allow Deputy Pro to send a screenshot switch on,
browser_looksends a screenshot of that tab over HTTPS, with your key, the page's title and address, and your agent's question. Deputy's server passes them through OpenRouter to Anthropic's Claude model on Amazon Bedrock, or on Google's Vertex AI if Bedrock is unavailable. Only zero-data-retention providers are allowed: none of them keeps the screenshot after answering or trains on it. Razin doesn't store screenshots, and no person looks at them. - A fingerprint of the last screenshot. To stop an agent stuck in a loop from paying for the same screenshot again and again, the server keeps a one-way SHA-256 hash of the most recent screenshot for each key, with how often it repeated. It can't be turned back into the image, and it's replaced when a different screenshot arrives.
- Page text for Pro's planner, sent the same way, under the same zero-data-retention rule, and not stored.
- Usage counts: actions per key, per day and per month, to enforce the plan's limits.
- Your key's record: your email address, Polar's customer and subscription ids, your plan and when it renews or ends.
Payment
Polar sells Deputy Pro as merchant of record and processes the payment. Razin never sees your card details.
Who receives it
| Recipient | What | Why |
|---|---|---|
| Cloudflare | Requests to Deputy's server, including your IP address | Hosts Deputy Pro |
| OpenRouter | Screenshots, page text, questions | Routes them to the model provider |
| Amazon (Bedrock) | Screenshots, page text, page title and address, questions | Runs the Claude model, with zero data retention |
| Google (Vertex AI) | The same, when Bedrock is unavailable or Gemini is chosen | Runs the Claude or Gemini model, with zero data retention |
| Polar | Payment details, email | Merchant of record |
How long it's kept
- Screenshots and planner text: not stored.
- The screenshot fingerprint: until a different screenshot arrives from the same key.
- Your key's record and usage counts: deleted 24 months after your plan last ended, or sooner if you ask.
Your controls
- Turn the screenshot switch off, remove your license key, or uninstall the extension, which deletes its settings.
- Remove
OPENROUTER_API_KEYto stopdeputy-mcpcalling OpenRouter. - Ask to access, correct, delete or export your data: write to hello@razin.ai.
Deputy is a developer tool and isn't directed at children under 16. For everything else, including the legal bases and international transfers, read the full policy.