Data retention and deletion policy

How long YesWeCheck, an email address validation service, keeps each category of data, and how it is deleted. This English version is provided for convenience. The French version prevails in the event of any discrepancy. Read the French version.

1. Principle

YesWeCheck limits the retention of data to the period necessary for the purpose pursued, the provision of the Service, legal obligations and the establishment or defence of legal claims. Periods depend on the nature of the processing and, for certain results, on the Customer's settings. Exporting a file creates a copy that the Customer must manage itself.

2. Retention periods

DataStarting eventPeriod or deletion
Address file imported for batch processingClosure of processingDeleted at closure
Detailed results of batch processingEnd of processing7 days; 30 days if the organisation chooses this option
Generated export filesCreation of the fileUp to 8 days
Audit report not unlockedEnd of the audit30 days
Processing statistics, without addressesEnd of processing90 days
Pseudonymised technical results, never disclosed to another customerVerificationUp to 30 days
Verification history in the accountRecordingUntil erased by the Customer or until the account is deleted
B2B Finder searchesDate of the search30 days
API call and email sending logsDate of the event90 days
Sign-in logs, recognised devices and key securityDate of the event180 days
Audit log of account actionsDate of the action365 days
Other technical logs and tablesDate of the eventUp to 12 months
Support tickets and messagesResolution of the request12 months
Support screenshotsReceipt of the screenshot30 days
Access to third-party toolsDisconnectionDeletion of authorisations and revocation of access
AI assistant tokensIssue or revocationAccess token 1 hour, renewable for 30 days; authorisation until revoked
Account dataDeletion requestDeleted after a 30-day grace period, during which the request can be cancelled, subject to legal obligations
Evidence of acceptance of termsAcceptanceDuration of the contractual relationship, then 5 years
Accounting documentsRelevant date for statutory retention10 years under the applicable rules
Record of cookie choiceRecordingAbout 6 months (179 days)
Full audience measurement identifierIssue12 months
Audience statisticsCollection25 months
YesWeCheck prospecting contactsLast relevant exchange3 years; objection list kept separately where necessary

3. Deletion on request and end of contract

The Customer can use the available features to delete certain history, files, keys, access or integrations. It can also delete its account from the application: deletion takes place after a 30-day grace period. Transaction data and records required for accounting, fraud prevention or the establishment or defence of legal claims may be kept separately, with restricted access, and are then anonymised as far as possible.

Where YesWeCheck acts as processor, the Customer has, under the DPA, the legal choice between return and erasure at the end of the service, subject to retention required by law.

4. Backups

Backups are encrypted and purged within 30 days. They are used solely for restoration and continuity of the Service. Deleted data may therefore remain in a backup for up to 30 days, without being used for any other purpose.

In the event of suspected fraud, an incident, a complaint, a legally valid request or litigation, certain strictly necessary data may be isolated and kept for the period justified by the purpose and the statutory time limits. This retention does not allow files to be reused for other purposes and is documented. Where the period depends on a dispute, it is reassessed periodically.

6. Roles and contacts

The Customer remains responsible for the retention of the copies it exports or keeps in its own tools. Data entrusted to a third-party integration activated by the Customer is subject to the terms of that integration. To request deletion or exercise a right, write to the data protection contact: [email protected]. Processing carried out as processor is governed by the DPA and the controller's instructions. See also the Privacy policy.