Do not assume that one permission covers all three. Domain limits, delivery rights and onward distribution rights must be checked separately. MarketJS, for example, describes a standard one-domain licence, custom multi-domain arrangements, compiled files for fixed-fee licences and hosted links for subscription licences. (marketjs.com)
Slots Launch’s pricing FAQ advertises use across unlimited sites, while its integration documentation requires domains to be registered. Those statements address its service arrangements; buyers should still obtain the content and territorial scope applicable to their use. (slotslaunch.com)
Use separate approval fields for:
- External linking: sending the visitor to an approved destination.
- Embedding: displaying a remotely served game within your page.
- Self-hosting: serving game files from infrastructure you control.
- Asset reuse: publishing screenshots, logos, audio or video.
- Redistribution: supplying access or files to another publisher.
For a publishing group, list each legal entity and domain rather than relying on “our network”. Ask what happens when you acquire a site, change a domain or sell a publication.
For self-hosting, also request explicit answers about compiled files versus source code, updates, security fixes and continued use after termination. MarketJS expressly distinguishes delivery of compiled games from ownership of its source code. (marketjs.com)