OJ
Sign in

Terms

What you can expect from OJPlay, and what we expect from you.

OJPlay is a small site run by the people who make OneJS. These terms are written to be read rather than to be survived, and they describe what the site actually does today. Where something is not built yet, it says so.

If anything here is unclear or looks wrong, write to hello@onejs.com. That is a person, not a queue.

Your account

You sign in with an email address. We mail you a six digit code, it lasts ten minutes, and it can be tried five times before it stops working. There is no password to lose.

You can also press Continue with Google or Continue with GitHub on the front page. Either way the address stays the identity: the provider is a way in, not the account. If the address the provider gives us is one it has verified, and it matches an account you already have, the two become one account rather than two. If the provider has not verified the address, we do not use it to reach an account at all, and you are asked for a code instead. So losing access to a Google or GitHub account never costs you your carts: the address and the code still work.

Your handle is made up for you the first time you sign in, or taken from your GitHub login or Google name if you use one, and you can change it then or later on your account page. It is what appears in the address of your profile and of every cart you publish. If you change it, the old handle stays yours: its addresses keep working, and nobody else can take it.

A session lasts thirty days. Signing out ends it, and the account page can end every session you hold at once if you think one has gone astray.

One account per person. If you want a second one, use a second address rather than sharing.

Your carts

Each cart is public, unlisted or private. Its source is public unless you make the repo private. A cart is what somebody plays, made from a repo: a public cart is listed on OJPlay, an unlisted one plays for anybody with its link, and a private one plays only for you. A repo holds the source of all its carts, and a public repo means all of it: anybody, signed in or not, can:

  • read its source and its history on the site
  • clone it with git, into a Unity project or anywhere else
  • fork it into their own account, if they have one
  • use it in their own carts and Unity projects with oj

A new repo is public, and its first cart is public, unless you make it private. A private repo's source, history and forks are yours alone, though anybody who can play one of its carts gets that cart's built code and files, since that is what playing it takes. An unlisted or private cart of a public repo still has public source: who can play a cart and who can read its code are two separate settings.

Edits you have made in the editor and not pushed are not part of this: they stay yours alone until you push them. So never push a password, a key or anything else you would not publish, since a push puts it in the repo's history for anybody to read.

The catalog and search engines list a public cart once it has been changed from what it started as. Until then it is on your profile and at its own address.

You can delete a cart or a whole repo at any time. Deleting a cart removes it from the catalog and makes its page and its origin answer as though it were not there. Deleting a repo does that for every cart of it and for its source too, and stops anybody new from adding it. Neither reaches back into copies somebody already took: a fork is a separate repo with its own id from the moment it is made, a clone is a repository on somebody's disk, and a cart that uses yours keeps the version it uses.

A version another cart uses stays. Changing the version in your cart's oj.json releases it, and a released version never changes. When somebody adds your cart with oj, we keep the version they added, or for a cart with no version the build that was running then, so their cart keeps working whatever you change later, and even if you delete yours. If you published something you should not have, like a password, write to hello@onejs.com and we will take it out.

You keep ownership of what you write. A public cart's code and your own files in it are offered under the MIT license, unless its oj.json names another. Whatever the license, making a cart public also lets other OJPlay users use it through oj and fork it on OJPlay, because that is what the site does with a public cart. None of this gives us ownership of your work, and we do not claim any.

Only publish what is yours to publish. If a cart ships art, audio or code you did not make, you need the right to share it here. A license covers only what you own, so mark each file that belongs to somebody else in oj.json, for example game art © Blizzard Entertainment, and the cart's page shows it beside the license.

What you may not put here

The short version is: nothing that would hurt somebody, and nothing that makes this a hosting service rather than a sketchbook.

  • Not yours to share, or someone else's to take down
  • Built to attack, mislead or impersonate anyone
  • Sexual content involving children, or content that exists to harass a person
  • Using a cart as file storage, a proxy, a miner, or a way to reach other people's machines

A cart runs on its own separate origin (<id>.onejsusercontent.com) precisely so that a mistake in one cannot reach the site or another cart. Do not go looking for a way around that; if you find one, tell us at hello@onejs.com and we will thank you properly.

Limits

There is nothing to buy. Making carts, publishing them, forking and cloning are open to any signed-in account.

The limits exist to keep a cart a cart: 2 MB of source across at most 100 files, no single source file over 512 KB, and up to 200 shipped files. A shipped file under 1 MB is kept with the cart, up to 64 MB in all. A file of 1 MB or more is stored on its own, up to 100 MB each, and an account's stored files may add up to 1 GB across all its carts, each file counted once however many of them use it. Every version of a stored file stays while a cart names it. An account can hold 100 carts. If you are pressing against these, what you are building has probably outgrown a browser tab, which is what opening it in Unity is for.

When we step in

Three things can happen to work on this site, and they are deliberately different from one another.

A cart can be hidden. It drops out of the catalog and its page answers as though it were not there, while its files and its history stay exactly where they are. This is the usual answer to a report: it stops the harm while somebody looks, and nothing is lost if the report turns out to be wrong.

An account can be suspended. Sessions stop working and the person cannot sign back in. Their carts stay up unless they are hidden separately, because a suspension is about a person rather than about their work.

A file can be removed. This one is not reversible. It is keyed to the file's content, so it takes that file out of every cart that carries it at once and refuses it if it is uploaded again. It is what a copyright notice gets, and it is why we do it rarely and record a reason every time.

To report a cart, a file or a person, write to hello@onejs.com and say which and why. If you are the rights holder for something published here, say so and point at the file; a link to the page it appears on is enough for us to find it.

If we hide or remove something of yours, ask us why and we will tell you.

Leaving

You can delete any cart from its settings, which takes its page and its origin down and leaves the repo and its other carts. Deleting a repo, from its History, takes every cart of it, its files and its history down and frees the space immediately. A version or build that another cart uses stays, unlisted. The cart's address, like its id, is never given to anything else.

There is no button that closes an account yet. Until there is, write to hello@onejs.com and we will do it by hand. We would rather admit that than point you at a control that does not exist.

The parts we cannot promise

This is a small site and it is early. Carts run in your browser, and what they can do depends on the browser and the machine. We may change how the site works, and occasionally something that worked will not.

We do not promise the site will be available, that a cart will keep running forever, or that nothing will ever be lost. Keep your own copy of anything that matters to you. git clone gets you the whole history, in a folder you can also open in Unity; it is a real backup, and one action. It has what you pushed, and not edits you have not pushed yet.

Nothing here tries to take away a right you have under the law where you live.

Changes

When these terms change we will change this page and update the date at the bottom. If a change materially affects what happens to your work, we will say so somewhere you will see it rather than quietly editing the page.

Last updated: 8 November 2026.

DocsDiscordTermsPrivacy© 2026 OneJS