Data processing agreement (DPA)
The processing agreement that governs the email addresses you entrust to YesWeCheck for validation. This English version is provided for convenience. The French version prevails in the event of any discrepancy. Read the French version.
Preamble and parties
This data processing agreement (the "DPA") is entered into between the Customer, identified in its account or order and acting as controller (or, where applicable, as authorised processor of a controller), and BIVAO CONSULTING, SARL, RCS Lille Métropole 750 315 327, intra-EU VAT number FR77750315327, publisher of the YesWeCheck service (the "Processor").
This DPA governs exclusively the personal data processing operations carried out on behalf of the Customer by YesWeCheck as part of the Service. Processing whose purposes are determined by BIVAO CONSULTING itself is described in its Privacy policy and does not fall within this DPA. Where the Customer acts as processor for a third party, it warrants that it holds the necessary instructions and authorisations and ensures that the contracts in its processing chain are consistent.
Article 1 - Definitions and order of precedence
The terms "personal data", "controller", "processor", "personal data breach", "processing" and "supervisory authority" have the meaning given to them in Regulation (EU) 2016/679. The Terms of sale and the Terms of use describe the commercial and functional terms; this DPA prevails in the event of conflict concerning an obligation relating to the processing of personal data on behalf of the Customer, subject to mandatory rules.
Article 2 - Subject matter, duration and instructions
YesWeCheck processes the Customer's data only to provide the services described in Annex A, for the term of the contract and according to the functional and legal periods provided for. The Customer's documented instructions comprise this DPA, the settings validly configured and its requests to the Service. Any additional instruction must be compatible with the Service and accepted in writing where its implementation requires development work, a cost or a departure from the security measures.
If YesWeCheck considers that an instruction infringes the GDPR or another applicable data protection provision, it informs the Customer, unless prohibited by law, and may suspend the performance of the instruction concerned until it is clarified. If the law requires processing irrespective of the Customer's instructions, the Customer is informed before the processing, unless the law prohibits this on important grounds of public interest.
Article 3 - Customer's commitments
The Customer determines the purposes, legal bases, recipients and periods appropriate to its own processing. It provides the information required to data subjects and handles their requests. It checks the lawfulness of files, imports, business address searches and subsequent prospecting. It undertakes not to submit sensitive or high-risk data requiring safeguards not provided for by the standard Service without prior agreement. It also ensures the confidentiality of its keys and exports.
These obligations do not relieve YesWeCheck of the obligations imposed directly on processors by the GDPR.
Article 4 - Confidentiality and authorised personnel
YesWeCheck ensures that the persons authorised to process the data are subject to an appropriate statutory or contractual duty of confidentiality, are authorised according to their duties and receive appropriate instructions. Access is limited to what is necessary for the service, authorised support and security.
Article 5 - Technical and organisational measures
YesWeCheck implements and maintains appropriate measures within the meaning of Article 32 of the GDPR, taking into account the state of the art, the costs of implementation, the nature of the processing and the risks. Annex B describes the measures in place. The arrangements may change in order to maintain an overall appropriate level of protection, without any unjustified substantial reduction. No clause guarantees zero risk.
Article 6 - Sub-processors
The Customer grants a general written authorisation to use the categories of sub-processors necessary for the provision of the Service, within the limits of the providers presented in Annex C. YesWeCheck undertakes to bind each relevant sub-processor to data protection obligations substantially equivalent to those of this DPA, to carry out appropriate checks and to remain liable to the Customer for the performance of those sub-processors' obligations in accordance with the GDPR.
YesWeCheck maintains the list of categories of sub-processors set out in Annex C and informs Customers of any intended addition or replacement at least 30 days before it takes effect, by email or by a notification in the account, allowing them to raise a reasoned objection relating to data protection. In a documented emergency (for example a security flaw or the failure of a provider), notification is given as soon as possible before the change or, failing that, immediately afterwards. The parties seek a reasonable solution; where a legitimate ground persists and no alternative is available, the Customer may terminate the processing concerned under the legal and contractual conditions. The named list of sub-processors is available on request, under a confidentiality undertaking.
Article 7 - Transfers outside the EEA
YesWeCheck undertakes to frame the international transfers of personal data for which it is responsible as processor in accordance with Chapter V of the GDPR. Depending on the flow, this may include an adequacy decision, the Data Privacy Framework for an effectively certified recipient, appropriate standard contractual clauses (SCCs), supplementary measures or any other basis permitted by law.
SMTP verification may require querying mail providers chosen through the configuration of the recipient's domain, which may be located in third countries. This technical transfer, inherent to the service, is explained to the Customer before use; the Customer decides whether or not to submit the address to this check. This instruction does not relieve the parties of examining the legal requirements actually applicable to each flow. Third-party integrations deliberately activated by the Customer also fall under its instructions and the recipients' own roles.
Article 8 - Assistance with rights and obligations
Taking into account the nature of the processing and the information available to it, YesWeCheck reasonably assists the Customer in responding to requests for access, rectification, erasure, objection, restriction and portability concerning the data it processes on the Customer's behalf. It also assists the Customer with impact assessments, prior consultations, security assessments and required exchanges with the authorities, to the extent provided for in Articles 28 and 32 to 36 of the GDPR.
Requests clearly outside the normal operation of the Service or requiring specific work may be subject to a proposal of reasonable costs, announced in advance, without reducing the assistance required by law.
Article 9 - Personal data breaches
As soon as it becomes aware of a personal data breach affecting the data processed for the Customer, YesWeCheck informs the Customer as soon as possible, without undue delay, by email to the administrators of the organisation concerned, and progressively provides the reasonably available information on its nature, likely consequences, the categories concerned and the measures taken or envisaged. It cooperates to enable the Customer to meet its own notification obligations, without guaranteeing an exhaustive analysis from the first notice.
The Customer remains responsible for determining its notification obligations towards the supervisory authority and data subjects, unless a specific documented mandate exists. A technical alert or an event that does not concern the Customer's personal data is not automatically treated as a breach within the meaning of the GDPR.
Article 10 - Return and deletion
At the end of the service, YesWeCheck deletes or returns the personal data processed on behalf of the Customer, at the Customer's choice, to the technical and contractual extent provided for and subject to any legal retention obligation. The exports available in the account and the closure of the account are the operational means of return or deletion. Periods and deadlines are specified in Annex A and in the Data retention policy.
Backups are encrypted and purged within 30 days; they are used only for restoration and continuity of the Service. Data retained under the law is not reused for other purposes.
Article 11 - Evidence and audits
YesWeCheck makes available the information necessary to demonstrate compliance with its obligations as processor and allows for audits, including inspections, conducted by the Customer or an auditor it mandates, under the conditions of Article 28(3)(h) of the GDPR. The parties give priority to documentary evidence, available independent reports and reasonable questionnaires, then, if this proves insufficient and necessary, a scheduled audit respecting the confidentiality, security and rights of other customers.
Audits are carried out within the limit of one audit per contract year, with 30 days' written notice, by the Customer or by an independent external auditor who is not a competitor of YesWeCheck, under appropriate confidentiality conditions. The audit gives no access to any data of other customers and must not disrupt the Service. The costs of the audit are borne by the requesting Customer, unless a significant breach by the Processor is established, without preventing an audit required by law.
Article 12 - Liability
Each party is liable for the obligations imposed on it by the GDPR and for the breaches attributable to it. The limitation of liability clauses of the Terms of use do not affect the direct rights of data subjects or the mandatory obligations provided for by the GDPR, including its Article 82. Recourse between the parties is assessed according to the applicable law and the allocation of responsibilities actually established.
Administrative fines or regulatory penalties incurred by YesWeCheck as a result of a breach by the Customer of its obligations count towards the liability cap applicable between the parties under the Terms of use.
Article 13 - Entry into force and evidence
The DPA is accepted together with the Terms of use, the Terms of sale and the Acceptable use policy by means of a single, unticked checkbox at sign-up; this acceptance is confirmed at the time of payment. It takes effect upon this acceptance, and at the latest before any personal data is processed on behalf of the Customer. The accepted version is archived with its timestamp. A substantial change is announced 30 days in advance, by email and by a banner in the application; a new acceptance is requested at the next purchase. Changes do not reduce mandatory safeguards.
---
Annex A - Description of the processing
Subject matter: verification of email addresses, syntax/DNS/SMTP analysis, classification and scores, enrichment of results, file processing, audit, exports, deduplication, activated integrations, business address search at the Customer's request.
Nature and purpose: one-off collection via the API, the interface, an import, a widget or an integration; technical querying; production and consultation of a result; necessary history and statistics; deletion according to the applicable settings. No commercial enrichment of files for YesWeCheck's own account is permitted.
Duration: for the duration of the service and according to the published retention periods: imported files deleted when processing closes; detailed batch results 7 or 30 days depending on the setting; export files up to 8 days after their creation; audits not unlocked 30 days; batch statistics 90 days; pseudonymised technical results up to 30 days, never disclosed to another customer; verification history kept until erased by the Customer or until the account is deleted; B2B Finder searches 30 days; log retention according to the data retention policy. Backups are encrypted and purged within 30 days.
Categories of data subjects: contacts, prospects, customers, correspondents and other holders of email addresses contained in the files or requests lawfully submitted by the Customer; staff and users of connected tools, where relevant.
Categories of data: email addresses, domains, first and last names where provided to the B2B Finder, import metadata, technical data required for the assessment, results, timestamps, minimised logs, enrichment data derived from the local part of the address (likely first and last name, gender associated with the first name, presumed age bracket, each with a confidence score). The standard Service is not designed to process special categories of data or data relating to criminal convictions.
Documented instructions: account settings, import, API verification, SMTP activation, export downloads, retention rules and connection/revocation of integrations.
Annex B - Security measures
- HTTPS on all public surfaces; encryption of stored addresses with AES-256-GCM, with keys managed by a dedicated key management service.
- Blind indexing with HMAC-SHA-256; no plain-text address column in operational storage.
- Protection of secrets: bcrypt for passwords; SHA-256 fingerprints of API keys; key rotation and revocation.
- Access control, logical separation of organisations, roles and permissions.
- Two-factor authentication (TOTP) with backup codes, alert on sign-in from a new device, PIN code for downloading exports, IP and domain restrictions on keys where configured, rate limiting and quotas.
- Firewall filtering inbound connections; administration access protected by a dedicated access control in addition to authentication.
- Minimised security logs, monitoring, incident management, corrective maintenance.
- Retention and erasure according to defined periods; encrypted backups, purged within 30 days.
- Supervision of authorised persons and providers, and confidentiality measures.
Annex C - Initial register of providers
| Provider | Role | Location / remarks |
|---|---|---|
| OVHcloud | Hosting, databases, encryption key management, email, technical services | France |
| Cloudflare | Security and delivery service through which all web and API traffic passes, including the content of requests; bot protection | Company established in the United States; global network |
Stripe / Sold through Link, LLC act in relation to payment mainly in their own roles; they are not automatically sub-processors for the processing of the Customer's address files. Connectors that the Customer activates with third parties may receive data on its instructions; their role is to be determined according to the situation. This register is kept up to date; any change is subject to the information provided for in Article 6. The named list of sub-processors is available on request, under a confidentiality undertaking.