title: Tobique First Nation — Technical compliance: What must the platform meet? | advennt.io canonical: https://advennt.io/jurisdictions/tobique-first-nation/technical/ [Jurisdictions](https://advennt.io/jurisdictions/) [Tobique First Nation](https://advennt.io/jurisdictions/tobique-first-nation/) Technical compliance Tobique First Nation · Question 08 of 11 # Technical compliance: What must the platform meet? Mixed · Uncertain · Not reviewed · 1 post-review update · Not reviewed · [Back to full Tobique First Nation report →](https://advennt.io/jurisdictions/tobique-first-nation/) Key section parameters | Jurisdiction | Tobique First Nation (CA-TFN) | |---|---| | Regulator | Recorded in register | | Favourability | Mixed | | Confidence | Uncertain | | Review status | Not reviewed · 1 post-review update · Not reviewed | | Last collected | 18 Oct 2026 | Summary answer Technical compliance is now framed by regulator-published material but remains thin at specification level. The General Code of Practice addresses system and data security, business continuity and game integrity, and the Act controls URL scope and payment-processing arrangements. Three previously op… Not reviewed Information added after the 4 Sep 2026 expert review — published for currency and labelled not reviewed. 5 Oct 2026 Not reviewed Licensees are reported to be required to geo-block a defined list of restricted markets, including the United Kingdom, the United States, Israel, Ontario, New Brunswick, and FATF-sanctioned countries, a low-confidence, fragile-sourced finding not independently confirmed against TGC's primary text. RNG certification, approved testing laboratories, and a technical standards body have not yet been assessed against any published TGC technical specification, meaning the jurisdiction's technical-compliance infrastructure cannot presently be verified as either GLI-equivalent or bespoke. Reported app-store and advertising-platform restrictions on Tobique-licensed products appear to derive from third-party platform policy rather than a TGC-specific technical instrument. Taken together, the technical-compliance picture for CA-TFN is one of asserted access controls without a corresponding, verifiable certification regime, and operators should treat RNG and platform-technical standards as unresolved diligence items pending a located TGC technical specification. ## Full section analysis Technical compliance is now framed by regulator-published material but remains thin at specification level. The General Code of Practice addresses system and data security, business continuity and game integrity, and the Act controls URL scope and payment-processing arrangements. Three previously operative technical findings have been withdrawn as unsubstantiated: a mandatory jurisdiction-wide geolocation requirement, a 'targeted' IP-blocking posture and a 'permissive' VPN-enforcement posture. None of these was traceable to a TGC instrument, and a licence-specific condition — if one exists — must be evidenced from the licence itself rather than inferred from advisory marketing. No approved testing-laboratory list, RNG certification specification, game-approval procedure or technical standards body has been located, so operators should assume that testing and certification expectations will be set at application stage by TGC or the applicable Direct Licensee and should obtain them in writing.