This Data Processing Agreement ("DPA") forms part of the agreement between you and us for DoubleCrawl. It is the contract required by Article 28(3) of Regulation (EU) 2016/679 (the "GDPR"). It covers the personal data we process for you when you use DoubleCrawl.
1. Scope and roles
1.1 "We", "us" and "our" mean BillTech Group sp. z o.o., ul. Złota 75A/7, 00-819 Warszawa, Poland. The District Court for the Capital City of Warsaw in Warsaw, 12th Commercial Division of the National Court Register, keeps our entry under KRS 0000681407. NIP 7010698224. REGON 367482813. Share capital PLN 5,022. DoubleData is our brand, and DoubleCrawl is a product of DoubleData.
1.2 "You" means the person or organisation that accepted the Terms and holds the DoubleCrawl account.
1.3 "Service" means DoubleCrawl, including its API, its MCP server and its dashboard. "Target site" means a site that you ask the Service to fetch.
1.4 "Customer Personal Data" means personal data that we process for you when we provide the Service. It can be found in:
- request data, which is what you or your agent send us for a fetch;
- page content, which is what a target site returns;
- request records, to the extent that we hold them for you and they contain personal data, as section 1.8 explains.
1.5 "Controller", "processor", "personal data", "personal data breach", "processing" and "data subject" have the meanings given in the GDPR.
1.6 This DPA applies when the GDPR applies to Customer Personal Data. You are the controller and we are your processor.
1.7 If you act for another controller, you are its processor and we are your subprocessor. You confirm that you have its authority to use the Service and to give us instructions. We take instructions only from you.
1.8 We are a separate controller for the personal data we use to run our business. This covers accounts, sign-in, security, billing, invoices, support contact details and sales enquiries. A request record can fall under both roles. We are a controller when we use it to count credits, show you your usage, answer questions about a bill, protect the Service, prevent abuse, make aggregated usage totals, meet legal duties and establish, exercise or defend legal claims. For those uses we may keep any of the fields that Annex 1 lists for request records, for the period in section 5 of our Privacy Policy. Our Privacy Policy applies to that data, and this DPA does not. We are your processor for any other use of a request record that you ask for, such as a support case you raise.
1.9 You accept this DPA when you accept the Terms. No separate signature is needed. This DPA is in electronic form, as Article 28(9) of the GDPR allows.
2. Processing details
2.1 Annex 1 sets out the subject matter, duration, nature and purpose of the processing, the types of personal data and the categories of data subjects.
2.2 You choose the pages and you decide what your requests contain. We have no duty to check whether a request or a page contains personal data.
2.3 This DPA applies to all Customer Personal Data we hold, however long we hold it. That includes data held only while a request runs and any data held after it ends.
2.4 During the term of this DPA, we keep Customer Personal Data only as long as we need it to provide the Service and follow your instructions, unless the law requires us to keep it longer. That period depends on how long a request takes to finish, what you need for a feature you use or a support case you raise, and any retention setting in the Service. If you choose a retention setting, it applies.
3. Your instructions
3.1 We process Customer Personal Data only on your documented instructions. This includes transfers to a third country or an international organisation. The exception is where European Union or Member State law requires us to process the data. In that case we tell you about the legal requirement before we process, unless that law forbids this on important grounds of public interest.
3.2 Your documented instructions are:
- this DPA and the Terms;
- each request sent to the Service, including its URL, country, method, headers and body;
- the settings you choose in the Service;
- any other written instruction that you send to [email protected] and that we confirm in writing.
3.3 A request made with your API key, or by an agent you have connected to your account, is your instruction. You decide who and what gets that access.
3.4 If an instruction needs something the Service does not do, we tell you. We can then agree a change, or you can stop using the affected part of the Service.
3.5 If we think an instruction infringes the GDPR or other European Union or Member State data protection law, we tell you immediately. We may hold that instruction until you confirm or change it. This does not make us responsible for checking your instructions or for giving you legal advice.
4. Confidentiality
4.1 We make sure that everyone we authorise to process Customer Personal Data has committed to confidentiality or is under an appropriate statutory duty of confidentiality.
4.2 We give access only to people who need it to provide the Service, to support you or to meet a legal duty. They process the data only on your instructions, unless European Union or Member State law requires otherwise.
4.3 We disclose Customer Personal Data only as this DPA or your instructions allow, or as the law requires. Sending a request to the target site you name is a disclosure on your instructions.
5. Security measures
5.1 We take all measures required by Article 32 of the GDPR. We apply technical and organisational measures that are appropriate to the risk. We take into account the state of the art, the cost of implementation, the nature, scope, context and purposes of the processing, and the risks to people.
5.2 As appropriate to the risk, these measures aim to:
- pseudonymise or encrypt personal data where that is suitable;
- keep our systems and services confidential, intact, available and resilient;
- restore availability of and access to personal data in a timely way after an incident;
- regularly test, assess and evaluate how well the measures work.
5.3 The Service's API and MCP endpoints use HTTPS. API requests are authenticated with a key sent as a bearer token. MCP clients that support OAuth sign in on first use, and other clients send a bearer key.
5.4 We may change our measures as technology and risks develop. A change must not materially reduce the protection of Customer Personal Data.
5.5 No method of transmission or storage is 100% secure, and we cannot guarantee absolute security.
5.6 You are responsible for the security of your account, your API keys and your agents, and for what you choose to send in a request.
6. Subprocessors
6.1 You give us general written authorisation under Article 28(2) of the GDPR to engage subprocessors, on the terms of this section.
6.2 The current list of subprocessors is available from [email protected].
6.3 Subprocessors may include companies in our group and suppliers of hosting, storage, email, support tools and the routes that carry requests to target sites.
6.4 We tell you at least 14 days before we add or replace a subprocessor, by email to the address on your account. If we must replace a subprocessor urgently to keep the Service secure or running, we may give shorter notice. We still tell you before the change, and you keep your right to object.
6.5 You may object on reasonable data protection grounds. To object, write to [email protected] before the notice period ends. We then work with you in good faith to find a solution. If we do not find one before the change takes effect, you may stop using the affected part of the Service or end your agreement with us. The Terms apply to any amounts paid. If you do not object in time, you accept the change.
6.6 We bind each subprocessor by contract to the same data protection obligations as this DPA. In particular, the subprocessor must give sufficient guarantees that it applies appropriate technical and organisational measures.
6.7 We remain fully liable to you for each subprocessor's performance of its obligations.
6.8 Target sites are not our subprocessors, because you choose them. The same applies to any third-party tool that you connect to your account. How a target site or a tool of your choice handles data is outside this DPA.
7. Data subject requests
7.1 You are responsible for answering people who exercise their rights under Chapter III of the GDPR. These are the rights to information, access, rectification, erasure, restriction, portability, objection and the rights on automated decisions.
7.2 Taking into account the nature of the processing, we help you with appropriate technical and organisational measures, as far as possible, so that you can answer these requests.
7.3 If a person contacts us directly about Customer Personal Data, we do not answer the request ourselves unless the law requires it. If we can tell that the request relates to you, we pass it to you without undue delay.
7.4 Pages can name people who have no relationship with us. We may not be able to find a person's data from a name alone. When you ask for help, give us the URL, the date and the X-DD-Request-Id value where you have them.
8. Help with security, assessments and regulators
8.1 Taking into account the nature of the processing and the information available to us, we help you meet your obligations under Articles 32 to 36 of the GDPR. We do this by giving you the information and support you reasonably need for:
- the security of processing (Article 32);
- notifying a personal data breach to the supervisory authority (Article 33);
- communicating a personal data breach to the people affected (Article 34);
- data protection impact assessments (Article 35);
- prior consultation with the supervisory authority (Article 36).
8.2 If a supervisory authority or another public authority asks us for Customer Personal Data or contacts us about it, we tell you, unless the law forbids it. We disclose only what the law requires.
8.3 We keep the records of processing required by Article 30(2) of the GDPR and cooperate with the supervisory authority as Article 31 requires.
9. Breach notification
9.1 We notify you without undue delay after we become aware of a personal data breach affecting Customer Personal Data and, where feasible, within 72 hours. We send the notice to the email address on your account.
9.2 As far as we know them, the notice describes:
- the nature of the breach, including the categories and approximate number of people and records concerned;
- the likely consequences;
- the measures we have taken or propose to take;
- a contact point for more information.
9.3 If we do not have all of this at once, we send it in stages without further undue delay.
9.4 We take reasonable steps to contain and investigate the breach and to limit its effects. You decide whether to notify a supervisory authority or the people affected, and section 8 applies.
9.5 A notice is not an admission of fault or liability.
10. International transfers
10.1 This section covers transfers of Customer Personal Data outside the European Economic Area ("EEA"). We make these transfers only on your instructions, including the authorisation in section 10.2. For transfers to subprocessors, and for delivery to you where section 10.4 applies, we follow Chapter V of the GDPR as sections 10.3 and 10.4 describe. Sections 10.5 and 10.6 cover the cases where we have no transfer tool in place.
10.2 The Service sends each request to the target site you name, with the headers and body you set. You can set the country a request comes from. If you do not, this DPA authorises us to choose the location. Target sites and request locations may be outside the EEA. The current list of request locations is available from [email protected]. If you need a specific location, set the country. By naming a target site, or by setting the country, you instruct us to send the request accordingly.
10.3 If a subprocessor outside the EEA receives Customer Personal Data, we rely on one of these safeguards:
- an adequacy decision of the European Commission, including Implementing Decision (EU) 2023/1795 for recipients certified under the EU-U.S. Data Privacy Framework;
- the Standard Contractual Clauses in Commission Implementing Decision (EU) 2021/914 (the "Clauses"), Module Three, with supplementary measures where needed;
- another mechanism allowed by Chapter V of the GDPR.
10.4 If you are outside the EEA, in a country without an adequacy decision, you act as controller, and the GDPR does not apply directly to your processing, Module Four of the Clauses applies when we deliver Customer Personal Data to you. You act as data importer and we act as data exporter. The Clauses form part of this DPA for that purpose, and Annex 2 gives the details they need.
10.5 Module Four does not cover you if you are outside the EEA and the GDPR applies directly to your processing under Article 3(2), or if you act as a processor under section 1.7. In those cases we have no transfer tool in place for delivery to you, unless an adequacy decision covers your country or we agree a tool with you in writing. Write to [email protected] before you send personal data through the Service.
10.6 We treat a request that carries personal data to a target site outside the EEA as a transfer made on your instruction. We do not agree transfer tools with target sites. You must have a ground under Chapter V of the GDPR for that transfer, or you must keep personal data out of the request.
10.7 You can get a copy of the safeguards we use by writing to [email protected]. We may remove commercial terms from the copy.
11. Audits
11.1 We make available to you all information necessary to show that we meet our obligations under Article 28 of the GDPR.
11.2 We allow for and contribute to audits, including inspections, carried out by you or by an auditor you appoint.
11.3 To start, write to [email protected]. We first try to answer with written information. If that is not enough, these conditions apply to the audit:
- you give us at least 30 days' notice and tell us the scope, unless a supervisory authority requires a shorter period;
- you audit no more than once in any 12 months, unless a personal data breach, a supervisory authority or reasonable grounds to suspect a breach of this DPA require another audit;
- the audit takes place in normal business hours and does not unreasonably disrupt our work;
- you and your auditor sign a confidentiality undertaking, and your auditor is not our competitor;
- you get no access to the data of other customers.
11.4 Each party bears its own audit costs. If an audit needs substantial time from us, we may ask you to cover our reasonable costs, as agreed before the audit starts.
11.5 These conditions do not limit the powers of a supervisory authority.
12. Deletion and return of data
12.1 When the Service to you ends, we delete or return all Customer Personal Data we hold, at your choice. We also delete existing copies, unless European Union or Member State law requires us to store the data. Data we hold as a controller under section 1.8 is not part of this. Some of it, such as request records, stays after the Service ends, for the periods in section 5 of the Privacy Policy.
12.2 Tell us your choice by writing to [email protected] no later than 30 days after the Service ends. If you choose return, we provide the data in a commonly used electronic format. If you make no choice in that time, we delete the data.
12.3 Once you have made your choice, or the 30 days have passed, we finish deletion or return without undue delay. This includes data held by subprocessors. Copies in backups are removed when the backups expire, and this DPA keeps applying to them until then. We confirm in writing if you ask.
12.4 If the law requires us to keep any of the data, we tell you which law applies, unless that law forbids it. We keep only what is required, and this DPA continues to apply to it.
12.5 While the Service runs, you can ask us to delete specific Customer Personal Data by writing to the same address. We do so without undue delay, as far as we can identify the data.
12.6 This section does not apply to data we hold as a controller. The Privacy Policy covers that data.
13. Your responsibilities
13.1 You are responsible for your own compliance with data protection law as controller. This includes:
- having a legal basis for each page you fetch and each use you make of the content;
- giving people the information the GDPR requires, including under Article 14 where you get their data from a page;
- meeting the principles of purpose limitation, data minimisation and storage limitation for the data you receive;
- making sure your instructions are lawful.
13.2 You use the Service only as the Terms and the Acceptable Use Policy allow. You must not fetch pages behind a login you don't own.
13.3 Send no more personal data than the fetch needs. Where you can, keep personal data out of URLs, headers and request bodies.
13.4 We do not ask you to send special categories of personal data or data on criminal convictions and offences. A page you choose may still contain them. If it does, you are responsible for having a legal ground to process that data.
13.5 Keep the email address on your account up to date. We use it for notices under this DPA.
14. Term, liability and general terms
14.1 This DPA applies for as long as we process Customer Personal Data for you. It ends when we have finished under section 12.
14.2 Liability under this DPA follows the Terms. Nothing in this DPA or the Terms limits a person's rights under Article 82 of the GDPR, or any liability that the law does not allow the parties to limit.
14.3 If documents conflict on personal data, the Clauses come first, then this DPA, then the Terms.
14.4 We may change this DPA only for one of these reasons:
- a change in the law or an order of a public authority;
- a change to the Service or our suppliers;
- to improve security or prevent abuse;
- to correct errors or make this DPA clearer.
14.5 We email each change to the address on your account at least 14 days before it takes effect, and we publish it on this page. The period can be shorter only if the law requires the change sooner. A change must not take this DPA below what Article 28 of the GDPR requires.
14.6 If the law requires a change, or a change does not reduce the protection of Customer Personal Data, it takes effect on the date in our email. You may end your agreement with us before that date. The Terms apply to any amounts paid.
14.7 Any other change takes effect for you only when you approve it. To approve, write to [email protected]. Silence is not approval. Until you approve, the earlier version keeps applying to you.
14.8 Polish law governs this DPA. If you are a consumer, you also keep the protection of the mandatory rules of the country where you usually live. Disputes go to the court set by the Terms. The Clauses have their own rules on law and courts.
14.9 Contact for this DPA: [email protected], +48 732 080 600, or BillTech Group sp. z o.o., ul. Złota 75A/7, 00-819 Warszawa, Poland.
Annex 1: Details of processing
Subject matter
We provide the Service to you. We fetch the pages you choose and deliver them to you or your agent.
Duration
From the time you first use the Service until we finish deletion or return under section 12.
Nature of the processing
Automated and continuous, for each request. It covers receiving requests, sending them to target sites, retrying them, retrieving responses, delivering them to you, storing data as needed for these steps, creating request records and deleting data.
Purpose
- To perform each fetch and deliver the page.
- To help with a support case you raise.
- To follow your other documented instructions.
Types of personal data
You choose the content, so any type of personal data may be involved. In particular:
- Request data: URLs and any identifiers in them, country, method, headers and request bodies. It may include session identifiers, cookies, tokens or credentials for a login you own.
- Page content: the target site's status, headers and body as sent. It may include names, contact details, job titles, online identifiers, posts, reviews, opinions, listing details and anything else on the page.
- Request records: these can include the time, URL, outcome, credits, duration, key, country, request ID and response headers.
Special categories of data
We do not ask for them. A page you choose may contain them, or data on criminal convictions and offences. Section 13.4 applies.
Categories of data subjects
- People named or shown on pages you fetch. Examples are people named on company websites, authors of reviews, mentions and forum posts, and people named in real estate listings, classified listings and job listings.
- Your staff, contractors, users and customers, where their data is in a request or a page.
- Holders of a login you own, where a request uses that login.
- Any other person whose data is in a request or a page you choose.
Subprocessors
Section 6 applies. The current list is available from [email protected].
Annex 2: Details for the Clauses
Module Three, subprocessors
We complete the details of Module Three in our contracts with subprocessors.
Module Four, delivery to you
- Data exporter: BillTech Group sp. z o.o., ul. Złota 75A/7, 00-819 Warszawa, Poland, as processor. Contact person: our privacy contact, [email protected], +48 732 080 600. Its activities are providing the Service.
- Data importer: you, as controller. Your name, address and contact person are those you gave us for your account. Contact: the email address on your account. Your activities are those for which you use the Service.
- Signature and date: accepting this DPA counts as signing the Clauses on the date of acceptance.
- Description of the transfer: Annex 1 applies. Transfers are continuous, for each request.
- Sensitive data: we do not ask for it, but a page you choose may contain it. Section 13.4 applies, and the measures in section 5 cover it.
- Retention: you decide how long you keep the data we deliver to you. Sections 2.4 and 12 set how long we keep it.
- Clause 7, the docking clause, does not apply.
- The optional wording in Clause 11(a) does not apply.
- Clause 17, governing law: the law of Poland.
- Clause 18, courts: the courts of Poland.