Legal
Deputy privacy policy
Who we are
Deputy is a product of Razin, part of Falaq. Falaq is the trading name of Zain Kamal Raisan, a sole trader in Dubai, United Arab Emirates ("we", "us"). We are the controller for the personal data described below. Privacy contact: hello@razin.ai.
What Deputy handles on your computer
When an AI agent you run uses Deputy, the extension reads the pages that agent works on: their content, forms and field values, links and buttons, console messages and network activity the page produces, and the tab URLs 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 this goes only to the deputy-mcp program on your own computer, over 127.0.0.1, and from there to your agent. It is not sent to us.
Your own model key (optional)
deputy-mcp can use a small language model to read a page for your agent. This only happens if you set your own OpenRouter API key in the OPENROUTER_API_KEY environment variable. Then, for those requests, 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 us, and it is handled under OpenRouter's privacy policy. Without a key, Deputy falls back to on-device keyword matching and sends nothing.
What is sent to us, with a Deputy license key
License check. The extension sends your license key to our server a few times a day to check that your plan is active. The request carries only the key, and we keep nothing from it beyond your key's record.
Screenshots. Only with Deputy Pro, and only after you switch on "Allow Deputy Pro to send a screenshot" on Deputy's setup page. When your agent calls browser_look, a screenshot of that tab is sent over HTTPS to our server, with your license key, the page's title and address, and your agent's question. Our server passes them to OpenRouter, which sends them to Anthropic's Claude model running on Amazon Bedrock or, if Bedrock is unavailable, on Google's Vertex AI. We require zero-data-retention providers only: none of them keeps the screenshot after answering or uses it to train models. We do not store screenshots, and no person looks at them.
To stop an agent stuck in a loop from paying for the same screenshot over and over, we keep a one-way fingerprint (a SHA-256 hash) of the most recent screenshot for each license key, with a count of how often it repeated and when it was first seen. A hash cannot be turned back into the image.
Page text for the planner. When Pro's planner is used, the page text and the question it needs are sent the same way, under the same zero-data-retention rule, to the same Claude model or to Google's Gemini model on Vertex AI if your agent asks for it. We do not store this text either.
Usage counts. To enforce plan limits, we count actions per license key per day and per month.
Your key's record. We issue your license key and keep a record of it: your email address, Creem's customer and subscription ids, your plan and when it renews or ends, and the checkout that created the key, so the page you return to after checkout can show it to you.
Your key by email. If we email you your license key, we send it to the address you paid with, once, through our email provider Resend.
Payment
Deputy Pro is sold through Creem (Armitage Labs OÜ), which processes payment as merchant of record. Creem tells us your email address, its customer and subscription ids, and what you bought, and we issue your license key. We never see your card details. We use this only to provide Deputy Pro and to answer your support requests. Creem handles your payment details under Creem's privacy policy.
Why we may process this data (legal bases)
- Screenshots: your consent, given with the screenshot switch. You can withdraw it at any time by turning the switch off.
- License key and its record, email (including sending you your key), usage counts and planner requests: to perform our contract with you, meaning to provide the plan you chose and enforce its limits.
- The screenshot fingerprint: our legitimate interest in stopping runaway loops from using up your plan.
Who receives it
| Recipient | What | Why |
|---|---|---|
| Cloudflare | Requests to our 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 |
| Creem (Armitage Labs OÜ) | Payment details, email, country | Merchant of record: sells Deputy Pro, takes payment, handles tax |
| Resend | Your email address and license key | Sends your key by email after you buy |
We may also share data with our professional advisers, such as accountants or lawyers, and with authorities where the law requires it. We never sell it.
International transfers
These providers may process data outside your country, including in the United States and the European Union. Where the law requires it, the transfers are covered by the providers' standard contractual clauses or an equivalent safeguard.
How long we keep it
- Screenshots and planner text: not stored by us. They are processed only to answer the request.
- The screenshot fingerprint: replaced when a different screenshot arrives from the same license key.
- Your key's record and its usage counts: deleted 24 months after your plan last ended, or sooner if you ask.
What we never do
No analytics or tracking. No ads. We do not sell or transfer your data, use it for anything other than Deputy's features, or use it to determine creditworthiness or for lending. Our use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.
Your controls and rights
- Turn the screenshot switch off, remove your license key, or uninstall the extension (which deletes its settings) at any time.
- Remove OPENROUTER_API_KEY to stop deputy-mcp from calling OpenRouter.
- Running your agent's own JavaScript requires Chrome's "Allow User Scripts" switch for Deputy, which is off unless you turn it on.
- Depending on where you live, you have the right to access, correct, delete or export the personal data we hold about you, to object to or restrict its processing, and to withdraw consent. Write to hello@razin.ai; we answer within one month. If you are in the EU, the EEA or the UK, you can also complain to your local data protection authority.
Children
Deputy is a developer tool and is not directed at children under 16. We do not knowingly collect data from children.
Security
Everything sent to Deputy Pro, OpenRouter or the model providers travels over HTTPS. The local connection never leaves your computer.
Changes
If this policy changes, we will update the date above, and Deputy will say so on its setup page before the change applies.