---
title: "Delta — Data protection"
canonical: https://vectorvida.com/en/module/delta
description: "Delta is VectorVida’s data protection layer: it de-identifies clinical data locally (on-premise) so you can use AI without exposing patient information, with NOM-024 compliance evidence."
site: VectorVida
language: en
revised: 2026-07-29
---

# Delta — Data protection

De-identification of clinical data, so you can use artificial intelligence without exposing patient data.

## What it is

Delta is VectorVida’s data protection layer. It automatically de-identifies sensitive patient information — name, address, CURP national ID, RFC tax ID, social security number, phone and postal code, among others — inside clinical notes and messages, so a clinic can use artificial intelligence (WhatsApp, cloud models and the other VectorVida modules included) without the patient’s personal data leaving the institution.

Delta runs locally, on-premise, so information never leaves the clinic’s own hardware, in line with NOM-024. Unlike a simple redaction tool, Delta is reversible inside the clinic’s secure environment: de-identified information can be re-linked to the correct patient when the workflow calls for it.

Every operation also produces compliance evidence: an immutable audit log, a de-identification certificate for each processed document, and a NOM-024 attestation package ready for audit.

## Features

- **Automatic de-identification of PHI in clinical text** — Hides personal data before it reaches any AI.
- **100% local / on-premise** — Air-gap capable. Data never leaves.
- **Mexican identifiers** — CURP, RFC, NSS, postal codes and +52 phone numbers.
- **Audit-ready evidence** — A NOM-024 attestation package for every operation.
- **Immutable audit log**
- **Per-document certificate**
- **Reversible re-identification inside the clinic’s secure environment.**
- **Measured and documented recall on Mexican identifiers.**
- **Monthly updates to the identifier package.**
- **Air-gap capable: information never leaves the institution.**

## Compliance

- Local, on-premise execution aligned with NOM-024-SSA3: sensitive information does not leave the institution.
- Every operation leaves auditable evidence: an immutable log, de-identification certificates and a NOM-024 attestation package.
- Personal data processing and de-identification under Mexico’s federal data protection law (LFPDPPP).

## Editions

_Choose the scope your institution needs. Every edition runs on the same local de-identification core._

### Delta Standard

De-identification and re-identification with an audit log and identifier updates.

- De-identification and reversible re-identification.
- Immutable audit log.
- Monthly updates to the identifier package.
- Support.

### Delta Compliance (Recommended)

Everything in Standard, plus audit-ready compliance evidence.

- Everything included in Delta Standard.
- A de-identification certificate for every document.
- NOM-024 attestation package.
- Recall SLA on Mexican identifiers.

### Delta Gateway

Hardened with an egress proxy and high availability, for hospitals and medical groups.

- Egress proxy that hardens perimeter protection.
- High availability.
- Built for hospitals and medical groups.

## Deployment

Delta runs inside the perimeter your institution controls. Choose the on-premise appliance or your own private cloud — either way, de-identification happens on your infrastructure and patient data does not leave it.

### Delta Box

_On-premise_

An appliance installed inside your institution. De-identification happens locally and is air-gap capable: patient information never leaves your premises.

### VPC

_Private cloud_

Deployed in your own private cloud (VPC), isolated and under your control, when you prefer cloud infrastructure with no resources shared with third parties.

## Frequently asked questions

### Does Delta work without an internet connection (air-gapped)?

Yes. Delta runs locally, on-premise, and is air-gap capable, so it can operate with no outbound route to external networks at all. Patient information never leaves the institution’s hardware.

### Which Mexican identifiers does Delta detect?

Delta de-identifies name, address, CURP national ID, RFC tax ID, social security number (NSS), +52 phone numbers and postal codes, among others, inside clinical notes and messages. Recall on those identifiers is measured and documented.

### Is the de-identification reversible?

Yes, inside the clinic’s secure environment. Unlike a redaction tool, de-identified information can be re-linked to the correct patient when the workflow requires it, without that mapping ever leaving the institution.

### What compliance evidence does Delta produce?

Each operation produces an immutable audit log, a de-identification certificate per processed document, and a NOM-024 attestation package ready for audit.

### Does Delta need the other modules to work?

No. Delta runs independently and can protect data the institution sends to WhatsApp, to cloud models or to any external AI tool, as well as to the other VectorVida modules.

### How is Delta deployed?

As on-premise hardware (the Delta Box) installed at the institution, or inside your own private cloud (VPC). The Gateway edition adds an egress proxy and high availability for hospitals and medical groups.

## In the stack

- [Núcleo](https://vectorvida.com/en/module/nucleo) — The sovereign foundation
- [Therion](https://vectorvida.com/en/module/therion) — Diagnostic intelligence
- [Kronos](https://vectorvida.com/en/module/kronos) — Predictive timeline
- [Gamma](https://vectorvida.com/en/module/gamma) — Record digitization