Privacy policy

How YesWeCheck, an email address validation service, processes personal data, and how to exercise your rights. This English version is provided for convenience. The French version prevails in the event of any discrepancy. Read the French version.

1. Controller and contact

BIVAO CONSULTING, SARL, RCS Lille Métropole 750 315 327, intra-EU VAT number FR77750315327, publishes YesWeCheck. For the data of its accounts, visitors, contacts, prospects and customers, BIVAO CONSULTING acts as controller. Data protection contact: [email protected].

For the email addresses and files provided by a customer that determines the purpose and essential means of the processing, YesWeCheck in principle acts as processor, in accordance with the DPA. Certain operations involving payment providers, receiving mail providers and third-party integrations may fall under other legal roles described below.

2. Principles

We use data to the extent necessary for the operation of the Service, security, support and the purposes stated. We neither sell nor rent customer files. No address is disclosed to another customer or used for any other purpose; pseudonymised technical results may be kept for up to 30 days for the reliability of the service. SMTP checks do, however, require exchanges with the infrastructure of the domains concerned. We apply defined retention periods and appropriate security mechanisms.

CategoriesExamplesPurposesMain legal basis
Account and usersName, email, organisation, rights, language, authenticationOpening the account, checking the address entered at sign-up, access, security, performance of the serviceContract; legitimate interest (service security, fraud prevention) for certain security measures
Sign-in securityIP address, browser, operating system, approximate location derived from the IP address, recognised devicesDetecting unusual sign-ins and alerting the user; identifying multiple accounts opened for abusive purposesLegitimate interest (account security, abuse prevention)
Service and APIRequests, timestamps, technical identifiers, statistics, limited logsProviding the checks, tracking usage, preventing abuseContract; legitimate interest (service security, abuse prevention) or legal obligation depending on the processing
Bot protectionVerification token, IP addressProtecting the sign-up and demonstration formsLegitimate interest (service security)
Website demonstrationAddress, or first name, last name and domain, entered by the visitorAllowing a limited trial of the serviceLegitimate interest (presentation of the service)
Orders and billingPlan, transaction history, company name, company identifier, country, amount and statusManaging the business relationship, accounting and evidenceContract; legal obligation
Acceptance of termsUser, organisation, document and version accepted, timestampEvidence of acceptance of the Terms of use, Terms of sale, Acceptable use policy and DPAContract; legitimate interest (evidence)
SupportMessages, attachments provided voluntarily, technical contextAnswering, diagnosing, improving the quality of supportContract; legitimate interest (quality of support, fraud prevention) depending on the context
Enrichment of resultsLikely first and last name, gender associated with the first name, presumed age bracket, each with a confidence score, derived solely from the local part of the addressSupplementing verification results, in batch processing as well as in single verification through the APIContract
YesWeCheck business prospectingName, business address, company and exchangesPresenting relevant services and managing objectionsLegitimate interest (B2B business development), subject to the rules on prospecting
Strictly limited audience measurementVisits and aggregated technical characteristicsInternal traffic statisticsLegitimate interest, where the conditions for exemption are actually met
Full audience measurementPseudonymous identifier, journey, origin of the visitAttribution and improvement of the experienceConsent

The addresses submitted for validation, imported files, results and data of contacts searched for using the B2B Finder constitute, where they are processed on behalf of the Customer, data processed on its instructions. The Customer determines the legal basis for the processing and the information to be provided to data subjects. Processing is not automatically lawful merely because the address is a business address.

YesWeCheck does not take any automated decision producing legal effects concerning data subjects within the meaning of Article 22 of the GDPR.

4. Payment and merchant of record

Purchases are processed through Stripe Managed Payments, with Sold through Link, LLC as Merchant of Record for the transactions concerned. The provider may process payment information, billing address and fraud screening data as controller of its own processing, under its own terms and privacy policy. YesWeCheck receives the information needed to credit the account, assist the Customer, manage the business relationship and meet its legal obligations. Full payment card numbers are not required in our Service management interface.

5. SMTP verification and public data

An SMTP check may involve exchanges with the mail servers of the domain of the address being examined, which may be located outside the European Economic Area. The receiving mail provider may receive the address being queried and process this information according to its own role and applicable law. External responses may be incomplete or misleading, which explains why a verdict may be inconclusive.

DNS queries and other public data about the domain may also be consulted. Pseudonymised data remains personal data within the meaning of the GDPR and is protected as such.

6. Recipients and providers

The parties involved are as follows:

The named list of processors may be provided on request to customers who demonstrate a need for it, under a confidentiality undertaking. Authorised employees, contributors or providers access information only to the extent necessary for their tasks.

7. Security

The measures in place include encryption of stored addresses (AES-256-GCM), HMAC-SHA-256 blind indexes, password hashing (bcrypt), API key hashing, key restrictions, two-factor authentication (TOTP), rate limiting, a firewall, protected administration access, technical logs and HTTPS connections. No measure reduces IT risk to zero. The Security policy and the DPA supplement this information.

8. Retention

The periods are summarised below; the Data retention policy sets out the starting points, deletions and legal exceptions.

CategoryPeriod
Imported address filesErased when processing closes
Detailed batch results7 days, or 30 days depending on the organisation's preference
Generated export filesUp to 8 days after their creation
Audit report not unlocked30 days
Batch statistics without addresses90 days
Pseudonymised technical resultsUp to 30 days
Verification history in the accountUntil deleted by the Customer or until the account is deleted
B2B Finder searches30 days
API call and email logs90 days
Sign-in logs, recognised devices and key security180 days
Audit log of account actions365 days
Other technical logsUp to 12 months
Support12 months after resolution; screenshots: 30 days
Access to third-party toolsUntil disconnection and revocation
AccountDuration of the relationship, then deletion after a 30-day grace period following the request, subject to remaining obligations
Evidence of acceptance of termsDuration of the contractual relationship, then 5 years
Accounting records10 years under the applicable regulations
Cookie consent choiceAbout 6 months
Pseudonymous identifier for full measurement12 months
Traffic statistics25 months
Prospecting contacts3 years after the last exchange, excluding any necessary objection list

The expiry of operational data does not exclude separate retention strictly necessary to comply with a legal obligation or to establish or defend a legal claim. Backups are encrypted and purged within 30 days. A copy exported and kept by the Customer is the Customer's own responsibility.

9. Cookies

YesWeCheck uses its own audience measurement tool, Umami, hosted by OVHcloud, for limited anonymous measurement and, with consent, full measurement. The Cookie policy details the trackers, their lifetimes, the choices available and how to withdraw consent. Strictly necessary trackers are used without consent where they meet the legal conditions; others are activated only after a valid choice.

10. Rights of individuals

Subject to the legal conditions, you may request access, rectification, erasure, restriction or portability, or object to processing, and withdraw your consent where it is the legal basis. You may set instructions regarding what happens to your data after your death under French law. Write to [email protected] describing your request; proportionate proof of identity may be required in the event of reasonable doubt. We normally reply within one month, subject to justified statutory extensions.

Where we act as processor for a customer, a request concerning that customer's file should normally be sent to the controller; we provide it with the assistance set out in the DPA. You may lodge a complaint with the CNIL, the French data protection authority (https://www.cnil.fr/). See also the GDPR page.

11. Children and misuse

YesWeCheck is not designed as a tool intended for children. Customers must not use the Service for unlawful profiling, prohibited prospecting or processing that infringes a person's rights. The lawfulness of using an address never follows from a validation verdict.

12. Changes to this policy

This policy may change to reflect changes in regulations, processors or operations. A significant change affecting mandatory information or individuals' choices will be communicated appropriately. Each version is identified and archived.