> For the complete documentation index, see [llms.txt](https://t22.caqualityearlylearning.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://t22.caqualityearlylearning.org/licensing/advertisements-and-license-number.md).

# Advertisements And License Number

101162

(a) No person or legal entity shall advertise or represent itself as a licensed child care center without first obtaining a current valid license from the Department.

    (1) Licensees shall reveal each child care center license number in all advertisements in accordance with Health and Safety Code Section 1596.861.

{% hint style="info" %}
Health and Safety Code Section 1596.861 provides:

(a) Each child day care facility licensed under this chapter, or Chapter 3.5, Chapter 3.6 shall reveal its license number in all advertisements, publications, or announcements made with the intent to attract clients.

(b) Advertisements, publications, or announcements subject to the requirements of subdivision (a) include, but are not limited to, those contained in the following: 

   (1) Newspaper or magazine. 

   (2) Consumer report. 

   (3) Announcement of intent to commence business. 

   (4) Telephone directory yellow pages. 

   (5) Professional or service directory. 

   (6) Radio or television commercial.
{% endhint %}

(b) Correspondence is considered a form of advertisement only if the intent is to attract clients. 

(c) Repealed by Manual Letter No. CCL-98-11, effective 11/1/98.

> NOTE: Authority cited: Section 1596.81(a), Health and Safety Code. Reference: Section 1596.861, Health and Safety Code.


---

# 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://t22.caqualityearlylearning.org/licensing/advertisements-and-license-number.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.