Skip to main content

Privacy Policy

Effective date: 7 October 2026

ScrapeOps Ltd ("us", "we", or "our") is an Irish company. We operate the https://scrapeops.io website and the ScrapeOps proxy, parser, monitoring, and MCP services (the "Service").

This page explains what we collect, how long we keep it, and who else receives it when you use the Service. Our Data Protection Policy describes the same practices in more detail. Unless otherwise defined here, terms have the same meanings as in our Terms and Conditions, accessible from https://scrapeops.io.

Information Collection And Use​

We collect the information below to provide the Service, bill for it, secure it, and improve it.

Types of Data Collected​

Account and website data​

When you register or contact us, we collect personal data such as your email address, name, phone number, and billing address. We also collect usage data about how the website is accessed, including IP address, browser type, the pages you visit, and the time of the visit.

Proxy and parser requests​

When you call the Proxy API, Parser API, or a ScrapeOps SDK, we process the request so we can fetch or extract the page and return the result to you.

We log the account email, the target URL, and the request content you send. Request content includes the HTTP method, request body or form fields, custom headers, and JavaScript rendering options. We also log the response size and content type.

We return the page or extraction result to you. We do not keep the full response. If we cannot read a response, the error log may include a short excerpt of it.

Failed requests are also stored for a short time so we can replay them while debugging. That copy includes the URL, request body, and headers. It does not include the response.

Very large files returned by a proxy provider may be stored with our hosting provider so we can deliver them to you.

If you use LLM extraction, we send the page URL and page content to our parser, which sends them to OpenRouter so a Gemini model can extract structured data. We store a usage record for that call (model, token counts, and cost). That usage record does not include the page HTML or the extraction result.

MCP and OAuth​

The ScrapeOps MCP server lets an AI client call the Proxy API for your account.

The MCP server does not store tool arguments or page results. A tool call is sent to the Proxy API, and the request is then handled as described above.

If you connect with OAuth, we store the client registration (client name and redirect URLs), the email address you use to sign in, and an encrypted copy of the account API key so the server can call the Proxy API for you. We do not store your password in the MCP server. You can revoke a connection at any time.

You can also connect the local MCP server with an API key in your own environment. In that mode the key stays in your configuration, and requests still follow the Proxy API path above.

Billing​

If you become a paying customer, we and our payment partners receive your name, billing address, email address, and VAT number if you provide one. Stripe processes the card payment. We cannot see your full card number.

Tracking & Cookies Data​

We use cookies and similar technologies to operate the website, remember preferences, and protect the Service.

You can instruct your browser to refuse cookies. If you do, some parts of the Service may not work.

Session Cookies​

We use session cookies to operate the Service.

Preference Cookies​

We use preference cookies to remember your settings.

Security Cookies​

We use security cookies to protect the Service.

Use of Data​

We use the data we collect to:

  • Provide, maintain, and secure the Service
  • Fetch pages through proxy providers and return results to you
  • Run LLM extraction when you ask for it
  • Authenticate MCP and OAuth connections
  • Measure usage and bill your account
  • Notify you about changes to the Service
  • Provide support
  • Detect, prevent, and fix technical and abuse issues

How Long We Keep Data​

  • Request logs are deleted after 14 days.
  • Failed-request copies used for debugging are kept for 30 minutes.
  • MCP access tokens expire after 1 hour. Refresh tokens expire after 30 days. Sign-in sessions for OAuth expire after 10 minutes, and authorization codes expire after 5 minutes.
  • Large files stored for delivery are marked to expire after 30 days.
  • Billing records for completed transactions are kept for as long as tax law requires.

You can ask us to delete your account by emailing info@scrapeops.io. We still have to keep completed transaction records for tax purposes.

Transfer Of Data​

ScrapeOps Ltd is established in Ireland. Our website and API servers run on DigitalOcean in Amsterdam. Request logs are stored in Datadog in the EU.

When you use LLM extraction, the page URL and page content are sent to OpenRouter. OpenRouter processes that request on its own infrastructure, which may be outside the EU.

Your information may also be processed in the country where a proxy provider fetches the target page.

We take steps to protect data when it is transferred, and we only share it as described in this policy.

Disclosure Of Data​

Service providers​

We share data with companies that process it on our behalf:

  • Proxy providers. The provider selected for a request receives the target URL. If you send a request body or custom headers, the provider receives those too, so it can fetch the page. We do not publish a list of every provider here. The provider changes by target site and request settings.
  • OpenRouter. For LLM extraction, OpenRouter receives the page URL and page content and runs Gemini models to return the extraction.
  • DigitalOcean. Hosts our website and API servers in Amsterdam, and stores large files we need to deliver.
  • Datadog. Stores request logs in the EU for 14 days so we can operate and improve the Service.
  • Stripe and Chargebee. Process payments and invoices.
  • SendGrid (Twilio). Delivers account and service email.
  • Google Analytics and Typeform. Google Analytics measures anonymized website use. Typeform collects answers when we ask you about the product.

These providers may use the data only to perform those tasks.

We also share transaction records with our accountants and with tax authorities when we file returns.

We may disclose personal data if we believe in good faith that it is necessary to:

  • Comply with a legal obligation
  • Protect and defend the rights or property of ScrapeOps Ltd
  • Prevent or investigate wrongdoing in connection with the Service
  • Protect the safety of users or the public
  • Protect against legal liability

Security Of Data​

We use commercially reasonable safeguards to protect your data. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.

OAuth account API keys are encrypted at rest. MCP passwords are not stored on the MCP server.

The Service may link to sites we do not operate. Their privacy practices are their own. Read the privacy policy of every site you visit.

Children's Privacy​

The Service is not directed at anyone under 18. We do not knowingly collect personal data from anyone under 18. If you believe we have, contact us and we will delete it.

Changes To This Privacy Policy​

We may update this policy from time to time. We will post the new policy on this page and update the effective date. Where appropriate, we will also notify you by email or a notice on the Service before the change takes effect.

Contact Us​

Questions about this policy: info@scrapeops.io

Help connecting ScrapeOps to ChatGPT, troubleshooting requests, or account questions: support@scrapeops.io