> For the complete documentation index, see [llms.txt](https://eztalks.gitbook.io/company/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eztalks.gitbook.io/company/trust/regulations.md).

# Regulations

EZTALKS has clearly laid out a Service Level Agreement and Terms of Service Agreement. The use of EZTALKS services by a person or a group should only be in accordance with these regulations.

Additionally, it is very important for the user to keep their local and federal communication rules and guidelines in mind. EZTALKS is not responsible for any illegal activity that users conduct through their EZTALKS accounts.

EZTALKS strictly condones the use of its services in a manner that is unacceptable ethically, legally, or morally. The users are themselves responsible for any content that they share through faxes using EZTALKS.

Any misuse of EZTALKS services can result in the permanent deletion of a user’s EZTALKS account. In case a user breaches any government law or regulation, it can result in legal liabilities for the user as well.

EZTALKS advises users to refer to their local laws in case they want to be aware of their State Laws regarding SMS/MMS or telephonic communication.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://eztalks.gitbook.io/company/trust/regulations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.