> For the complete documentation index, see [llms.txt](https://docs.authgear.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.authgear.com/customization/built-in-ui/privacy-policy-terms-of-service.md).
# Privacy Policy & Terms of Service Links
You can add a privacy policy and a terms of service link to the sign up page.
## Change in the Portal
These two links can be easily added in the project Portal
1. Go to **UI Settings** in the Portal
2. Fill in the **Privacy Policy Link** and **Terms of Service Link** in the **Link Settings** section
3. **Save** the settings.
The values will be used as the `href` of `` HTML tag so they must be valid URL. If both of the links are left empty, the whole paragraph on the signup page will be hidden.
## Edit translation.json
You can also add these links by including two special translation keys in translation.json.
The keys are `terms-of-service-link` and `privacy-policy-link`. The values will be used as the `href` of `` HTML tag so they must be valid URL.
For example,
```javascript
{
"terms-of-service-link": "https://mycompany.com/terms-of-service",
"privacy-policy-link": "https://mycompany.com/privacy-policy"
}
```
If you wish to hide the whole paragraph, set BOTH to empty string.
---
# 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.authgear.com/customization/built-in-ui/privacy-policy-terms-of-service.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.