Part I · Privacy Policy
Website: datafuel.ai
Controller: Double C S.r.l.
Version: 1.0
Effective date: 3 October 2026
This Privacy Policy explains how Double C S.r.l. processes personal data in connection with datafuel.ai, the Datafuel dashboard, and the Datafuel services.
It is prepared under Articles 13 and 14 of Regulation (EU) 2016/679 (GDPR) and the Italian Privacy Code, Legislative Decree No. 196/2003, as amended.
Part I · 1. Controller and contacts
The controller is Double C S.r.l., an Italian limited liability company, with registered office at Via del Fosso della Magliana 34G, 00148 Rome, Italy.
VAT number and tax code: IT17516471004
PEC: double.c@pec.it
Double C S.r.l. has not appointed a Data Protection Officer. For privacy questions and requests, contact privacy@datafuel.ai.
For other matters, you may use the following addresses:
- Legal matters: legal@datafuel.ai
- Security matters: security@datafuel.ai
- Abuse reports: abuses@datafuel.ai
- Customer support: support@datafuel.ai
- Commercial enquiries: sales@datafuel.ai
Part I · 2. Categories of data subjects
This Policy applies to visitors of the website.
It applies to people who create or use a Datafuel account.
It applies to prospective customers and people who contact Datafuel before opening an account.
It applies to customers, their authorised users, sub-users, and billing contacts.
It applies to device owners who participate in the residential SDK programme. The SDK has a separate privacy notice. That notice governs the SDK collection and the relationship with the relevant partner app. This Policy describes only Datafuel’s related processing where applicable.
Datafuel services are not offered to people under 18. Datafuel does not knowingly collect or use data from children.
Part I · 3. Data collected and processing activities
The following sections describe the main processing activities. Each section identifies the purpose, the legal basis, and the applicable retention period.
3.1 Website operation and analytics
Datafuel processes technical data needed to deliver and secure the website. This may include IP address, browser and device information, timestamps, requested resources, and basic server logs.
Datafuel uses Google Analytics 4 for analytics only after the visitor gives consent through the cookie or consent mechanism. Analytics help Datafuel understand website use and improve the site.
The legal basis for consent-based analytics is the visitor’s consent. Consent may be withdrawn at any time through the available consent settings. Withdrawal does not affect processing carried out before withdrawal.
Website technical data is retained for the period needed for operation and security. Analytics data is retained according to the configured Google Analytics retention settings. The exact settings must be confirmed before publication of this Policy.
3.2 Advertising pixels
Datafuel uses advertising technologies supplied by Meta, LinkedIn, Reddit, and X.
These technologies are activated only after consent where required by applicable law. They may be used to measure campaigns, create audiences, and show or evaluate advertising.
Meta, LinkedIn, Reddit, and X act as independent controllers for their own processing. Their processing is governed by their own privacy information and settings.
The legal basis for Datafuel’s activation of these technologies is consent. Consent may be withdrawn through the consent settings. Advertising-partner retention periods are set by the relevant partner and must be checked in the applicable partner notices.
3.3 Live chat and pre-sales communications
When a person uses the live chat or contacts Datafuel, Datafuel may process name, email address, chat content, contact details, company information, intended use case, technical information, and the person’s communications.
The purpose is to answer questions, provide support, assess a prospective service relationship, and prevent abuse.
The legal basis is the performance of pre-contractual measures requested by the person, the performance of a contract where the person is already a customer, and Datafuel’s legitimate interest in managing communications and protecting its services.
Live chat and support records are retained for three months, unless a longer period is necessary to resolve a dispute, comply with a legal obligation, or establish, exercise, or defend a legal claim.
Datafuel uses LiveChat and Futurebase for live chat and related customer communications.
3.4 Account, service, and billing data
When a person creates or uses an account, Datafuel may process name, email address, company, intended use case, account credentials, authentication data, IP-whitelist data, sub-user information, service configuration, usage, balance, invoices, payment status, and communications relating to the account.
Payment providers may process payment details. Datafuel does not need to receive or store the full payment-card data processed by the relevant payment provider.
The purposes are to create and administer the account, provide the services, provision proxies and APIs, manage sub-users and budgets, process payments, prevent fraud, provide support, send service notices, and enforce the contractual terms and acceptable-use rules.
The primary legal basis is performance of the contract or pre-contractual measures. Datafuel may also rely on a legal obligation for accounting, tax, invoicing, and payment records, and on legitimate interests for security, fraud prevention, service administration, and enforcement of contractual rights.
Account data is retained for 12 months after account closure, unless a longer period is required by law. Invoices and records required by Italian tax law are retained for 10 years.
If payment fails, the account may be suspended until payment is made. If non-payment continues, the account may be closed after 30 days. Data is then handled under the retention periods in this Policy.
3.5 KYC and restricted access
Datafuel may request identity verification before enabling mail ports, government sites, or other restricted domains. Verification may be provided through Sumsub or Stripe Identity.
Depending on the verification process, the data may include identity details, identity-document information, verification results, fraud-risk signals, and information supplied by the person during verification. Datafuel does not request more information than is reasonably needed for the relevant verification purpose.
The purposes are to comply with legal and regulatory requirements where applicable, assess access to restricted services, prevent fraud and abuse, and protect Datafuel, customers, and third parties.
The legal bases are compliance with a legal obligation where one applies, and Datafuel’s legitimate interest in fraud prevention, security, abuse prevention, and controlled access to restricted services.
KYC verification data is retained for five years after account closure. Verification data held by Sumsub or Stripe Identity may be subject to the relevant provider’s retention policy.
KYC may involve automated checks carried out by the verification provider. Based on the confirmed company facts, Datafuel does not make a decision producing legal or similarly significant effects solely by automated processing. A KYC outcome may lead to manual review or a request for further information. If a solely automated decision is introduced, Datafuel will provide the information and safeguards required by Article 22 GDPR, including information about the logic, the significance and consequences of the processing, and the right to request human intervention and contest the decision.
3.6 Proxy connection logs
For consumption-based rotating proxy products, Datafuel may process the timestamp, customer IP address, bytes transferred, and target domain or URL.
The purpose is to secure the network, investigate abuse, respond to incidents, enforce the acceptable-use rules, and establish, exercise, or defend legal claims.
The legal basis is Datafuel’s legitimate interest in security, abuse handling, service integrity, and legal protection. Datafuel balances these interests against the rights and freedoms of the individuals concerned and limits the data and retention period to what is needed for those purposes.
These proxy connection logs are retained for 14 days.
Datafuel does not keep connection logs for dedicated static products, according to the confirmed company facts. Other account, billing, security, or support records may still be retained under the periods stated elsewhere in this Policy.
3.7 Scraping API request metadata and results
When a customer uses a Scraping API, Datafuel may process account identifiers, API credentials or authentication data, request timestamps, requested URLs or queries, selected options, model or proxy parameters, job status, usage, cost, error information, webhook details, and other request metadata.
Scraping API results may include the content returned to the customer, including extracted pages, structured fields, Markdown, HTML, screenshots, or model responses. The customer owns the extracted data and is responsible for ensuring that its collection and use are lawful.
The purposes are to execute requests, return results, provide analytics, calculate usage and charges, operate webhooks and storage delivery, troubleshoot failures, secure the service, and provide support.
The legal basis is performance of the contract. Datafuel may also rely on legitimate interests for security, fraud prevention, service improvement, and legal protection.
Scraping API request metadata is retained for 30 days. Scraping API results are available for download for 30 days and are then deleted, subject to backups and any longer period required for legal claims or obligations.
3.8 Support records and CRM
Datafuel may process support requests, tickets, chat content, contact details, account identifiers, technical information, and records of actions taken by support staff.
The purpose is to provide and document customer support, investigate incidents, and manage the customer relationship.
The legal basis is performance of the contract, pre-contractual measures, and Datafuel’s legitimate interest in service management, quality control, security, and legal protection.
Support chats and tickets are retained for three months, unless a longer period is needed for a dispute, legal obligation, or legal claim.
Datafuel uses an internal CRM and HubSpot for CRM and customer-relationship management. CRM and marketing records are retained until consent is withdrawn or for 24 months after inactivity, unless a longer period is required for a legal or contractual purpose.
3.9 Marketing emails
Datafuel may send marketing emails where the recipient has given consent.
Datafuel may also send marketing communications to an existing customer about similar products or services under the applicable soft opt-in rules. The recipient may object when the message is sent and in every later message.
The purposes are to send information about Datafuel products, services, updates, and offers.
The legal basis is consent or, where the legal conditions are met, Datafuel’s legitimate interest in direct marketing to existing customers. Every marketing email includes an unsubscribe method.
Marketing records are retained until consent is withdrawn or for 24 months after inactivity, subject to evidence needed to record consent, objections, or unsubscribe requests.
3.10 Training data from extracted pages
Datafuel may store extracted pages in a pseudonymised and PII-stripped form to train future Datafuel AI models.
The purpose is to develop, test, and improve Datafuel’s future AI models and related services.
The legal basis is Datafuel’s legitimate interest in research, development, and service improvement. Before using data for this purpose, Datafuel applies a balancing assessment that considers the nature of the data, the reasonable expectations of customers, the safeguards applied, the possibility of re-identification, and the impact on individuals.
Datafuel removes or strips personal identifiers where reasonably possible and limits the data used for training. Customers can use the opt-out switch in the dashboard to exclude their data from future training runs.
An opt-out does not retrain or alter a model that has already been trained. Datafuel must define and publish the applicable retention period for training datasets before publication of this Policy. Until that period is confirmed, the training data must not be treated as subject to a shorter retention period than the underlying Scraping API result or the period necessary for the stated development purpose.
Part I · 4. Retention table
- Account data after account closure — 12 months, unless a longer legal period applies
- Invoices and tax records — 10 years, as required by Italian tax law
- KYC verification data — 5 years after account closure; provider-held data may follow the provider’s policy
- Proxy connection logs for consumption-based rotating products — 14 days
- Connection logs for dedicated static products — No connection logs retained, according to the confirmed facts
- Scraping API request metadata — 30 days
- Scraping API results — Available for download for 30 days, then deleted, subject to backups and legal holds
- Support chats and tickets — 3 months
- Backups — 30-day rotation; deletion propagates within 30 days
- Residential SDK data — 180 days; see the separate SDK Privacy Notice
- Security and audit logs — 12 months
- Marketing and CRM data — Until consent withdrawal or 24 months of inactivity
- Website analytics data — According to the configured Google Analytics 4 retention settings; confirm before publication
- Advertising-platform data — According to the relevant independent controller’s retention policy
- Training datasets — To be confirmed and published before the training-data feature is launched or used
Datafuel may retain information for a longer period where necessary to comply with a legal obligation or to establish, exercise, or defend a legal claim.
Backups are maintained on a 30-day rotation. A deletion request may therefore take up to 30 days to propagate through backup systems, unless a longer retention is required by law or necessary for security.
Part I · 5. Recipients and processors
Datafuel may disclose personal data to authorised personnel, professional advisers, authorities where required by law, and service providers that process data on Datafuel’s behalf.
The confirmed sub-processors and service providers are listed below. Their role and location should be kept current in the operational vendor register.
- Stripe — Card payments and payment processing · International provider; exact processing locations and transfer mechanism to be confirmed in the vendor register
- Stripe Identity — Identity verification and KYC · International provider; exact processing locations and transfer mechanism to be confirmed
- CoinGate — Cryptocurrency payments · International provider; exact processing locations and transfer mechanism to be confirmed
- Payssion — Local payment methods · International provider; exact processing locations and transfer mechanism to be confirmed
- Sumsub — Identity verification and KYC · International provider; exact processing locations and transfer mechanism to be confirmed
- Hetzner Online GmbH — Website, dashboard, API, and backup hosting · Hetzner Cloud infrastructure in Germany; the group structure and any non-EEA access safeguards are described in Section 6
- Cloudflare — Website delivery, security, and infrastructure services · International provider; the website uses Cloudflare. Exact data-centre routing and transfer mechanism must be confirmed
- HubSpot — CRM and customer relationship management · International provider; exact processing locations and transfer mechanism to be confirmed
- Google — Google Analytics 4 · International provider; exact processing locations and transfer mechanism to be confirmed
- LiveChat — Live chat · International provider; exact processing locations and transfer mechanism to be confirmed
- Futurebase — Live chat and customer communications · International provider; exact processing locations and transfer mechanism to be confirmed
- Telehouse — Colocation for Scraping API infrastructure · Telehouse New York Teleport, 7 Teleport Dr, Staten Island, NY 10311, United States
- Meta — Advertising technologies · Independent controller; international processing under Meta’s own terms and safeguards
- LinkedIn — Advertising technologies · Independent controller; international processing under LinkedIn’s own terms and safeguards
- Reddit — Advertising technologies · Independent controller; international processing under Reddit’s own terms and safeguards
- X — Advertising technologies · Independent controller; international processing under X’s own terms and safeguards
Datafuel may also disclose data to courts, regulators, law-enforcement bodies, payment authorities, tax authorities, and other public bodies where disclosure is required or permitted by law.
Part I · 6. International transfers
Datafuel uses providers that may process personal data in the European Economic Area and in countries outside the EEA.
Hetzner and Cloudflare have US parent-company or group connections. Datafuel uses the European infrastructure identified in the company facts where applicable. Any access from, or transfer to, a non-EEA group entity is subject to an applicable transfer mechanism and documented safeguards.
The Scraping API is processed on Datafuel’s dedicated servers in Germany and in the United States at the Telehouse New York Teleport facility. The US processing location is therefore a direct international transfer or access context.
US advertising partners act as independent controllers. Their own privacy notices describe their processing and transfer arrangements.
Where required, Datafuel uses the European Commission’s Standard Contractual Clauses adopted by Decision (EU) 2021/914, together with a transfer impact assessment and supplementary technical or organisational measures where appropriate.
Where a recipient is certified under the EU-US Data Privacy Framework and the certification covers the relevant transfer, Datafuel may rely on that adequacy mechanism. The applicable certification should be checked at the time of each transfer.
Data subjects may request further information about the applicable safeguards by contacting privacy@datafuel.ai.
Part I · 7. Data subject rights
Subject to the conditions and limits in the GDPR and the Italian Privacy Code, a data subject may ask Datafuel to:
- confirm whether personal data is being processed and provide access to it;
- correct inaccurate or incomplete data;
- erase data where a legal ground for erasure applies;
- restrict processing where a legal ground for restriction applies;
- receive data provided to Datafuel in a structured, commonly used, machine-readable format where the right to portability applies;
- object to processing based on legitimate interests;
- object to direct marketing at any time;
- withdraw consent at any time where processing is based on consent;
- request human intervention and contest a decision where the GDPR provides those safeguards for automated decision-making.
To exercise a right, email privacy@datafuel.ai. Datafuel may request information needed to verify the requester’s identity. Requests are normally handled within one month. That period may be extended by two months where necessary because of complexity or the number of requests.
Datafuel will explain any refusal or limitation and the available remedies. Requests are normally free of charge, subject to the rules for manifestly unfounded or excessive requests.
A data subject may lodge a complaint with the Italian supervisory authority:
Garante per la protezione dei dati personali
Piazza Venezia 11
00187 Rome, Italy
Website: garanteprivacy.it
A data subject may also lodge a complaint with the supervisory authority in the Member State of habitual residence, place of work, or place of the alleged infringement, where the GDPR permits it.
Part I · 8. Security measures
Datafuel applies technical and organisational measures designed to protect personal data against unauthorised access, loss, alteration, disclosure, and destruction.
Measures include access controls, authentication and two-factor authentication, IP whitelisting where available, role-based access, encryption in transit where supported, monitoring, logging, backups, incident handling, supplier controls, and data-retention limits.
The dashboard and API infrastructure is hosted on Hetzner Cloud in Germany. The Scraping API also runs on Datafuel-owned dedicated servers in Germany and the United States. No security measure can eliminate every risk.
Datafuel maintains a responsible-disclosure process. Security reports may be sent to security@datafuel.ai.
Part I · 9. Residential SDK
The residential SDK uses a separate consent flow and a separate SDK Privacy Notice.
The SDK may process the device IP address, country, network type, and operating system. Consent is collected through the partner application and may be withdrawn by the device owner.
SDK data is retained for 180 days. The SDK may not be integrated into children’s applications, and device owners must be at least 18 years old.
The separate SDK Privacy Notice must explain the partner-app relationship, the consent wording, the purpose of using device resources and IP address, the withdrawal process, recipients, international transfers, and the rights of device owners.
Part I · 10. Changes to this Policy
Datafuel may update this Policy when its processing activities, services, providers, or legal obligations change.
The current version is identified by a version number and effective date at the beginning of the Policy.
For material changes, Datafuel will provide an appropriate notice through the website, dashboard, or email where required.
Current version: 1.0
Effective date: 3 October 2026
Part I · 11. Notice at Collection and additional information for United States residents
This section supplements the Privacy Policy for residents of California and of other US states with comprehensive privacy laws (including Virginia, Colorado, Connecticut, Utah, Texas and Oregon). It uses the categories defined by the California Consumer Privacy Act (CCPA) as amended by the CPRA. Where this section and the rest of the Policy differ, the more protective statement applies.
Categories of personal information we collect, purposes, and whether they are sold or shared
- Identifiers (name, email address, company, account identifiers, IP address) — to create and operate your account, invoice you, provide support and prevent fraud. Not sold. Shared with advertising partners only through cookies and pixels you have consented to.
- Commercial information (products purchased, credits and traffic used, payment records) — to provide the Services, bill you and keep statutory accounting records. Not sold or shared.
- Internet and network activity (website analytics, pages visited, connection metadata on consumption proxy products, Scraping API request metadata) — to operate and secure the Services, measure the website and, with your consent, measure advertising. Shared for cross-context behavioural advertising only through consented pixels (Meta, LinkedIn, Reddit, X).
- Geolocation data (country and city derived from IP address) — to deliver location-based features, comply with sanctions and detect fraud. Not sold or shared.
- Government identifiers and identity documents (only when we request KYC verification) — to verify identity and unlock restricted access, processed by Sumsub or Stripe Identity. Not sold or shared.
- Professional information (company, role, intended use case) — to qualify accounts and provide support. Not sold or shared.
- Inferences (risk and fraud signals derived from the above) — to protect the Services. Not sold or shared.
- Sensitive personal information — we do not collect sensitive personal information except identity documents for KYC, which we use only to verify identity, never to infer characteristics.
Retention. Each category is kept for the period stated in Part III (Data Retention and Deletion), or for as long as necessary for the purpose stated above, whichever is shorter, unless a longer period is required by law.
Sale and sharing. Datafuel does not sell personal information for money. Datafuel shares personal information for cross-context behavioural advertising only through advertising cookies and pixels, and only after you have accepted them in the cookie banner. We do not knowingly sell or share the personal information of anyone under 16.
Do Not Sell or Share My Personal Information. You can opt out at any time by choosing Reject all or disabling the Marketing and advertising category in the cookie banner, available from the Cookie preferences link in the footer. We honour Global Privacy Control signals sent by your browser as a valid opt-out of sharing. Opting out does not affect strictly necessary cookies or the operation of your account.
Your rights. Depending on your state, you may have the right to know what personal information we hold about you, to access it in a portable format, to correct it, to delete it, to opt out of sale or sharing, to limit the use of sensitive personal information, and not to be discriminated against for exercising these rights. Submit a request at privacy@datafuel.ai or through your dashboard. We verify requests against your account details, respond within 45 days (extendable once by 45 days where permitted), and allow an authorised agent to act on your behalf with written authorisation. If we decline a request, you may appeal by replying to our response; we answer appeals within the period your state law requires.
Sources and recipients. We collect personal information directly from you, from your devices through cookies and pixels, from our payment and verification providers, and from our proxy and API infrastructure when you use the Services. We disclose it to the service providers and contractors listed in Part VII, Annex III (Sub-processors), for the business purposes stated above, under contracts that restrict their use of the information.
Notice at Collection. This section, together with the cookie banner and the privacy links shown at signup and checkout, constitutes our notice at or before collection for California residents. Last updated 3 October 2026.
Datafuel does not currently meet the CCPA's applicability thresholds and provides this notice voluntarily, in the same form it will take when the thresholds are met.
Part II · 2. How consent works
Datafuel uses strictly necessary tools without consent where they are strictly necessary to transmit a communication or to provide a service expressly requested by the user.
Datafuel does not activate non-essential analytics, marketing, advertising, or optional functional tracking tools before consent.
Consent is given through the first-layer banner or the preference panel. No category is pre-selected, except the strictly necessary category, which cannot be disabled because it is required for the website or a requested service to work.
The banner presents “Accept all”, “Reject all”, and “Customise” with equal visual weight. The banner does not use a cookie wall.
Consent can be withdrawn or changed at any time through the Cookie preferences control in the website footer. Withdrawal is as easy as giving consent.
Datafuel records the consent event, the selected categories, the banner or policy version, the time of the choice, and the relevant website or device information needed to demonstrate the choice and enforce it.
Datafuel asks for consent again after six months or after a material change to the purposes, providers, or tracking tools. A new request may also be required where the applicable law or the Authority’s guidance requires it.
Part II · 3. Categories of tools used
3.1 Strictly necessary tools
These tools are needed to operate the website, maintain security, manage sessions, remember consent choices, prevent abuse, or provide a service requested by the user.
- Datafuel — Session management, security, consent-management storage, and service operation · Session or as required for the relevant function; exact names and lifetimes to be confirmed by the production scan · First party · Datafuel Privacy Policy
- Cloudflare — Website delivery, security, performance, and protection against abusive traffic · Provider-set; exact cookie names and lifetimes to be confirmed by the production scan · Third party · Cloudflare Cookie Policy
Strictly necessary tools do not require consent under Article 122 when they are used only for the purposes described above. If a Cloudflare tool is used for an optional purpose, it must be placed in the relevant optional category and blocked until consent.
3.2 Analytics tools
Datafuel uses Google Analytics 4 to understand how visitors use the website and to measure website performance.
Google Analytics 4 is loaded only after consent. If Datafuel configures analytics in a manner that satisfies the Italian Authority’s conditions for analytics tools that may be treated as technically necessary, the configuration and the relevant conditions must be documented before the tool is treated as exempt from consent.
- Google — Google Analytics 4; website statistics and performance measurement · Provider-set; exact cookie names and lifetimes to be confirmed by the production scan and GA4 configuration · Third party · Google Analytics privacy information
The legal basis for consent-based analytics is consent. Analytics are not activated before consent.
3.3 Marketing and advertising tools
Datafuel may use advertising pixels and tags to measure campaigns, create or measure advertising audiences, attribute conversions, and support advertising activities.
These tools are activated only after consent.
Meta, LinkedIn, Reddit, and X may process information as independent controllers under their own terms. Their own policies explain their processing, retention, and available controls.
- Meta — Meta Pixel; campaign measurement, audience creation, and advertising measurement · Provider-set; exact cookie names and lifetimes to be confirmed by the production scan · Third party · Meta Privacy Policy
- LinkedIn — LinkedIn Insight Tag; campaign reporting, audience analytics, and advertising measurement · Provider-set; exact cookie names and lifetimes to be confirmed by the production scan · Third party · LinkedIn Cookie Policy
- Reddit — Reddit Pixel; campaign measurement and advertising attribution · Provider-set; exact cookie names and lifetimes to be confirmed by the production scan · Third party · URL to be confirmed against Reddit’s current official policy before publication
- X — X Pixel; campaign measurement and advertising attribution · Provider-set; exact cookie names and lifetimes to be confirmed by the production scan · Third party · URL to be confirmed against X’s current official policy before publication
The legal basis for these tools is consent. Rejecting or withdrawing marketing consent does not prevent access to the website.
3.4 Functional tools
Datafuel uses LiveChat and Futurebase for live chat and customer communications. These tools may be used to display the chat function, preserve a chat session, identify the conversation, and route a request to support.
A tool used only to provide a chat function expressly requested by the user may be strictly necessary for that interaction. Optional analytics, profiling, or marketing functions supplied by the same provider remain disabled unless consent is given.
- LiveChat — Live-chat session and support communications · Session or provider-set; exact cookie names and lifetimes to be confirmed · Third party · URL to be confirmed against LiveChat’s current official policy before publication
- Futurebase — Live-chat and customer-communication functions · Session or provider-set; exact cookie names and lifetimes to be confirmed · Third party · URL to be confirmed against Futurebase’s current official policy before publication
The website must not activate optional functional tracking before consent. If the chat is necessary only after the user opens or requests it, the implementation should load the relevant provider only at that point.
Part II · 4. First-party and third-party tools
A first-party tool is set by datafuel.ai or on its behalf. A third-party tool is set or accessed by an external provider.
Third-party providers may process data under their own privacy policies. Some providers may act as processors for particular functions and as independent controllers for others. The live configuration and contracts determine the applicable role.
Part II · 6. Consent records
Datafuel keeps a record of the choices made through the consent mechanism. The record may include the time of the choice, the selected categories, the consent-banner version, the website version, and technical information needed to link the record to the relevant device or browser.
The record is used to demonstrate compliance, apply the selected preferences, respond to requests, and prevent repeated consent requests during the applicable period.
The consent-record retention period must be confirmed in the production configuration and documented in the Privacy Policy and vendor register. It must not exceed what is necessary to demonstrate the choice and comply with legal obligations.
Part II · 8. Legal references
The storage of information on, or access to information from, a user’s device generally requires prior informed consent unless the tool is strictly necessary for transmission or for a service expressly requested by the user under Article 122 of the Italian Privacy Code.
The Italian Data Protection Authority’s 10 June 2021 Guidelines on cookies and other tracking tools should be applied to the banner, preference panel, consent recording, and withdrawal design. The exact production implementation must be checked against those Guidelines before launch.
Part II · 2. Come funziona il consenso
Datafuel utilizza gli strumenti strettamente necessari senza consenso quando sono necessari esclusivamente per trasmettere una comunicazione o per fornire un servizio espressamente richiesto dall’utente.
Datafuel non attiva strumenti facoltativi di analisi, marketing, pubblicità o tracciamento funzionale prima del consenso.
Il consenso è espresso tramite il banner di primo livello o il pannello delle preferenze. Nessuna categoria è preselezionata, salvo la categoria strettamente necessaria, che non può essere disattivata perché indispensabile al funzionamento del sito o del servizio richiesto.
Il banner presenta i comandi “Accetta tutto”, “Rifiuta tutto” e “Personalizza” con pari evidenza visiva. Il banner non utilizza un cookie wall.
Il consenso può essere revocato o modificato in qualsiasi momento tramite il comando Preferenze cookie nel footer del sito. La revoca è semplice quanto la prestazione del consenso.
Datafuel registra l’evento di consenso, le categorie selezionate, la versione del banner o della Policy, l’ora della scelta e le informazioni sul sito o sul dispositivo necessarie a dimostrare la scelta e ad applicarla.
Datafuel richiede nuovamente il consenso dopo sei mesi o dopo una modifica sostanziale alle finalità, ai fornitori o agli strumenti di tracciamento. Una nuova richiesta può essere necessaria anche quando lo impongono la legge applicabile o le indicazioni del Garante.
Part II · 3. Categorie di strumenti utilizzati
3.1 Strumenti strettamente necessari
Questi strumenti sono necessari per gestire il sito, mantenere la sicurezza, gestire le sessioni, memorizzare le scelte sui cookie, prevenire abusi o fornire un servizio richiesto dall’utente.
- Datafuel — Gestione sessione, sicurezza, memorizzazione del consenso e funzionamento del servizio · Di sessione o per il tempo necessario alla funzione; nomi e durate esatti da verificare con la scansione del sito in produzione · Prima parte · Informativa Privacy Datafuel
- Cloudflare — Distribuzione del sito, sicurezza, prestazioni e protezione dal traffico abusivo · Stabilita dal fornitore; nomi e durate esatti da verificare con la scansione del sito in produzione · Terza parte · Cloudflare Cookie Policy
Gli strumenti strettamente necessari non richiedono consenso ai sensi dell’articolo 122 quando sono utilizzati esclusivamente per le finalità sopra indicate. Se uno strumento Cloudflare è utilizzato per una finalità facoltativa, deve essere incluso nella categoria facoltativa pertinente e bloccato fino al consenso.
3.2 Strumenti di analisi
Datafuel utilizza Google Analytics 4 per comprendere come i visitatori usano il sito e per misurarne le prestazioni.
Google Analytics 4 viene caricato solo dopo il consenso. Se Datafuel configura lo strumento in modo da rispettare le condizioni del Garante per gli strumenti di analisi assimilabili a quelli tecnici, la configurazione e il rispetto delle condizioni devono essere documentati prima di considerarlo esente dal consenso.
- Google — Google Analytics 4; statistiche e misurazione delle prestazioni del sito · Stabilita dal fornitore; nomi e durate esatti da verificare con la scansione del sito e la configurazione GA4 · Terza parte · Informazioni privacy Google Analytics
La base giuridica degli strumenti di analisi soggetti a consenso è il consenso dell’utente. Gli strumenti di analisi non sono attivati prima del consenso.
3.3 Strumenti di marketing e pubblicità
Datafuel può utilizzare pixel e tag pubblicitari per misurare campagne, creare o misurare audience pubblicitarie, attribuire conversioni e supportare attività pubblicitarie.
Questi strumenti sono attivati solo dopo il consenso.
Meta, LinkedIn, Reddit e X possono trattare informazioni in qualità di titolari autonomi secondo i propri termini. Le loro informative descrivono le attività, i periodi di conservazione e gli strumenti di controllo disponibili.
- Meta — Meta Pixel; misurazione campagne, audience e pubblicità · Stabilita dal fornitore; nomi e durate esatti da verificare con la scansione del sito · Terza parte · Informativa Privacy Meta
- LinkedIn — LinkedIn Insight Tag; report campagne, analisi audience e pubblicità · Stabilita dal fornitore; nomi e durate esatti da verificare con la scansione del sito · Terza parte · LinkedIn Cookie Policy
- Reddit — Reddit Pixel; misurazione campagne e attribuzione pubblicitaria · Stabilita dal fornitore; nomi e durate esatti da verificare con la scansione del sito · Terza parte · URL da verificare sull’informativa ufficiale Reddit vigente prima della pubblicazione
- X — X Pixel; misurazione campagne e attribuzione pubblicitaria · Stabilita dal fornitore; nomi e durate esatti da verificare con la scansione del sito · Terza parte · URL da verificare sull’informativa ufficiale X vigente prima della pubblicazione
La base giuridica è il consenso. Il rifiuto o la revoca del consenso al marketing non impediscono l’accesso al sito.
3.4 Strumenti funzionali
Datafuel utilizza LiveChat e Futurebase per la chat e le comunicazioni con i clienti. Questi strumenti possono servire a mostrare la chat, mantenere una sessione, identificare la conversazione e inoltrare una richiesta all’assistenza.
Uno strumento utilizzato esclusivamente per fornire una chat espressamente richiesta dall’utente può essere strettamente necessario per quella interazione. Le funzioni facoltative di analisi, profilazione o marketing dello stesso fornitore restano disattivate fino al consenso.
- LiveChat — Sessione di chat e comunicazioni di assistenza · Di sessione o stabilita dal fornitore; nomi e durate esatti da verificare · Terza parte · URL da verificare sull’informativa ufficiale LiveChat vigente prima della pubblicazione
- Futurebase — Chat e comunicazioni con i clienti · Di sessione o stabilita dal fornitore; nomi e durate esatti da verificare · Terza parte · URL da verificare sull’informativa ufficiale Futurebase vigente prima della pubblicazione
Il sito non deve attivare strumenti funzionali facoltativi prima del consenso. Se la chat è necessaria solo dopo che l’utente la apre o la richiede, l’implementazione dovrebbe caricare il fornitore solo in quel momento.
Part II · 4. Strumenti di prima e terza parte
Uno strumento di prima parte è installato da datafuel.ai o per suo conto. Uno strumento di terza parte è installato o consultato da un fornitore esterno.
I fornitori terzi possono trattare i dati secondo le proprie informative. Lo stesso fornitore può agire come responsabile per alcune funzioni e come titolare autonomo per altre. Il ruolo applicabile dipende dalla configurazione effettiva e dai contratti.
Part II · 5. Gestione e revoca del consenso
È possibile selezionare o rifiutare le categorie facoltative dal banner o dal pannello delle preferenze.
È possibile riaprire il pannello in qualsiasi momento selezionando Preferenze cookie nel footer del sito.
È inoltre possibile cancellare o bloccare i cookie dalle impostazioni del browser. Le impostazioni del browser possono cancellare le preferenze memorizzate dal sito e rendere necessario effettuare nuovamente la scelta.
Il blocco dei cookie strettamente necessari può incidere sulla sicurezza, sulle sessioni, sul login o sui servizi richiesti.
Part II · 6. Registrazione del consenso
Datafuel conserva una registrazione delle scelte effettuate tramite il meccanismo di consenso. La registrazione può includere l’ora della scelta, le categorie selezionate, la versione del banner, la versione del sito e le informazioni tecniche necessarie a collegare la registrazione al dispositivo o al browser interessato.
La registrazione serve a dimostrare la conformità, applicare le preferenze, rispondere alle richieste e non ripetere la richiesta durante il periodo applicabile.
Il periodo di conservazione della registrazione del consenso deve essere verificato nella configurazione di produzione e documentato nella Privacy Policy e nel registro dei fornitori. Non deve eccedere quanto necessario a dimostrare la scelta e a rispettare gli obblighi di legge.
Part II · 8. Riferimenti normativi
La memorizzazione di informazioni sul dispositivo dell’utente o l’accesso a informazioni già memorizzate richiede generalmente il consenso informato preventivo, salvo che lo strumento sia strettamente necessario per la trasmissione o per un servizio espressamente richiesto dall’utente ai sensi dell’articolo 122 del Codice privacy.
Le Linee guida del Garante del 10 giugno 2021 su cookie e altri strumenti di tracciamento devono essere applicate al banner, al pannello delle preferenze, alla registrazione del consenso e alla procedura di revoca. L’implementazione effettiva in produzione deve essere verificata prima del rilascio.
Part III · Data Retention and Deletion
Version: 1.0 · Effective: 3 October 2026
- Account data — Life of account plus 12 months after closure; then deleted or anonymised unless tax or legal retention applies
- Billing and invoices — 10 years where required by Italian tax law
- KYC data — 5 years from account closure, held by the verification provider
- Consumption-product connection metadata — 14 days, rolling deletion
- Dedicated static-product connection logs — None retained
- Scraping API request metadata — 30 days
- Scraping API results — 30 days for customer retrieval, then deleted
- Training data — Pseudonymised and PII-stripped; retained for the training purpose; opt-out excludes future runs only
- Support and chat transcripts — 3 months
- Marketing and CRM — Until consent withdrawal or 24 months of inactivity
- Backups — Rolling 30 days; deletion propagates within 30 days
- Residential SDK data — IP, country, network type, OS for 180 days
- Security and audit logs — 12 months
Part III · Deletion mechanics
Customers may request deletion by contacting privacy@datafuel.ai or closing the Account through the dashboard. At closure, Datafuel disables access, allows reasonable export where available, deletes data under the table, and retains data subject to legal obligations or legal holds.
A legal hold suspends deletion only for the data and period necessary for a claim, investigation, or legal obligation. Enterprise customers may request a deletion certificate after completion of deletion, subject to backup rotation and legal retention.
Backups are not restored solely to delete an item. A deletion propagates through the rolling backup cycle within 30 days, unless a legal hold applies. Models already trained are not retrained after a training-data opt-out.
Part IV · International Data Transfers
Version: 1.0 · Last updated: 3 October 2026
Datafuel processes some information outside the EEA. This includes Scraping API processing on Datafuel-owned servers at Telehouse New York Teleport, 7 Teleport Dr, Staten Island, NY 10311, United States. Some providers, including Stripe, HubSpot, Google, LiveChat, Cloudflare, and advertising partners, may also process data in the United States or other third countries.
Where required, Datafuel uses the European Commission Standard Contractual Clauses adopted by Decision (EU) 2021/914, using the appropriate controller-to-processor or processor-to-processor module. Datafuel performs transfer impact assessments and applies supplementary measures such as encryption, access control, minimisation, segregation, and retention limits.
Datafuel may rely on the EU-US Data Privacy Framework where the recipient is certified and the certification covers the relevant transfer.
Customers may request a copy of the applicable safeguards or further information by contacting privacy@datafuel.ai. The request may be subject to confidentiality and security redactions.
Part V · Residential SDK Privacy Notice (for device owners)
Controller: Double C S.r.l., Via del Fosso della Magliana 34G, 00148 Rome, Italy. Contact: privacy@datafuel.ai. No DPO has been appointed.
Part V · 1. Purpose and legal basis
The SDK lets an opted-in device provide a network exit point for access to public websites. The legal basis is consent under Article 6(1)(a) GDPR. Consent is separate, affirmative, optional, and can be withdrawn with one tap as easily as it was given.
Part V · 2. Data collected
Datafuel collects the device IP address, country, network type, and operating system. Datafuel does not read the device owner’s browsing content or intentionally identify the device owner to business customers.
Part V · 3. Retention and recipients
SDK data is retained for 180 days. Business customers see the IP address used as a network endpoint, not the device owner’s identity. Data may be shared with authorised service providers and used for security, billing, abuse handling, and network operation.
Part V · 4. Traffic transparency
Public web requests may pass through the device’s network connection. The SDK is not designed to read the device owner’s browsing content. Datafuel’s AUP prohibits unlawful, abusive, harmful, and restricted uses. Datafuel may suspend a customer or block traffic where abuse is detected.
Part V · 5. Transfers and security
Data may be processed outside the EEA under SCCs 2021/914, adequacy decisions, the EU-US Data Privacy Framework where applicable, and supplementary measures. Datafuel applies access control, encryption where appropriate, minimisation, monitoring, and retention limits.
Part V · 6. Rights
The device owner may request access, correction, deletion, restriction, portability, or object to processing. Consent may be withdrawn at any time. Contact privacy@datafuel.ai. A complaint may be lodged with the Garante per la protezione dei dati personali at garanteprivacy.it.
Device owners must be at least 18. The SDK may not be integrated into children’s apps.
Part VI · 1. Infrastructure
The website is protected and delivered through Cloudflare. The dashboard, API, and backups use Hetzner Cloud in Germany. The Scraping API also runs on Datafuel-owned dedicated servers in Germany and the United States.
Part VI · 2. Controls
Datafuel uses encryption in transit and at rest where appropriate, least-privilege access, authentication, access reviews, logging, monitoring, vulnerability management, supplier review, incident response, and network controls.
Backups use a rolling process with an RPO of 24 hours and an RTO of 8 hours.
Part VI · 3. Incidents and continuity
Datafuel maintains incident-response and business-continuity procedures. Under the DPA, Datafuel notifies customers of a personal-data breach without undue delay and in any event within 48 hours after awareness.
Part VI · 4. Vendors and assurance
The public Sub-processor List identifies relevant infrastructure and service providers. SOC 2 and ISO 27001 are in progress with a target of Q1 2027. They are not current certifications and must not be presented as completed.
Part VI · 5. Requests
Customers may request the security questionnaire or DPA at security@datafuel.ai or legal@datafuel.ai, subject to verification and confidentiality.
Part VI · 1. Scope
In scope: datafuel.ai, the dashboard, Datafuel APIs, and the residential SDK. Out of scope: third-party services, social engineering, denial-of-service testing, physical testing, spam, and actions that access or expose other users’ data.
Part VI · 2. Rules
Researchers must act in good faith, minimise access, avoid disruption, stop testing when sensitive data is encountered, and not exfiltrate, alter, persist in, or publicly disclose data. Test accounts and test data must be used where possible.
Part VI · 3. Reports
Send reports to security@datafuel.ai. Include affected asset, summary, reproduction steps, impact, evidence, timestamps, and contact details. Datafuel aims to acknowledge within 3 business days.
Part VI · 4. Triage and fixes
Target handling: critical acknowledgement within 1 business day and mitigation as soon as practicable; high triage within 3 business days and target fix within 30 days; medium triage within 10 business days and target fix within 60 days; low triage within 20 business days and target fix within 90 days. These are targets, not guarantees.
Coordinated disclosure may occur after remediation and agreement on timing.
Part VI · 5. Safe harbour and rewards
Datafuel will not pursue legal action against good-faith research that follows this Policy, except where required to protect people, systems, or legal rights. Datafuel may recognise researchers on a recognition page with consent.
A monetary bug bounty is available for eligible reports. Reward tiers: critical [amount to be inserted]; high [amount]; medium [amount]; low [amount]. Eligibility, duplicate reports, severity, and payment method are determined by Datafuel after review.
Part VII · Data Processing Agreement
Controller: the Customer. Processor: Double C S.r.l. (Datafuel).
Version: 1.0 · Effective: 3 October 2026
1. Scope and roles
For personal data the Customer routes through proxies or extracts through Scraping APIs, Datafuel processes the data on the Customer’s documented instructions and acts as processor under Article 28 GDPR.
The sole stated exception is Datafuel’s storage of pseudonymised, PII-stripped extracted pages for training its own model under legitimate interest. For that purpose Datafuel acts as an independent controller. The Customer may opt out through the dashboard switch. The Privacy Policy and Scraping API Terms describe that processing.
2. Subject matter, duration, nature and purpose
The subject matter is proxy routing, scraping, rendering, storage, delivery, support, security, and related processing. Processing lasts for the Services period and any legally required or agreed deletion period.
Datafuel processes data to execute the Customer’s requests, route traffic, return outputs, operate webhooks, provide support, secure the Services, investigate abuse, and comply with law.
3. Data and data subjects
Data may include whatever the Customer routes or extracts, including identifiers, contact data, browsing or target content, IP addresses, URLs, queries, account identifiers, and connection metadata on consumption products. Data subjects may include the Customer’s users, target-site visitors, employees, customers, and other persons appearing in routed or extracted data.
4. Instructions and confidentiality
Datafuel follows documented instructions in the Order, Terms, AUP, API requests, dashboard settings, and this DPA. Datafuel informs the Customer if an instruction appears unlawful. Authorised personnel are bound by confidentiality.
5. Security
Datafuel applies Article 32 GDPR measures in Annex II, including access control, least privilege, authentication, encryption in transit and at rest where appropriate, logging, monitoring, backups, incident response, supplier controls, and deletion controls. SOC 2 and ISO 27001 are in progress, with a target of Q1 2027; they are not current certifications.
6. Sub-processors
The Customer gives general authorisation to the sub-processors in Annex III. Datafuel gives 30 days’ notice before a new sub-processor processes Customer data. The Customer may object on reasonable data-protection grounds. If the objection cannot be resolved, the Customer may terminate the affected Service where the Terms permit.
7. Assistance
Taking account of the processing, Datafuel assists with rights requests, security obligations, DPIAs, consultations, audits, and breach investigations. Datafuel notifies the Customer of a personal-data breach without undue delay and in any event within 48 hours after awareness.
8. Deletion and return
At the Customer’s choice, Datafuel returns or deletes personal data at the end of the Services, unless law requires retention. Consumption-product connection metadata is retained for 14 days. API results are normally available for 30 days. Backups follow a rolling 30-day cycle.
9. Audits
Datafuel makes available information needed to demonstrate compliance and permits reasonable audits. Audits require reasonable notice, confidentiality, and security controls. Certifications, questionnaires, independent reports, and remote evidence may satisfy an audit where proportionate.
10. Transfers
Transfers follow Annex IV. The parties use SCCs 2021/914 Module 2 where the Customer is controller and Datafuel processor, and Module 3 where Datafuel engages a processor. Datafuel performs a transfer impact assessment and applies supplementary measures.
11. Liability and precedence
The Terms of Service govern commercial liability. This DPA governs data protection. Mandatory GDPR rights prevail. If this DPA conflicts with the Terms on data processing, this DPA prevails.
12. Termination
This DPA begins when the Customer accepts it online and ends when Datafuel no longer processes Customer personal data, subject to required retention.
Annex I — Processing description
Subject: proxy routing and API extraction. Duration: Service term plus deletion periods. Purposes: performance, delivery, support, security, abuse handling. Data: routed or extracted personal data, URLs, IPs, account data, and consumption metadata. Subjects: persons represented in Customer data and users of target services.
Annex II — Technical and organisational measures
Access is role-based and least-privilege. Administrative access uses strong authentication. Data is encrypted in transit and at rest where appropriate. Systems are monitored and logged. Backups use a 30-day rotation with RPO 24 hours and RTO 8 hours. Personnel receive confidentiality and security instructions. Vulnerability management, incident response, vendor review, segregation, rate controls, and deletion procedures apply.
Annex III — Sub-processors
Version: 1.0 · Last updated: 3 October 2026
Datafuel may appoint the providers below to process customer data. Account owners receive email notice at least 30 days before a new sub-processor processes customer data. Customers may object under the DPA on reasonable data-protection grounds. Subscribe to change notices: [subscription link to be inserted].
- Stripe — Card payments · Account, billing, payment metadata · International · SCCs or adequacy where applicable · Provider DPA/privacy terms to be confirmed
- Stripe Identity — KYC · Identity and verification data · International · SCCs or adequacy where applicable · Provider terms to be confirmed
- CoinGate — Crypto payments · Account and payment metadata · International · SCCs or adequacy where applicable · Provider terms to be confirmed
- Payssion — Local payment methods · Account and payment metadata · International · SCCs or adequacy where applicable · Provider terms to be confirmed
- Sumsub — KYC · Identity and verification data · International · SCCs or adequacy where applicable · Provider terms to be confirmed
- Hetzner Online GmbH — Dashboard, API, backups · Account, usage, API and backup data · Germany · EEA processing; safeguards for any non-EEA access · Provider terms to be confirmed
- Cloudflare — Website delivery and security · IP, request and security metadata · International · SCCs or adequacy where applicable · Provider terms to be confirmed
- HubSpot — CRM and email · Contact, account, support and marketing data · International · SCCs or adequacy where applicable · Provider terms to be confirmed
- Google — GA4 analytics · Website and analytics identifiers · International · Consent plus SCCs or adequacy where applicable · Provider terms to be confirmed
- LiveChat — Support chat · Contact and chat content · International · SCCs or adequacy where applicable · Provider terms to be confirmed
- Futurebase — Support chat · Contact and chat content · International · SCCs or adequacy where applicable · Provider terms to be confirmed
- Telehouse New York Teleport, 7 Teleport Dr, Staten Island, NY 10311 — Colocation for Scraping API processing on Datafuel-owned servers · API requests, results and service metadata · United States · SCCs, TIA and supplementary measures · Provider terms to be confirmed
Part VII · Independent controllers — advertising partners
Meta, LinkedIn, Reddit, and X may process advertising and measurement data as independent controllers. Their processing occurs under their own policies and only after the user’s cookie consent where required. Their policy links must be kept current in the Cookie Policy.
Annex IV — International transfers
Transfers may use SCCs 2021/914 Module 2 or Module 3 as applicable, a transfer impact assessment, encryption, minimisation, access controls, and EU-held keys where available. Processing at Telehouse New York is in the United States. The EU-US Data Privacy Framework may be used where the recipient is certified and the certification covers the transfer.