Terms

Totem Terms of Service v1

Draft — not yet effective. Last updated August 19, 2026. This draft describes the service as it works today. It requires review by Victor and a lawyer before publication.

These terms govern use of Totem, a browser-game publishing service operated as Totem Labs Forge ("Totem," "we," or "us"). By creating a creator account, publishing a game, or using Totem as a player, you agree to these terms.

1. What Totem does

Totem lets a creator connect an AI coding tool through Totem's MCP server, upload a static browser-game build, and publish that build at a shareable Totem link. Totem validates the uploaded archive, adds the Totem browser SDK, stores the deployed files, and serves the game inside a Totem play page.

Totem also provides play analytics, optional player tags, scores and public leaderboards. Totem does not host creator-run server code. Stateful features provided by Totem use Totem's own API.

Publishing and discovery are separate:

• A published game is unlisted by default. It does not appear in Totem's

public game index unless its creator lists it.

• Unlisted does not mean private. Anyone who has or discovers a game or lane URL

can open it.

• Published game files are served publicly from an isolated game origin. They

must not contain secrets, private source files, credentials, or material that is not meant to be downloaded.

Totem currently has no paid plans, checkout, payment processing, advertising, or revenue-sharing system.

2. Creator accounts and API keys

Creators sign in with GitHub and choose a public Totem handle. Registration is open; an invite code may record who introduced a creator, but an invite is not required to register.

You are responsible for activity through your creator account and API keys. Keep API keys private. Do not put them in a game build, source file, public prompt, screenshot, or support message. Totem stores API keys as hashes and cannot show the complete key again after it is created.

Creator handles and game slugs become part of public links. A retired creator handle remains reserved so that an old link cannot later be inherited by a different creator.

3. Your games remain yours

Creators retain all rights, title, and interest in the games and other content they submit to Totem. Publishing through Totem does not transfer ownership to Totem.

To operate the service, you give Totem a non-exclusive, worldwide, royalty-free license to host, copy, validate, extract, cache, serve, and display the game files and metadata you submit. This license also allows Totem to add the Totem SDK tag and build manifest required for publishing, and to present the game through its play page, install metadata, and social preview.

This license is limited to operating, securing, and presenting Totem. It ends when deletion of the game is completed, except that:

• copies already held in browser or CDN caches may remain until they expire or

are purged; and

• Totem may retain the factual record of a platform takedown described in

section 7.

Totem retains its rights in the Totem service, software, documentation, name, and branding. Those rights do not include ownership of your game.

4. What creators are responsible for

You may publish a game only if you have the rights needed to publish every file in its build. You are responsible for the game, its code, its content, and any external service or data collection that you add to it.

Do not use Totem to publish or operate:

• malware, credential theft, deceptive downloads, or code intended to damage a

device or service;

• content that infringes another person's intellectual-property, privacy, or

publicity rights;

• unlawful content or activity;
• impersonation or materially deceptive claims about who made or operates a

game;

• content intended to exploit, threaten, or harass people; or
• attempts to bypass Totem's upload checks, sandbox, access controls, rate

limits, or service boundaries.

Totem checks archive structure, file types, size, and common unsafe paths before publishing. Those checks do not review whether you own the content or whether the game complies with law. That remains your responsibility.

If your game collects data independently of Totem or connects to another service, you are responsible for explaining that to players and for the conduct of that service. Totem's Privacy Policy (./privacy-policy.md) covers Totem's own collection, not a creator's separate collection inside a game.

5. Players, analytics, and leaderboards

Opening a live Totem game creates or reuses an anonymous Totem player record and records a play session. Totem's injected SDK reports session start, heartbeat, visibility change, and session end events. A game can also report a game-over event and score. More detail appears in the Privacy Policy (./privacy-policy.md).

Player tags and leaderboard entries are public. A player should not choose a tag that reveals information they do not want to make public. Scores are sanity-checked and rate-limited, but Totem does not promise cheat-proof leaderboards.

Creators receive analytics for their own games. Analytics can contain delayed, incomplete, duplicated, or inaccurate events when a browser closes, loses its connection, blocks storage, or sends malformed data.

6. Service limits and availability

Totem is an early service. Upload size and file-count limits, supported file types, request limits, and other operational limits are enforced by the service and may change as Totem changes.

Totem does not provide an uptime or permanent-storage guarantee. Keep your own source code and build backups. A successful publish is not a promise that a game or any past build will be hosted forever.

7. Manual game suspension

Totem's operator may manually suspend a game. Suspension takes the game and all of its lanes offline. Totem may use this control in response to security, abuse, rights, legal, or service-protection concerns. A suspended direct game link returns an unavailable response until an operator restores it.

The operator action records who performed it, when, the reason, the affected creator handle and game, and the status change. The record is append-only so a restoration does not erase the original takedown.

Automated moderation is not part of the current service. A creator who wants to ask about a suspension can contact Totem through https://x.com/vikgmdev. Do not send an API key or other secret in that message.

8. Deleting an account or game

Totem does not yet provide a self-service delete button or delete API for creator accounts or games.

To request deletion, contact Totem through https://x.com/vikgmdev and identify the GitHub account, creator handle, and game involved. Do not include an API key. Totem will verify control of the creator account before carrying out the request manually.

Deleting a creator account requires deletion of its games, builds, creator memberships, and API keys. Public CDN or browser caches can take time to stop serving copies. Append-only operator takedown records may remain after account or game deletion. The Privacy Policy describes the current retention behavior in more detail.

9. No payments, ads, or sale of data

Totem does not process payments, run ads, or sell creator or player data. If that changes, Totem must update these terms and the Privacy Policy before the new activity begins.

10. Changes to these terms

Totem may revise these terms as the service changes. The current version will show its update date. A material new data use or product model must be described before it begins, not added to these terms after the fact.

11. Contact

The current public contact for Totem Labs Forge is https://x.com/vikgmdev. Do not send passwords, API keys, OAuth tokens, or private game files through X.