> For the complete documentation index, see [llms.txt](https://tmediadocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tmediadocs.telcobridges.com/operations-and-support/support/policies/rohs.md). # RoHS Restriction of Hazardous Substances Directive (or RoHS) is a directive of the European Union concerning the use of certain hazardous substances in electrical and electronic equipment. ### TelcoBridges and RoHS TelcoBridges endorses the action taken by the European Union in Directive 2011/65/EU concerning the Restriction on Hazardous Substances (RoHS). Our products meet the requirements of the European Union's RoHS Directive (2011/65/EU). ### Waste Electrical and Electronic Equipment (WEEE) - Product Recycling In support of our environmental goals, TelcoBridges offers a formal product take-back and recycling program in Europe that complies with the European Union Directive 2002/96/EC on waste electrical and electronics equipment (“WEEE Directive”). Equipment that is returned through this program will be handled in an environmentally safe manner using processes that comply with the WEEE directive requirements. Please contact us for further information. ### References * [Wikipedia article](http://en.wikipedia.org/wiki/Restriction_of_Hazardous_Substances_Directive) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://tmediadocs.telcobridges.com/operations-and-support/support/policies/rohs.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.