Skip to content

Updated 28 October 2026

Privacy Policy

This policy covers two different kinds of data. We control your account data. You control the publicly accessible pages you ask us to collect, and we process those pages on your instructions.

Who is responsible

For your account, billing and security logs, ScrapingHawk is the controller. For rows collected from public pages at your request, you are the controller and we are the processor. We follow the instructions in the task: the template you chose and the inputs you supplied.

The operator's registered address will be published on this page before paid orders open. Until then, contact support@scrapinghawk.example.com. If we offer the service to people in the EEA or the UK without being established there, we will name an Article 27 representative on this page first.

Account data we collect

  • Name, email address, and a hash of your password if you set one.
  • The account identifier returned by Google or GitHub, if you use those logins. We ask for the verified email address and the name those services provide.
  • Session records, and API token names and identifiers. The full token secret is shown once and is not stored in a form we can read back.
  • Task inputs, run logs, result files, the credit balance and the credit ledger.
  • IP address and user agent of sign-in and API requests, used to limit abuse and protect the session.

Pages you ask us to collect

The service fetches publicly accessible pages and extracts the fields defined by the template. A public page can contain personal data about someone who is not our customer, such as a name, a public profile or a business listing. We collect it only to produce your result file. We do not use it for our own marketing, and we do not sell it.

Why we use account data

  • To provide the service and account for charges. The legal basis is the contract.
  • To send the messages you trigger, such as email verification and password reset. The legal basis is the contract. We do not send marketing mail.
  • To limit abuse, keep the service reliable and defend claims. The legal basis is our legitimate interest. You can object, as described below.
  • To keep a record the law requires. The legal basis is a legal obligation.

Cookies

The session cookie od_session is httpOnly and keeps you signed in. It is required for the console. NEXT_LOCALE remembers the language you picked. Signing in with Google or GitHub uses a short-lived cookie so we can match the reply to the login you started. We do not use advertising cookies or third-party analytics. To count visits and see how the site is used, the browser stores a visitor id in local storage. Page views and product actions are stored with that id, the IP address, the browser, and the device type and region derived from them. We delete those records after 90 days.

How long we keep it

We keep account data while the account is open. After you close it, or after we close it, we delete or anonymise that data, unless a legal duty, an unpaid amount or a dispute requires a longer record. Result files and run logs are kept for 30 days after the run finishes, then deleted.

Who receives it

Infrastructure that hosts the application, the database and the files. An email provider, when we send verification and reset messages. A payment provider, when you buy credit. Google or GitHub, if you choose those logins, under their own terms. A court, regulator or other authority when the law requires disclosure. We do not sell personal data.

International transfers

Servers may be outside your country. When we transfer personal data from the EEA, the UK or Switzerland to a country without an adequacy decision, we use a lawful transfer tool such as the standard contractual clauses.

Your rights

Where the GDPR or the UK GDPR applies, you can ask us to access, correct, delete or restrict your account data, and you can ask for a copy of the account data you gave us. You can object to processing based on legitimate interests. You can complain to your supervisory authority. Where we rely on consent, you can withdraw it. To use a right, email support@scrapinghawk.example.com. We may need to confirm the request comes from the account holder.

For personal data inside a result file, the customer who ran the task is the controller. If they pass a person's request to us, we will help them respond.

Children and changes

The service is not directed at anyone under 16, and we do not knowingly create accounts for them. We post changes to this policy on this page and update the date above. A change that materially affects your account is also sent to the email on the account.