Politique de confidentialité
Privacy Policy and IAB Europe TCF Attestation
BCOVERY SAS – Last updated: 27 April 2026
IAB Europe Transparency & Consent Framework attestation
BCOVERY SAS participates in the IAB Europe Transparency & Consent Framework and complies with its Specifications and Policies. BCOVERY SAS uses IAB Europe-assigned Vendor ID 1069.
This section is the public attestation of compliance published by BCOVERY SAS for its participation in the IAB Europe Transparency & Consent Framework (“TCF”).
1. Who we are
This website and the services described in this notice are operated by BCOVERY SAS, a French simplified joint-stock company registered with the Paris Trade and Companies Register under number 853 472 603, with registered office at 40 rue Pascal, 75013 Paris, France. Intracommunity VAT number: FR01853472603.
For privacy and TCF questions, you can contact us at support@bcovery.com or raphael.nataf@bcovery.com.
2. Scope of this notice
This notice covers BCOVERY’s corporate website/contact handling and BCOVERY’s current activities as a digital advertising trading desk and TCF Vendor. In its current TCF operation, BCOVERY does not deploy publisher-side JavaScript tags, SDKs or other client-side technologies on publisher websites or apps to collect information directly from end-user devices.
BCOVERY may receive and process pseudonymous advertising identifiers, hashed identifiers, IP address-derived information, device identifiers, campaign data, TC Strings and other privacy signals from SSPs, DSPs, data providers, identity partners and other advertising partners. Where those data relate to an identified or identifiable individual, BCOVERY treats them as personal data.
3. TCF purposes and legal bases
BCOVERY declares and uses TCF Purposes only to the extent they correspond to its actual processing operations and only when the relevant TC String, Publisher restrictions and contractual permissions support the processing.
| TCF item | How BCOVERY uses it | Legal basis declared |
|---|---|---|
| Purpose 1 – Store and/or access information on a device | Not used for BCOVERY’s current TCF vendor activity. BCOVERY does not place or read its own cookies, localStorage, IndexedDB, SDK identifiers or similar storage on publisher users’ devices. | Not used |
| Purpose 2 – Use limited data to select advertising | Use limited contextual or technical advertising data received from partners to determine ad eligibility, delivery constraints, frequency and campaign suitability without relying on a personalised advertising profile. | Consent or legitimate interest; default legitimate interest where permitted by the TC String and Publisher restrictions. |
| Purpose 3 – Create profiles for personalised advertising | Create or update pseudonymous audience pools, segments, retargeting criteria or other advertising profiles from partner-provided identifiers or audience records. | Consent only. |
| Purpose 4 – Use profiles to select personalised advertising | Activate consented audience segments or user-level campaign eligibility rules to select personalised advertising. | Consent only. |
| Purpose 5 – Create profiles to personalise content | Not used. | Not used |
| Purpose 6 – Use profiles to select personalised content | Not used. | Not used |
| Purpose 7 – Measure advertising performance | Measure and report advertising performance, including impressions, clicks, conversions, reach/frequency, attribution and campaign effectiveness. | Consent or legitimate interest; default legitimate interest where permitted. |
| Purpose 8 – Measure content performance | Not used for non-advertising content performance. | Not used |
| Purpose 9 – Understand audiences through statistics or combinations of data from different sources | Not used unless expressly activated in a future documented processing flow. | Not used |
| Purpose 10 – Develop and improve services | Use limited operational and campaign data to improve BCOVERY services, reporting, quality controls, partner integrations and security processes. BCOVERY does not use this purpose to build or improve personalised advertising profiles. | Consent or legitimate interest; default legitimate interest where permitted. |
| Purpose 11 – Use limited data to select content | Not used. | Not used |
Special Purposes
| Special Purpose | Use | Legal basis declared |
|---|---|---|
| Special Purpose 1 – Ensure security, prevent and detect fraud, and fix errors | Detect invalid traffic, fraud, abuse, integration errors and security incidents; troubleshoot campaign delivery and reporting issues. | Legitimate interest |
| Special Purpose 2 – Deliver and present advertising and content | Process technical information necessary to receive/respond to advertising requests, facilitate ad delivery through partners, route users to landing pages and ensure technical compatibility. | Legitimate interest |
| Special Purpose 3 – Save and communicate privacy choices | Receive, read, store for limited audit purposes and pass TC Strings or equivalent privacy signals so BCOVERY and Vendor-partners can respect users’ choices and Publisher restrictions. | Legitimate interest |
4. Features, Special Features and categories of data
Depending on the campaign and partner workflow, BCOVERY may rely on the following TCF Features in support of the declared Purposes: matching and combining data from other data sources, linking different devices where a partner-provided identity or device graph is lawfully available, and identifying devices based on information transmitted automatically where applicable. BCOVERY does not use Special Feature 1 (precise geolocation data) or Special Feature 2 (active scanning of device characteristics) in its current TCF operation.
The categories of personal data that may be processed in the current TCF scope include IP addresses, device characteristics, device identifiers, browsing and interaction data, non-precise location data, user profiles/audience segment membership and privacy choices such as TC Strings. Probabilistic identifiers are processed only where an identity partner, DSP or other documented partner workflow supplies or generates them for BCOVERY with an appropriate legal basis and contractual controls. BCOVERY does not currently declare authentication-derived identifiers, user-provided data or precise location data for the TCF processing described here unless a future workflow is added and the GVL is updated. BCOVERY does not intentionally process special categories of personal data or data relating to criminal convictions under the TCF.
5. Device storage disclosure
BCOVERY does not currently use client-side storage or access mechanisms on publisher users’ devices for its TCF vendor activity. BCOVERY’s Vendor Device Storage & Operational Disclosure JSON is available at https://www.bcovery.com/dsd-bcovery.json.
BCOVERY’s corporate website and customer console may use strictly necessary technical cookies or similar technologies for website security, login, session management or preferences. These website/console technologies are separate from BCOVERY’s TCF vendor processing on publisher digital properties.
6. Recipients and partners
BCOVERY may share personal data, TC Strings and campaign data with advertising ecosystem partners where necessary for the purposes described above, including SSPs, DSPs, data providers, identity partners, measurement partners, clients/advertisers and technical service providers. BCOVERY verifies, contractually and operationally, that personal data is transmitted only where the recipient has an appropriate legal basis and authority to process it.
7. Retention
BCOVERY applies limited retention periods. Unless a shorter partner, legal-basis or deletion requirement applies, BCOVERY uses a maximum retention period of 90 days for user-level audience activation, personalised advertising, advertising measurement, delivery, security/fraud/error and privacy-signal operations. Limited service development and improvement records may be retained for up to 365 days where necessary, minimised and not used to build or improve personalised advertising profiles.
8. International transfers
BCOVERY does not intentionally transfer personal data to countries that do not provide an adequate level of protection for the TCF processing described in this notice. Where a future partner, processor or sub-processor involves a restricted transfer, BCOVERY will document the transfer and implement an appropriate transfer mechanism and safeguards.
9. Your choices and rights
On publisher websites and apps, your TCF choices are usually collected and communicated by the publisher’s Consent Management Platform. You can use that interface to grant or withdraw consent, object to legitimate-interest processing where available, and manage Vendor choices. BCOVERY respects TC Strings and Publisher restrictions received through the TCF.
You may also contact BCOVERY at support@bcovery.com to exercise your rights of access, rectification, erasure, restriction, objection and portability where applicable. You may lodge a complaint with the competent supervisory authority, including the CNIL in France.