> For the complete documentation index, see [llms.txt](https://ask.birdie.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ask.birdie.ai/admin-and-settings/security/lgpd-data-privacy.md).

# LGPD & Data Privacy (Brazil)

This page documents the Brazil-specific aspects of how Birdie anonymizes and protects personal data under the *Lei Geral de Proteção de Dados* (LGPD). It complements the region-neutral [Data Anonymization Process — Speech-to-Text Pipeline](/admin-and-settings/security/data-anonymization-process-speech-to-text.md), which describes the end-to-end flow, the categories of PII removed, and the redaction techniques used.

## Anonymization under LGPD Art. 12

LGPD Art. 12 places **anonymized data** outside the scope of the law: data that, by reasonable and available technical means, can no longer be associated with an individual. The LGPD distinguishes this from **pseudonymized data**, where the link to the individual is merely replaced by a reversible reference that can be restored using additional information — which is **not** sufficient to take data out of scope.

Birdie's redaction produces anonymized data, not pseudonymized data. The full technical argument — destructive replacement with a single fixed `[REDACTED]` label, no mapping table/token vault/key, a one-way transformation, and persistence of only the redacted text — is set out in [Why the Result Is Irreversible Anonymization](https://ask.birdie.ai/admin-and-settings/security/pages/KVG8N1hWhb96LALkNqcZ#4.-why-the-result-is-irreversible-anonymization).

Applied to Art. 12: because no "additional information" capable of reversing the redaction is ever produced or stored, the redacted transcript cannot be re-associated with an individual by reasonable technical means. It therefore meets the LGPD's irreversibility criterion for anonymized data.

## Brazilian identifiers redacted

In addition to the general PII categories (names, phone numbers, email addresses, physical addresses, credit cards, bank accounts, passwords, dates), Birdie applies dedicated pattern rules for Brazilian identifiers:

| Identifier | Example                                        |
| ---------- | ---------------------------------------------- |
| CPF        | `123.456.789-00`, `12345678900`                |
| RG         | `12.345.678-9`                                 |
| CNH        | 11-digit license numbers                       |
| Bank data  | `Banco 001`, `Agência 1234`, `Conta 1234567-8` |

These patterns run as the deterministic safety net (Stage 2) described in the [anonymization pipeline](https://ask.birdie.ai/admin-and-settings/security/pages/KVG8N1hWhb96LALkNqcZ#3.-how-the-anonymization-works), after the semantic (language-model) redaction stage.

## Data residency for Brazil

{% hint style="info" %}
For clients in Brazil, in compliance with the LGPD, transcription and anonymization run in GCP region `southamerica-east-1` prior to final persistence at the global index in GCP region `us-central-1`, Iowa.
{% endhint %}

***

**See also:**

* [Data Anonymization Process — Speech-to-Text Pipeline](/admin-and-settings/security/data-anonymization-process-speech-to-text.md) — full flow, PII categories, and redaction techniques.
* [PII & PHI anonymization](/admin-and-settings/security/pii-and-phi-anonymization.md) — the two anonymization paths and the full list of PII/PHI types.
* [UK, GDPR & Data Privacy FAQ](/admin-and-settings/security/uk-gdpr-and-data-privacy-faq.md) — international data-transfer and privacy questions.

#### Additional sources

* [Privacy Policy](https://birdie.ai/privacy-policy)
* [Data Processing Agreement](https://birdie.ai/data-processing-agreement)
* [Security Policy](https://birdie.ai/security-policy)
* [Trust Center](https://trust.birdie.ai/)


---

# 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://ask.birdie.ai/admin-and-settings/security/lgpd-data-privacy.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.