> For the complete documentation index, see [llms.txt](https://docs.perkville.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.perkville.com/features/agency/ad-terms.md).

# Ad terms

This page describes what content is prohibited from the Perkville ad platform

**Prohibited Content**

The following is prohibited from being featured in advertisements as products, or in content including image and text, or in the website(s) linked to within the ad:

* Gambling;
* Tobacco;
* Marijuana;
* Guns and ammunition;
* Multilevel marketing;
* Payday loans and similar financial services;
* Cryptocurrency;
* Political content;
* Religious content;
* Pornography or sexually explicit content;
* Escort services, mail-order bride or spouse finders, international marriage brokers, and other similar services;
* Statements about products claiming to prevent, treat, or cure health issues (e.g., illness or disease) that have not been approved by the applicable government authority or are not permitted under applicable law or regulation;
* Advertising for prescription medication that cannot legally be sold over-the-counter; and
* Content that is fraudulent or that Perkville determines in good faith is intended to mislead a recipient or cause harm or damage

These limitations are required to protect email deliverability across the platform. Ads or advertisers that violate these terms will be removed. Perkville may modify these terms at any time, without notice.

Please visit <https://info.perkville.com/terms> to view all of the terms for advertisements and agencies.


---

# 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://docs.perkville.com/features/agency/ad-terms.md?ask=<question>&goal=<user_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.
