External requests, links, analytics and sitelocks: portal policies

What each portal publishes on network requests, outgoing links, third-party analytics and sitelocks, with not published marked where a portal is silent.

Published
Sources checked

Portals restrict what a game may load from the network and where it may send players. The rules differ more than any other requirement, and a build that is fine on one portal fails review on another. This page sets out what each of the eight options on this site publishes as of 2026-10-01, and says “not published” where the docs are silent. Use the Portal Readiness Checker to find absolute or external URLs in a build before you submit.

At a glance

Option External requests Outgoing links Third-party analytics Sitelock or domain check
Poki Blocked by default; exceptions by approval (policy) Through PokiSDK.openExternalLink() (requirements) Case by case; Google products cannot be approved Not published
CrazyGames Allowed; judged by time to gameplay (technical) Limited exceptions in the menu (gameplay) ByteBrew recommended; consent notice if extra personal data Allowed; domain list published (sitelock)
GameDistribution Not published as a rule; externally hosted games not accepted Not allowed (FAQ) Not allowed (guidelines) Not published
GameMonetize Not published Allowed (FAQ) Not published Not published
Y8 Not published Not allowed (FAQ) Not published Blacklist check in the SDK (protection)
itch.io Allowed over HTTPS (HTML5 docs) Not restricted on the pages read Not published Not published
YouTube Playables Only Google or YouTube APIs (privacy) Not allowed (design) Not exempt from the call ban Not published; obfuscation banned
H5 Games Ads Not published Not published Not published Not published

Poki

Poki blocks all external requests by default and asks you to bundle fonts, assets and libraries (requirements). The external resources policy names Google Fonts, externally hosted images or audio, and CDN-hosted libraries such as jsDelivr as not allowed, along with in-game chat and external account systems such as email, Google or Facebook sign-in.

Three kinds of exception can be approved: externally hosted multiplayer servers, analytics (GameAnalytics, ByteBrew or in-house, case by case; no Google products, Google Analytics included) and leaderboard services (possible exceptions). You request each one under Settings → CSP in Poki for Developers with the exact URLs and their purpose. If approved, Poki updates the game’s Content Security Policy; you must link a hosted privacy policy inside the game, then re-upload so the cache resets (getting approved).

Links are stated two ways. The hard requirements say to remove splash screens and outgoing links (hard requirements). The content standards say any button that opens an external link, such as a YouTube channel or Discord page, must call PokiSDK.openExternalLink('URL') instead of navigating directly (content standards). A game that links out at all also needs an in-game privacy policy and a hosted policy URL (platform integration).

// Poki: never navigate directly. Route every outbound button through the SDK.
discordButton.onclick = () => PokiSDK.openExternalLink('https://example.com/community');

CrazyGames

CrazyGames allows externally hosted or loaded files and evaluates them by the time it takes to reach gameplay, which must stay at 20 seconds or less (technical). A game that collects personal data beyond the SDK’s events must show new players a terms or privacy notice (user consent). External logins (Facebook, Google, email) must be disabled unless integrated as the account page describes (account integration). For deeper analytics, the requirements intro recommends ByteBrew, a third-party tool.

Cross-promotion of other games or platforms is not allowed. Exceptions, as long as none is the main call to action in the menu: community links such as Discord or a dev site that do not lead to a playable web version, Steam or Epic links on desktop only in the main menu or at the end of a demo, backlinks to CrazyGames pages, links to other games in the same series, and a privacy policy or terms. App store links are never allowed in-game (gameplay).

Sitelocks are allowed. The sitelock page gives a hostname check for crazygames.com and its subdomains, and for iframe submissions a frame-ancestors CSP that must include *.crazygames.com plus both app origins:

Content-Security-Policy: frame-ancestors 'self' *.crazygames.com https://app.crazygames.com capacitor://app.crazygames.com;

That line is CrazyGames’ own corrected example. Without the capacitor:// origin, iOS app players get a white screen and only a CSP violation in the console.

GameDistribution

Games submitted after 1 May 2021 may not contain outgoing links (FAQ). The developer guidelines (section 6) list social, ad, shop, survey, affiliate and sharing links as examples; your logo is welcome on the loading screen, menu or credits as long as it is not clickable, and app store references go in the catalog page’s Backlinks tab. Section 7 bans collecting or storing data from the game, any cookies or trackers not from GD (Google Analytics, Facebook Pixel and Mixpanel among the examples), and logins without a separate agreement.

The terms add that games may not link outside the platform without consent and may not include third-party ads, purchases or tracking software (Terms 2.6.7-2.6.8, developer terms). Externally hosted games are not accepted, except real multiplayer games. A general rule on runtime requests and any sitelock guidance are not published.

GameMonetize, Y8 and itch.io

  • GameMonetize allows external links and your own branding in all games (FAQ). Rules on external requests, analytics and sitelocks are not published.
  • Y8 bans external links in games: no other websites, app stores, social media, payment, gaming-platform or promotional pages; social links belong on the studio page. Your own or third-party ads are not allowed, and unauthorized ad scripts, pop-ups or redirects can lead to removal (developer FAQ). Instead of an allowlist sitelock, the SDK’s isBlacklisted() call reports whether the current domain is on Y8’s list of sites known to copy games, so the game can direct players to its official page (protection).
  • itch.io requires HTTPS for any request to another domain (HTML5 docs) and asks you to avoid third-party login walls unless necessary, for example for DRM or server-side settings (quality guidelines).

YouTube Playables

Playables may not make external calls except to Google or YouTube APIs, may not try to bypass that block, and may not show QR-like graphics, login screens or prompts for personal data (privacy and data). The certification FAQ says internal analytics are not exempt and that all game data must ship in the bundle; remote data access is a pilot with select titles (certification FAQ). The CSP string in the test suite guide limits connect-src to 'self' blob: data:, which is how the block shows up in testing.

Clickable links to external content, in-game sharing prompts and extra user agreements are all disallowed (design). Code obfuscation is banned too, which rules out the obfuscation step CrazyGames suggests for a sturdier sitelock.

Google H5 Games Ads

The Ad Placement API docs say the AdSense tag and API calls should run in the same document as the game canvas (game structure). They publish no rules on other requests, links, analytics or sitelocks, because the game runs on your own site.

What to check before you submit

  • Search the build for http://, https://, fetch(, XMLHttpRequest, WebSocket and font or CDN URLs; bundle anything the target portal blocks.
  • List every analytics, leaderboard or multiplayer endpoint, and get it approved where the portal requires that (Poki) or remove it (GameDistribution, YouTube Playables).
  • Make link buttons portal-aware: openExternalLink() on Poki, menu-only and conditional on CrazyGames, removed for GameDistribution, Y8 and YouTube Playables. A per-portal build flag, as in one codebase, many portal builds, keeps this manageable.
  • If you sitelock, allow every origin the portal publishes, and test the CrazyGames iOS app case.
  • Add an in-game privacy notice where the portal asks for one (Poki with exceptions or links; CrazyGames with extra data).

What is not published

GameMonetize, Y8, itch.io and H5 Games Ads publish no rule on analytics. No portal here except CrazyGames publishes a list of origins to allow, and only CrazyGames and Y8 document a domain check. GameDistribution publishes no general rule on runtime requests. Silence is not permission; ask the portal before relying on an external service.

Questions

Can I use Google Analytics in a portal game?
Not on Poki, which says Google products including Google Analytics cannot be approved, and not on GameDistribution, which lists it among banned trackers. YouTube Playables blocks all external calls, analytics included.
Can I link to my Discord or Steam page from inside the game?
It depends on the portal. CrazyGames allows community and store links in the menu with conditions; Poki requires its openExternalLink() call; GameDistribution, Y8 and YouTube Playables do not allow clickable outgoing links. GameMonetize allows external links.
Does a sitelock break my game on CrazyGames?
It can if it misses an origin. CrazyGames lists every domain to allow, including its app host app.crazygames.com under both the https and capacitor schemes, and warns that a frame-ancestors rule without the capacitor origin shows a white screen in the iOS app.

Sources

  1. External resources policy (Poki for Developers guide)developers.poki.com, accessed
  2. Requirements and quality guidelines (Poki for Developers guide)developers.poki.com, accessed
  3. Sitelock (CrazyGames docs)docs.crazygames.com, accessed
  4. Technical requirements (CrazyGames docs)docs.crazygames.com, accessed
  5. Gameplay requirements (CrazyGames docs)docs.crazygames.com, accessed
  6. Requirements introduction (CrazyGames docs)docs.crazygames.com, accessed
  7. Account integration requirements (CrazyGames docs)docs.crazygames.com, accessed
  8. Can my game contain outgoing links? (GameDistribution FAQ)gamedistribution.com, accessed
  9. Developer guidelines (GameDistribution)static.gamedistribution.com, accessed
  10. Developer terms (GameDistribution)static.gamedistribution.com, accessed
  11. FAQ (GameMonetize)gamemonetize.com, accessed
  12. Developer FAQ (Y8 Developer Portal)developer.y8.com, accessed
  13. SDK protection (Y8 docs)docs.y8.com, accessed
  14. Uploading HTML5 games (itch.io docs)itch.io, accessed
  15. Quality guidelines (itch.io docs)itch.io, accessed
  16. Privacy and data requirements (YouTube Playables)developers.google.com, accessed
  17. Design requirements (YouTube Playables)developers.google.com, accessed
  18. Certification FAQ (YouTube Playables)developers.google.com, accessed
  19. Test suite guide (YouTube Playables)developers.google.com, accessed
  20. HTML5 game structure (Ad Placement API, Google for Developers)developers.google.com, accessed