> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sazabi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Data handling

> How Sazabi encrypts, stores, retains, and deletes the telemetry you send — where it lives, how long it stays, and how it is used.

Sazabi processes the telemetry you send strictly to provide the service, on your instructions. Your data is never sold, and it is never used to train models. This page explains what happens to your data from the moment it leaves your infrastructure.

## Encryption

Every connection to Sazabi is encrypted with TLS 1.2 or higher in transit, and data at rest is encrypted with AES-256. Telemetry is protected from your infrastructure to Sazabi's storage layer, and the credentials you connect are encrypted before they are stored.

## Storage and retention

Sazabi uses managed log storage — there is no storage backend for you to provision or secure. Everything you send is indexed for the agent's queries and kept for your plan's retention window. When data ages past that window, it is deleted automatically; logs older than the window are not retained. See [Log storage & retention](https://docs.sazabi.com/guides/instrument/storage.md) for the full model. If your organization needs logs processed in its own cloud account and stored in infrastructure it owns, see [Bring your own cloud (BYOC)](https://docs.sazabi.com/security/byoc.md).

## Data residency

You choose the region your project's data lives in when you create the project — a United States or European Union region — so telemetry stays in the region that matches your data sovereignty requirements. The region is fixed for the life of the project. See [Log storage & retention](https://docs.sazabi.com/guides/instrument/storage.md) for how to choose a region.

## Deletion

Your data leaves Sazabi in three ways:

* **Retention expiry** — data is deleted automatically once it passes your retention window.
* **Stream or source removal** — removing a log source stops new data; historical records age out on the normal retention schedule.
* **Project deletion** — deleting a project removes the telemetry stored for it.

## How your data is used

Sazabi is a data processor: it works with your data only to run the product for you. Your data is never used to train models — neither Sazabi's nor its providers'. Sazabi uses enterprise API tiers that contractually exclude submitted content from model training, and passes that same commitment through to you in its Data Processing Addendum. No model is tuned on your data without an explicit, written opt-in.

## Redact sensitive data

You decide what leaves your systems, and Sazabi can redact common sensitive values for you at intake.

### Redact at intake

Turn on **Redact sensitive data** in [Settings > Project](https://app.sazabi.com/settings/project) to redact logs for every log stream in the project. Sazabi replaces matching values with a placeholder before ingested logs are stored or shown to the agent:

| Data | Placeholder |
| - | - |
| Email addresses | `[EMAIL]` |
| Phone numbers | `[PHONE]` |
| US Social Security numbers | `[SSN]` |
| Payment card numbers | `[CARD]` |
| Secrets — cloud access keys, API keys and tokens, JWTs, bearer tokens, passwords, private keys | `[SECRET]` |

Values under attribute names that always carry a secret, such as `authorization`, `cookie`, or `password`, are redacted whatever they look like. A redacted log records the kinds that were replaced in its `sazabi.redactions` attribute.

* The setting is off by default. Project admins can change it; there is no CLI equivalent.
* It applies to logs received after you turn it on. Logs already stored are not changed.
* Requests that fail intake, such as a malformed or oversized payload, can be kept unredacted in Sazabi's internal failure queue.
* Detection uses fixed patterns, so it does not catch names, addresses, health information, or other free-form personal data.

### Redact at the source

For data that must never reach Sazabi, strip it at the source — redact secrets and sensitive fields at your log source or collector, the point where you own the data. The [Production checklist](https://docs.sazabi.com/get-started/production-checklist.md) walks through this decision before you rely on Sazabi in production.

## Further reading

> [card] [Log storage & retention](https://docs.sazabi.com/guides/instrument/storage.md)
>
> Managed storage, the retention window, and choosing your region.

> [card] [Compliance](https://docs.sazabi.com/security/compliance.md)
>
> Certifications, audit reports under NDA, the DPA, and subprocessors.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.