# Niadra architecture, security and GDPR

> The architecture, the six security layers, GDPR and LGPD compliance, and the Niadra documentation.

URL: https://niadra.com/en/recursos

# How Niadra works on the inside.

The architecture, the security layers, GDPR and LGPD compliance, and the technical documentation.

## Architecture

### Everything is kept, nothing is rewritten

Every conversation goes into a record that only grows. Nothing is changed afterwards. Erasing is a separate operation that walks through everything derived from that data and produces a receipt.

### The same person on every channel

Each identifier (phone, email, tax ID, login) comes in with its source and its weight. Merging profiles is reversible: if two people are merged by mistake, Niadra splits them without losing the history of either.

### The memory updates with every conversation

As soon as a conversation ends, specialized models extract facts, preferences, open items, promises and the outcome. Each item keeps the date and the conversation it came from, and no fact goes in without evidence.

### Context ready before the agent asks

Each customer’s context is prepared ahead of time, per channel and per agent. During the conversation, delivery takes under 100 ms and is always the same for the same request: no model improvises along the way.

### The entire history, searchable

The agent searches by meaning and by keyword across everything that has happened with the customer, filters by period, channel and topic, and opens a specific conversation. Every result comes back with date, channel and outcome, and respects the permissions of whoever asked.

### Built to cost little on your model

The context is compact and runs from what changes least to what changes most. The AI provider reuses the beginning, and you pay for it once per conversation, not with every message.

## Six layers of security

Each layer protects the data on its own. Reaching a piece of data would mean getting through all of them.

1.  1
    
    ### Infrastructure
    
    Run and monitored by Niadra, around the clock, on cloud infrastructure certified to ISO 27001, SOC 2 and PCI DSS. Private network, with no direct path from the internet to the data, across multiple availability zones. Encrypted backups and tested restores.
    
2.  2
    
    ### Encryption
    
    AES-256-GCM at rest and TLS 1.3 in transit, with a second, field-level cipher for personal data. Each company has an exclusive key, and every piece of data is bound to the company that owns it: if a bug mixes records from two companies, decryption fails instead of leaking.
    
3.  3
    
    ### Keys
    
    Master keys live in HSMs validated to FIPS 140-3 Level 3 and never leave them. Automatic rotation, and separation between who uses and who administers the key. On the Regulated plan, the keys belong exclusively to your company’s dedicated environment.
    
4.  4
    
    ### Access
    
    Everything denied by default. Each agent has its own credential and permissions, and the rule is purpose-based: the collections agent never reads health data. In the Console, SSO through SAML 2.0 or OIDC, mandatory MFA and access roles.
    
5.  5
    
    ### Customer identity
    
    A phone number is not a password. The context changes according to how much the conversation has already proven about who the person is, across five verification levels, and sensitive data only shows up after confirmation.
    
6.  6
    
    ### Audit
    
    Every read produces a record chained by SHA-256 hash, with the daily root sealed in immutable storage: who read, what, why and when. Tamper-proof, and streamed to your SIEM in real time.
    

## Privacy and compliance

### GDPR and LGPD

Niadra acts as the data processor, and you remain the controller. The data processing agreement (DPA) and the list of subprocessors are part of the contract.

### Data subject rights, through the API

Access, correction, portability and erasure. Erasure walks through everything derived from that data and produces a receipt.

### Configurable retention

You define how long each type of data is kept. When the period ends, the data is erased for real, and backups expire within a documented window.

### Your data never trains models

Not ours, not anyone else’s. The AI providers that process conversations operate with no retention and no training on your data.

### Sensitive data masking

Tax IDs, card numbers and other sensitive data are detected and masked before they reach any AI model.

### Data residency

You choose the region where the data lives. Nothing leaves it without your written authorization.

### Penetration testing

Regular tests by an independent firm, with the report available under a confidentiality agreement, and a responsible disclosure channel.

### Incident response

A response plan with named owners, and notification to your team within the window agreed in the contract.

## Documentation

Integration guides, the complete API reference, Python and TypeScript SDKs, the MCP server and examples that run without changes. Also in plain text (/llms.txt), so your coding agent can do the integration on its own.

[Ask for documentation access](/en/enterprise?interesse=docs)