Multi-brand operators frequently run brands under different licenses. A casino group might hold an MGA license for one brand and a Curacao license for another. A forex broker family might have a CySEC-regulated brand alongside an offshore FSC-regulated brand. Each license comes with specific requirements about affiliate disclosures, marketing approvals, and data handling.
Sharing affiliate data across brands licensed in different jurisdictions can create regulatory exposure. If Brand A is MGA-licensed and Brand B is Curacao-licensed, affiliate marketing materials approved for Brand B may violate MGA advertising standards. A shared affiliate pool without brand-level compliance controls is a liability.
Compliance Boundaries by Layer
Layer
Brand-Level Requirement
Portfolio-Level Requirement
Affiliate agreements
Brand-specific T&Cs reflecting the correct license and jurisdiction
Portfolio-level brand guidelines that all brands must follow
KYC and verification
Some jurisdictions require affiliate KYC; scope depends on license
Shared KYC results can reduce duplicate verification if data sharing is permitted
Data handling
GDPR, LGPD, or other local data laws may differ per brand market
Data processing agreements must specify which entities process affiliate data
Geo-restrictions
Brand-specific blocked markets based on license conditions
Portfolio-level geo-blocking rules that override brand-level permissions
Affiliate Agreement Architecture
The cleanest approach is a two-layer agreement structure. A master affiliate agreement covers portfolio-wide rules: payment terms, anti-fraud obligations, intellectual property, dispute resolution, and termination rights. Brand-specific schedules attach to the master agreement and define the commission structure, marketing guidelines, and compliance requirements for each brand.
Brand schedule A: commission structure, marketing rules, license-specific disclosures for Brand A
Brand schedule B: commission structure, marketing rules, license-specific disclosures for Brand B
Affiliates sign the master once and accept brand schedules as they get approved for each brand
Do not use a single affiliate agreement for all brands unless every brand operates under the same license in the same jurisdiction. License-specific clauses -- especially around responsible gambling disclosures, financial promotions rules, and marketing approval processes -- must be brand-specific.
Data Isolation in Practice
When brands operate across jurisdictions with different data protection laws, you need to define clear data boundaries. Player data from an MGA-licensed casino cannot flow freely to a Curacao-licensed brand. Affiliate performance data may be aggregated at the portfolio level for reporting, but personally identifiable player data must stay within the correct regulatory boundary.
In Forex, this is particularly important when one brand serves EU clients under MiFID II and another serves clients outside the EU under an offshore license. IB referral data, trading volumes, and commission calculations must be processed within the correct regulatory perimeter. Cross-brand IB referrals need explicit client consent and regulatory sign-off.
Compliance isolation does not mean operational isolation. You can run a unified affiliate management platform with brand-level permission controls, separate data partitions, and role-based access. The platform handles the complexity; your team operates efficiently.
Key Takeaways
Brands under different licenses require brand-specific affiliate agreements and marketing approvals
A two-layer agreement structure (master + brand schedules) balances efficiency with compliance
Player data must respect jurisdictional boundaries -- aggregate affiliate metrics, but isolate player data per brand
Compliance isolation does not require separate platforms -- permission controls and data partitions solve this
Geo-blocking rules at portfolio level can prevent affiliates from promoting restricted brands in blocked markets