> For the complete documentation index, see [llms.txt](https://docs.edgetag.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.edgetag.io/faq/faq/compliance-and-security.md).

# Compliance and Security

#### Can EdgeTag be implemented for a HIPAA compliant brand?

Yes, EdgeTag can be implemented for HIPAA compliant brands. We respect HIPAA policies and maintain strict user privacy standards to ensure compliance with healthcare data protection requirements.

#### Is EdgeTag GDPR compliant compared to GTM?

Yes, EdgeTag offers better GDPR compliance than GTM.\
**Key Advantages:**\
\- GTM loads from Google CDN before consent checking, creating potential GDPR breaches\
\- Blotout EdgeTag provides self-hosting options and consent-first approach\
EdgeTag acts as data controller with user-level audit trails

Documentation: Visit our Trust Center for detailed compliance information: <https://trust.blotout.io/>

#### Can EdgeTag help me in the event of a bot attack?

**Enterprise WAF Protection:** Yes, EdgeTag includes enterprise-grade Web Application Firewall (WAF) protection powered by Cloudflare that automatically detects and filters bot traffic.\
**Automatic Bot Filtering:**  The system identifies and blocks malicious bot attacks while preserving legitimate user data and ensuring your analytics remain accurate.\
**Data Integrity:** This protection helps maintain clean, reliable tracking data by preventing bot traffic from skewing your conversion metrics and campaign performance data.\
**Always-On Protection:** The WAF protection runs continuously in the background, providing real-time bot detection and filtering without requiring manual intervention or affecting legitimate user experience.


---

# 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.edgetag.io/faq/faq/compliance-and-security.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.
