Back to Workspace
Legal

Terms of Service

LiveCodeShare-Pro
Last Updated
July 25, 2026

The short version
LiveCodeShare-Pro is a free collaborative code editor. You keep ownership of everything you write. Don't use it to break the law or to hurt other people's sessions. Rooms are encrypted with a password only you hold — if you lose it, nobody can recover that room, including us. That's most of it; the details follow.
On this page
  1. 01Accepting these terms
  2. 02Who can use the Service
  3. 03Rooms and passwords
  4. 04Acceptable use
  5. 05Where your code runs
  6. 06Your content stays yours
  7. 07Third-party services
  8. 08A free service, provided as-is
  9. 09Warranties and liability
  10. 10Changes and contact

01Accepting these terms

By creating or joining a workspace on LiveCodeShare-Pro (the "Service"), you agree to these Terms and to our Privacy Policy. If you don't agree with something here, the honest advice is simple: don't use the Service. There is no account to close — just stop using it.

02Who can use the Service

You need to be at least 13 years old, or the minimum age required to consent to data processing where you live. You also need to be legally able to agree to terms like these in your jurisdiction.

There are no accounts. You pick a display name when you enter a room — it can be a pseudonym. If you connect Google Drive for backups, you sign in with Google and are responsible for that credential like any other.

03Rooms and passwords

Workspaces are protected by a room name and password that you choose. That password is also the basis of the encryption key for the room's content.

  • Guard your room passwords. Anyone who has the name and password can enter the room.
  • We never see or store the password. If it's lost, the room's encrypted content is permanently unrecoverable — there is no reset flow, by design.
  • Temporary rooms are cleaned up automatically after a period of inactivity.

04Acceptable use

You agree not to use the Service to:

  • Break any applicable law or regulation.
  • Infringe someone else's intellectual property, privacy, or other rights.
  • Distribute malware or malicious code through shared workspaces, run targets, or links.
  • Disrupt, overload, or attempt unauthorized access to the Service, its servers, or other users' sessions.
  • Store, transmit, or execute content that is unlawful or defamatory.

Code you execute through the run system goes into sandboxes (see the next section) — trying to escape those sandboxes or abuse the executors counts as disruption. We can suspend or block access for breaches of any of this.

05Where your code runs

The RUN system offers several execution targets, and it matters which one you pick:

  • Browser JS and WebNode run entirely inside your own browser tab.
  • Cloud runs send the file being executed (plus any stdin you typed) to Wandbox, a third-party compilation service, under its own terms. Don't cloud-run code or data you are not comfortable sending to a third party.
  • Local Bridge executes code on your own machine, under your control and at your own risk.

06Your content stays yours

You retain full ownership of all code, files, and messages you create in the Service. We claim no rights over your workspace content.

  • Room code and chat are encrypted in your browser (WebCrypto AES-GCM 256) before transmission, so we cannot read them.
  • Files you back up to Google Drive live in your Drive account, under your control.
  • You are responsible for what you share and for having the rights to share it.

07Third-party services

Parts of the Service are built on third parties, each governed by its own terms:

  • Google OAuth & Drive for optional backups — see the Google Terms of Service and the Google API Services User Data Policy. We request only the drive.file scope, which limits access to files created or opened by LiveCodeShare-Pro.
  • Agora carries the voice, video, and screen-share streams.
  • Wandbox compiles and runs cloud executions, as described above.
  • Vercel hosts the site.
  • Google AdSense serves ads on some pages.

If you configure your own AI API key, requests to that AI provider are made with your key and are governed by that provider's terms.

08A free service, provided as-is

LiveCodeShare-Pro is free. It is provided on an "as is" and "as available" basis. We work on uptime and stability, but we don't promise the Service will be uninterrupted, error-free, or secure at all times — maintenance, updates, third-party outages (for example the cloud compiler), or plain bugs can cause downtime.

Back up work that matters to you: export the workspace as a .zip, save to your Drive, or use the disk-folder mode so files live on your own machine.

09Warranties and liability

To the fullest extent permitted by law, the Service comes without warranties of any kind, express or implied — including implied warranties of merchantability, fitness for a particular purpose, and non-infringement. You use it at your own risk.

To the maximum extent permitted by applicable law, neither LiveCodeShare-Pro nor its operator is liable for indirect, incidental, special, consequential, or punitive damages, or for loss of data, profits, or goodwill, arising from your use of the Service.

10Changes and contact

When these Terms change, the "Last Updated" date at the top changes with them. Using the Service after an update means you accept the revised Terms — if a change bothers you, that's a good reason to check this page now and then.

Questions about these Terms? Write to us — messages go straight to the operator's inbox.

L
LiveCodeShare-Pro
WorkspaceContactTermsPrivacy
(c) 2026 LiveCodeShare-Pro. Built by Labi Rana Magar.