BeOp is now Collective Audience!
Collective Audience is a solution for creating and disseminating editorial or advertising content, also called components. This content is created via a dedicated platform, the DASHBOARD, while a WIDGET allows the content to be interacted with directly on the publishers’ websites.
Parties involved:
The publishers and their advertising agencies use Collective Audience for the purpose of creating content to collect opinions from their audiences, carry out surveys, organize contests - subject to rules or otherwise - or test users’ knowledge by creating quizzes. Collective Audience also allows them to monetize their space by activating the advertising tool, which allows them to disseminate content from partner advertisers. Collective Audience is committed to prioritizing editorial components; in addition, sponsored content will only use free space not utilized by partner media.
Advertisers and their agencies use Collective Audience to create sponsored content designed to collect information, conduct surveys, and measure user engagement and interaction with the advertised brand.
Users who browse the publishers’ websites utilize the Collective Audience WIDGET to interact with the component’s creator.
Finally, Collective Audience possesses its own advertising activity that receives orders from agencies and/or advertisers in order to create, schedule and disseminate sponsored campaigns on behalf of brands.
Data:
Collective Audience may be compelled to collect data on how Collective Audience WIDGETS are used by the user. Collective Audience distinguishes between two types of data:
1 - Service data:
Necessary for the proper functioning of our online services, these data are collected through proprietary Collective Audience tracking, and used by Collective Audience for Collective Audience. They represent how the WIDGET is used by the users, and, among other things, enable us to:
- Effectively collect information on user participation with components
- Create statistics in order to determine the results of diverse surveys
- Inform the user or the component's creator of a component's number of participants.
To further ensure the proper functioning of our online services, a cookie is installed on the publisher's domain ONLY to identify users and ensure they can browse properly using a Collective Audience widget. Among other things, this cookie enables us to:
- Effectively collect information on user participation with components
- Enable users to continue using a component at the point where they left it during a previous browsing session
- Keeps users from seeing the same sponsored component again if they have already provided responses
Without the users’ consent, Collective Audience will not use the service data collected to create user profiles in order to display targeted or personalized advertising.
2 - Additional data:
When users participate via Collective Audience forms, or when engaging or registering with our partners, their personal data are collected and stored by Collective Audience on European servers, and can be exported by the component's owner for a period of 13 months.
Collective Audience's partners may use third-party tracking services, which may subsequently be used to display personalized advertising to users via tools other than those of Collective Audience. These third parties are only authorized to use the collected information to ensure their services function properly.
Collective Audience acts in the capacity of technical service provider for these partners, and thus agrees to provide them with all the tools necessary to properly acquire user consent via the Collective Audience DASHBOARD. The component’s creator must decide whether it is necessary to include a means of acquiring consent to use personal data.
Finally, Collective Audience joined the IAB's TCF in September 2019 in order to acquire user consent for the following purposes:
- Storing and accessing a third-party cookie (see below)
- Personalizing the advertising/component based on a user's utilization of Collective Audience
- Targeted dissemination of the advertising/component based on the information collected via a Collective Audience third-party cookie
- Measuring the effectiveness of the advertising/component on users
- Using the geographic location of users to provide them with content adapted to their location
If users do not consent to the use of the third-party cookie, Collective Audience agrees not to fulfill the purposes mentioned above in order to disseminate a component that requests it. Advertising delivered back via the user’s WIDGET will be selected randomly from content not requiring these selective and restrictive criteria.
Cookie definition
A cookie is a small file stored on a user's hard drive in a transparent manner when browsing certain websites, and which stores information for subsequent visits. A technology present on website A and website B will be incapable of reading information from the other website.
A first-party cookie is used to store information for a single domain, that of the website the user is visiting when the cookie is installed, or for a third-party domain if the user consents.
A third-party cookie is used to store information for the entire Web and is specific to the technology that installed it at a given point in time. If this technology is present on website A and website B, it will be capable of reading information from both websites.
On the publisher domain
| Cookie name | Domain | Function | Duration |
|---|---|---|---|
beopid | Publisher domain | Preserve session information across reloads and identify users as unique | 1 year |
On the advertiser domain
| Cookie name | Domain | Function | Duration |
|---|---|---|---|
beopSessionId | Advertiser domain | Count sessions correctly | Session |
beopConversionContext | Advertiser domain | Preserve conversion context information (campaign ID, referrer page…) across reloads | Session |
On Collective Audience domain, as third-party
| Cookie name | Domain | Function | Duration |
|---|---|---|---|
beopConversionRedirect | Collective Audience | Pass conversion context information (campaign ID, referrer page…) to the advertiser website | Session |
caud_sync | Collective Audienceo | Store a pseudonymous identifier to synchronize the technical identifiers (buyerUids) provided by advertising partners (SSPs/DSPs) in order to ensure proper campaign delivery and performance measurement via OpenRTB. | 7 days |
On Collective Audience domain, as first party
| Cookie name | Domain | Function | Duration |
|---|---|---|---|
token | Collective Audience | Identify user | 15 minutes |
as | Collective Audience | Keep the user logged as the account they wish | Session |
language | Collective Audience | Show the platform in the preferred language | 1 year |
Analytics cookies
As part of the continuous improvement of its services, Collective Audience also uses Matomo, a web analytics solution.
Matomo collects anonymised browsing data (pages visited, session duration, traffic sources, etc.) on the website and the desk.collectiveaudience.co dashboard. This data does not allow for the direct identification of visitors and is used exclusively for aggregated statistics and for improving the user experience.
Use of data:
In general, the data can be used to correct errors, improve Collective Audience products, and, subject to agreement, transmit information to partners (cf. 2 - Additional data).
Simple campaigns
As part of its campaigns without retargeting purposes, Collective Audience agrees to extract browsing data only for dissemination at that moment and for statistical purposes, and not to create user profiles. Collective Audience does its best to anonymize the browsing IP address as early as possible in the data storage chain. Among browsing data used for dissemination and statistics, we list:
- the URL of the visited web page
- the location determined by the IP address
- hardware information (telephone, PC, brand, etc.)
- browser information (Name and browser version)
- a user identifier retrieved by a cookie that we may have installed for the user
These different data enable us to make sure the various services are functioning correctly in order to:
- Keep from presenting the same component to the same person for voting
- Semantically target the context in which the component is disseminated
- Geographically target the context in which the component is disseminated
- Analyze the context in which the component is currently, or has been, disseminated
Targeted campaigns
As part of its retargeting campaigns, and with the user's consent, Collective Audience collects the following information in addition to that which it collects for simple campaigns:
- A cross-site user identifier
- A history of the user's visibility with the Collective Audience components delivered to the user
- A history of the user's interactions with the Collective Audience components delivered to the user
These different data enable Collective Audience to:
- Perform cookie syncing with third-party data providers
- Accurately target users and their areas of interest for advertising selection
Users:
While browsing, users will be invited to consult this policy outlining the proper functioning of the Collective Audience services and how we use their data (cf. 1 - Service data).
For any additional data, the Collective Audience WIDGET or the publisher's Consent Management Platform (or CMP) displaying the component will request consent on a case-by-case basis according to the component parameters established by the partners.
Rights to the data:
Users can ask to view their participation history for Collective Audience components at any time. A button is available in the user account settings on the Collective Audience platform, or directly in the WIDGET on the publishers’ web pages. Accessing and viewing the history requires users to register for a Collective Audience account with a valid email address.
Right to be forgotten:
Users can ask to be forgotten/erased from the Collective Audience data storage systems at any time. A button is available in the user account settings on the Collective Audience platform, or directly in the WIDGET on the publishers’ web pages. Users are processed and definitively forgotten, which will make it impossible to use the data stored with Collective Audience. In order to conserve statistics, user votes will not be erased, but rather anonymized. It will be impossible to associate a vote with a user. Collective Audience agrees to send an email to any partner that has collected information on the user requesting to be forgotten. This email will indicate the user's desire to be forgotten and ask the partner to anonymize the user as well.
In addition, the button below enables the user to delete any cookie stored for the domain beop.io
If you've reset Collective Audience cookies, you may have to choose again the settings below:
Data storage period:
The cookie stored in the user's browser by Collective Audience to ensure that the website functions properly will expire after 13 months. Collective Audience has adopted a continuous improvement approach so that all its services that store and use data are assigned a date on which this data expires or is forgotten.
The cookie stored for retargeting purposes expires after 24 hours and is refreshed at each visit.
Legal Notice:
Collective Audience reserves the right to disclose the information collected in the event of an investigation aimed at preserving public order, human rights, and people's safety.
Collective Audience may, if bought out or sold, transfer the information collected to another technical specialist, and, if necessary, notify its users of the steps to follow so they can continue benefiting from the guarantees provided under this policy.
Collective Audience reserves the right to change this policy in order to comply with legal requirements, or in the interest of transparency in the event we change the way in which we collect or use the data.
IAB Europe Transparency & Consent Framework (TCF) integration details
Thanks to the IAB TCF v2.2, Collective Audience is collecting and respecting user choices for these purposes:
| Purpose | Description | How Collective Audience uses it |
|---|---|---|
| Store and/or access information on a device (Purpose 1) | Cookies, device identifiers, or other information can be stored or accessed on your device | Collective Audience uses cookies called caud_sync to store a pseudonymous mapping of partner buyerUids and beopid to save an historical state of the delivery for a given user on a given domain. These are required to support OpenRTB delivery, frequency capping, and campaign measurement. They are only written and read when the user has given valid consent. |
| Select basic ads (Purpose 2) | Ads can be shown to the user based on the content being viewed, approximate location, or device type | When Collective Audience delivers a sponsored format that requires frequency capping, device-type targeting (computer, mobile…), or approximate IP-based geolocation, consent is required if cookies are involved. Without consent, Collective Audience continues to serve purely contextual ads without storing any identifier. |
| Measure ads performance (Purpose 7) | The performance and effectiveness of ads that users see or interact with can be measured | Collective Audience is a survey and opinion company. It needs to measure performance of sponsored campaigns for invoicing and reporting. When identifiers are used (cookies), consent is required. For aggregated server-side metrics without identifiers, Collective Audience may rely on legitimate interest. |
| Measure contents performance (Purpose 8) | The performance and effectiveness of editorial or sponsored content can be measured | As all our formats are considered "content", Collective Audience measures their performance for its customers. Consent is required when cookies or identifiers are involved. Aggregated contextual analytics may rely on legitimate interest. |
| Apply market research to generate audience insights (Purpose 9) | Market research can be used to learn more about the audiences who view and interact with ads and content | Collective Audience may aggregate responses from polls and surveys to generate audience insights. No individual profiles are created. This processing may rely on legitimate interest for aggregated insights, and requires consent when cookies or identifiers are involved. |
| Develop and improve products (Purpose 10) | Data can be used to improve existing systems and develop new products | Collective Audience runs A/B tests and feature experiments, tracking only aggregated metrics. No personal data is used in these processes. This processing is based on legitimate interest. |
| Use limited data to select content (Purpose 11) | Content can be shown to the user based on contextual and technical data, without creating a profile | When Collective Audience delivers editorial or sponsored content using contextual signals (URL, keywords, device type), this can be done under legitimate interest. If cookies are used, valid consent is required. |
| Ensure security, prevent fraud, and debug (Special Purpose 1) | Data can be used to monitor for and prevent fraudulent activity, and ensure systems and processes work properly and securely | As a survey company, Collective Audience must ensure interactions come from real humans and not bots, to guarantee data quality. This purpose does not require consent. |
| Technically deliver ads or content (Special Purpose 2) | Device can receive and send information that allows users to see and interact with ads and content | The Collective Audience script queries its servers to decide whether to show editorial or sponsored content, based on publisher settings. This technical delivery does not require consent. |
Purposes declared but not currently used directly by Collective Audience
For transparency, Collective Audience declares these purposes because synchronized identifiers (buyerUids) may be used downstream by SSP/DSP partners, even if Collective Audience does not itself perform such processing:
| Purpose | Description | Why Collective Audience does not use it directly |
|---|---|---|
| Create a personalised ads profile (Purpose 3) | A profile can be built about the user and his interests to show personalised ads | Collective Audience never creates or stores any personalised ad profile. However, identifiers shared with SSP/DSP partners may be used by them, conditional on user consent. |
| Select personalised ads (Purpose 4) | Personalised ads can be shown based on a user profile | As no profiles are created or stored by Collective Audience, we cannot directly select personalised ads. Downstream partners may do so if consent is granted. |
| Create a personalised content profile (Purpose 5) | A profile can be built to show personalised content | Collective Audience does not build or store personalised content profiles. Downstream partners may use identifiers for this purpose, conditional on consent. |
| Select personalised content (Purpose 6) | Personalised content can be delivered based on a profile | Collective Audience itself does not personalise content based on profiles. In the future, new features may allow limited personalisation (e.g. retargeting users who answered “A” to a poll with follow-up content), in which case this purpose will apply only with explicit user consent. |
Features declared by Collective Audience
| Feature | Description | Why Collective Audience needs it |
|---|---|---|
| Receive and use automatically-sent device characteristics for identification (Feature 3) | Device can be distinguished from others based on information it automatically sends, such as IP address or browser type | Collective Audience hashes IP addresses as soon as they are received (non-reversible). This hash may be used for anti-fraud. Browser type is used to manage compatibility of content delivery. |
Features not used:
- Match and combine offline data sources
- Link different devices
- Use precise geolocation data
- Actively scan device characteristics for identification
Legitimate Interest Justification
| Purpose | Description | Legitimate interest defense for Collective Audience |
|---|---|---|
| Measure ads performance (P7) | The performance and effectiveness of ads users see or interact with can be measured | Collective Audience is a survey and opinion company. It has a legitimate interest in measuring the effectiveness of sponsored campaigns to invoice and report to its customers. These measures are never associated with individuals but processed in aggregate form. |
| Measure content performance (P8) | The performance and effectiveness of editorial or sponsored content can be measured | In Collective Audience’s approach, everything is “content” (editorial or sponsored). It is therefore a legitimate interest to measure the effectiveness of this content for customers. Measurements are aggregated and never linked to individual users. |
| Apply market research to generate audience insights (P9) | Poll and survey responses can be aggregated to generate audience insights | Collective Audience aggregates survey results to produce audience indicators. No individual profiling is performed. The legitimate interest relies on providing analytical value to customers without disproportionate impact on user privacy. |
| Develop and improve products (P10) | Data can be used to improve existing systems and develop new products | As a technology company, Collective Audience has a legitimate interest in running A/B tests and experiments to improve its services. These tests rely only on aggregated and anonymised metrics, never on individual user data. |
| Use limited data to select content (P11) | Content can be selected based on contextual or technical signals, without creating a profile | Collective Audience may deliver editorial or sponsored content using only contextual data (URL, device type, keywords). This limited and non-intrusive processing relies on the legitimate interest of providing relevant services to publishers and users, without harming privacy. |
Standard Contractual Clauses
Collective Audience uses the following third-party services to host their own services. Here are their Standard Contractual Clauses that protect your data in the EU:
- Google (PDF Document)
- Amazon Web Services (PDF Document, see annex 2)
- MongoDB (PDF Document, see annex 1)
Contact us:
Collective Audience is always mindful of any questions you may have, such as those concerning your personal data, and we urge you to contact us by email at the following address: [email protected]
You can also send us a letter at the following address:
Collective Audience - The Odyssey 33 rue La Fayette 75009 Paris - France
