Copyright & Takedown Policy

Tenux respects intellectual-property rights and expects its users to do the same. Because of how Tenux works, the picture is different from a typical website: your code and files live on your own machine. This page explains how to reach our designated agent, where Tenux can act on a copyright complaint, and where it cannot.

1. Our designated agent

Tenux LLC has designated an agent to receive notifications of claimed infringement under the Digital Millennium Copyright Act, registered in the U.S. Copyright Office’s DMCA Designated Agent Directory:

Copyright Agent
Tenux LLC
2778 Portola Way
Merced, CA 95348
Phone: (209) 600-9148
Email: [email protected]

Please send only copyright notices and counter-notices to this agent.Other questions go to [email protected].

2. How to send a notice

To be effective under 17 U.S.C. §512(c)(3), your notice must be a written communication to our designated agent that includes substantially the following:

  • A physical or electronic signature of a person authorised to act on behalf of the owner of the exclusive right allegedly infringed.
  • Identification of the copyrighted work claimed to be infringed (or, if one notice covers several works, a representative list of them).
  • Identification of the material claimed to be infringing, or of the reference or link to it, with information reasonably sufficient for us to locate it (for example, the Cloud VM, preview URL, or repository listing).
  • Information reasonably sufficient for us to contact you, such as your address, telephone number, and email address.
  • A statement that you have a good-faith belief that use of the material in the manner complained of is not authorised by the copyright owner, its agent, or the law.
  • A statement that the information in the notice is accurate and, under penalty of perjury, that you are authorised to act on behalf of the owner of the exclusive right allegedly infringed.

Knowingly misrepresenting that material is infringing can make you liable for damages under 17 U.S.C. §512(f).

3. Our relay is a conduit, not a host (17 U.S.C. §512(a))

For the core service — the on-device agent, our tunnels and relay, and direct peer-to-peer connections — Tenux is a transmission conduit. These function as the “transitory digital network communications” described in 17 U.S.C. §512(a): the transmission is initiated by you (or someone you connect with), it is carried out by an automatic technical process without our selection of the material or its recipients, the content is passed through without modification, and we keep no copy of it — the relay records only connection metadata such as byte counts and liveness, never the bytes themselves.

Because we hold no copy of material that is only transmitted through Tenux, there is nothing for us to take down; the right place to address it is usually the person operating the machine that is serving the material. Where we can act on infrastructure we control (for example, disabling a relay tunnel or a preview URL that is being used to transmit infringing material), we may do so, and we will forward valid notices to the responsible user where appropriate.

4. Rented Cloud VMs (§512(c))

If you rent a Tenux Cloud VM, your workspace content is stored on a Tenux-provisioned cloud volume at your direction. On a valid notice about material stored on a Cloud VM, we will act expeditiously to remove or disable access to the identified material — which may include suspending the VM — and notify the responsible user.

5. Listings of open-source repositories (§512(d))

We are preparing a feature that lists and links to open-source repositories hosted on GitHub so you can clone them to your own machine. That list is an information-location tool under 17 U.S.C. §512(d): Tenux shows a listing and a link, but does not host the repository itself.

On a valid notice identifying a listing or link on Tenux, we will act expeditiously to remove the listing or disable the link. The repository and its contents are hosted by GitHub, not Tenux — to have the repository itself taken down, send a notice to GitHub under its own DMCA policy.

6. Counter-notice

If material of yours was removed or disabled and you believe that was a mistake or misidentification, you may send a counter-notice to our designated agent at [email protected]. Under 17 U.S.C. §512(g)(3) it must include your physical or electronic signature; identification of the material and the location where it appeared before it was removed or disabled; a statement under penalty of perjury that you have a good-faith belief it was removed or disabled as a result of mistake or misidentification; and your name, address, and telephone number, with a statement that you consent to the jurisdiction of the federal district court for your address (or, if you are outside the United States, any judicial district in which Tenux may be found) and that you will accept service of process from the person who sent the original notice or that person’s agent.

7. Repeat infringers

In appropriate circumstances we terminate the accounts of users who are repeat infringers.

8. Related policies

See also our Terms of Service and Acceptable Use Policy.