This policy explains how we handle personal data when you visit doublecrawl.com, contact us or use DoubleCrawl. It follows the EU General Data Protection Regulation, Regulation (EU) 2016/679 (the "GDPR").
1. Data controller
DoubleCrawl is a product of DoubleData. DoubleData is a brand of BillTech Group sp. z o.o. In this policy, "we", "us" and "our" mean that company.
BillTech Group sp. z o.o. is the controller of the personal data described in this policy, except where section 2 says otherwise.
- Address: ul. Złota 75A/7, 00-819 Warszawa, Poland
- Register: National Court Register, kept by the District Court for the Capital City of Warsaw in Warsaw, 12th Commercial Division
- KRS: 0000681407
- NIP: 7010698224
- REGON: 367482813
- Share capital: PLN 5,022
- Privacy contact: [email protected], +48 732 080 600
2. Who this policy covers
This policy covers:
- visitors to doublecrawl.com
- people who contact us, for example about sales or a launch
- account holders, including people who sign in through an MCP client
- workspace members and people invited to a workspace
- people who act for a customer, such as billing contacts
- people whose data appears in URLs, headers or other request records we hold
- people who report abuse or ask us to stop requests to a site
Personal data in requests and fetched pages
DoubleCrawl fetches the pages that customers ask for. Requests and fetched pages can hold personal data, including data about people who have no relationship with us. Examples are an ID in a URL, a name in a review and contact details on a company website.
The customer decides what to fetch and why. When the customer decides why and how that data is used, or acts for someone who does, we process it on instructions as a processor or subprocessor. The Data Processing Agreement covers that processing, not this policy. The customer is responsible for telling you how it uses the data.
We also hold request records, such as URLs and headers, for our own purposes. We are the controller when we use them for billing, showing usage, security, abuse prevention, aggregated usage totals, legal duties and legal claims. If your data appears in those records, we got it from the customer or agent that sent the request, and sections 4 to 7 and section 10 of this policy apply to you.
If your data appears in a fetched page, please contact the customer that requested it. If you don't know who that is, write to [email protected]. We can't always tell which customer fetched a page. Where we can, we will pass your request on or help the customer answer it.
This policy does not list page content as something we use for our own purposes. If we decide to use it that way, we will change this policy and the Data Processing Agreement first and tell you the purpose and the legal basis.
3. What we collect
What we hold depends on how you use DoubleCrawl. We may collect the data below.
Website visits
Our hosting systems may record standard server log data, such as IP address, time, page requested and browser details.
Links from this website to the sign-up page can carry campaign labels, such as utm_source. If you sign up, we may keep those labels with your account.
Enquiries and launch notices
If you email us, we receive your email address, your name and what you write. This includes messages that ask us to tell you when a product goes live.
If you join a waitlist on this website, we receive your email address, the products and plan you picked, and the page and button you signed up from.
Abuse reports and stop requests
If you report abuse or ask us to stop requests to a site, we receive your name, your email address, how you are connected to the site and what you tell us.
Account and profile
- email address and password, or sign-in details from a third-party sign-in provider
- email verification details
- name, photo, time zone and display settings
Security
- two-step verification settings, recovery codes and passkeys
- sessions and trusted devices, including device, browser and last active time
- IP address and approximate location, such as city and country, which we work out from the IP address
- sign-ins, failed sign-ins and other security events, such as creating a key
Agents and API keys
- agent name, device name, approximate location and last used time
- agent budgets and permissions
- messages an agent sends to you through the service, such as the reason for a top-up request
- key name, who created it, dates, prefix and last characters
- key limits, expiry, allowed sites and allowed IP addresses
Requests and usage
- time, target URL, result, credits used, duration, key and country
- request IDs and response headers
- usage totals by domain, key, status, level and country
URLs and headers can contain personal data. The content of requests and responses is covered in section 2 and section 5.
Workspaces
We hold each member's email address, role, sign-in method and last active time. Workspace settings can also affect members, for example a rule that requires two-step verification.
Billing and payment
- company name, address, country, VAT ID, invoice email and purchase order number
- plan, invoices, payments and payment failures
- card brand, last four digits and expiry date
- a cancellation reason, if you give one
A payment provider processes full card numbers. We do not intend to store them.
Support and service messages
We keep what you send us and what we reply, including any URLs, request IDs and page data you share. We use page data you share only to answer that case. We may also keep records of alerts and notices we send you.
Connected tools
If you connect a tool for alerts, such as a chat or webhook service, we hold the details we need to reach it, such as a webhook URL, and the alerts we send to it.
Where we get this data
Most of it comes from you, your agent or your use of the service. We may also get data from:
- a workspace member who invites you and gives us your email address
- your company, if it manages your access
- a sign-in provider you choose
- our payment provider
- public VAT registers, such as the EU VIES system
- a customer or its agent, if your data appears in a request
- a person who reports abuse or asks us to stop requests to a site
Do you have to give us data?
You don't have to give us personal data to read this website. To create an account, we need an email address or a sign-in provider. To buy a paid plan, we need billing details, and tax law requires some of them. Without this data we can't open the account or issue the invoice. We also need the details of each request to perform it, and we record some data automatically when you use the service. Other details, such as a profile photo, are optional.
We do not ask for special categories of personal data, such as health data. Please do not send them to us.
4. Why we process it and our legal bases
Each purpose below has its legal basis under Article 6(1) of the GDPR. Where a purpose lists both contract and legitimate interest, contract applies when you are the customer. Legitimate interest applies when you act for a company that is the customer, or when your data appears in a request that someone else sent.
Run and secure the website
We use server logs to deliver pages, keep the site secure and find faults. Legal basis: our legitimate interest in running a secure website, Article 6(1)(f).
Provide the account and the service
We create and run your account, connect your agents, authenticate keys and perform the fetches you ask for. Legal basis: contract, Article 6(1)(b). If your company is our customer, the legal basis is our legitimate interest in providing the service to your company, Article 6(1)(f).
Run workspaces
We handle invitations, roles and access for each workspace. Legal basis: contract, Article 6(1)(b), or our legitimate interest and the customer's in managing access to a shared workspace, Article 6(1)(f).
Charge, invoice and keep tax records
We charge for plans and credits, send invoices, check VAT IDs and keep accounting records. Legal basis: contract, Article 6(1)(b), and legal obligation, Article 6(1)(c). If your company is our customer, our legitimate interest in charging that customer, Article 6(1)(f), replaces contract.
Protect accounts and the service
We use security records and request logs to protect accounts, prevent fraud and abuse, and enforce our Terms and Acceptable Use Policy. Legal basis: our legitimate interest in keeping the service and its users safe, Article 6(1)(f).
Handle abuse reports and stop requests
We review each report, reply to you, stop or limit requests where needed and may tell the customer concerned. Legal basis: our legitimate interest in keeping the service lawful and responding to site owners, Article 6(1)(f).
Measure use and answer billing questions
We use request logs and usage records to count credits, show you your usage and answer questions about a bill. Legal basis: contract, Article 6(1)(b), or our legitimate interest in accurate billing, Article 6(1)(f).
Provide support
We answer your questions and solve problems. Legal basis: contract, Article 6(1)(b), or our legitimate interest in supporting our customers, Article 6(1)(f).
Send service messages
We send sign-in codes, balance and spend alerts, invoices, security notices and changes to our terms. Legal basis: contract, Article 6(1)(b), or our legitimate interest in keeping users informed, Article 6(1)(f).
Improve the service
We use usage totals and performance measures to fix faults and improve reliability. This data is aggregated and leaves out target URLs and page content. We may also use campaign labels from sign-up links to see which pages bring new users. Legal basis: our legitimate interest in improving the product and our website, Article 6(1)(f).
Answer enquiries
We reply to sales and other questions. Legal basis: steps you ask us to take before a contract, Article 6(1)(b), or our legitimate interest in answering business enquiries, Article 6(1)(f).
Tell you about a launch
If you ask us to tell you when a product goes live, we send you that notice. Legal basis: consent, Article 6(1)(a). You can withdraw it at any time.
Marketing
We may send product news by email with your consent, or where the law permits it without consent. Legal basis: consent, Article 6(1)(a), where the law requires it. Otherwise our legitimate interest in direct marketing, Article 6(1)(f). You can unsubscribe using the link in the email or by writing to us. We may still send you service messages.
Legal claims and legal duties
We establish, exercise or defend legal claims. Legal basis: our legitimate interest in protecting our rights, Article 6(1)(f). We also answer lawful requests from authorities and meet other legal duties. Legal basis: legal obligation, Article 6(1)(c).
5. Retention
We keep personal data only as long as we need it for the purposes above, including to meet legal, accounting and reporting duties. We use these periods and criteria:
- Website server logs and security logs: security logs include sign-ins, failed sign-ins and other security events. We keep these logs while a fault, security event or abuse could still come to light and need checking. We then delete or anonymise them.
- Account, profile, workspace, agent, key and connected tool data, and security settings such as passkeys and recovery codes: while your account is open. After you delete your account, we delete or anonymise this data within 90 days, apart from the records listed below. Copies in backups are removed when the backups expire.
- Saved payment details, such as card brand, last four digits and expiry date: until you remove them, or until you delete your account and have paid any amount due. Records of past payments stay with the accounting records below.
- Request logs, usage records and agent messages: for the purposes in section 4, and at the latest until the limitation period for claims about that request ends. We use a shorter period if the service lets you set one. Totals used for invoices are kept with billing records.
- Request and response content: we may keep this content after a page is delivered. The Data Processing Agreement and any settings in your account govern how long.
- Invoices and accounting records: 5 years from the end of the calendar year in which the tax fell due, or longer if the law requires it.
- Contract records and evidence for claims: until the limitation period ends. Under Polish law this is usually 3 years for business claims and up to 6 years for other claims, and it normally ends on the last day of a calendar year.
- Enquiries, other than launch requests: until we have dealt with your enquiry and any follow-up has ended. If you become a customer, the rules for your account apply.
- Launch notices: your address stays on the send list until we send the notice or you withdraw consent. We then keep a record of your consent, and of any withdrawal, until the limitation period for claims about it ends.
- Abuse reports and stop requests: until the report is closed and the limitation period for claims about it ends. We keep a stop request for as long as we apply it.
- Marketing: until you unsubscribe or object. We then keep a record of that choice so that we can respect it.
- Support cases: until the case closes and any follow-up has ended. If a case could lead to a claim, we keep the records we need until the limitation period ends.
We may keep a specific record longer if the law requires it, or until a dispute, abuse case or investigation ends. We may keep anonymised data that no longer identifies anyone.
6. Recipients and subprocessors
We do not sell personal data. We share it only as described here.
Suppliers
We use suppliers in these categories:
- hosting, database, storage and monitoring
- network suppliers that carry fetch requests to target sites
- email delivery and communication tools
- sign-in services
- payment and tax services
- support and customer relationship tools
We require suppliers that act as our processors to work under a written contract and only on our instructions. Some suppliers, such as payment providers, may act as independent controllers. The Data Processing Agreement covers subprocessors for data we process for customers.
Others
- Companies in our group, where they help us with sales, support or operations.
- The customer concerned, if we pass on an abuse report or stop request so that they can respond. We leave out your name and contact details, unless you agree or the law requires us to share them.
- Professional advisers and auditors.
- Courts and public authorities, where the law requires it. Where the law only allows us to report a breach of our Acceptable Use Policy, we share only data we hold for our own purposes.
- A new owner, if we sell or transfer the business.
Recipients you choose
- Target sites. A fetch request goes to the site you name, with the headers and body you send.
- Other members of your workspace. Depending on their role, they may see members, usage, logs, keys and invoices.
- Tools you connect, such as chat or webhook services for alerts. Alerts can include domain names, key names and agent messages. The operator of each tool handles that data under its own terms.
- A sign-in provider you choose.
You can ask us which recipients received your data. We will tell you.
7. International transfers
We are based in Poland. Our suppliers and group companies may process personal data in countries outside the European Economic Area, including the United States. When that happens, we rely on one of these safeguards:
- a European Commission adequacy decision, including Implementing Decision (EU) 2023/1795 for US recipients certified under the EU-U.S. Data Privacy Framework
- Standard Contractual Clauses adopted by the European Commission, with supplementary measures where needed
- another mechanism allowed by Chapter V of the GDPR
You can ask for a copy of these safeguards at [email protected].
Fetch requests
A fetch request goes to the site you name, wherever that site is. You can choose a country. If you don't choose a country, we choose the location. This means a request, and any personal data in it, can leave the European Economic Area and pass through suppliers that carry the traffic.
The Data Processing Agreement covers transfers of data we process for customers. We do not agree safeguards with target sites. A request goes to a target site at the direction of the person who sends it. Please don't put personal data in a request unless you need to.
8. Cookies
We build the public pages of doublecrawl.com without analytics tags, advertising tags or third-party trackers.
The dashboard at app.doublecrawl.com uses cookies or similar storage that are strictly necessary to keep you signed in and protect your account. Our hosting or security suppliers may also set cookies that are strictly necessary to deliver or protect the site. Strictly necessary cookies of this kind don't need your consent.
If we add analytics, advertising or other optional cookies, they will stay off until you allow them. We will update this policy first and give you a way to change your choice.
9. Automated decisions
We do not intend to make decisions based solely on automated processing that have legal or similarly significant effects on you.
The service does use automatic rules. For example, it rejects requests above your limit or when you are out of credits. It also picks the level that a page needs and bills the level it took. These rules run the service and protect it.
If an automatic check leads us to restrict your account and you disagree, write to [email protected] and a person will review it.
10. Your rights
Under the GDPR you have the right to:
- access your personal data and get a copy
- correct data that is wrong or incomplete
- have your data erased in the cases the GDPR sets out
- restrict how we process your data
- receive data you gave us in a portable format, where we process it by automated means based on consent or contract
- object to processing, as explained below
- withdraw consent at any time
- complain to a supervisory authority
Your right to object
You can object at any time to processing based on our legitimate interests, for reasons that relate to your situation. We will then stop, unless we have compelling legitimate grounds or need the data for legal claims. You can object to direct marketing at any time, for any reason, and we will stop.
Withdrawing consent
Withdrawing consent does not affect processing we carried out before you withdrew it.
How to use your rights
Write to [email protected], or use the dashboard where it offers export or deletion. It is free. We may ask you to confirm your identity. We will reply within one month. If a request is complex, we may need up to two more months, and we will tell you if so.
Some rights have limits. For example, we can't erase invoices that tax law requires us to keep.
Complaints
You can complain to the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych), ul. Stawki 2, 00-193 Warszawa, Poland. You can also complain to the supervisory authority in the EU country where you live or work, or where you think the infringement took place.
People in the United States
If a US state privacy law applies to you, you may have the right to know, delete and correct your data, and to opt out of a sale of it. You can send a request by email or through an authorised agent. We will not discriminate against you for using your rights.
11. Children
DoubleCrawl is not intended for children. You must be at least 18 to sign up, as our Terms say. If you think a child has given us personal data, write to us and we will delete it.
12. Security
We use technical and organisational measures designed to protect personal data. No method of transmission or storage is 100% secure, so we can't guarantee absolute security.
13. Changes to this policy
We may change this policy. We will publish the new version on this page with a new date. If a change affects you in a significant way, we will tell account holders by email before it takes effect.
14. Contact
For anything about this policy or your personal data, write to [email protected], call +48 732 080 600, or send a letter to BillTech Group sp. z o.o., ul. Złota 75A/7, 00-819 Warszawa, Poland.