> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/account/performance-and-security/hide-sensitive-data-in-url.md).

# Hide sensitive data in URL

If one or several URL might contain sensitive data as a URL parameter, you can tell the tag to avoid collecting it.

## Block simple URL parameter

1. Go to the [sensitive data page](https://app2.abtasty.com/settings/tracking/sensitive-data)
2. Set the parameter you want the tag to ignore
   1. for example, input `email` if you want to remove an email from this sample URL: `https://www.mywebsite.com/account?email=email@example.com` .
3. You can add as many parameters as you need

## Block a parameter based on a regular expression

1. Go to the [sensitive data page](https://app2.abtasty.com/settings/tracking/sensitive-data)
2. Set the required regular expression that the tag needs to evaluate to ignore a URL parameter
   1. for example, to define the URL <https://example.com/url-part-to-hide/other-part>, enter the following expression (https?://example.com/).\*?(/other-part)

{% hint style="info" %}
As evaluating a regular expression as a performance cost, always prefer a simple URL parameter filter if possible.
{% endhint %}


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.abtasty.com/account/performance-and-security/hide-sensitive-data-in-url.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.