Skip to content

Data Processing Agreement for a Scraping API

A data processing agreement (DPA) sets out how a service provider handles personal data on a customer's behalf.

OUTPUT FORMATSHTMLJSONMarkdown

For a web-scraping API, the agreement has to cover an unusual shape of processing: the customer decides which pages to request, and those pages may contain personal data that the provider never selected. This page explains the roles, the customer and provider duties, the transfer and sub-processor mechanics, and the practical checks worth making before relying on a DPA.

Who is the controller and who is the processor

The customer is the data controller for the processing described in the agreement, and the provider is the data processor. That split matters because the processor acts on the controller's documented instructions, not on its own goals. Where the provider handles its own commercial contact data — invoicing, account management, support and compliance checks — it acts as an independent controller for that narrower set of data.

The agreement applies to all processing the provider carries out on the customer's behalf in connection with the service. The scope, nature, purpose, duration, data categories and data-subject categories are described in a processing-activities exhibit, so the customer can see exactly what is covered rather than inferring it from marketing pages.

A useful way to test the split: if a decision changes which pages are requested or what is done with the returned content, it belongs to the customer. If a decision concerns how the provider's infrastructure runs the request, it belongs to the provider.

What the customer must be able to show

The customer confirms it has a valid legal basis, has issued the required privacy notices, can evidence consent where consent is the basis, and has completed any required data protection impact assessment before processing starts. It also undertakes not to instruct the provider to process personal data in a way that would breach applicable data protection law.

There is a specific point about scraping requests. When a customer submits requests through the API, the provider's infrastructure may process personal data contained in the scraped pages. The customer is solely responsible for making that activity lawful. The customer also indemnifies the provider against liability, fines, penalties or costs arising from the customer's failure to meet these obligations.

In practice, that means the DPA does not transfer the lawfulness question to the provider. A customer scraping pages that contain personal data still needs its own basis, notices and assessment.

The processor's operating commitments

The provider processes personal data only on documented instructions, unless EU or member-state law requires otherwise; in that case it informs the customer before processing unless the law bars disclosure on public-interest grounds. It also notifies the customer promptly if it believes an instruction infringes data protection law.

Personnel authorised to process personal data are bound by confidentiality obligations, and access is limited to those who need it to deliver the service. Security measures are described in a dedicated exhibit and are reviewed against the risk of the processing, as Article 32 GDPR requires.

On data-subject rights, the provider forwards a request relating to the customer's data to the customer's registered contact address within ten business days, does not answer the data subject directly unless instructed, and cooperates with information about the categories and location of the personal data held. On wider compliance, it assists with Articles 32 to 36 GDPR; standard assistance carries no extra charge, while requests needing extraordinary effort are quoted in advance.

Sub-processors: authorisation, notice and objection

The customer grants general written authorisation for the sub-processors listed in the sub-processor exhibit. The provider enters into a written sub-processing agreement with each one, imposing data-protection obligations equivalent to those in the DPA, and remains fully liable to the customer for each sub-processor's performance to the same extent as if it were performing the processing itself.

Changes follow a defined sequence. The provider gives at least thirty calendar days' prior notice before adding or replacing a sub-processor, by updating the published exhibit and emailing the customer's registered account address. Customers who want change notifications can opt in by email.

If the customer does not object in writing within fifteen calendar days of the update being posted, consent is deemed given. Objections must rest on reasonable data-protection grounds and are raised by email. The provider works in good faith to resolve them; if that fails, the customer's sole remedy is to terminate the affected portion of the service on written notice.

A practical control map for this process:

  • Trigger: a sub-processor is added or replaced.
  • Notice channel one: the published sub-processor exhibit is updated.
  • Notice channel two: email to the registered account address.
  • Minimum notice period: thirty calendar days.
  • Objection window: fifteen calendar days from posting.
  • Objection grounds: reasonable data-protection concerns.
  • Fallback if unresolved: terminate the affected portion of the service.

International transfers and the transfer mechanism

Personal data originating in the EEA, or the UK where applicable, is not transferred to a third country, and sub-processors are not authorised to make such a transfer, unless an appropriate Chapter V GDPR mechanism is in place.

For transfers to sub-processors in third countries, including the United States, the provider relies on the Standard Contractual Clauses, Module 2 (controller-to-processor). Accepting the DPA authorises the provider to enter into those clauses with sub-processors on the customer's behalf, solely to ensure Chapter V compliance. A copy is available on request. For UK personal data, the provider relies on the UK International Data Transfer Addendum to the EU SCCs where UK GDPR requires it.

If an adequacy decision or other transfer mechanism is invalidated or substantially amended, the provider notifies the customer promptly and the parties cooperate in good faith on an alternative lawful mechanism without undue delay.

Breach notification: the 48-hour clock and what it contains

The provider notifies the customer within forty-eight hours of becoming aware of a personal data breach affecting data processed under the DPA. The shorter window exists so the customer can meet its own 72-hour notification duty to the supervisory authority under Article 33 GDPR.

The notice includes, to the extent then known: the nature of the breach and the approximate number of affected data subjects and records; the provider's data-protection contact; the likely consequences; and the measures taken or proposed to address the breach and mitigate its effects. Where information is incomplete at first, it may follow in phases without undue delay. Notices go to the customer's registered account email address, so that address should be actively monitored.

A failure distinction worth keeping clear: a missed internal escalation is a customer-side monitoring gap, while a late or incomplete provider notice is a processor-side obligation issue. The DPA allocates the notification duty to the provider but leaves the customer responsible for its own regulatory filing.

Audit rights, return and deletion

The provider makes available the information reasonably needed to show DPA compliance and permits audits by the customer or an independent auditor it appoints. Audits are limited to once per calendar year unless a breach or supervisory-authority investigation gives reasonable cause for another. The customer gives at least sixty calendar days' prior written notice except in urgent cases; third-party auditors must be bound by confidentiality and must not be a direct competitor; and audits run during normal business hours with minimal disruption.

The provider can also discharge the audit obligation by handing over assurance evidence rather than hosting an inspection. Acceptable evidence is a SOC 2 Type II report, an ISO 27001 certificate, or an equivalent third-party assurance report, provided two conditions hold: the document is up to date, and its scope genuinely answers the customer's compliance requirements. Neither condition is optional. A lapsed certificate, or one covering controls unrelated to the customer's questions, does not satisfy the clause, so the customer may reasonably ask which controls and which period the report covers before accepting it in place of an audit.

On termination or expiry, or on written request, the provider returns a complete copy of the personal data in a commonly used, machine-readable format and/or securely deletes or destroys it and existing copies held by it and its sub-processors. That is completed within thirty calendar days, after which a written certification of deletion is available on request. Data may be retained beyond that period only where EU or member-state law requires it.

When the provider acts as controller for contact data

For the customer's operational and commercial contacts, the provider acts as an independent controller for invoicing, account management, support and compliance verification. The data processed is surname, first name, professional email, professional telephone number and position held.

The legal bases are performance of the contract for account management and invoicing, and the provider's legitimate interests for maintaining a lawful commercial relationship and verifying counterparty compliance. Retention runs for the duration of the commercial relationship plus the applicable statutory limitation period, five years under French law.

Contacts can exercise access, rectification, erasure, restriction, objection and portability rights by email or by post, and can complain to the CNIL. The customer is responsible for informing its own contacts about this processing. More detail on the provider's controller-side processing sits in its privacy policy.

Liability, updates and survival

Each party's liability under the DPA is subject to the limitations and exclusions in the Terms of Service. The provider is not liable for damage resulting from the customer's instructions, the customer's failure to comply with data protection law, or unlawful use of the service by the customer or its users.

The DPA takes effect when the customer first accepts the Terms of Service and lasts for the duration of those terms. The provider may update it to reflect changes in law, supervisory-authority guidance or the service, giving at least thirty days' prior notice of material changes by posting the updated version with a revised effective date and emailing the customer's registered address. Continued use after the effective date constitutes acceptance. On termination, the DPA ends automatically, subject to the return-and-deletion obligations. The deletion, contact-data, liability, governing-law and general-provisions sections survive termination, along with the survival clause itself.

Governing law and jurisdiction follow the Terms of Service, without prejudice to mandatory provisions of applicable data protection law. The DPA, the Terms of Service and any applicable SCCs form the entire agreement on personal-data processing and supersede earlier arrangements on that subject. If a provision is invalid or unenforceable, the rest continues in force, and a failure to enforce a provision is not a waiver.

The three exhibits at a glance

The processing-activities exhibit records the subject-matter, duration, nature, purpose, data types, data-subject categories, processing locations and special-category position. It notes that processing is primarily in the EU and that cross-border transfers are governed by the EU SCCs. It also records that the provider does not intentionally process special categories of personal data on the customer's behalf.

The sub-processor exhibit lists each approved sub-processor with its country, service, personal data processed and transfer mechanism. EU-located providers are marked as requiring no transfer mechanism; US-located providers are marked with EU SCCs 2021, Module 2 (controller-to-processor).

The security exhibit sets out the technical and organisational measures by control domain, from accountability and access control through encryption, logging, network security and vendor management. The list is expressly not exhaustive, and the provider reserves the right to add measures as threats and practices evolve.

The full exhibit tables are reproduced in the accompanying protected table modules and should be read in their original form rather than summarised.

A pre-signature checklist

Before relying on a scraping-API DPA, confirm the following against the actual document:

  • Controller and processor roles are stated, and any controller-side processing by the provider is carved out.
  • The processing-activities exhibit names the data types, data subjects and locations, including the special-category position.
  • The customer's lawfulness, notice, consent and impact-assessment duties are explicit.
  • Sub-processor authorisation, notice period, objection window and fallback remedy are all present.
  • The transfer mechanism is named for each third-country sub-processor, with a route to obtain a copy.
  • The breach-notice window and required contents are stated, and the registered contact address is monitored.
  • Audit frequency, notice period, auditor restrictions and assurance-report alternatives are clear.
  • Return, deletion, the completion window and deletion certification are specified.
  • Liability, update notice and survival clauses are consistent with the Terms of Service.

A worked example: a customer scrapes a public directory page that includes staff email addresses. The customer chose the page and the fields, so it is the controller and must have a basis and notices for that collection. The provider runs the request and may hold request metadata and returned content in logs, so it is the processor for that flow. If a sub-processor is later replaced, the customer has thirty days' notice and fifteen days to object on data-protection grounds; if the objection cannot be resolved, the affected portion of the service can be terminated.

Processing activities exhibit
ElementDetails
Subject-matterProvision of web data-extraction and scraping API services, and associated support services.
DurationFor the term of the provision of the Service, provided by the provider under the General Terms and Conditions of Service, where the provider acts as the Data Processor.
NatureCollection, storage, retrieval, transmission, structuring, use, and deletion of Personal Data in connection with the execution of API requests submitted by the Customer.
PurposeProviding the Services as instructed by the Customer; enabling the Customer to collect publicly available web data at scale; log management, billing, live support, and transactional communications.
Types of Personal Data(a) API and account data: API keys, IP addresses, request metadata, usage logs; (b) Scraped-content data: any Personal Data contained in web pages scraped via the API, the scope of which is determined solely by the Customer; (c) Support data: name, email, content of support tickets and chat messages.
Categories of Data Subjects(a) The Customer's authorized users; (b) Individuals whose Personal Data may appear in web pages scraped at the Customer's instruction (determined solely by the Customer); (c) The Customer's employees and other contacts.
Processing LocationsPrimarily – EU. All cross-border transfers are governed by EU SCCs as set out in Exhibit 2.
Special CategoriesThe provider does not intentionally process Special Categories of Personal Data on behalf of the Customer.

Reproduced from the published processing-activities exhibit dated March 23, 2026; check the current version before relying on it.

Approved sub-processors exhibit
Sub-processorCountryServicePersonal Data ProcessedTransfer Mechanism
Google Cloud PlatformParis (main), multi-DC EU for backupCloud HostingName, email, log data, API request metadataEEA, no transfer mechanism required
DatapacketNetherlands, France, Czech Republic (EU)Dedicated ServersLog data, API request metadataEEA, no transfer mechanism required
Crisp IM SASFrance (EU)Live Chat & SupportName, email, chat messagesEEA, no transfer mechanism required
Customer.ioUSATransactional & Marketing EmailName, professional emailEU SCCs 2021, Module 2 (C-to-P)
Datadog, Inc.USALog Management & MonitoringIP addresses, API request logs, error metadataEU SCCs 2021, Module 2 (C-to-P)
Chargebee, Inc.USASubscription & BillingName, email, billing address, subscription dataEU SCCs 2021, Module 2 (C-to-P)
Stripe, Inc.USAPayment ProcessingName, email, payment card data (PCI-DSS)EU SCCs 2021, Module 2 (C-to-P)

Reproduced from the published sub-processor exhibit last updated March 23, 2026; the live list may change with thirty days' notice.

Technical and organisational security measures exhibit
#Control DomainMeasure
3.1Accountability and GovernanceDesignated accountable personnel are appointed to oversee data security and compliance with legal requirements.
3.2Audit and Compliance ChecksRegular assessments of the effectiveness of technical and organizational measures are conducted to verify and continuously improve data security.
3.3Business Continuity PlanAvailability and access to Data are restored in a timely manner in the event of a physical or technical incident. Redundancy and capacity planning are maintained for all critical services.
3.4Confidentiality AgreementsNon-disclosure and confidentiality agreements are in place with all service providers who maintain or service equipment used to store Data.
3.5Control of Access RightsAccess to Data is controlled through a technical authorization system that restricts permissions to individuals whose work functions require access. Password standards (minimum length, complexity or passphrases, lockouts) and session timeouts are enforced. Usernames and passwords are confidential and non-transferable; formal procedures govern the allocation and revocation of access rights.
3.6Data Backup and RecoveryBackup and recovery processes are in place to ensure Data can be recovered and retrieved from backups reliably and within agreed timeframes.
3.7Data DestructionSecure data-destruction processes are in place to ensure Data is irreversibly destroyed when the media containing it is no longer required.
3.8Data EncryptionData is pseudonymized and encrypted both at rest and in transit using strong cryptographic protocols to ensure confidentiality and integrity.
3.9Data Protection PoliciesPolicies on data handling, processing, and retention are established and enforced to guide employees in data-protection best practices.
3.10Employee Training and AwarenessRegular security-awareness training is conducted to educate employees on data security, phishing, social engineering, and best practices.
3.11Logging and MonitoringLogins to databases containing Data can be retrospectively reviewed. The provider monitors databases and provides access logs and reports upon request.
3.12Network SecurityFirewalls, intrusion detection/prevention systems (IDS/IPS), and VPNs are used to secure network boundaries and protect against unauthorized access.
3.13Physical Access ProtectionUnattended premises containing computer equipment and personal information are locked to protect Data from unauthorized use, exposure, or theft.
3.14Risk Management ProgrammeRegular risk assessments are performed, risk registers are maintained and updated, and risk-mitigation strategies are applied as part of a continuous risk-management programme.
3.15Secure CommunicationExternal data transmissions are protected by technical measures that enable access logging and ensure encryption of data in transmission channels outside systems controlled by the provider.
3.16Security of ProcessingThe continued confidentiality, integrity, availability, and resilience of processing systems and services is maintained and regularly tested.
3.17Third-Party Vendor ManagementVendors and service providers on the provider's premises are supervised. Media containing Data is removed from the premises if on-site maintenance cannot be performed.

Reproduced from the published security-measures exhibit; the list is expressly not exhaustive and may be extended as threats and practices evolve.

Frequently asked questions

Is the scraping-API provider the controller or the processor?

For the processing described in the processing-activities exhibit, the customer is the controller and the provider is the processor. The provider acts as an independent controller only for its own commercial contact data, such as invoicing, account management, support and compliance verification.

Who is responsible when scraped pages contain personal data?

The customer. Submitting requests through the API can cause the provider's infrastructure to process personal data in the scraped content, and the customer is solely responsible for making that activity lawful. The customer also indemnifies the provider for liability, fines, penalties or costs arising from its failure to comply.

How much notice is there before a sub-processor changes, and how can a customer object?

At least thirty calendar days' prior notice, given by updating the published sub-processor exhibit and emailing the registered account address. If the customer does not object in writing within fifteen calendar days of the update being posted, consent is deemed given. Objections must rest on reasonable data-protection grounds; if they cannot be resolved in good faith, the customer's sole remedy is to terminate the affected portion of the service on written notice.

Why is the breach-notification window 48 hours?

So the customer can meet its own 72-hour notification duty to the supervisory authority under Article 33 GDPR. The notice covers the nature of the breach and approximate numbers affected, the provider's data-protection contact, likely consequences, and measures taken or proposed. Incomplete details may follow in phases without undue delay.

What happens to personal data after the service ends?

On termination, expiry or written request, the provider returns a complete copy in a commonly used, machine-readable format and/or securely deletes or destroys it and existing copies held by it and its sub-processors. That is completed within thirty calendar days, with written certification of deletion available on request. Data may be kept longer only where EU or member-state law requires it.

Can a customer audit the provider, and how often?

Yes, once per calendar year unless a personal data breach or supervisory-authority investigation gives reasonable cause for another. The customer gives at least sixty calendar days' prior written notice except in urgent cases, auditors must be bound by confidentiality and must not be a direct competitor, and audits run during normal business hours with minimal disruption. A current SOC 2 Type II report, ISO 27001 certificate or comparable third-party assurance report may stand in for the audit where it adequately addresses the customer's compliance requirements.