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.
Support requests are handled in GrooveHQ, which stores your name, email address, and the conversation.
Sign-up checks
We check new sign-ups to stop fraud and abuse:
- hCaptcha checks that a person, not a bot, is signing up. It receives your IP address and browser signals.
- We block sign-ups from disposable email domains.
- We send your name, email address, sign-up IP address, referrer, and timezone to OpenRouter, which returns an automated risk score.
If the risk score is high, the account is blocked automatically and our team is alerted so a person can review it. Accounts with a raised risk score may also need to verify a phone number by SMS, which Twilio sends. If your account is blocked and you think that is a mistake, email support@scrapeops.io and a person will review the decision.
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 Stripe 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.
Marketing
If you subscribe to our newsletter, beehiiv stores your email address and subscription status.
If you arrive through an affiliate link, FirstPromoter records the referral so we can pay the affiliate. It receives the email address of the account that signs up and the amounts that account pays.
When you sign up or buy a plan, we tell OpenAI's ChatGPT Ads service so we can measure our advertising. We send a hashed (SHA-256) copy of your email address, your IP address, and your browser user agent. We do not send your email address in readable form.
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
- Check sign-ups for fraud and abuse
- Detect, prevent, and fix technical and abuse issues
- Measure how well our marketing works
How Long We Keep Data
- Request logs are deleted after 7 days.
- Failed-request copies used for debugging are kept for 7 days.
- 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.
- Database backups are kept for 7 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, API, and proxy servers run on DigitalOcean in Amsterdam. Our main database, proxy caches, and file storage are on DigitalOcean in London. The Parser API cache is on DigitalOcean in New York. Request logs are stored in Datadog's EU region in Germany.
When you use LLM extraction, the page URL and page content are sent to OpenRouter in the United States. Several of the account, billing, support, and marketing providers listed below are also in the United States.
Your information may also be processed in the country where a proxy provider fetches the target page.
The United Kingdom has an EU adequacy decision. For transfers to other countries outside the EEA, we rely on the EU-U.S. Data Privacy Framework where the provider is certified, or on the EU Standard Contractual Clauses. Our Subprocessor List shows each provider and where it processes data.
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. At sign-up, it receives your name, email address, sign-up IP address, referrer, and timezone to produce a risk score.
- DigitalOcean. Hosts our website, API servers, database, and caches in Amsterdam, London, and New York, and stores large files we need to deliver.
- Datadog. Stores request logs in the EU (Germany) for 14 days so we can operate and improve the Service.
- Stripe. Processes payments and subscriptions.
- Mailgun. Delivers account and service email.
- Twilio. Sends SMS codes when a sign-up needs phone verification.
- hCaptcha. Checks that sign-ups come from people, not bots.
- GrooveHQ. Hosts our support inbox.
- Slack. Delivers internal alerts to our team. These can include your account email and sign-up details.
- Google Analytics and Google Tag Manager. Measure pseudonymous website use.
- beehiiv. Sends our newsletter.
- FirstPromoter. Tracks referrals from our affiliate programme.
- OpenAI (ChatGPT Ads). Measures sign-ups and purchases from our ads, using a hashed email address, IP address, and browser user agent.
These providers may use the data only to perform those tasks. Our Subprocessor List gives more detail on each one.
We also share transaction records with our accountants and with tax authorities when we file returns.
Legal requirements
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.
Links To Other Sites
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