Build with Blockmaker responsibly.

1. Agreement and early access

By creating a Blockmaker account, adding a game, or using the API or official SDKs, you agree to these terms and acknowledge the Privacy notice. If you act for a studio or other organisation, you confirm that you have authority to accept them for that organisation. If you cannot legally agree, do not use the service without an authorised adult or representative.

Blockmaker is currently an early-access service. Features and limits may change, and some features may be labelled beta, experimental, or unavailable. A statement that setup or a wallet proof involves “no payment to Blockmaker” describes the current setup flow; it does not promise that every feature will remain free. Network fees and third-party charges may still apply.

2. Accounts and wallets

Your connected Algorand wallet proves ownership of your Blockmaker account. One account can contain multiple separately scoped games. You are responsible for controlling that wallet, keeping its recovery phrase safe, reviewing every signing request, and maintaining a recovery plan. The contact email is for account-related communication and support—not a way to recover the owner wallet.

Provide accurate game and contact details, keep them current, and give collaborators only the access they need. Do not share an account or claim a game, wallet, brand, or identity you do not control.

3. Credentials and security

Each game’s public game ID can appear in client code. Its server key cannot. Store server keys in a private backend or secret manager, never in a web bundle, Unity build, repository, screenshot, support issue, or AI chat. Use the public AI guide URL—not a secret—when handing work to a coding agent.

You are responsible for allowed origins, backend authorisation, collaborator access, transaction limits, key rotation, and safe integration of the SDKs. If a credential may be exposed, revoke or rotate it promptly. Never send Blockmaker or support staff a wallet recovery phrase or private key.

4. Your game and players

You—not Blockmaker—publish and operate your game. You are responsible for:

• the game’s code, content, rules, availability, moderation, player support, refunds, and promises;
• testing the complete integration, including failures, retries, duplicate requests, wallet behaviour, and recovery paths;
• telling players what data and blockchain actions the game uses, obtaining required consent, and handling player requests;
• age checks, child-safety measures, consumer rights, accessibility, taxes, sanctions, export rules, licences, and other laws that apply to the game;
• the design, funding, caps, eligibility, tax treatment, and legality of tokens, NFTs, prizes, purchases, and rewards; and
• making sure you have rights to all game content, brands, assets, player data, and code you send to or use with Blockmaker.

Blockmaker’s tenant boundaries help isolate games, but they do not replace your own authentication, input validation, server-side authority checks, monitoring, backups, or professional security review.

5. Acceptable use

Do not use Blockmaker to:

• break the law, infringe rights, deceive or exploit players, or distribute malware;
• access another account or game without permission, probe for data beyond authorised security testing, or evade access, rate, treasury, or abuse controls;
• expose credentials, interfere with the service, overload infrastructure, automate abusive requests, or use Blockmaker as a general-purpose public proxy;
• impersonate Blockmaker, a game, a player, or another person;
• offer unlawful gambling, wagering, lotteries, securities, investment products, money transmission, sanctions evasion, or other regulated activity without the licences, advice, and controls required by law; or
• store highly sensitive or regulated data unless Blockmaker has expressly agreed in writing that the service is suitable for it.

Good-faith security research must avoid accessing other users’ data, moving assets, degrading the service, or publishing exploit details before a safe reporting route is agreed. Follow the security-reporting process.

6. Blockchain, managed features, and rewards

Public blockchains can be delayed, congested, reorganised, upgraded, attacked, or unavailable. Transactions may carry fees, be irreversible once confirmed, and remain public permanently. Token and NFT ownership can change between checks. You must independently review addresses, assets, applications, amounts, caps, and signing authority before using real value.

Blockmaker is not intended to be a bank, exchange, broker, trustee, investment adviser, or safekeeping service. We do not promise custody, recovery, liquidity, price, yield, profit, or continuing value for any wallet, token, NFT, prize, or reward. Optional managed-wallet and reward-treasury features are technical game tools; using them does not transfer your legal, tax, security, or regulatory responsibilities to Blockmaker.

Do not fund a game treasury with more than you are prepared to put at risk. Use an isolated wallet, conservative owner-set limits, idempotent server requests, and small live tests. Blockmaker may refuse or hold an ambiguous payout while its exact transaction status is checked.

7. Third-party services

Blockmaker relies on hosting, email, wallet, blockchain node/indexer, storage, and other infrastructure providers. A game may also enable optional wallet-funding guidance, wallet, or media services. Their availability, fees, terms, privacy practices, and network behaviour are outside Blockmaker’s control. You are responsible for reviewing the third-party services your game enables.

Links and SDK references do not mean that Blockmaker guarantees or endorses a third party, asset, game, or transaction.

8. Data and privacy

The Privacy notice explains Blockmaker’s current practices. You must provide your own appropriate privacy notice to players and use Blockmaker only for information you are allowed to process. Do not put confidential information into public game names, public AI guides, blockchain transactions, or public support issues.

9. Availability and changes

The service is provided for early testing without a service-level agreement. We may add, remove, limit, pause, or change features, SDKs, quotas, providers, or supported chains. We may perform maintenance or respond to security and reliability incidents without advance notice when necessary.

Keep your own source code, configuration records, recovery information, and exports or backups that your game needs. Do not design a game so that a temporary Blockmaker or blockchain outage creates unsafe behaviour or irreversible player loss.

10. Ownership and feedback

You keep ownership of your game and content. You give Blockmaker only the permissions reasonably needed to host, process, transmit, back up, and display that material to provide the features you choose.

Blockmaker and its licensors retain rights in the service, branding, documentation, and SDK materials, subject to any open-source licence published with specific code. If you voluntarily give product feedback, we may use it to improve Blockmaker without an obligation to pay you or keep the idea exclusive.

11. Disclaimers and liability

To the fullest extent the law permits, Blockmaker is provided “as is” and “as available”. We do not promise that it will be uninterrupted, error-free, completely secure, suitable for a particular game or legal regime, or that blockchain information will always be current or correct.

You accept the risks of integrating an early service and of blockchain activity. To the fullest extent permitted by law, Blockmaker is not responsible for indirect or consequential loss, lost profits, lost game data, loss caused by your code or credentials, wallet compromise, third-party failure, or changes to a blockchain or asset. Nothing in these terms excludes or limits liability that applicable law does not allow to be excluded or limited, or overrides mandatory consumer rights.

12. Suspension and ending use

You may stop using Blockmaker and request deletion as described in the Privacy notice. Remove SDK calls and rotate or revoke credentials you no longer need.

We may limit or suspend access where reasonably needed to protect the service, other users, or the public; investigate suspected abuse; comply with law; or respond to a breach of these terms. Where practical, we will explain the reason and a route to resolve it. Blockchain transactions already confirmed cannot be reversed by ending Blockmaker access.

13. Updates and contact

We may update these terms as Blockmaker develops. The date above identifies the current version. If a change is material, we should make it visible on this page or through the service where practical. Continuing to use Blockmaker after an update means accepting the updated terms.

No dedicated support email or postal address is currently published. Read Blockmaker Support for the public contact route and instructions for reporting sensitive issues safely.