Page 1 of 21 Last

Upd

ated

Apr

il 20

13

| V

ersi

on 3

.201

3

Form MGA/51/2011-13

System DocumentationName of Applicant Submitting this form Date

DD MM YY

Remote Gaming Class Platform

• PleasecompleteinBlockCapitalsandinblackinkandreturnthiscompletedformtotheMaltaGamingAuthority(the‘Authority’)

• AllDocumentsmustbecompletedinEnglish

• DocumentsprovidedinotherlanguagesmusthaveasignedEnglishtranslationattachedtheretoandcertifiedthatitisatruecopyandtranslationofanyoriginalsubmitted

• UseN/Ainresponsetoanyquestionwhichisnotapplicable

• Ifthereisnotenoughspaceonthisformforanyparticularanswerkindlyattachasheethereto.Writethesectionnumberatthetopofthesheetandyoursignature

• TheAuthorityreservestherighttorequestadditionalinformation

• IfthereareanychangesintheinformationprovidedinthisApplicationForm,itistheApplicant’sresponsibilitytoadvisetheAuthorityimmediately.Failuretodosocouldresultinsuspensionorrevocationoftherelevantlicence/authorisation

• AllAuthorityformsattachedhavetobeoriginal

• AllAgreementsattachedshouldbecertifiedtruecopies

Page 2 of 21 Last

Upd

ated

Apr

il 20

13

| V

ersi

on 3

.201

3

1 Personal Information & Business Plan

1.1 Application for a Remote Gaming Licence (Form MGA/51/2010-01)

1.2 Shareholder, Directors, CEO and Ultimate Beneficiary Owners information

1.2.1 Foreachqualifyingshareholderwith5%ormoreinterest,orDirector,CEOorUBO:

1.2.1.1 PersonalDeclarationForm(Form MGA/51/2010-02)

1.2.1.2 Copyofpassport

1.2.1.3 Originalbirthcertificate

1.2.1.4 Policeconductcertificate

1.2.1.5 Bankreference

1.2.1.6 Passportsizephoto

1.2.1.7 Statementofaffairs

1.2.1.8 Bookmakerlicenceifissuedinothercountries

1.2.2 InthecaseofUBO’stheFiduciaryAgreementbetweenthetrusteeandtheUBOisrequired

*Reference Notes

*ReferencerefersstrictlytotheDocumentNumber,PageNumberandParagraphNumber

Page3of21 Last

Upd

ated

Apr

il 20

13

| V

ersi

on 3

.201

3

1.3 Business Plan

1.3.1 TheBusinessPlanshouldinclude:

1.3.2 OverviewofBusinessandObjectivesofOperation

1.3.3 Proposedcompanystructureincludinghumanresourcestobeemployed

1.3.4 Natureofgamestobeoffered

1.3.5 Technologiestobeused

1.3.6 Overviewofapplicationsoftware

1.3.7 Threeyearforecast,including:

1.3.7.1 Marketingandsalesplan

1.3.7.2 Forecaststatementofcomprehensiveincomeandaforecaststatementoffinancialposition

1.3.7.3 Forecaststatementofcashflows

1.3.7.4 Financingplan

Reference Notes

Page4of21 Last

Upd

ated

Apr

il 20

13

| V

ersi

on 3

.201

3

2 Operations

2.1 Statutory Documentation

2.1.1 AnEEAcountryCompanyRegistrationCertificate

2.1.2 Memorandum&ArticlesofAssociation:

2.1.2.1 Thecompany'smainobjectsincludedinthememorandum&articlesofassociationshouldbetheoperationofremotegaming

2.1.2.2 Thepaid-upissuedsharecapitalstatedinthememorandum&articlesofassociationshouldbe€100,000foraClass1,Class1on4,Class2,andaClass2on4and€40,000foraClass3,Class3on4,andaClass4

2.1.3 BusinessEntityForm:

2.1.3.1 FundsManagement

2.1.3.2 NameofCommercialBankers

2.1.3.3 OperatingAccountNumbers

2.1.3.4 Players'AccountNumbers

2.1.4 Declaration from an EEA Licensed Credit Institution Declaration with respect Players' FundsAccounts:

2.1.4.1 Adeclarationbythecredit institutionholdingtheplayers' fundsaccountsstatingthat itwillnotattempttoenforceorexecute,anycharge,write-off,set-offorotherclaimagainstaclients'account

Reference Notes

Page5of21 Last

Upd

ated

Apr

il 20

13

| V

ersi

on 3

.201

3

2.1.4.2 Adeclarationbythecredit institutionholdingtheplayers' fundsaccountsstatingthat itwillnotcombinetheaccountwithanyotheraccountinrespectofanydebtowedtoitbytheLicensee

2.1.4.3 Adeclarationbythecreditinstitutionholdingtheplayers'fundsaccountsstatingthatitshallcreditanyinterestpayableonaclients'account,onlytothataccount

2.1.4.4 Anauthorisationbythecreditfinancialinstitutionbywhichaplayers'accountisheldtodiscloseanyinformationasmayberequestedbytheAuthorityinrespectofaplayers'account

2.2 Company Policies

2.2.1 InformationSecurityPolicy:

2.2.1.1 TheobjectivesoftheInformationSecurityPolicyshould includethe integrity,confidentialityandavailabilityoftheinformation

2.2.1.2 TheInformationSecurityPolicyshouldaddressthesafeguardingofdata,inlinewiththeobjectivesofthepolicy:

2.2.1.2.1 The InformationSecurityPolicy shouldcontainprovisionswith respect toportablecomputersandmedia

2.2.1.2.2 TheInformationSecurityPolicyshouldcontainprovisionsforthedisposalofmedia

2.2.1.2.3 TheInformationSecurityPolicyshouldcontainprovisionsforthedisposalofequipment

2.2.1.3 TheInformationSecurityPolicyshouldaddressthesafeguardingofapplications,inlinewiththeobjectivesofthepolicy

2.2.1.4 The InformationSecurityPolicyshouldaddress thesafeguardingofequipment, in linewith theobjectivesofthepolicy

2.2.1.5 The Information Security Policy should address the safeguarding of networks, in line with theobjectivesofthepolicy

Reference Notes

Page6of21 Last

Upd

ated

Apr

il 20

13

| V

ersi

on 3

.201

3

2.2.1.6 TheInformationSecurityPolicyshouldaddressthethreatofviruses,inlinewiththeobjectivesofthepolicy

2.2.1.7 TheInformationSecurityPolicyshouldaddressthethreatofintrusion,inlinewiththeobjectivesofthepolicy

2.2.1.8 TheInformationSecurityPolicyshouldcontainadataclassificationsystem,categorizingdataandtherespectivemeasuresaccordingtoitsimportance

2.2.2 IncidentResponsePolicy:

2.2.2.1 TheIncidentResponsePolicyshouldincludeacategorisationofincidents

2.2.2.2 TheIncidentResponsePolicyshouldcaterforanincidentresponseteamanditsresponsibilities

2.2.2.3 TheIncidentResponsePolicyshouldcoverthereportingbytheKeyOfficialthroughtherespectiveformsofanyincidentstotheAuthoritywithin24hours

2.2.3 UserManagementPolicy:

2.2.3.1 TheUserManagementPolicyshouldincludeprovisionswithrespecttoacceptableemailuse

2.2.3.2 The User Management Policy should include provisions with respect to robust passwordmanagement

2.2.3.3 TheUserManagementPolicyshouldincludeprovisionswithrespecttoemployment/termination

2.3 Company Procedures

2.3.1 HumanResourcesRoles&Responsibilities:

Reference Notes

Page7of21 Last

Upd

ated

Apr

il 20

13

| V

ersi

on 3

.201

3

2.3.1.1 TheHumanResourcesRoles&Responsibilitiesdocumentshouldcontainanorganisationalchart

2.3.1.2 The Human Resources Roles & Responsibilities document should include detailed roles andresponsibilitiesinformation:

2.3.1.2.1 The Human Resources Roles & Responsibilities document should include the role andresponsibilitiesoftheMLRO

2.3.1.2.2 The Human Resources Roles & Responsibilities document should include the role andresponsibilitiesoftheKeyOfficial

2.3.2 Systemaccessrightsshouldbegrantedonaneed-to-knowbasis:

2.3.2.1 The System Access Control document should contain a procedure detailing the assignment ofaccessrights

2.3.2.2 TheSystemAccessControldocumentshouldcontainSystemaccessrightlevelsperjobdesignation

2.3.2.3 TheSystemAccessControldocumentshouldcontainaphysicalaccessrightlevelperjobdesignation

2.3.2.4 The SystemAccessControl should document the controls in placewith respect to any remoteaccesstotheSystem

2.3.2.5 TheSystemAccessControlshouldincludeprovisionsforaccessbythirdparties

2.3.3 FinancialAccountingprocedures:

2.3.3.1 TheFinancialAccountingproceduresshouldincludeaccountingandreconciliationprocedures

2.3.3.2 TheFinancialAccountingproceduresshouldincludethecompilationofmonthlymanagementaccounts

2.3.3.3 TheFinancialAccountingproceduresshouldstatethattheLicenseeshall,within180daysfromtheendofitsfinancialyear,filewiththeAuthorityanauditedsetoffinancialstatementspreparedinaccordancewithinternationalfinancialreportingstandards

Reference Notes

Page8of21 Last

Upd

ated

Apr

il 20

13

| V

ersi

on 3

.201

3

2.3.3.4 TheFinancialAccountingproceduresshouldstatethattheLicenseeshall,withinthirtydaysfromtheendofthehalfyearlyperiod,lodgewiththeAuthorityinterimfinancialstatementspreparedinaccordancewithinternationalfinancialreportingstandards,showingtheLicenceholder’sresultsandsignedbythekeyofficial

2.3.3.5 The Financial Accounting procedures should state that the Licensee shall effect payment to theAuthorityofthetaxdueinrespectoftheprecedingmonthbynotlaterthanthetwentiethdayofthefollowingmonth

2.3.3.6 AnoriginalorcertifiedtruecopyoftheLetterofEngagementofexternalauditorsshouldbesubmitted

2.3.3.7 The Financial Accounting procedures should include the submission of a monthly reportreconcilingmonth-endbalancesofallplayers'fundsintheaccount'scurrencyandinEuro,heldincreditinstitutionsandintransit,supportedbycreditinstitutions'andpaymentserviceproviders'statements,withthemonth-endplayerliabilities,supportedbyaSystemreport

2.3.3.8 The Financial Accounting procedures should include the total gaming tax due at month end,togetherwithacomputationofsuchafigureinthecaseofaClass2,Class2on4,Class3andClass3on4operations

2.3.4 BusinessContinuityandDisasterRecovery:

2.3.4.1 The Business Continuity Plan should identify the possible disruptive events threatening thebusinesscontinuityoftheoperation

2.3.4.2 TheBusinessContinuityPlanshouldincludecontingencyplanswithrespecttoeachidentifiedthreat

2.3.4.3 The Business Continuity Plan should include the time required to resume normal operationsfollowingtheoccurrenceofeachidentifieddisruptiveevent

2.3.4.4 TheBusinessContinuityPlanshouldincludeanescalationprocedure,includingcontactpersons,tobefollowedontheeventualoccurrenceofeachidentifiedthreat

2.3.4.5 TheBusinessContinuityplanshouldincludearoutinetestingplanwithrespecttorecoveryplans

2.3.4.6 InthecaseofaClass4operation,theBusinessContinuityPlanshouldcaterforanalternatesitefromwhichtoresumetemporaryoperationsduringamajordisruption

Reference Notes

Page 9 of 21 Last

Upd

ated

Apr

il 20

13

| V

ersi

on 3

.201

3

2.3.5 BackupProcedure:

2.3.5.1 The Backup Procedure should include details of the data which will be backed-up and therespectivefrequency

2.3.5.2 TheBackupProcedureshouldincludethetypeofbackups

2.3.5.3 TheBackupProcedureshouldincludeprovisionsfortheoffsitestorageofbackups

2.3.5.4 TheBackupProcedureshouldincludeamediarestoretestingplan

2.3.6 ChangeManagementProcedure:

2.3.6.1 TheChangeManagementprocedureshouldincludeachangeapprovalprocedureforanyrequiredchangesinsoftware,hardware,andnetworkconfiguration

2.3.6.2 TheChangeManagementprocedureshouldstatethatapprovalbytheAuthoritywillbesoughtbytheKObeforechangesareimplemented

2.3.6.3 The Change Management procedure should include the utilisation of the Authority's IncidentReportandDecommissioningofEquipmentforms

2.3.6.4 The Change Management procedure should include the request to the Authority for anysealingrequired

2.3.7 FraudManagementProcedures:

2.3.7.1 KnowYourClient(KYC)Procedures:

2.3.7.1.1 TheKYCProceduresshouldstatethatplayerswhoarenotregisteredwillnotbeallowedtoplay

2.3.7.1.2 TheKYCProceduresshoulddetailtheplayerregistrationprocedure, includingwhatdatawillberequestedfromtheplayers

Reference Notes

Page 10 of 21 Last

Upd

ated

Apr

il 20

13

| V

ersi

on 3

.201

3

2.3.7.1.3 TheKYCProceduresshoulddetailhowtheSystemwillpreventminorsfromregistering

2.3.7.1.4 TheKYCprocedureshouldgivedetailsonhowduediligenceandenhancedduediligencewillbecarriedout

2.3.7.1.5 TheKYCprocedureshoulddetailhowtheemailaddressprovidedbyplayerswillbeverifiedbeforeregistrationisconsideredcomplete

2.3.7.2 AntiMoneyLaundering(AML)Procedures:

2.3.7.2.1 TheAnti-MoneyLaunderingProceduresshoulddetailthemonitoringandverificationsthatwillbecarriedoutforthepurposeofdetectingmoney-launderingactivities

2.3.7.2.2 TheAnti-MoneyLaunderingProceduresshoulddetailthereportingofsuspiciousmoney-launderingactivitiesandtherespectivereportingofsuchcasestotheAuthorityandtheFIAU

2.3.7.3 PayoutManagementProcedures:

2.3.7.3.1 ThePayoutManagementProceduresshouldstate that the identityofplayerswillbeverifiedoncumulativewithdrawalsof€2,330

2.3.7.3.2 ThePayoutManagementProceduresshouldstatethattheLicenseewillonlyremitwithdrawalstothesameaccountfromwhichthefundsoriginated

2.3.7.3.3 ThePayoutManagementProceduresshouldincludethatnocashdeposits/withdrawalswillbeeffected

2.4 System Hardware and Applications Details

2.4.1 SystemArchitecture:

2.4.1.1 TheSystemArchitecturedocumentshouldincludealistofallthehardwareinuse,therespectivespecifications,thelocationofthehardware,andanyvirtualmachinesinuse

2.4.1.2 TheSystemArchitecturedocumentshouldincludedetailsaboutthesecurityoftheSystem

Reference Notes

Page 11 of 21 Last

Upd

ated

Apr

il 20

13

| V

ersi

on 3

.201

3

2.4.2 ApplicationArchitecture:

2.4.2.1 TheApplicationArchitecturedocumentshouldlistthenameofalltheapplicationsinuse,includingthe games and the website, the version number, the company that developed the software, adescriptionofthesoftwareandtheserversonwhicheachapplicationresides

2.4.2.2 TheApplicationArchitecturedocumentshouldcontainadescriptionofhowtheapplicationsinteractwitheachother

2.4.3 NetworkInfrastructure:

2.4.3.1 The Network Infrastructure document should include a network schematic showing all thehardwareandvirtualmachinesinoperationwiththerespectiveinternalIPaddresses

2.5 Random Number Generator

2.5.1 TheRandomNumberGenerator(RNG)documentshouldstatethebrandandmodeloftheRNGandwhetheritisahardwareorsoftwareRNG

2.5.2 An original or certified true copy of a test certificate, from an independent EEA based testinglab,issued in the nameof the company applying for the license, certifying that theRNG, as anintegralpartwithinthegamingsystemiscompliantwiththerequirementoftheRemoteGamingRegulations,namelytheThirdSchedule,shouldbesubmitted.

2.6 Specification of the Gaming System

2.6.1 TheSpecificationoftheGamingSystemdocumentshouldincludethenameoftheownerofthesoftware

2.6.2 TheSpecificationoftheGamingSystemdocumentshouldincludethenameoforganisationwhichdidthetestingandtherespectivetestscarriedout

2.6.3 TheSpecificationoftheGamingSystemshoulddetailtheprocesses,rulesandparametersofthegames:

Reference Notes

Page 12 of 21 Last

Upd

ated

Apr

il 20

13

| V

ersi

on 3

.201

3

2.6.3.1 The Specification of the Gaming System document should detail how the Gaming System willprovidetheplayerwiththefunctionalityrequiredbyPartIXoftheRemoteGamingRegulations

2.6.3.2 Gamedetailsshouldincludethenameofthegameandtherespectiveversionnumber

2.6.3.3 Gamedetailsshouldincludethenameofthecompanythatdevelopedthegame,andtherespectiveSoftwareLicensingAgreementincaseitwasnotdevelopedin-house

2.6.3.4 Gamedetailsshouldincludeadescriptionofthegame

2.6.3.5 Gamedetails should includegeneral screenshotsandscreenshots showingmonetaryamountsquotedwiththecurrencysymbol

2.6.3.6 Gamedetailsshouldincludeadescriptionofanybonusgames,andtherespectivescreenshots

2.6.3.7 Gamedetailsshouldincludealist,pictureanddescriptionofallbuttonsavailable

2.6.3.8 Gamedetailsshouldincludealist,pictureanddescriptionofallgamesymbols

2.6.3.9 Gamedetailsshouldincludetheprobabilityandpayoutofeachwinningcombination

2.6.3.10 Gamedetailsshouldincludetheoverallreturntoplayerrate,anditscomputation

2.6.3.11 Inthecaseofjackpots,gamedetailsshouldincludeinformationofhowthejackpotisfunded

2.6.3.12 Inthecaseofslots,thegamedetailsshouldincludethelayoutofeachreel

2.6.4 TheSpecificationoftheGamingSystemdocumentshouldprovidedetailsonGameRiskManagement:

2.6.4.1 GameRiskManagement-Class1:

Reference Notes

Page13of21 Last

Upd

ated

Apr

il 20

13

| V

ersi

on 3

.201

3

2.6.4.1.1 Detailsonriskmanagementshouldbeprovided

2.6.4.1.2 Detailsonjackpotmanagementshouldbeprovided

2.6.4.2 GameRiskManagement-Class2:

2.6.4.2.1 Informationonmarket/eventmanagementshouldbeprovided

2.6.4.2.2 Detailsonoddscompilationwithrespecttoriskmanagementshouldbeprovided

2.6.4.2.3 Detailsonexposuremanagementshouldbeprovided

2.6.4.2.4 Detailsonthemanagementoflivebettingshouldbeprovided

2.6.4.3 GameRiskManagement-Class3:

2.6.4.3.1 Detailsonthemonitoringandpreventionofcollusionshouldbeprovided

2.6.4.3.2 Detailsonthemeasurestodetectmoneylaunderingtransactionsshouldbeprovided

2.6.4.3.3 Detailsonthemeasurestodetecttheutilisationofbots/devicesfromplayersshouldbeprovided

2.6.4.4 GameRiskManagement-Class4:

2.6.4.4.1 Detailsontheturnkeysolutionsofferingshouldbeprovided

2.6.4.4.2 DetailsonthereportingcapabilitiesoftheSystemshouldbeprovided

Reference Notes

Page14of21 Last

Upd

ated

Apr

il 20

13

| V

ersi

on 3

.201

3

2.6.4.4.3 Detailsonthemanagementofjackpotsacrossoperatorsshouldbeprovided

2.6.4.4.4 DetailsonthesegregationbetweenOperatorsshouldbeprovided

2.6.4.4.5 DetailsontheleasingofequipmenttoOperatorsshouldbeprovided

2.7 Terms and Conditions

2.7.1 TermsandConditions'GeneralInformation:

2.7.1.1 TheTermsandConditionsshouldincludeaversionnumber,dateoflastupdate,andifapplicable,avalidityperiod

2.7.1.2 TheTermsandConditionsshouldincludetheregisterednameandaddressoftheLicensee

2.7.1.3 TheTermsandConditionsshouldincludetheofficialLicencenumberanddateofissue

2.7.1.4 TheTermsandConditionsshouldstatethattheLicenseeislicensedinMaltaandregulatedbytheMaltaGamingAuthority

2.7.1.5 TheTermsandConditionsshouldstatethatitistheplayer'sresponsibilitytoknowiftheirgamingislegal

2.7.1.6 TheTermsandConditionsshouldstatethatthelawsofMaltaapply

2.7.1.7 In case of Terms and Conditions in different languages, all versions should reflect the sameprinciples

2.7.1.8 IncaseofTermsandConditionsindifferentlanguages,theprevailinglanguageincaseofinterpretationshouldbestated

Reference Notes

Page15of21 Last

Upd

ated

Apr

il 20

13

| V

ersi

on 3

.201

3

2.7.1.9 IncaseoftheprevailingTermsandConditionsarenotavailableinEnglish,afaithfultranslationinEnglishoftheprevailingversionshouldbesubmitted

2.7.1.10 TheTermsandConditionsshouldstatethatanychangestotheTermsandConditionswillbenotifiedtoplayersinadvanceandtheplayermustre-confirmacceptance,beforechangescomeintoeffect

2.7.2 TermsandConditions'provisionswithrespecttoBonusSchemeConditions:

2.7.2.1 AnybonusTermsandConditionsshouldsufficientlydetailtheconditionsofthebonusscheme

2.7.2.2 Any bonus Terms and Conditions should include a version number, date of last update, and ifapplicable,avalidityperiod

2.7.2.3 IncaseofanybonusTermsandConditionsindifferentlanguages,allversionsshouldreflectthesameprinciples

2.7.2.4 IncaseofanybonusTermsandConditionsindifferentlanguages,theprevailinglanguageincaseofinterpretationshouldbestated

2.7.2.5 IncaseofanybonusTermsandConditionstheprevailinglanguagewhichisnotavailableinEnglish,afaithfultranslationinEnglishoftheprevailingversionshouldbesubmitted

2.7.3 TermsandConditions'provisionswithrespecttoExceptionalCircumstances:

2.7.3.1 The Terms and Conditions should include conditions for cancellations, refunds, losses and/oroddsamendment

2.7.3.2 TheTermsandConditionsshouldincludethattheLicenseereservestherighttolimit/refusebets

2.7.3.3 TheTermsandConditionsshouldincludetheproceduresformiscarriedand/orabortedgames

2.7.3.4 TheTermsandConditionsshouldincludetheconditionsfortheLicenseetoapplyitsrighttoterminateeventsand/orgames

2.7.3.5 TheTermsandConditionsshouldincludeproceduresintheeventoferrorinpublishedodds,paytablesorgamingsoftware

Reference Notes

Page16of21 Last

Upd

ated

Apr

il 20

13

| V

ersi

on 3

.201

3

2.7.4 TermsandConditions'provisionswithrespecttoPlayerRegistration&DeregistrationProcess:

2.7.4.1 The Terms and Conditions should state that the Licensee prohibits player collusion and takesmeasurestoprohibituseofdevices,suchasrobots,thatdistortnormalgameplay

2.7.4.2 TheTermsandConditionsshouldstatethatplayersmustbeatleast18inordertoregisterortheapplicableageintherespectivecountry

2.7.4.3 TheTermsandConditionsshouldstatethatplayersmustgiveavalididentification,addressandcontactemailorpersonaltelephonenumber

2.7.4.4 TheTermsandConditionsshouldstatethatplayersmusthaveonlyoneaccount

2.7.4.5 TheTermsandConditionsshouldstatethatplayersmustregisterpersonally

2.7.4.6 TheTermsandConditionsshouldstatethatplayersmustmaintainaccountdetailsup-to-date

2.7.4.7 The Terms andConditions should state that it is prohibited for players to sell, transfer and/oracquireaccountsto/fromotherplayers

2.7.4.8 TheTermsandConditionsshouldstatethatitisprohibitedforplayerstotransferfundsamongstplayeraccounts

2.7.4.9 The Terms and Conditions should state a player registrationmay be refused or closed at theLicensee'ssolediscretionbutcontractualobligationsalreadymadewillbehonoured

2.7.4.10 TheTermsandConditionsshouldstatewhichpersonalinformationshouldbekept/destroyedbytheLicensee

2.7.4.11 TheTermsandConditionsshouldstatethata'KnowYourClient'procedurewillbecarriedoutwhenplayersdepositmoney

2.7.4.12 TheTermsandConditionsshouldstatethecountriesfromwhichregistrationisprohibited

2.7.5 TermsandConditions'provisionswithrespecttoDeposits:

Reference Notes

Page17of21 Last

Upd

ated

Apr

il 20

13

| V

ersi

on 3

.201

3

2.7.5.1 TheTermsandConditionsshouldstatethatplayershavetherighttoclosetheiraccount,detailingtherelativeproceduretobefollowed

2.7.5.2 TheTermsandConditionsshouldincludethemethodsavailablefordeposits

2.7.5.3 TheTermsandConditionsshouldstatethetimingdepositsrequiredforqualification/withdrawalforeachmethodavailable

2.7.5.4 TheTermsandConditionsshouldstateanydepositlimits

2.7.5.5 TheTermsandConditionsshouldincludetheprocessingfees,whereapplicable

2.7.6 TermsandConditions'provisionswithrespecttoWithdrawals:

2.7.6.1 The TermsandConditions should state that players shall not treat theLicensee as a financialinstitutionnorexpectinterestontheirdeposits

2.7.6.2 TheTermsandConditionsshouldincludethewithdrawalmethods,options,settlementtimeandanydelaysimposedbytheLicensee

2.7.6.3 TheTermsandConditionsshouldstatethattheidentityofaplayerwillbeverifiedoncumulativewithdrawalsof€2,330

2.7.6.4 TheTermsandConditionsshouldstatethatwithdrawalswillberemittedonlytothesameaccountfromwherethefundspaidintotheplayer'saccountoriginated

2.7.6.5 TheTermsandConditionsshouldincludeanywithdrawalprocessingfees,whereapplicable

2.7.6.6 The Terms and Conditions should state any restrictions on withdrawal of funds not used forwagering/betting

2.7.7 TermsandConditions'provisionswithrespecttoInactive/DormantandClosedAccounts:

2.7.7.1 The Terms andConditions should state that if no transaction has been recorded on a player'saccountforthirtymonths,theLicenseeshallremitthebalanceinthataccounttotheplayerandtotheAuthorityiftheplayercannotbecontactedsatisfactorily

Reference Notes

Page18of21 Last

Upd

ated

Apr

il 20

13

| V

ersi

on 3

.201

3

2.7.7.2 TheTermsandConditionsshouldincludeanyfeesapplicablewithrespecttoinactive/dormantaccounts

2.7.8 TermsandConditions'provisionswithrespecttoPlayerSelfProtectionMechanisms:

2.7.8.1 TheTermsandConditionsshouldexplaintheplayerselfprotectionmechanismsstipulatedbytheRegulations,namelytherighttosetfinanciallimitsonwagersandlosses,righttosetlimitsonsessiontime,rightofselfexclusionforadefiniteorindefiniteperiodoftimeandacooldownperiodofsevendaysafterthelicenseehasreceivedthenotice

2.7.9 TermsandConditions'PrivacyPolicy:

2.7.9.1 ThePrivacyPolicyshouldstatethepurposeofthecollectionofpersonaldata

2.7.9.2 ThePrivacyPolicyshouldstatewhowithintheorganisationshallhaveaccesstopersonaldata

2.7.9.3 ThePrivacyPolicyshouldstatethatthesupplyofpersonaldatatothirdpartiesisonanopt-inbasis

2.7.9.4 The Privacy Policy should state the circumstances inwhich the Licensee has the obligation toforwardinformationtotherelevantAuthorities

2.7.10 TermsandConditions'provisionswithrespecttoAnti-MoneyLaundering:

2.7.10.1 TheTermsandConditionsshouldstatethatitisunlawfultodepositmoneyfromill-gottenmeans

2.7.10.2 TheTermsandConditionsshouldstatethatalltransactionsarecheckedtopreventmoneylaundering

2.7.10.3 The Terms and Conditions should state that suspicious transactions will be reported to therelevantAuthorities

2.7.11 TermsandConditions'provisionswithrespecttoPlayerComplaints:

Reference Notes

2.7.7.3 The Terms and Conditions should include details and procedures for recovering funds held indormant,closed,blockedandexcludedaccounts

Page 19 of 21 Last

Upd

ated

Apr

il 20

13

| V

ersi

on 3

.201

3

Reference Notes

2.7.11 TermsandConditionsprovisionswithrespecttoPlayerComplaints:

2.7.11.1 The Terms and Conditions should include a clear outline on how the Licensee handles playersupport/complaints

2.7.11.2 TheTermsandConditionsshould includethemethodsavailablefor lodgingcomplaintsandtherespectivecontactdetails,whichmustbeinternationallyaccessible

2.7.11.3 TheTermsandConditionsshouldstatethatplayershavetherighttobringdisputestotheAuthority,atcomplaints@mga.org.mt,ifdeemedunresolved

2.7.12 TermsandConditions'provisionswithrespecttochatrooms:

2.7.12.1 TheTermsandConditionsshouldstatethepurposeofthechatroomsandtheapplicablecodeofethics

2.7.12.2 TheTermsandConditionsshouldstatetheresponsibility/liabilityfortheuseofthechatrooms

2.7.12.3 TheTermsandConditionsshouldstatethelimitationsontheuseofthechatrooms

2.7.12.4 TheTermsandConditionsshouldstatethecontrolsthatareinplace

2.7.12.5 TheTermsandConditionsshouldstatethatchatroomsaremoderated

2.7.12.6 TheTermsandConditionsshouldstatethatallconversationsareloggedandrecorded

2.7.12.7 TheTermsandConditionsshouldstatethatcollusionthroughtheuseofthechatroomsorseparatechatisprohibited

2.7.12.8 TheTermsandConditionsshouldstate that theLicenseereservestheright toremovethechatroomsifabused

2.7.12.9 TheTermsandConditionsshouldstatethatanysuspiciouschatswillbereportedtotheAuthority

Page 20 of 21 Last

Upd

ated

Apr

il 20

13

| V

ersi

on 3

.201

3

2.8 Contracts with Business Partners

2.8.1 AgreementswithPaymentSystems/Gateways:

2.8.1.1 AgreementswithEEAlicensedPaymentServiceProviders

2.8.2 AgreementswithSoftwareProviders:

2.8.2.1 AgreementswithSoftwareProvidersintheeventthatthegamingsoftwareisnotdevelopedin-house

2.8.3 OtherContractswithParent/Group/AffiliateCompanies:

2.8.3.1 Anyservices,outsourcingofoperations, leasedequipment,etc., shouldbeaccompaniedby therespective Agreements. All access rights emanating from the Regulations and granted to theAuthorityshouldbeincludedintheseAgreements

2.8.3.2 Agreementwithco-locationfacilityshouldincludeaconfidentialityclausewithrespecttoplayers'data

I,(NameandSurname)___________________________________________________,representing(company)__________________________________________astheapplicant, herebycertifythattheinformationaboveiscorrectandthatthedocumentsmarkedaresubmittedwiththisform.

_______________________________________________

SignatureofRepresentative

Title: SystemDocumentation

Author: StephenSaliba,SystemsandFinancialAuditor,MaltaGamingAuthority

Derivation: SystemDocumentationChecklist

Reference Notes

Page 21 of 21 Last

Upd

ated

Apr

il 20

13

| V

ersi

on 3

.201

3

Version2.2011(uploadedonlineOctober2011)Version3.2013(uploadedonlineApril2013)

Status: FinalVersion

SummaryofChanges: 2011June–Version1.20112011September–Version2.2011Draft12011October–Version2.2011Draft22011November–Version2.2011

Circulation: UploadedontotheMGAWebsite

RequiredAction: N/A

FileName/Location: SystemDocumentationMGA-51-2011-13

Approval:

Document Control information

________________________________Joseph Cuschieri, Executive ChairmanMalta Gaming Authority

Origination Date: N/A

Reviser(s): Karl Brincat Peplow, Adrian Cortis, Rebekah Duca, Jason Farrugia.

Date of last revision: 9th April 2013

Version: Version 1.2011 (uploaded online June 2011)