Compliance module customizations
This document outlines the necessary customizations that Sybo must complete before integrating and testing the compliance module within their app. It also details the specific items Sybo needs to provide for integration into the compliance module to facilitate the testing process.
Why we need customizations
The compliance module was initially developed for internal use and is therefore somewhat tied to Outfit7's specific needs. As we transition this module into a market-ready product, customization options will be incorporated. However, for the present and for testing purposes, these customizations will be handled manually.
Once Sybo provides the necessary materials and customization details, the Outfit7 engineering team will integrate them into the module. This will enable us to deliver a Sybo-branded compliance module.
Types of customizations
UI assets
The graphical assets of the UI elements displayed on the consent and age screening screens within the compliance module can be customized to align with the visual style of Sybo games. For the purpose of the test, we suggest to use the logo and general brand background assets.
| UI assets |
|---|
 |
 |
TCF consent
Disclosures
The publisher must display the general disclosures on the first and second layers of the consent screens. These disclosures are located in the upper portion of both the initial and secondary layers.
The current configuration of these disclosures is shown below, and is compared to Sybo's current consent screen setup.
| TCF initial layer disclosure | TCF secondary layer disclosure |
|---|---|
 |
 |
| Disclosures currently used in Sybo apps | |
 |
 |
The current Sybo disclosures on the compliance module consent screens can be used for the test. However, these disclosures can be modified upon Sybo's request, if necessary.
Consent collection
Publisher can choose which purposes (and legitimate interests) they will enable for consent collection. Since consent collection is focused on users giving consent for IBA advertising, the current setup allows for the collection of the following consents:
Purposes
- Purpose #1: Store and/or access information on a device
IAB Stack
- Stack #39: Personalised advertising, advertising measurement, audience research and services development
Special Purposes and Features
- Ensure security, prevent and detect fraud, and fix errors
- Deliver and present advertising and content
- Save and communicate privacy choices
| Consent collection | Legitimate interests |
|---|---|
|
 |
The IAB has standardized the text used to describe purposes; publishers can only choose which ones to enable for data collection.
Age limits
Configurable age values are used to determine if a user meets the age limit. Each country has its own age limit configuration. During the CM integration into the Sybo app, the Sybo team will need to provide age limits which will be used for the test.
The following age limit template setup requires Sybo's review and potential modifications:
| Countries | Age limit |
|---|---|
| North America | |
| US | 16 |
| European market | |
| HR,DE,HU,IE,LI,LU,NL,PL,RO,SK,CH | 16 |
| CZ,FR,GR,SI | 15 |
| AT,BG,CY,IT,LT,ES | 14 |
| BE,DK,EE,FI,IS,LV,MT,NO,PT,SE,GB | 13 |
| Other | |
| CN, KR | 14 |
| Rest of the world | 13 |
The user’s age has to be greater than the age limit defined in order for the user to pass the age limit.
IBA compliance check
The primary focus of the test will be on the functionalities related to interest-based advertising. A compliance check for "interest-based advertising" will be offered within the app, to be used wherever the game logic requires a decision on whether to allow IBA or not.
The compliance check is a rule, defined and authored by the legal team, which defines whether a specific provider can serve interest-based advertising. This check is called from within the game in order to pass correct signals to ad provider integrations, controlling the SDK to serve the ad traffic in line with the regulation limitations.
| Countries | Age limit |
|---|---|
| North America | |
| US | If a user passes the age limit hasn’t opted out in the device settings then allow interest based advertising |
| European market (TCF)x | |
| HR,DE,HU,IE,LI,LU,NL,PL,RO,SK,CH | If a user passes the age limit hasn’t opted out in the device settings gives consent #1 for the vendor then allow interest based advertising for vendor (TCF string is also made available) |
| CZ,FR,GR,SI | |
| AT,BG,CY,IT,LT,ES | |
| BE,DK,EE,FI,IS,LV,MT,NO,PT,SE,GB | |
| Other | |
| CN, KR | same as US |
| Rest of the world |
The compliance check involves straightforward logic, provided and verified by the Sybo legal team, which operates based on the following conditions:
- "Opt-out": CM considers the user’s opt-out preference.
- TCF consent: CM processes the TCF string, with the publisher deciding which purposes and stacks are available to users in the CM. Additionally, vendors specify the purposes they require for interest-based advertising, with the final filtering taking place on their end.
- Age screening response: CM includes the user’s answer to age verification.
- Consent/opt-out signals: CM takes into account consent or opt-out signals from the device or app settings, including ATT on iOS.
The Outfit7 engineering team will integrate this logic into Sybo's SDK, making it available for use in Sybo’s game during the test.